Page 1 of 1

Version 9 - NTSUSER Files

Posted: Thu Mar 18, 2021 3:27 pm
by gcl
Upgraded from version 8 to version 9 and imported existing jobs using the wizard. Version 9 is trying to copy the NTSUSER files:

[17/03/2021 19:30:10] Archiving files to 5_C.zip
[17/03/2021 19:30:10] Added folder C:\Users\SP020\
[17/03/2021 19:30:10] Warning: Skipping file C:\Users\SP020\NTUSER.DAT
The process cannot access the file because it is being used by another process
[17/03/2021 19:30:10] Warning: Skipping file C:\Users\SP020\NTUSER.DAT
Network path was not found (zip1). (srFileOpenError)
[17/03/2021 19:30:10] Warning: Skipping file C:\Users\SP020\ntuser.dat.LOG1
The process cannot access the file because it is being used by another process
[17/03/2021 19:30:10] Warning: Skipping file C:\Users\SP020\ntuser.dat.LOG1
Network path was not found (zip1). (srFileOpenError)
[17/03/2021 19:30:10] Warning: Skipping file C:\Users\SP020\ntuser.dat.LOG2
The process cannot access the file because it is being used by another process
[17/03/2021 19:30:10] Warning: Skipping file C:\Users\SP020\ntuser.dat.LOG2
Network path was not found (zip1). (srFileOpenError)

I can manually add a filter to exclude these files, but this hasn't been necessary with previous versions of FBackup.

Re: Version 9 - NTSUSER Files

Posted: Fri Mar 19, 2021 11:16 am
by Adrian (Softland)
Hi,

It seems to be related to the Volume Shadow Copy issue with was solved in build 199
Please download the latest version of FBackup 9.0.199 from our website and try again.
Let us know if you still have the problem.

Re: Version 9 - NTSUSER Files

Posted: Fri Mar 19, 2021 4:10 pm
by gcl
Hi

Many thanks for the reply.
I've downloaded and installed FBackup 9.0.199 and it's fixed the problem with the NTSUSR files. I have two PCs which have completed clean backups with no errors, however a third PC still has the 'Log warning for missing folder that is not missing' problem that others have reported. Log file and FKC file attached.

Re: Version 9 - NTSUSER Files

Posted: Thu Mar 25, 2021 12:27 pm
by Adrian (Softland)
@gcl

I created a ticket for this false warning problem and we will fix it.