Microsoft Knowledge Base Email Alertz

(295856) - Describes an error that occurs when you try to use a script that contains a call to a WScript object method in MOM 2000 and MOM 2005.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 295856 - Last Review: December 4, 2007 - Revision: 2.4

Script does not run and "Interface has too many methods to fire events from" message appears in the alert history in MOM 2000 and MOM 2005

This article was previously published under Q295856

SYMPTOMS

When a script that contains a call to a WScript object method, for example the WScript.CreateObject, that runs as a response to an alert, the script is not completed successfully. The History tab for the alert contains the following error message as the exit code:
Interface has too many methods to fire events from
Also, the History log may display the name of the script as "(null)" instead of using the name of the script.

CAUSE

This behavior occurs because the objects that are available to scripts that run in the Windows Script Host environment, for example the WScript object, do not exist in the MOM scripting runtime. The MOM Scripting Engine treats WScript objects as syntax errors. Also, some methods that use the WScript object require user interaction. Do not call objects like Wshell.Popup() or WShell.SendKeys in a MOM scripting environment. These objects can cause the scripts to fail.

STATUS

This behavior is by design.

MORE INFORMATION

MOM 2000


The MOM agent has a separate script context and does not automatically create a WScript object. However, you can create and use any object under the WScript object model. For example, the following syntax creates a WshShell object:
Set oShell = CreateObject("WScript.Shell")


You can find most of the WScript object’s functionality in the MOM script context or in the helper object OpScrUtil that was included with MOM 2000. See the Scripting Help topic in MOM 2000 for more information.

MOM 2005
For more information about script with MOM 2005, see the MOM SDK. To do this, visit the following Web site:
http://technet.microsoft.com/en-us/opsmgr/bb498241.aspx (http://technet.microsoft.com/en-us/opsmgr/bb498241.aspx)

APPLIES TO
  • Microsoft Operations Manager 2000 Enterprise Edition
  • Microsoft Operations Manager (MOM) 2005
Keywords: 
kbscript kbopmaneventmgmt kbopmanalerts kberrmsg kbevent kbtshoot kbbug kbpending KB295856
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate