KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : ER00033 Unable to open file C:/$$xo-volume

Last Update: 2015-12-15 21:59:13 UTC

Error Message: 

'ER00033  Unable to open file C:/$$xo-volume'  ....  'The system cannot find the file specified.(2), #open files=0'

 

Description:  You are running a full system scenario and you receive the above error, this error generally will occur about 7 or so times and then it will stop the scenario. 

 

Solution:  This error will occur the second the vss snapshot that RHA took of the volume in question is either deleted or locked by some other program.  You can check the snapshots that the master has by running 'vss admin list shadows' in a command prompt on the master.  You would need to look in the RHA logs however in order to find the snapshot ID for the volume that is getting this error (if you need assistance with this please give the support line a call and open a ticket).  You would then need to look for that snapshot ID in the list of snapshots in the command window, this will tell you if the snapshot exists or not.  If it does exist and we are still getting this error it is possible some other application that uses VSS may be locking the VSS snapshots preventing RHA from reading them.  At that point I would review all running applications on that system and close all of them that use vss till the snapshot becomes unlocked, to see if it is still locked or getting deleted you should resync your scenario.

In one occurence of this error the customer checked their application and system windows event logs and found the following error:

Event ID: 25 Source: VolSnap

Error Description:
The shadow copies of volume were aborted because the diff area file could not grow in time. Consider reducing the IO load on this system to avoid this problem in the future.

After reviewing this error on eventid.net we found a Microsoft KB with a hotfix for this vss issue for Windows 2003:

http://support.microsoft.com/kb/887827

The customer applied this fix and rebooted the master and restarted the scenario error free. 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments