FB9 warnings, Network path was not found (zip1). (srFileOpenError)

Post here if you have problems installing or using FBackup
Post Reply
mwalker212
Posts: 6
Joined: Thu Apr 18, 2019 9:30 am

FB9 warnings, Network path was not found (zip1). (srFileOpenError)

Post by mwalker212 »

Running latest version 9.223, jobs copied from FB8. I am getting a lot (read 1000's) of warnings in the backup log for files being skipped that all work perfectly in FB8.
Just one example from the log:
FB9:
[12/04/2021 09:25:33] Warning: Skipping file C:\ProgramData\Microsoft\Windows\Start Menu\Programs\FBackup 9\FBackup 9.lnk
Network path was not found (zip1). (srFileOpenError)

FB8:
[12/04/2021 09:36:49] Added file C:\ProgramData\Microsoft\Windows\Start Menu\Programs\FBackup 9\FBackup 9.lnk

No network paths are involved in the sources or destination so, what's the issue?

Adrian (Softland)
Posts: 1760
Joined: Thu May 23, 2013 7:57 am

Re: FB9 warnings, Network path was not found (zip1). (srFileOpenError)

Post by Adrian (Softland) »

Hi,

That is a false warning. It should be fixed in the current build: 9.0.226
Please download it from the website and run again the backup.
Let us know if you have any other problem.

mwalker212
Posts: 6
Joined: Thu Apr 18, 2019 9:30 am

Re: FB9 warnings, Network path was not found (zip1). (srFileOpenError)

Post by mwalker212 »

Hi Adrian,
Have just tried with the latest 9.0.238 and it's still the same, I'm afraid.

Adrian (Softland)
Posts: 1760
Joined: Thu May 23, 2013 7:57 am

Re: FB9 warnings, Network path was not found (zip1). (srFileOpenError)

Post by Adrian (Softland) »

Hi,

Please send us to info[at]fbackup[dot]com the following files:
- the last backup log
- the .fkc catalog file from the backup destination

mwalker212
Posts: 6
Joined: Thu Apr 18, 2019 9:30 am

Re: FB9 warnings, Network path was not found (zip1). (srFileOpenError)

Post by mwalker212 »

Done.

mwalker212
Posts: 6
Joined: Thu Apr 18, 2019 9:30 am

Re: FB9 warnings, Network path was not found (zip1). (srFileOpenError)

Post by mwalker212 »

FYI, something in the last couple of releases appears to have finally fixed this issue.

Post Reply