WSP schema changes that have just been published on the standby server via pdm_publish are corrupted when the CA Service Desk Manager (CA SDM) service on the standby is started again after failing to start the first time.


Article ID: 17441


Updated On:


CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



The CA SDM 12.9 Implementation Guide includes a section titled, "Publish Schema Modifications". That section includes guidance that is specific to an Advanced Availability configuration. In particular, it includes an explanation about the automatic suppression of version control after running pdm_publish. Specifically, when pdm_publish is run, pdm_publish creates a version control file. Whenever the version control file exists and the CA SDM service is started, on the same system, the version control is disabled; before the startup of the service completes, the version control file is automatically deleted.

The deletion of the version control file during the startup of the service occurs regardless of whether or not the start of the service completed successfully.

If the start of the service failed, then, since the version control is no longer disabled, the next attempt to start the CA SDM service is done with version control enabled. The effect is that, WSP customizations existing on the background server are propagated to this standby server even if they do not necessarily match the published changes.


Until the CA Service Desk Manager service starts successfully on the Standby server after having run the required pdm_publish to pick up WSP changes, turn off version control before attempting to start the CA SDM service again.

To turn off version control, run the following command:

pdm_server_control -v


Component: ARGIS