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
Release Automation 6.x
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.
Available options for fixing problems introduced by upgrading the Windows OS are:
Solution 1 : Add quotes characters in binary path to NolioAgent service (before or after upgrade)
Solution Before OS Upgrade
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
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
Solution 2 : Remove/Re-add the NolioAgent Service
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