Windows Proxy (cspmagentd) or A2A Client (cspmclientd) Service is set up and working, but it fails to load on server reboot.

Products

• CA Privileged Access Manager - Cloakware Password Authority (PA)
• CA Privileged Access Manager (PAM)

Issue/Introduction

After rebooting a server that is running the Windows Proxy (cspmagentd) or A2A Client (cspmclientd) Service it is found that the service has not been properly started.

• Restarting the service manually allows the service to start properly.
• Once running the service works as expected without problems.

Cause

The Windows Proxy & A2A services require the Windows networking service (lanmanworkstation) to be loaded before they can properly load. When using Automatic Start (and even Delayed Automatic Start) it is possible that the network driver will not be loaded before the service. When this happens the service will fail to start when it tries to communicate with the CA PAM server. 

 

Environment

Release: PAMDKT99500-2.7-Privileged Access Manager-NSX API PROXY
Component:

Resolution

Open a command window as Administrator and run the following two commands.

Note: Be careful if you decide to modify these commands, they are syntax sensitive. 

 

1. Run this first command to add the network service as a dependency for starting the A2A/Windows Proxy service. This will stop the A2A/Windows Proxy service from trying to load until after networking is loaded:

A2A:  # sc config cspmclientd depend= lanmanworkstation start= delayed-auto

Windows Proxy: # sc config cspmagentd depend= lanmanworkstation start= delayed-auto

 

2. (Optional) Run this second command to set the A2A/Windows Proxy service to try restarting a few times in the event of start-up errors:

A2A:  # sc failure cspmclientd actions= restart/120000/restart/120000// reset= 120

Windows Proxy: # sc failure cspmagentd actions= restart/120000/restart/120000// reset= 120

Additional Information

More info on the how the sc commands work can be found here: Microsoft Technet - sc Command Reference