SD_Jexec File log error

book

Article ID: 131975

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction



Following error messages appear in the log DMS\logs\TRC_CF_SD_JEXEC_*.log :
 
CFAMConfigFileRe|CFAMConfigFileReader|000000|DETAIL | GetCurrentTag : Current tag is : ClassIDConfiguration and expected is ProcIDConfiguration 
CFSDConfigFileRe|CFSDConfigFileReader|000000|ERROR | Searching for ProcIDConfiguration and not found 

CFAMConfigFileRe|CFAMConfigFileReader|000000|DETAIL | GetCurrentTag : Current tag is : ProcIDList and expected is sdProcID 
CFSDConfigFileRe|CFSDConfigFileReader|000000|ERROR | Searching for sdProcID and not found


Do these messages indicate a problem ?
 

Environment

Client Automation 14.0 SP2

Resolution


No these messages do not indicate a problem with Client Automation and they could be ignored.

sd_jexec.exe does a scan of XML file DSM\Agent\OSConfig.xml.
When it searchs for tag ProcIDConfiguration, it first finds the tag ClassIDConfiguration.
So following lines are put in log :
 
CFAMConfigFileRe|CFAMConfigFileReader|000000|DETAIL | GetCurrentTag : Current tag is : ClassIDConfiguration and expected is ProcIDConfiguration 
CFSDConfigFileRe|CFSDConfigFileReader|000000|ERROR | Searching for ProcIDConfiguration and not found 



But sd_jexec.exe continues the research and finds the expected tag.

It is exacly the same for tag sdProcID :
 
CFAMConfigFileRe|CFAMConfigFileReader|000000|DETAIL | GetCurrentTag : Current tag is : ProcIDList and expected is sdProcID 
CFSDConfigFileRe|CFSDConfigFileReader|000000|ERROR | Searching for sdProcID and not found


Conclusion :
These 2 error messages could be ignored. They do not indicate a problem with ITCM.