If the nx.env file has been manually edited using a text editor, it can cause improper characters to save in the nx.env file causing a corrupt nx.env file, in turn, causing the system to throw Debug Assertion Failure errors when any Service Desk executable is run.
To prevent this problem from happening, always use the command line commands to update nx.env variables in the nx.env and in the nx.env template file as well.
The commands are as follows:
To add it to the nx.env:
pdm_options_mgr -c -s LDAP_NESTED_GROUPS -v no -a pdm_option.inst
To add it to the nxenv_nt.tpl file:
pdm_options_mgr -c -s LDAP_NESTED_GROUPS -v no -a pdm_option.inst -t
If the problem is already occurring, the best way to remediate it would be to locate the most recent backup from the same machine where the problem is occurring, and take the nx.env file from the backup and place it in the NX_ROOT directory after renaming the corrupt nx.env file to "BAD_NX.ENV.BAD" - Remember you can NOT copy an nx.env file from one system to another as it has hashed values stored in it that will not be read by the system the file is copied to.
Release: UAPMAC990JPP-12.6-Asset Portfolio Management-Asset Configuration