Backward Compatibility Script Error Scom 2007
Service Manager Data Center Hyper-V 2012 App Controller 2012 Data Protection Manager 2012 Operations Manager 2012 Virtual Machine Manager Essentials (SCE) Automation & Scripting Powershell Orchestrator Service Mgmt Automation (SMA) Blog Azure By Example Cloud Config Manager CP Development Cross-Platform Data Protection Mgr Essentials (SCE) Hyper-V KB MP Development Operations Manager Orchestrator Powershell SCC Cafe SCVMM Service Manager Service Mgmt Automation (SMA) Virtualization Windows Azure Pack Downloads Azure Config Manager Cross Platform Data Protection Manager Essentials (SCE) Hyper-V MP Development Operations Manager Orchestrator Powershell Scripts SCVMM Service Manager Service Mgmt Automation (SMA) SQL Queries Tools and Utilities Windows Azure Pack Pack Catalogs Management Packs Integration Packs ResearchThis! ShareThis! Podcasts Wiki LogIn Cluster monitoring "Backward Compatibility" script error and "module connection" failure Forum: Operations Manager4 Viewing 1 post (of 1 total) August 31, 2012 at 6:17 am #95396 CataphractParticipant I am trying to monitor a SQL 2008 R2 failover cluster configured on a 2 physical nodes windows 2008 R2 cluster (SCOM version is 2007 R2 CU5). node1: physical node 1 node2: physical node 2 virtualnode: the cluster virtual node virtualnodedtc: the distributed transaction coordinator associated with the cluster Currently node2 hosts virtualnode 3 events are raised on the node1: EventID: 9100 An error occurred on line 105 while executing script ‘MOM Backward Compatibility Service State Monitoring Script' Description: The remote server machine does not exist or is unavailable: ‘GetObject' Instance name: virtualnodedtc EventID: 10401 Module was unable to connect to namespace ‘\\virtualnodedtc\root\cimv2' HRESULT: 0x800706ba Details: The RPC server is unavailable. Instance name: virtualnodedtc EventID: 26002 The Windows Event Log Provider was unable to open the Application event log on computer virtualnode The provider will retry opening the log every 30 seconds. Most recent error details: The RPC server is unavailable. Instance name: virtualnodedtc The agent proxy setting is set on physical nodes. No cluster account is configured since the SCOM agent is running as local system on both physical nodes. (I have tried to set a cluster account with local admin right on both physical node but the errors are still present.) On the cluster configuration side only virtualnode is declared in the DNS. Is it needed to declare the virtualnodedtc component in the DNS ? Is there something I missed in SCOM configuration ? Thanks Author P
of "An error occurred on line 123 while executing script 'MOM Backward Compatibility Service State Monitoring Script'" Problem: When an Operations Manager 2007 SP1 agent is installed on a computer that is running Windows 7 or Windows Server 2008 R2, an alert may occur in the Operations console or an event may be logged on the computer that is being monitored. The alert reports that backward compatibility scripts failed. The following are the details that are present in the alert and its corresponding event on the agent. Collapse this tableExpand this table Alert field Value Alert Backward Compatibility Script Error Alert description An error occurred on line 123 while executing http://www.systemcentercentral.com/forums-archive/topic/cluster-monitoring-backward-compatibility-script-error-and-module-connection-failure/ script 'MOM Backward Compatibility Service State Monitoring Script' Source Microsoft VBScript runtime error Description Type mismatch: 'get' Log Name: Operations Manager Source: Health Service Modules Event ID: 9100 Level: Error Description: An error occurred on line 123 while executing script 'MOM Backward Compatibility Service State Monitoring Script' Source: Microsoft VBScript runtime error Description: Type mismatch: 'get' Impact: Low. This occurs because Windows 7 and Windows Server 2008 R2 have some services that http://jairocetina.blogspot.com/2010/10/compatibility-script-error-alerts-are.html have null values that the script does not expect. Therefore, the script fails with an error. The services for which these scripts fail are not critical. Therefore, you can safely ignore this alert. Workaround: Ignore the alert or upgrade to Operations Manager 2007 R2. This issue is resolved for Operations Manager 2007 SP1 by applying the update rollup that is documented in the KB article 971541. More Info: http://support.microsoft.com/kb/974722 http://support.microsoft.com/kb/971541 Posted by Jairo Cetina at 13:24 No hay comentarios: Publicar un comentario en la entrada Entrada más reciente Entrada antigua Página principal Suscribirse a: Enviar comentarios (Atom) About Me Jairo Cetina Bogota DC, Colombia ing.cetina@gmail.com Ver todo mi perfil for VMware ESXi Stats Followers Blogs Andrés Lozada Smart Cities - Motor para Gestión Pública 4/4 Consulta Del Guruinformatico Open Source Thin Client para VIEW tinycorebuilder CPD-Free Esta es la jubilación que nos espera? El Blog de Josep Ros Alertas en sistemas automatizados de carga y descarga en terminales portuarios El Blog de Virtualización - Jose Maria Gonzalez, vExpert 10 ¿Cómo crear un fichero de variables en OpenStack? Hans Avendano Polycom RoundTable 100??? How Exchange Works John Baker's BritBlog Online FREE Training: Creating and Managing a Private Cloud with System Center 2012 Jump Start NetoMeter Blog Letsencrypt Windows Client: How to Install Le
modified by: SystemLast modified time: 6/27/2007 1:20:31 PM Alert description: An error occurred on line 550 while executing http://microsoft.public.opsmgr.managementpacks.narkive.com/dPWZEmp4/backward-compatibility-script-errors script 'DHCP Server 2003 - Scope Monitoring'Source: Microsoft VBScript runtime errorDescription: Invalid procedure call or argumentOne or more workflows were affected by this.Workflow name: DHCP_Scope_Monitoring_1_2_RuleInstance name: Microsoft.Windows.Server.DHCP.Microsoft_Windows_2003_DHCP_Servers_InstallationInstance ID: {9BC0DA39-C2D6-9841-F86A-25D6DBE29042}Management group: BLAHAlert view link: "http://SCOM:51908/default.aspx?DisplayMode=Pivot&AlertID={90d11ae1-eaf2-4968-a4c8-bd5b21939a27}"Notification subscription ID generating this message: {C9E02866-A91A-6EB7-9CC0-C478A6B78972}I have backward compatibility the following two unique alerts been generated on all my print servers and dhcp servers. The servers in questions are all Windows 2003 R2 x86 with the latest patches and service packs.The SCOM Server does have the MOM 2005 Backwards backward compatibility script Compatability Management Pack version 6.0.5000.1 installed.Alert: Backward Compatibility Script ErrorSource: PETRUCHIO.domainPath: PETRUCHIO.domainLast modified by: SystemLast modified time: 6/27/2007 1:20:31 PM Alert description: An error occurred on line 550 while executing script 'DHCP Server 2003 - Scope Monitoring'Source: Microsoft VBScript runtime errorDescription: Invalid procedure call or argumentOne or more workflows were affected by this.Workflow name: DHCP_Scope_Monitoring_1_2_RuleInstance name: Microsoft.Windows.Server.DHCP.Microsoft_Windows_2003_DHCP_Servers_InstallationInstance ID: {9BC0DA39-C2D6-9841-F86A-25D6DBE29042}Management group: BLAHAlert view link: "http://SCOM:51908/default.aspx?DisplayMode=Pivot&AlertID={90d11ae1-eaf2-4968-a4c8-bd5b21939a27}"Notification subscription ID generating this message: {C9E02866-A91A-6EB7-9CC0-C478A6B78972}Alert: Backward Compatibility Script ErrorSource: PETRUCHIO.domainPath: PETRUCHIO.domainLast modified by: SystemLast modified time: 6/27/2007 1:51:46 PM Alert description: An error occurred on line 361 while executing script 'Print Server - State Monitoring'Source: Microsoft VBScript runtime errorDescription: Invalid procedure call or argumentOne or more workflows were affected by this.Workflow name: Run_State_Monitoring_2_RuleInstance name: Mi