W3404 EC=Account Disabled

[SirNtwrk]

I have a bunch of user directories that do not appear to get backed up all of a sudden. In the log, I get a W3404 error, unable to open file (\\path...., EC= ACCOUNT DISABLED)

I assumed that the account used to back up these folders was simply disabled, but it is not. Using other domain admin accounts also does not work. I even created a separate job for the user's folders and had the same error. If I right-click the job and click Modify User Name, then click the server share and verify, nothing happens to indicate there is an issue.

Has anyone else come across this?

 

[davidmichel]

What about the user that is the owner of that folder?

 

[SirNtwrk]

It is kind of strange...all the permissions are set the same way on those folders. NTFS security is set to everyone full control, and the share permission is for the user - change, and domain admins - full control. Their are about 30 folders on the D$ drive, and starting with the letter J and down, the folders will not backup. The user accounts are not disabled and have access to those files and others.

Something that is really messed up here is that if I choose the user share to backup, not the D$ drive, the files backup correctly. I am doing that experiment now. I found out that this is also happening at our sister company, where we got the software to begin with.

 

[SirNtwrk]

I solved this one on my own, but here is the answer in case anyone else comes across this.

The file server uses InnoculateIT as the virus protection. When ArcServe got to an infected file on this users home drive, the virus protection quarantined the account accessing the file (not sure why InnoculateIT does it this why, but the do) for 90 minutes. The had the effect of stopping the backup for all files for the next 90 minutes. After 90 minutes, the account was unlocked and they system would work normally again. That is why a check the next morning to see if any accounts were in fact disabled came up empty and why backing up the shares worked as long as I did not choose the share were the infected file exsisted.

Thanks for your response.