tldcd.lock failed with LOCK_OP_FAILED: Error: -3 (trying to add new robot)
Updated: 18 Jul 2011 | 2 comments
This issue has been solved. See solution.
Installing a new Spectra T120 on a Windows Server 2003 x64 machine that already remotely managed a L180 known as TLD(0). When adding the new robt as TLD(1) it can be seen and added but device manager will not stay running and errors out immediately after restarting it.
in the application event log:
TLD(0) [1564] Lock of F:\Program Files\Veritas\Volmgr\misc\tldcd.lock failed with LOCK_OP_FAILED: Error: -3
The pop up says "Error connecting to oprd on "server name": oprd returned abnormal status (96).
The robot and drives are correctly seen in device manager. Any body have an idea how to make this thing love the new robot?
thanks
Discussion Filed Under:
Comments
A few possible
A few possible causes:
http://www.symantec.com/docs/TECH141672
http://www.symantec.com/docs/S:TECH152640
this can also be caused by out-of-date device mappings files.
Here are the latese device mappings files for windows
http://www.symantec.com/docs/TECH162166
and, while I'm here, unix/ linux
http://www.symantec.com/docs/TECH162165
Regards,
Martin
If only I added robots more than once every 5 years
Had to simply restart NB procs on the master and everything is working fine.
Would you like to reply?
Login or Register to post your comment.