Rsm Cannot Manage Library Changer1. The Database Is Corrupt
And check you Event Viewer - System Log for any Events ID 5, 7, 9, 11 or 15 coming from the SCSI driver or tape driver. (Print sources don't count). Unselect the option, Run application on this computer.5. Select “Manage” then click on “Device Manager” 3). Also, based on other forum post, it was mentioned that the autoloader SCSI ID must be lower than the tape drive SCSI ID. http://stevemattley.com/rsm-cannot/rsm-cannot-manage-library-1-the-database-is-corrupt.html
Hi Lou, Here is the part from the log file that you requested. It is important that you have the most recent device drivers for your version of BE. The database is corrupt error in Alerts Ivan_P Level 4 04-18-2007 12:46 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Good Luck - Hi Lou, Based on your guide, you stated: -Modify registry key - HKLM\\Software\\VERITAS\\ADAMM "Enable robotic library tape device release" to 1 -Delete: HKLM\\System\\CurrentControlSet\\Control\\SCSIChanger -Delete: HKLM\\System\\CurrentControlSet\\Services\\SCSIChanger -Delete: C:\\Program Files\\VERITAS\\Backup
The database is corruptbut I get the DCOM error message instead now. The Problem occured after the installation of Service Pack 1 Windows 2003 Server (Domain Controller).HP Support Packs auf Version 7.1 and 7.3Its a Proliant DL380 G3 Server with a Compaq CD-Rom After installing autoloader driver from HP, Windows has detected the autoloader as HP MSL G2 1x8 autoloader. The library is in RANDOM mode.
I tried to disable remote storage manager from services,applied all hotfix belong to ms and symantec,put symanted on live update also.I also tried to delete the tape drive from device management The version of 11d we are using is rev6235, with hotfixes 6, 9, 10, 11, 13, 15 and 16 installed. Generated Thu, 10 Nov 2016 14:50:25 GMT by s_wx1196 (squid/3.5.20) ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: http://0.0.0.8/ Connection Robert Fidler Springfield, Missouri Ioscan -fnC disk Class I H/W Path Driver S/W State H/W Type Description ===== disk.
Open Quotes for Changer - ERROR = 0x0000007B (ERROR_INVALID_NAME) ========== ========== ========== ========== ========== ========== . Any solutions?RegardsWolfgang 0 Kudos Reply Jack Hodson Occasional Visitor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 09-28-2005 08:44 PM Deleting the CDRom driver and the Removable Storage Libarie does not help.Has anyone an idea? 0 Kudos Reply All Forum Topics Previous Topic Next Topic 5 REPLIES Jack Hodson Occasional Visitor However, BackupExec does not detect the autoloader (robotics library).
Delete the SCSIChanger key. 6. Problems were encountered during the configuration of your storage devices. Please try the request again. Any advise on how to proceed from here?
Select the option to stop the Backup Exec services 4. When I try to manually add a device, it only detects the tape drive. You've reached the right place. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : RSM cannot manage library Tape2.
The lower SCSI ID for medium changers doesn't matter when using LUNs. weblink We have every kind of drivers you'll ever need. The database is corrupt error in Alerts Patty_McGowan Level 6 Employee 04-19-2007 07:14 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report the problem has been ibrahim_bazarwa Level 3 10-06-2009 01:16 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content the problem
Close REGEDIT 8. I've looking for a driver of the meduim changer library on the sysmatec site, but no luck. I downloaded and installed and rebooted the media server, and now it detects the autoloader. navigate here The system returned: (22) Invalid argument The remote host or network may be down.
Please try the request again. I have also this problem on a HP server after upgrading to Windows Server 2003 SP1. The resolution is lengthy but you should be able to follow along with the instructions below.
The database is corrupt error in Alerts Patty_McGowan Level 6 Employee 04-18-2007 12:49 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report
The database is c... I've also tried the suggested solution but it didn't fix the problem. Thanks. Then downloaded and install the updated device drivers for Windows Servers x86-32bit.
Labels: 12.x and Earlier Backup and Recovery Backup Exec Best Practice Tip-How to 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! The database is c... View solution in original post 0 Kudos Reply 9 Replies Hi Ibrahim, Try the CraigV Moderator Partner Trusted Advisor Accredited 10-05-2009 05:11 AM Options Mark as New Bookmark Subscribe Subscribe to his comment is here Click on the “Update” button 7).
If I'm still having troubles I will call to open a support ticket. Go to Solution RSM cannot manage library Tape2. I'd like to thank you both Fazrul and Lou Buffetta for your help and attention to details. Select "Uninstall and remove all VERITAS device drivers from your system" b.
Click Start | Run, and type REGEDIT. Check Windows Device Manager to insure both the Medium Changer and Tape Drive has been recognized 18. Follow the rest of the on-screen prompts until you are finished Have Backup Exec "RE-DISCOVER" the tape devices ===== ===== ===== ===== ===== ===== ===== ===== -From within Backup Exec, go The...
Community Windows Server 2003 CommunityCategoryBoardUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as Looks like Backup Exec polls Colin_Weaver Level 6 Employee Accredited Certified 09-24-2009 04:01 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Error 3: id: 34113 (Server: "KPMT-SPRG-SMS1") (Job: "Backup 00014") Backup 00014 -- The job failed with the following error: A hardware error occurred. The database is corrupt.
Let's see how Backup Exec is recognizing the library. Based off the previous post I will rehash the steps needed to install the autoloader and tape drive. Go to the Applications tab and select NtmsSvc, click Properties.3. Here is a sample of the alerts:RSM cannot manage library Tape0.