Troubleshooting HTTP 503 Error when trying to access LRM after a Windows Credential Update
Last updated
Was this helpful?
Last updated
Was this helpful?
By default, Local Run Manager (LRM) should be configured to use the 'LocalSystem' identity within Internet Information Services (IIS). However, if users are importing runs into LRM from a network location, it is required to configure LRM to have a different logon identity within IIS to allow them permission to do this.
If a user has configured LRM to logon with specific credentials in IIS (such as sbsuser), then it is required to update them within IIS after updating the password for that account. If the user does not update the credentials within IIS, the LRM Application pool will not be able to start and it will not be possible to access Local Run Manager. Chromium will often return the message 'Service Unavailable: HTTP Error 503. The service is unavailable.' when attempting to access LRM.
Use the following steps to update the identity credentials for LRM within IIS:
Confirm if users are importing runs from a network location into LRM and need to have LRM configured in IIS.
This is not required to output the data to a network location, so the majority of users do not need this and should revert the system back to the default 'LocalSystem' Identity.
Login to instrument as 'sbsadmin' user as IIS will require Administrator privileges.
Alternatively, right click on Internet Information Services and select 'Run As Administrator'.
Open IIS Manager from Control Panel > Administrative Tools > Internet Information Services Manager.
In the left panel in IIS, select Application pools from the drop-down menu. In the middle panel, check whether Local Run Manager is running.
If Local Run Manager is stopped due to a credential issue, it will show the following:
Right-click Local Run Manager and select Advanced Settings.
Navigate to the Identity property, click on the row, and then click the ellipsis on the right.
If the user is not importing runs into LRM from a network location, Illumina recommends changing back to the default 'LocalSystem' Identity under 'Built In Accounts'.
If the user imports runs from network folder or storage, configure Internet Information Services with the Custom account. Make sure Custom account is selected then select Set.
Enter the username and the updated password, and select OK.
Navigate back to Application Pools and make sure Local Run Manager status is now "Started". If it is not, right-click on Local Run Manager and select 'Start'.
Navigate back to the left panel in IIS, and expand the option for Sites underneath Application pools.
Right-click Local Run Manager, navigate to Manage Website and Restart site.
This enables Local Run Manager to start in the browser (https://localhost). Then, proceed to update the Service logon credentials using the following Illumina Knowledge Article.
How to update update Windows 10 account credentials on Benchtop Instruments
For any feedback or questions regarding this article (Illumina Knowledge Article #5988), contact Illumina Technical Support techsupport@illumina.com.
