Are you running Control-M agent with domain user account or with localsystem? What error does it display in logs?
First thing i would do is check free space. I typically don't have issues with windows agents but when i do its usually the result of not enough space on the server (usually the result of dump from some other application and isn't cleaned up).
We have the same problem. The account used to launch the service must be local administrator of the Windows Server.
I'm still looking for ways to make the account launch the Control-M/Agent service without being an administrator because it's a security flaw.
You should have something more meaningful in the Windows system event log which will indicate why it has failed to start.
1 of 1 people found this helpful
It's not really a security flaw if used properly:
-Create account (local or domain) with local admin privileges
-Set Control-M Agent service to run with that account
-Configure LogOn As User (including adding the account above to the corresponding Local Security Policies)
-Add accounts that will run jobs to the agent using ctmpwd utility (locally) or via CCM (centralized)
You can now only run jobs with the accounts you defined with ctmpwd/CCM; your risk is as big as the privileges you grant to these accounts.
Any job trying to run in that agent with an account not defined in ctmpwd/CCM will fail, even if the job is set to run with the account with which the Control-M Agent service is running (unless you added that account to ctmpwd/CCM).
You can further increment security by making sure your EM users can only define jobs with the accounts they're supposed to (ie. Authorizations > User or Group > Owners).
It's a security flaw for my IT ^^.
We are already in this configuration. I just wanted to know if it was possible to override it.
Thanks for your answers.
This can also occur when the account being used to run the service is not defined as a local admin account on the server.