When trying to start caf.exe after an install of agents you get an error starting caf , SmInitialize The command failed error code 1.

Document ID : KB000025488
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms: 

After installing CA Client Automation agents, CAF service and agent will not start. 
When running caf start you get the following errors:


Starting caf service...
Waiting for service to confirm startup...
Connecting to caf process...
CA DSM r12 Common Application Framework 12.9.0.338
Starting all DSM services...
Session messaging server (smserver)...Worker process did not send a ready
message - continuing anyway.
Connecting to session messaging server...

[0] Retrying connection...
...
[9] Retrying connection...

Failed to connect: A required subsystem failed to start. Please check logs for details.: SmInitialize The command failed. c:\Program Files\ca\dsm\bin\CAF.exe exited on <hostname> with error code 1.

 

Environment:  

ALL CA Client Automation versions

All supported Operating Systems

 

Resolution:

1.)    When you see the below output for CAF STATUS command,
            "Failed to connect: A required subsystem failed to start. Please check logs for details.: SmInitialize The command failed.
           C:\Program Files\ca\dsm\bin\CAF.exe exited on <hostname> with error code 1."
 
2.)  Check the TRC_CF_CFSMSMD log and see if you find the following entry
           CFPorting_LoadLibrary: failed to load awmsq: The specified module could not be found.
 
3.)   This would happen if the PATH variable does not have the path to awmsq.dll located under " C:\Program Files\CA\SharedComponents\CAM\bin"

4.)   Add the path to the awmsq.dll under the PATH Variable under System Variables of the agent.
 
5.)   CAF should now start along with all agents and you can verify using caf status command.

 

Additional Information: 

For information on supported Operating Systems see the CA Client Automation Compatibility Matrix    

Available on the http://support.ca.com website.