I would check the file server agent ACLs along with the local permissions on the folders the appserver is trying to copy the files to.
What ever user is running the snapshot (that collects files) needs to have permission via the file server ACLs to write the files to the file server.
Have you tried logging on as Administrator and manually copying over those files? Just because you're Administrator doesn't necessarily mean you have access to them. Or they could even be locked files.
For example, on a box here I just did the following (not using our product)
1. cd "C:\Documents and Settings\LocalService\Local Settings\Application
2. dir (noticed that UsrClass.dat is there)
3. copy UsrClass.dat C:\
The process cannot access the file because it is being used by another process.
0 file(s) copied.
If you intend on checking the backup files option (which you must be doing since it's trying to copy the file to the file server), then you really have no choice but to exclude files that you can't access.
The handle.exe utility from www.sysinternals.com shows that this file is locked by the following:
System pid: 4 764: C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat
So this is a System file that we currently don't have access to due to some type of locking or some other such action by the system.
Sean , you were spot on. The local Admin found something similar. We are testing an App deploy by doing a snapshot and then doing a delta package after the app install and so a concern is if any of these files get updated as part of the App install, the delta package would miss them.
Does anyone have a standard Exclude list for a snapshot on a Windows server ? Snapshot keeps failing for all the files that are owned and locked by the SYSTEM like "/C/Documents and Settings/LocalService/NTUSER.DAT"