[March 29, 2017 12:39:56 PM CDT +831ms] t@1831864640 InCharge Framework ASL_MSG-*-ASLP-trapd/SNMP_TrapConf.asl: Error in trap configuration file on line no :110
[March 29, 2017 12:39:56 PM CDT +831ms] t@1831864640 InCharge Framework ASL_MSG-*-ASLP-trapd/SNMP_TrapConf.asl: 111=> <--------------------------From Previous Install Base Version : 9.2.2.0 ---------------------------->
[March 29, 2017 12:39:56 PM CDT +831ms] t@1831864640 InCharge Framework ASL_MSG-*-ASLP-trapd/SNMP_TrapConf.asl: Error in trap configuration file on line no :111
[March 29, 2017 12:39:56 PM CDT +832ms] t@1831864640 InCharge Framework ASL_MSG-*-ASLP-trapd/SNMP_TrapConf.asl: Error in trap configuration file on line no :120
[March 29, 2017 12:39:56 PM CDT +832ms] t@1831864640 InCharge Framework ASL_MSG-*-ASLP-trapd/SNMP_TrapConf.asl: 121=> <--------------------------From New Install Base Version : 9.4.1.0 ----------------------------->
[March 29, 2017 12:39:56 PM CDT +832ms] t@1831864640 InCharge Framework ASL_MSG-*-ASLP-trapd/SNMP_TrapConf.asl: Error in trap configuration file on line no :121
As the message above indicated, the trap configuration file that you are using for the trap exploder contains the indicated entries. Once the trap configuration file is located, one should see within the file line entries such as:
<--------------------------START CONFLICT--------------------------------> <--------------------------From Previous Install Base Version : 9.2.2.0 ----------------------------> <Section of code or text from 9.2.2.0> <--------------------------From Previous Install Local Install Version : 9.2.2.0 ----------------------------> <Section of code or text from 9.2.2.0> <--------------------------From New Install Base Version : 9.4.1.0 -----------------------------> <Section of code or text from 9.4.1.0> <--------------------------END CONFLICT---------------------------------->
Resolution
Remove the line entries from the trap configuration file. Next time the domain is restarted the error message will not appear.