Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Unable to start ACC service on Windows Server - Agent Logon Failure

Kalpan2
Tera Contributor

We installed the agent-client-collector-4.2.1-windows-x64 on one of our Windows servers. Post installation, it created the servicenow user with "Run as a service" permission and all packaged folders as mentioned in the Install the Agent Client Collector on a Windows machine manually guide. However, the Agent Client Collector service did not start. We tried to start the service manually and received an error message, "Error 1069: The service did not start due to a logon failure."

We have re-installed the client multiple times with the same outcome. Any suggestions/help will be greatly appreciated.

1 ACCEPTED SOLUTION

Doci1
Kilo Sage

@Kalpan2 interesting. I woudl start with Event Viewer on the server, isn't there any more specific information?

as a second step I will use one liner installation with extended debuging during the installation and as a third step, I woudl install ACC as a system. Here is the command:

msiexec /i <msi_file_path> /quiet /qn /norestart /L*vx C:\temp\Your.log ACC_API_KEY=aaaaaaaaaasdasdasdasdasdasdasdas ACC_MID=wss://192.168.x.x:1234/ws/events ACC_ALLOW_LIST=False LOCALUSERNAME=SYSTEM

 

LinkedIn: www.linkedin.com/in/tomáš-dočkal-441029123

View solution in original post

2 REPLIES 2

Doci1
Kilo Sage

@Kalpan2 interesting. I woudl start with Event Viewer on the server, isn't there any more specific information?

as a second step I will use one liner installation with extended debuging during the installation and as a third step, I woudl install ACC as a system. Here is the command:

msiexec /i <msi_file_path> /quiet /qn /norestart /L*vx C:\temp\Your.log ACC_API_KEY=aaaaaaaaaasdasdasdasdasdasdasdas ACC_MID=wss://192.168.x.x:1234/ws/events ACC_ALLOW_LIST=False LOCALUSERNAME=SYSTEM

 

LinkedIn: www.linkedin.com/in/tomáš-dočkal-441029123

Kalpan2
Tera Contributor

Thanks for responding. ServiceNow HI Support engineer suggested us to use the following which worked:
1. Uninstall - "msiexec /x <Msi package>"

2. Re-install - "msiexec /i <msi package>"