You need to look at each target in the job run log and determine what the error is. it could be different for each system.
This is the error for most of the failed servers:
Error Apr 1, 2011 5:38:59 PM com.bladelogic.app.collector.AssetCollectionException: Unable to parse file: /app/bladelogic/NSH/tmp/WorkItem-Thread-131301659731128.ini: A SAXParseException occurred during parsing: Expected an element name: Line = 4, Column = 2(component=Modified Template New (camsbup5), selector=Extended Object:Inetd Services)
1 of 1 people found this helpful
Can you live browse to one of the failed servers, then into ‘Extended Object’ and look for ‘Inetd Services’. If you don’t see it there we might need to enable live browse in the template (if the EO is local to the template). This will make the problem easier to reproduce.
Also – do you know what security compliance you are running? CIS, DISA, something you created?
This is Minimum Baseline Security compliance template.
I have live browsed one of the failed server and refreshed the "inetd service". It's giving me the same error as i mentioned in the earlier post.
Live browsed the successfull server and "inetd service" functioning well.
In the Component templete, live browse to this service is in enabled state only.
Ok, so find that script and fix it. who created your ‘minimum baseline security template’ ?