Skip to main content

Error 1053 - 'The service did not respond to the start or control request in a timely fashion'

Steps you can take to resolve the LMX server service failing to start due to a missing LIBLMXVENDOR.DLL file.

Written by Arthur Ashdown

If your antivirus software has quarantined or deleted the LIBLMXVENDOR.DLL file, the LMX server service will fail to start, and you may see one or both of the following errors:

  • The service did not respond to the start or control request in a timely fashion.

  • The code execution cannot proceed because LIBLMXVENDOR.DLL was not found. Reinstalling the program may fix this problem.

To resolve this, you need to restore the file from quarantine and add it to your antivirus exclusion list.

⚠️Important: The LIBLMXVENDOR.DLL file should be located in the following directory: C:\Program Files (x86)\X-Formation\LM-X End-user Tools 4.7.5. If it is missing, your antivirus software has likely quarantined or deleted it.


Restore the file and configure your antivirus exclusion

The steps below use BitDefender as an example. If you use a different antivirus product, the process will be similar — refer to your antivirus documentation for the equivalent steps.

BitDefender

To restore the quarantined file and prevent it from being removed again:

  1. Open BitDefender and navigate to the quarantine section.

  2. Locate the LIBLMXVENDOR.DLL file and restore it from quarantine.

  3. Add the file or its directory to the BitDefender exclusion list to prevent it from being quarantined again.

📌Note: If you are unsure how to configure exclusions in BitDefender or another antivirus product, contact your IT administrator for assistance.


Restart the LMX server service

Once the file has been restored and the exclusion configured, restart the LMX service to reconnect to Orchestrate.

  1. Open the Windows Services panel by pressing Windows + R, typing services.msc, and pressing Enter.

  2. Locate the LM-X License Server service in the list.

  3. Right-click the service and click Restart.

The service should now start successfully, and you will be able to log back into Orchestrate.

📌Note: If the service still fails to start after completing these steps, contact Access support for further assistance.

Did this answer your question?