LTO5 LTFS Configurator Service not started, Exit Code: 203

[Owen20]

HP Storage Works Ultrium 3000 SAS connected to LSI card on Win 10 Pro.  

StoreOpen and HPE L&TT recognizes the drive and I have formatted the tape to LTFS.

When I try to map the drive so that I can drag and drop files for cold storage, I get the following error:

Service not started!

Currente State: 1

Exit Code: 203

Check Point: 0

Wait Hint: 0

https://imgur.com/a/5cuu1K8

I can't find any information or guides to what Current State 1 or Exit Code 203 means or how I can fix it.

[Gans_Tapes · Accepted solution]

Hello @Owen20 ,

The first step would be to verify that you are running a supported config (Server + OS + HBA+firmware). Please refer to the following compatibility matrix / SPOCK. (Requires HPE Passport sign in)
https://h20272.www2.hpe.com/SPOCK/Pages/spock2Html.aspx?htmlFile=hw_storeever.html 

1. I suspect this to be related to one of the internal services not started.
2. Check the event viewer logs to confirm if you see event ID 100 / 101 / 7000. These point to a failed start of service due to a likely missing file.
3. If you are running an older version of LTFS utility, uninstall the same. Download and isntall the latest 3..5.0. (https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=1009214665&tab=driversAndSoftware)  , reboot the server. Install the application again and reboot one more time then attempt to map the drive.  

If these fail, I suggest you please gather an HPS report,  event viewer logs  and a support ticket to open a case to investigate further. 

[Owen20]

I deleted the old version of HPE StoreOpen 3.4.2 and Reinstalled 3.5, rebooted.

By chance I went into Device Manager and disabled the tape drive, then upon renabling, all the icons on the desktop flashed and the mapping completed! The drive showed up in file explorer and am currently transferring files.  I hope this sticks.  Thank you for your help!

https://imgur.com/jsP5nTG   

[Gans_Tapes]

@Owen20 

Thank you for confirming the resolution. Glad to see this issue resolved   

[JoshWAOSOS]

Disabling the drives and enabling them again solved this error for me today. Thank you Owen20!