Back up full of errors again if tested but not if extracted.
-
Backup full of errors again. :(
Just ran my backup in PA 11.50.37 (Beta 2)
At first I though it could be back to where we were in This Thread maybe even worse this time.
After I ran my backup I tested it and it did not even ask for my password, off it went and at the end I got the message:- Warning: 2287 Error(s) found in the archive: My Backup-27-03-2009.zip
So I thought oh no here we go again.
But no. If I extract the archive I get asked for my password as usual and it extracts fine.
So I guess somebody somewhere has broke something. :D
Luxor
-
what happens when you run it next time?
-
and what do the errors say?
-
Same next time I run it.
and what do the errors say?
All it says is –> CRC ERROR
And at the end.
Warning: 2287 Error(s) found in the archive: My Backup-27-03-2009.zip
-
create new name for the backup and try it and then try it again, see what happens then please…
-
Ok spywolf.
Firstly I have tried with some of the backup archives I have created over the past month. Same error every time, so it’s not just newly ceated ones.
Created new name tried again and again, same error.
Created a new backup, same error.
Created another one with just one folder from My Docs, same error.Changed my backup type to 7zip and it works fine.
Asks for my password, tests the archive and no errors. Like my usual zip archives it extracts fine too.So it seems to be a problem with zip archives only as far as I can tell.
Luxor
-
send us your pbs, it will explain few things.
You are testing archive in backup? What happens if you test the same archive inside PA later on?
-
send us your pbs, it will explain few things.
I have created a new one specially for you, very small just a few files in 1 folder. Same settings as my normal backup. Nothing private to worry about.
I will attach it here for quickness if that’s Ok.You are testing archive in backup?
No. Just testing the archive itself. Opening it up in PA and clicking on test.
-
eh, you should have said you were testing the file :-).
It seemed as if it was happening in backup, not actual PA. -
eh, you should have said you were testing the file :-).
Thought I did.
@Luxor:After I ran my backup I tested it and it did not even ask for my password, off it went and at the end I got the message:- Warning: 2287 Error(s) found in the archive: My Backup-27-03-2009.zip
Sorry for the misunderstanding but I thought it was clear in my explanation.
Luxor
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
Just noticed if I browse to the file in explorer and use shell extension Test. Then that is fine.
Password box appears and it runs with no error. -
basically no pass is asked for testing, hence the errors… if you open single file, password will be saved for the session and it will work fine.
-
Ok now you’ve lost me.
For years now I have been running my backup script. Then opened the resulting archive in PA then hit the test button and always had to put in my password. The test runs and I get the report.
If I understand you correctly, I now having to open my archive then open a single file, then put in my password to the view the file and only then I can test the whole archive. :confused:
To do that rather than just with one click (the way I have always done it) seems a bit long winded to me.
-
Ok now you’ve lost me.
For years now I have been running my backup script. Then opened the resulting archive in PA then hit the test button and always had to put in my password. The test runs and I get the report.
If I understand you correctly, I now having to open my archive then open a single file, then put in my password to the view the file and only then I can test the whole archive. :confused:
To do that rather than just with one click (the way I have always done it) seems a bit long winded to me.
its a bug, not an feature :-).
archive itself is fine though, which is the important part.
thanks!
-
-
Please check beta 3 via web update or download page and let us know if this issue has been fixed… thank you!
-
Fixed in beta 3