iainc
asked on
ARCserve Manager " Failed to create empty document"
Windows Server 2003 R2, Arcserve R11.5SP2
Connection to server via remote desktop
Manager opens but then fails with message
Brightstor ARCserve Backup
Failed to create empty document
Works fine when not using remote desktop connection i.e. when using the direct server session
The site is far away and I need the remote functionality
Thanks Iain
Connection to server via remote desktop
Manager opens but then fails with message
Brightstor ARCserve Backup
Failed to create empty document
Works fine when not using remote desktop connection i.e. when using the direct server session
The site is far away and I need the remote functionality
Thanks Iain
ASKER
It is definitely related to remote desktop. See my otiginal post - it works fine when accessed directly at the server. Will try renaming the subdirectory and let you know. Thanks
Sorry that was not clear to me. That being the case run the ARCserve Manager on your local system and select the remote system to see if it works.
ASKER
The server with Arcserve is at location A.
If I run Manager in the server session at A it works fine
If I am at location B, connect to the server at A with my laptop using remote desktop and then run Manager in the laptop session - it fails.
Thanks
If I run Manager in the server session at A it works fine
If I am at location B, connect to the server at A with my laptop using remote desktop and then run Manager in the laptop session - it fails.
Thanks
I was thinking from running the Manager from location B and selecting the ARCserve server at location A.
You can select to just install the Manager but if you are running XP Home on the laptop it is not an option.
Check the ARCserve\temp directory, it should be empty when there are no jobs running.
You can select to just install the Manager but if you are running XP Home on the laptop it is not an option.
Check the ARCserve\temp directory, it should be empty when there are no jobs running.
I believe this is an IE7 issue!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Leave the manager closed, stop the Job Engine, rename the subdirectory 0000001.qsd.
Then startup the Job Engine and the Manager.
If that work there is either a corrupt job in the queue or the queue itself.