Wanda, you might try going out to the Sysinternals web site
(http://www.sysinternals.com) and getting the filemon and handle utilities
to see what kind of activity might be going on on that volume.
Also, make sure Windows Explorer isn't running, as if the focus is on that
drive, that might cause it to appear locked. Similarly, if you have any
other system monitoring tools that might be scanning the drive, that could
also cause it to appear locked. Maybe an antivirus program?
These are just guesses, as I don't have a more specific idea about what
the trouble could be.
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[email protected]
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Please respond to
"ADSM: Dist Stor Manager"
ADSM-L AT VM.MARIST DOT EDU
Image restore error
We have successfully used image restore on a test Win2K server in the past
and gotten it to work.
Now we are trying to use image restore on a different Win2K machine.
On this machine, the drive in question is a raw drive, and the restore
with these messages in dsmerror.log:
ANS1287E Volume could not be locked
Image restore failed for \\server12\j$ <\\server12\j$> with rc 4190.
Resetting rc so any other requests can continue.
There is no page space on j$, we don't see any processes running that
be using that drive.
Any ideas what to look for?
Do you normally expect to reboot the machine before doing an image
Server is 126.96.36.199 on Windows
Client is 188.8.131.52 on Win2K.
"* I/O, I/O, It's all about I/O *" -(me)