The System Center Operations Manager Support Team Blog

This is the OpsMgr 2007 blog for the Microsoft support team. If you were looking for the SCOM 2007 or MOM 2005 blog then you are in the right place.

OpsMgr 2007 Solution: Management Pack scripts fail and consume large amounts of memory

OpsMgr 2007 Solution: Management Pack scripts fail and consume large amounts of memory

  • Comments 4
  • Likes

image

Here's an issue that was sent to me courtesy of a couple different Support Engineers in our Operations Manager group.  Apparently we're getting a call or two on this and they thought it might help if we got the word out.

Issue: You may notice that on certain machines running the OpsMgr agent, cscripts fail and then consume large amounts of memory (e.g. 100MB or more).  This can cause virtual memory errors such as this:

Event Type:      Warning
Event Source:   Health Service Modules
Event ID:          21402
Description: Forced to terminate the following process started at <time> because it ran past the configured timeout 120 seconds.

Command executed:    "C:\WINDOWS\system32\cscript.exe" //nologo "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 22\1662\AD_Database_and_Log.vbs" false {24FC5C13-D587-5C71-820F-D146FFDF4917} 0.2 500000 200000 0.05
Working Directory:    C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 22\1662\

One or more workflows were affected by this. 

Cause: This can occur in some circumstances if the computer in question is using a version of Windows Script prior to 5.7.

Resolution: Apply the Windows Script 5.7 or later update.  Windows Script 5.7 can be downloaded here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4&DisplayLang=en

Note: A special thanks to Shamir Abdul Aziz and Ted Sendler for their work on this.

J.C. Hornbeck | Manageability Knowledge Engineer

Comments
  • PingBack from http://healthfood.linkablez.info/?p=74886

  • That's fine and good for XP and 2003 machines, what about Windows 7 and Windows Server 2008 R2?

  • So after some digging I found the following:

    Alert: Script or Executable Failed to run

    Issue: Lots of Script or Executable Failed to run errors on the same system all failing at the same time (in this case about a half-dozen or more would all fail with a 21402 (timeout).

    Resolution: WMI was non-functional on the system (stuck at 100% utilization one processor). Stopped the WMI service, when that failed killed the process and re-started the WMI service.

    It was buried on this page:

    www.systemcentercentral.com/.../Default.aspx

    This seems to be more in line with out situation, we have a lot going on and frequently see the WMI service freak out on random clients. This is an outstanding issue for us, for which we've been unable to find a resolution for.

    But at least I know that I can potentially restart WMI to solve this particular error.

  • aziz fazizollah321 @gmail.com

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment