NolioAgent Service Not Starting After Windows Upgrade - Error 1053
search cancel

NolioAgent Service Not Starting After Windows Upgrade - Error 1053

book

Article ID: 258440

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

Unable to start Nolio Agent service on a server.  When I try to start it I receive an error.

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

Environment

Release Automation 6.x

Cause

After upgrade of Windows Operating System (example : Windows 2016 to Windows 2022), the short path names in binary path for Nolio Agent service are transformed by full path name.

Ex :
Before Upgrade the service Nolio Agent is configured with a path like this :
C:\PROGRA~2\Broadcom\RELEAS~1\bin\nolio_w.exe -s C:\PROGRA~2\Broadcom\RELEAS~1\conf\wrapper.conf

After the OS Upgrade the path becomes :
C:\Program Files (x86)\Broadcom\ReleaseAutomationAgent\bin\nolio_w.exe -s C:\Program Files (x86)\Broadcom\ReleaseAutomationAgent\conf\wrapper.conf

And startup of the service does not work because there are no quotes characters to protect the spaces in path names.

In C:\Program Files (x86)\Broadcom\ReleaseAutomationAgent\bin\wrapper.log we could see this error :

FATAL  | wrapper  | 2026/02/26 12:32:48 | The argument 'Files' is not a valid property name-value pair.

Resolution

Available options for fixing problems introduced by upgrading the Windows OS are:

  • Solution 1 - Add quotes characters in binary path to NolioAgent service. This could be done before or after OS upgrade.
    or
  • Solution 2 - Remove/Re-add the NolioAgent Service
    or
  • Solution 3 - Uninstall/Reinstall the NolioAgent

 

Solution 1 : Add quotes characters in binary path to NolioAgent service (before or after upgrade)

Solution Before OS Upgrade

  1. Execute this command to check the binary path set to Nolio Agent service 

    sc qc nolioagent2

    Example before OS upgrade :
    C:\PROGRA~2\Broadcom\RELEAS~1\bin\nolio_w.exe -s C:\PROGRA~2\Broadcom\RELEAS~1\conf\wrapper.conf



  2. Then execute this to add quote characters around path :

    sc config nolioagent2 binpath= "\"C:\PROGRA~2\Broadcom\RELEAS~1\bin\nolio_w.exe\" -s \"C:\PROGRA~2\Broadcom\RELEAS~1\conf\wrapper.conf\""

    and check with sc qc nolioagent2 that new binary path contains the quotes characters :

 

Solution After OS Upgrade

  1. Execute this command to check the binary path set to Nolio Agent service 

    sc qc nolioagent2

    Example :
    C:\Program Files (x86)\Broadcom\ReleaseAutomationAgent\bin\nolio_w.exe -s C:\Program Files (x86)\Broadcom\ReleaseAutomationAgent\conf\wrapper.conf



  2. Execute this command to add quote characters around path :

    Example : 
    sc config nolioagent2 binpath= "\"C:\Program Files (x86)\Broadcom\ReleaseAutomationAgent\bin\nolio_w.exe\" -s \"C:\Program Files (x86)\Broadcom\ReleaseAutomationAgent\conf\wrapper.conf\""

 

Solution 2 : Remove/Re-add the NolioAgent Service

  1. Open services.msc. Look at the Nolio Agent service and take note of:
    • the service account used to start the agent.
    • the install path of the agent
  2. Open a command prompt - with Run As Administrator, cd to the directory noted in step 1. 
  3. Run the command: remove_deployer_service.cmd
  4. Refresh the services.msc list to make sure the service was gone.
  5. Open the command prompt to re-add the service using the command: install_deployer_service.cmd
    • This returned an error about the service was marked for deletion. This means that we need to reboot. 
    • Reboot
  6. Open the command prompt to re-add the service using the command: install_deployer_service.cmd
  7. Open services.msc and opened the properties for the newly added NolioAgent
    • Select the Log On tab.
    • Specify the username noted in step1 along with its password.
  8. Start the NolioAgent service
  9. Confirm the NolioAgent was reflecting as "Reachable" in the ROC (Release Operations Center). 

 

This KB Article can be used if you are uninstalling/reinstalling the agent on a machine that has multiple instances of the NolioAgent installed: Second install of nolioagent on windows fails