I have been investigating the ‘Scan Failure’ and ’Network Failure’ errors when running in session 0. I been looking the SMB messages between the local computer and the server with Wireshark and this is what I have found so far.
If you have two separate profiles, call them ‘A’ and ‘B’, profile ‘A’ backs up ~90,000 files from the local computer to the server and profile ‘B‘ backs up ~8,000 again for the local computer to the server, both profiles use the same share on the server but different directories and therefore my understanding is that they will share the same SMB connection (they are also both fast backups and profile ‘A’ is the first profile of a group but I don’t think that this relevant).
If both profiles start as schedule tasks in session 0 at roughly the same time then they both start correctly and successfully login to the server and then start to scan the local computer as expected. Because profile ‘B’ has less files to scan, and files to back up, it finishes while profile ‘A’ is still scanning the local computer. When profile ‘B’ finishes a SMB logout message is set to the server. When profile ‘A’ has finished scanning the local computer it then attempts to log back into the server, however this fails and this appears to be because the password is wrong, at this point the profile fails with the ‘Scan Failure’ error (and the second profile in the same group as profile ‘A’ fails with the ‘Network Failure’).
Both these profiles will run correctly if you ensure that independently with no other profiles running.
Andrew.
If you have two separate profiles, call them ‘A’ and ‘B’, profile ‘A’ backs up ~90,000 files from the local computer to the server and profile ‘B‘ backs up ~8,000 again for the local computer to the server, both profiles use the same share on the server but different directories and therefore my understanding is that they will share the same SMB connection (they are also both fast backups and profile ‘A’ is the first profile of a group but I don’t think that this relevant).
If both profiles start as schedule tasks in session 0 at roughly the same time then they both start correctly and successfully login to the server and then start to scan the local computer as expected. Because profile ‘B’ has less files to scan, and files to back up, it finishes while profile ‘A’ is still scanning the local computer. When profile ‘B’ finishes a SMB logout message is set to the server. When profile ‘A’ has finished scanning the local computer it then attempts to log back into the server, however this fails and this appears to be because the password is wrong, at this point the profile fails with the ‘Scan Failure’ error (and the second profile in the same group as profile ‘A’ fails with the ‘Network Failure’).
Both these profiles will run correctly if you ensure that independently with no other profiles running.
Andrew.
