UNSOLVED

timcstl

updated

23 years ago

T

timcstl

1 Message

0

13572

December 31st, 2002 14:00

The Remote Storage File service hung on starting.

I have a Poweredge 4400 Win2000 Server that has the The Remote Storage File service hung on starting.   I can later manually start it.  Looked on the MS site and could not find anything.  Has anyone seen this before?  Is it a big issue?

Thanks

  • DELL-Mark A

    2 Intern

    •

    2521 Posts

    629

    0

    Posted January 2nd, 2003 15:00

    Hi,

    Do you have the Dell OpenManage products installed?

    Are you receiving these messages in the Windows 2000 system event viewer?
    Removable Storage Service: Unable to register COM class objects.
    Removable Storage Service: RSM was stopped

    If so, try renaming these 2 files:
    .../OpenManage/oldiags/vendor/pcdoctor/modules/tapedrivediag.exe
    .../OpenManage/oldiags/vendor/pcdoctor/modules/tapelibrarydiag.exe

    This problem will be resolved with the next revision of the Dell OpenManage products.

  • mrdavidc

    1 Message

    629

    0

    Posted May 15th, 2003 12:00

    RE:"If so, try renaming these 2 files:
    .../OpenManage/oldiags/vendor/pcdoctor/modules/tapedrivediag.exe
    .../OpenManage/oldiags/vendor/pcdoctor/modules/tapelibrarydiag.exe"

    What do we rename them to, or does it matter? For example, should I rename the "tapedrivediag.exe" to "tapedrivediag.bak" or something like that, or is there a different name it should be??

     

    I get the errors also.

  • TonyAGS

    3 Posts

    629

    0

    Posted September 19th, 2003 15:00

    I just downloaded and installed the 3.5 version of OpenManage.  This issue still does not seem to be fixed.
  • 629

    0

    Posted September 19th, 2003 18:00

    Same Problem here...

    6 month old error...

    any updates?

     

     

     

  • maklen

    3 Posts

    629

    0

    Posted December 7th, 2003 18:00

    I just installed OpenManage 3.6 on a new server and am still getting the same error.  At least the workaround works.

  • 629

    0

    Posted December 8th, 2003 15:00

    I haven't installed the new version yet, but from what I have been hearing it doesn't fix this issue.

    Is this ever going to get fixed?  Is there a larger problem that end users aren't aware of, that has to be resolved?