Missing variables in NX.env after running pdm_configure
search cancel

Missing variables in NX.env after running pdm_configure


Article ID: 45297


Updated On:


CA Service Management - Service Desk Manager CA Service Desk Manager


After running pdm_configure, most NX variables are missing from the end of the NX.env file that were there prior to running pdm_configure and The NX.env template file was unchanged and looks correct. At the end of the NX.env file it ends with something like the following or maybe a few lines more:


Service Desk Manager 17.X


pdm_configure uses version control to help create the NX.env. One of the files that is important for this to work correctly is the client_nx.env file located in the site folder of the Service Desk install directory. pdm_configure will pull from the client_nx.env of the active background server and because of this, if the client_nx.env file is incorrect on the active background server, the NX.env file is not created correctly.


1.) Navigate to the NX_ROOT\site folder on each Background and Standby server.
2.) Backup each client_nx.env file and open them to compare them.
3.) Take the largest client_nx.env file and copy it and overwrite the other client_nx.env files.
4.) Run pdm_configure on all affected servers and verify the NX.env is now complete.