Task fails with "BatchResponse" error
-
Wednesday, April 11, 2012 4:02 PM
Hi
We are trying to test our new Management Packs and we are having problems running a WMI task on an endpoint.
The error we see is :
"Initialization of a module of type "BatchResponse" (CLSID "{9F96E9EF-EA39-4352-AE5B-E6E0AB20E4CA}") failed with error code The filename, directory name, or volume label syntax is incorrect. causing the rule "CustomManagementPack.Stop.All.Task" running for instance "SOMEWHERE.SOMEDOMAIN.LOCAL" with id:"{FE3EDC89-9E3B-2F05-7CEA-A58F50A7DE1A}" in management group "OpsManager".
Error Code: -2130771961 (Unknown error (0x80ff0007))."I have confirmed that the WMI script we are trying to run works successfully when run from a Command prompt on that endpoint.
Info:
Ops Manager 2007 R2 (6.1.7221.0)
Server: Windows Server 2008 Enterprise R2 SP1 (both SCE server and endpoint).
I cannot find any other useful references to this error on the web :(
I have tried using ProcMon to find out what is wrong, but that doesn't show anything "incriminating"!
What is confusing us more is that the script has not changed from our previous Management Pack, where it ran with no problems. The only thing we have changed in the new pack are to switch from a WMI script for Discovery to a FilteredRegistryDiscoveryProvider.
The monitoring side of the packs is working fine and we have other tasks that are not WMI which also execute without a problem. It just seems to be the WMI tasks.
Can anyone shed some light on this for me?
Cheers
Ged
All Replies
-
Thursday, April 12, 2012 8:43 AMModerator
Hello Ged,
Is this issue related with SCE (Essentials 2010) or SCOM (Operations Manager 2007 R2)? For you have mentioned both products, I am a little confused.
If this is a question about SCOM, please use the following Forums, which would be the best resource in your scenario.
System Center Operations Manager Forums
http://social.technet.microsoft.com/Forums/en-US/category/systemcenteroperationsmanagerRegarding the script error, I would like to suggest you try the following:
1. Try the methods in the following post:
Getting lots of Script Failed To Run alerts? WMI Probe Failed Execution? Backward Compatibility Script Error?http://blogs.technet.com/b/kevinholman/archive/2009/06/29/getting-lots-of-script-failed-to-run-alerts-wmi-probe-failed-execution-backward-compatibility-script-error.aspx
2. Check anti-virus software exclusions settings:
Anti-virus software may cause script failures in OpsMgr 2007
http://blogs.technet.com/b/operationsmgr/archive/2009/01/22/anti-virus-software-may-cause-script-failures-in-opsmgr-2007.aspx3. Adjust the monitoring. If you don’t have a component to discover and monitor, you can override the related discovery and monitor.
Essentials 2010– Improving Default Monitoring
http://blogs.technet.com/b/systemcenteressentials/archive/2010/02/24/essentials-2010-improving-default-monitoring.aspxThanks,
Yog Li
TechNet Community Support
-
Thursday, April 12, 2012 9:26 AM
Apologies for the confusion. This is an Operations Manager 2007 question.
I'll make sure I put any future posts in that forum.
Thanks for the links. I had read all of those posts, none of which solved the problem but, happily, I have found the issue.
Answer:
I used ProcessMonitor again to watch what the MonitoringHost process was doing on the endpoint when trying to execute the script. I noticed that when it was trying to create the script file, using the name supplied in the XML, it was failing. It was at that point I realised that our Management Pack had an invalid value for the <scriptname> element.
We auto generate our SCOM packs using T4 code generation so, altering the T4 scripts to write the correct value solved the problem.
Ged
- Marked As Answer by Simply Ged Thursday, April 12, 2012 9:26 AM
-
Friday, April 13, 2012 6:26 AMModerator
Hi Ged,
Very glad to hear the issue resolved. And thanks for sharing your experience, which can help other community members facing similar problems.
Also, if you have any further concerns, please do not hesitate to let us know and we are happy to be of further assistance.
Thanks,
Yog Li
TechNet Community Support

