The solution is to correct the XML definition of custom Software signature in problem.
In order to find it easily we could use this method :
1- On one agent machine, open a DOS prompt and execute following command :
amswsigscan.exe -D "C:\Program Files\CA\DSM\Agent\units\00000001\uam\W0000569.XML" "%TEMP%\amsoft.xml"
- Replace C:\Program Files\CA\DSM\Agent\units\00000001\uam by the valid path on the machine.
- Replace W0000569.XML by the valid XML filename stored on the machine.
If there is a problem in xml file an error message like this one appears :
XML parse error (not well-formed (invalid token)) on line 1888963
Invalid XML [FATAL]
2- Open the XML file with a text editor and go to the mentioned line. The Software definition in problem is found :
On Unix/Linux the method is the same. The command line is :
caevmscli -D "/opt/CA/DSM/Agent/AM/data/work/l0000564.xml" "/tmp/amosoft.xml"
Replace /opt/CA/DSM/Agent/AM/data/work/l0000564.xml by the valid path and filename for l0*.xml file
3- Try to find what is the invalid syntax or characters and in ITCM GUI, edit the software definition and correct the syntax of XML definition.