Backward Compatibility Script Error Scom 2012

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Backward Compatibility Script Error System Center - Operations Manager > Operations Manager - Management Packs Question 0 Sign in to vote Hi, I have SCOM 2007 R2 version 6.1.7221.0 installed and the SCOM agent distributed to my servers. On some of my Windows 2008 R2 standard servers, I get the following error: Date and Time: 10-06-2011 01:53:37 Log Name: Operations Manager Source: Health Service Modules Event Number: 9100 Level: 1 Logging Computer: ALYNC3.silk.local User: N/A Description: An error occurred on line 120 while executing script 'MOM Backward Compatibility Service State Monitoring Script' Source: Microsoft VBScript runtime error Description: Out of memory One or more workflows were affected by this. Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring Instance name: ALYNC3.silk.local Instance ID: {CED1D294-259B-1BA3-2593-0578A1F6E960} Management group: SilkSystemCenter Event Data: < DataItem type =" System.XmlData " time =" 2011-06-10T01:53:37.2742473+02:00 " sourceHealthServiceId =" 2B69344C-8AD0-D779-B456-AA8742334CE5 " > < EventData > < Data > SilkSystemCenter < Data > System.Mom.BackwardCompatibility.ServiceStateMonitoring < Data > ALYNC3.silkeborg.local < Data > {CED1D294-259B-1BA3-2593-0578A1F6E960} < Data > 120 < Data > MOM Backward Compatibility Service State Monitoring Script < Data > Microsoft VBScript runtime error < Data > Out of memory Can you help me locate the reason for this error? Kind regards, Carl-Marius Tuesday, June 14, 2011 6:44 AM Reply | Quote Answers 0 Sign in to vote Hi, Please check if the following information will help: 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 http://social.technet.microsoft.com/Forums/en-US/sy

Monitoring Script' Source: Microsoft VBScript runtime error Description: The remote server machine does not exist or is unavailable One or more workflows were affected by this. Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring Instance name: Instance ID: {9B0201BA-B140-872E-B01A-9657DD8921AE} Management group: Any idea what is going on and how to fix this? I guess I have to test a script, but which one and how do I do this? I'm quite unfamiliar with MS scripts. Regards, Chris October 11th, 2010 5:08pm This happens on some older (way out of https://social.technet.microsoft.com/Forums/systemcenter/en-US/aab278f2-dd92-4e87-8c7a-06c374406d64/backward-compatibility-script-error?forum=operationsmanagermgmtpacks date) management packs - there was a generation of early management packs that were MOM 2005 conversions. They relied on backwards compatability libraries. You really want to get up to date and not run these old converted packs. Microsoft Corporation Free Windows Admin Tool Kit Click here and download it now October 11th, 2010 6:20pm Allright, there is the "MOM 2005 Backward http://www.networksteve.com/enterprise/topic.php/How_to_test_SCOM_scripts/?TopicId=16310&Posts=12 Compatibility" MP. When I open this one from the Administration Panel, I can see there aren't any MP depending on this one. Are we still having the issue you described. October 11th, 2010 6:55pm It's not going to be very easy or intuitive. The backwards compat workflows require slightly more advanced knowledge to test and see runtime data. And that's after you have figured out which script it is. There should be some context around what script is bombing somewhere, but not in the context you posted above. Once you find the MP, you'll need to export the XML and search the entire thing for script blocks. Hopefully there will be some clues you can use in the event log or somewhere else in an associated alert. Good luck with that. If you find more context, post it and we'll try to help.HTH, Jonathan Almquist - MSFT Free Windows Admin Tool Kit Click here and download it now October 12th, 2010 7:26am Hi, I also noticed the similar error in the “Known issues with Operations Manager 2007 SP1” list of the Kn

on October 12, 2009 by opsmgrunleashed The Operations Manager R2 management pack is automatically installed when you install System Center Operations Manager. How to Install the Operations Manager MP Download the Operations Manager Management Pack management pack guide from https://opsmgrunleashed.wordpress.com/2009/10/12/opsmgr-r2-by-example-the-operations-manager-management-pack/ the Management Pack Catalog (http://technet.microsoft.com/en-us/opsmgr/cc539535.aspx) and is the “Operations Manager 2007 R2 Management Pack Guide.doc” Read the Management Pack guide as this covers items such as how to enable recovery for Health Service Heartbeats and creating Run As accounts. Create an OperationsManager_Overrides management pack to contain any overrides required for the MP. Operations Manager MP Tuning / Alerts to look for The following alerts were encountered and resolved while tuning the Operations backward compatibility Manager management pack (these are listed in alphabetical order by Alert name): Alert: AD Agent Assignment: Admins User Role needs at least one domain account Issue: AD integrated agent deployment was not functional. The OpsMgr service was installed and running on the agent but would not show up in the pending management folder. Resolution: Per product knowledge, “Add the security group, which was provided as parameter to MOMADAdmin.exe to the Operations Manager Administrators backward compatibility script User Role.” In the OpsMgr console -> Administration -> Security -> User Roles -> Operations Manager Administrators, added the group specified when using the MomADAdmin.exe program to configure AD Integration. Closed the alert, re-started services on the server where AD agent assignment was failing (no change). Restarted the three services (in SP 1 these were OpsMgr Config Service, OpsMgr Health service, OpsMgr SDK Service, in R2 they are now System Center Data Access, System Center Management, System Center Management Configuration) and the agent appeared in of the OpsMgr console -> Administration -> Device Management -> Pending Management as expected. Alert: Agent proxying needs to be enabled for a health service to submit discovery data about other computers. Issue: The agent specified in the alert description does not have agent proxy enabled. Resolution: Found the name of the system within the alert description field (dc.abcco.com), copied the server name and opened the administration node -> Device Management -> Agent Managed and filtered on the name of the server (pasted in). Right-click on the server, go to the Properties on the Security tab. Check the Allow this agent to act as a proxy and discover managed objects on other computers checkbox. This is an alert rule so it will not auto-close, manually closed the alert on the monitor