Export (0) Print
Expand All

Troubleshooting Removable Storage

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2


What problem are you having?

Windows cannot detect the library after you install it.

Cause:  The library may not be supported by Windows.

Solution:  Verify that the library is supported by Windows. For a comprehensive list of the libraries supported by Windows operating systems, see the hardware compatibility information in the Windows Catalog. You can access the Windows Catalog from Support resources. Make sure you have configured the library according to any guidelines listed for the applicable library.

Cause:  The library may not be properly connected to your computer.

Solution:  Verify that the library is properly connected to your computer. If an automated library is connected to a SCSI host adapter (by means of a SCSI cable), make sure there are no SCSI ID conflicts with other devices in your computer, such as your hard drive or CD-ROM drive. In addition, verify that all cables are installed and terminated properly in accordance with the guidelines for SCSI operation, especially that the maximum length for such cables is not exceeded.

Removable Storage has stopped the automatic configuration process for an automated library.

Cause:  Occasionally, Windows will configure a drive inside an automated library before the library itself has been configured. In this situation, Removable Storage will complete the configuration process once Windows is done configuring the library.

Solution:  Verify that Windows has recognized the library and associated drives and has configured the device drivers correctly.

Removable Storage was unable to automatically configure an automated library.

Cause:  The library may not support drive-element address reporting. Consequently, Removable Storage cannot map each drive in the library to a particular drive bay.

Solution:  Use only libraries that support drive-element address reporting, and connect all library drives on the same SCSI bus as the associated drive bay. For information on whether your library supports drive-element address reporting, consult the library manufacturer.

Solution:  If Removable Storage still cannot automatically configure your library correctly, you will need to manually configure it. However, do not use this method unless it is absolutely necessary because manually configured libraries do not recognize system configuration changes and also involve registry changes. For information on how to configure your libraries manually, see "Managing Data with Removable and Remote Storage" at the Microsoft Windows Resource Kits Web site.

The library is configured correctly but is malfunctioning.

Cause:  Many such problems can be caused by hardware device errors.

Solution:  See the Windows system event log for details. You can use Event Viewer to view the error messages stored in the event log. Look for specific Removable Storage error messages as well as for device, drive, and controller error messages to pinpoint the source of the problem. Contact the library manufacturer once you have ruled out Removable Storage as the source of the problem.

When configuring a media pool, Removable Storage cannot detect the media type.

Cause:  The library may not contain any tapes or disks.

Solution:  Before you create a new media pool, insert media into each automated library you want Removable Storage to control.

You cannot set or change security for Removable Storage.

Cause:  Removable Storage requires that you have administrative credentials for these operations.

Solution:  Verify that you are logged on with administrative credentials.

I cannot access the Computer Management extension snap-ins on a remote computer.

Cause:  The Remote Registry service is not running on the remote computer.

Solution:  Ensure that the Remote Registry service is started on the remote computer.

See also:  Start, stop, pause, resume, or restart a service. You need appropriate credentials on the remote computer to start the service.


  • You might also receive this error message if the remote computer is running Windows 95. Computer Management does not support remote access to computers that are running Windows 95.

Community Additions

© 2016 Microsoft