Jairo Cetina

Problem: Alert: Processing Backlogged Events Taking a Long Time Source: SERVERNAME Status: New Path: SERVERNAME Last modified by: System Last modified time: 10/23/2010 10:34:28 AM Alert description: The Windows Event Log Provider monitoring the Application Event Log is 679802383 minutes behind in processing events. This can occur when the provider is restarted after being offline for some time, or there are too many events to be handled by the workflow. Workaround: Install Update Rollup for Operations Manager 2007 Service Pack 1 (KB971541) More Info: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=05d7785d-fe69-48bc-8dfa-72a77c8936bf http://support.microsoft.com/kb/971541

Problem: Installation of the Web Console role on Windows Server 2008 R2 fails with an "Unknown error (0x80005000)" error message. Impact: The Web Console role cannot be installed. Workaround: You must add the IIS 6 Management Compatibility component because it contains the prerequisites that are required for the installation and operation of the Operations Manager 2007 Web Console. To install the IIS 6.0 Management Compatibility Components by using Server Manager, follow these steps: Click Start , click Administrative Tools , and then click Server Manager . In the console tree, expand Roles , right-click Web Server (IIS) , and then click Add Role Services . In the Select Role Services pane, scroll down to IIS 6 Management Compatibility . Click to select the IIS 6 Metabase Compatibility check box and the IIS 6 Management Console check box. Click Next on the Select Role Services page, and then click Install on the Confirm Installati...

Problem: When you use the Discovery Wizard to perform a push installation of the Operations Manager 2007 SP1 agent on a Windows Server 2008 R2 or Window 7 system, the installation task may fail with an "A COM Proxy was called from the wrong context" error message. Impact: You cannot install the agent on this system by using the Operations Manager 2007 Discovery Wizard. Workaround: Log on to the system locally and perform a manual agent installation. For more information, visit the following Microsoft TechNet Web site: http://technet.microsoft.com/en-us/library/cc950516.aspx 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/971541 http://support.microsoft.com/kb/974722

Problem: When an Operations Manager 2007 SP1 agent is installed on a computer that is running Windows 7 or Windows Server 2008 R2, the following event may be logged in one or more event logs. Additionally, value for the number of minutes is very large. Log Name: Operations Manager Source: Health Service Modules Event ID: 26017 Level: Warning Description: The Windows Event Log Provider monitoring the %1 Event Log is %2 minutes behind in processing events. This can occur when the provider is restarted after it is offline for some time, or there are too many events to be handled by the workflow. Impact: None. These events are generated because of the delta between timestamps is calculated incorrectly. The event log processing is actually working correctly, and the events can be ignored. Workaround: No workaround is required. Ignore the events or upgrade to Operations Manager 2007 R2. This issue will be fixed in updates that will be available in the futur...

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 script 'MOM Backward Compatibility Service State Monitoring Script' Source Microsoft VBScript runtime error ...

Problem: When you try to install the Operations Manager 2007 SP1 agent Server Core installations of the 64-bit edition of Windows Server 2008 R2, the operation fails, and you receive the following error message: Windows Installer Service could not be accessed This issue occurs because the Operations Manager 2007 SP1 setup for 64-bit systems has some components that must run in 32-bit emulation, and the required subsystem is not installed by default in a Server Core installation of Windows Server 2008 R2. Workaround: You can upgrade to Operations Manager 2007 R2. Or, follow these steps on each system on which this issue occurs: Log on to the computer on which you want to install the agent. Run the following command to install the necessary subsystem: Start /w ocsetup ServerCore-WOW64 Note The Ocsetup.exe program takes case-sensitive parameters. Therefore, you must use type "ServerCore-WOW64" with the capitalization exactly as it appears here. ...

Problem: After you upgrade the operating system from Windows Server 2003 to Windows Server 2008 R2, the Adtserver service does not start. Additionally, the following event is logged: Event ID: 4672 AdtServer encountered the following problem during startup: Task: Open Audit Database Failure: An error occurred connecting to the database Error: 0x00000002 Error Message: The system cannot find the file specified. Error2: The system cannot find the file specified when we attempt to start the service manually. Impact: The service that performs the audit collection service (ACS) Server functions cannot start. This occurs for both Operations Manager SP1 and Operations Manager R2. During ACS startup, the location of the Open Database Connectivity (ODBC) driver that is used for the data source is queried to make sure that it matches the location that is used in setting up the data source name (DSN). In Windows Server 2008 R2, the registry parameter for the l...

Problem: After you upgrade the operating system on a Root Management Server to Windows Server 2008 R2, the following services may continue to stop unexpectedly: In Operations Manager 2007 SP1: The OpsMgr Config service and the OpsMgr SDK service In Operations Manager 2007 R2: System Center Management Configuration and System Center Data Access In this case, some events are logged for these service terminations in the System log. These events have a source of "Service Control Manager" and an Event ID of 7031. Impact: No SDK connectivity will be available. The Operations Console, Connectors, and any other SDK client connections will fail. Additionally, the Root Management Server will be unable to calculate or distribute new configurations, such as updates to group memberships, new or updated overrides, or management pack distribution. Workaround: This issue is resolved for Operations Manager 2007 SP1 by applying the update rollup that is docume...

Event Type: Warning Event Source: OpsMgr SDK Service Event Category: None Event ID: 26371 Date: 12/13/2007 Time: 2:58:24 PM User: N/A Computer: RMSCOMPUTER Description:The System Center Operations Manager SDK service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/rmscomputer and MSOMSdkSvc/rmscomputer.domain.com to the servicePrincipalName of DOMAIN\sdkaccount Every time the SDK service starts, it tries to update the SPN’s on the AD account that the SDK service runs under. It fails, because by default, a user cannot update its own SPNs. Therefore we see this error logged Procedure: Run ADSIEdit as a domain admin. Find the SDK domain account, right click, properties. Select the Security tab, click Advanced. Click Add. Type “SELF” in the object box. Click OK. Select the Properties Tab. Scroll down and check the “Allow” box for “Read servicePrincipalName” and “Write s...

In some situations we need to move OperationsManger Database to another computer for different reasons, for example: Hardware Limitations Database and Root Management server is on the same server. Fault Tolerance Procedure: Back up Operations Manager database including the Master. Back up the encryption key on the root management server by using the SecureStorageBackup.exe utility. Verify you have installed and configured the new SQL Server Instance as the existing one. Stop the Operations Manager Services (OpsMgr Config Service, OpsMgr SDK Service, and OpsMgr Health Service for Root Management Servers and OpsMgr Health Service for Management Servers) on the Management Servers in the Management Group before proceeding. In a clustered root management server environment, use Cluster Administrator (Windows Server 2003) or Failover Cluster Management (Windows Server 2008) to configure each of the three services listed above with the Take Offline opt...

Event Type: Warning Event Source: Health Service Modules Event Category: None Event ID: 10401 Date: Time: User: N/A Computer: Description: Module was unable to connect to namespace '\\.\ROOT\CIMV2' This has happened 1 times since this instance was loaded. HRESULT: 0x80041015 Details: Transport failure Note: Install KB958254: · Hosts a Microsoft Operations Manager 2007 Root Management Server · Hosts a Microsoft Operations Manager 2007 Management Server · Hosts a Microsoft Operations Manager 2007 Gateway Server · Hosts a Microsoft Operations Manager 2007 manually installed agent (Discovery-based agent deployment not used in Windows 2000) See: http://support.microsoft.com/kb/958254/en-us

Event Type: Error Event Source: Health Service Modules Event Category: None Event ID: 10102 Date: 16.06.2008 Time: 14:02:25 User: N/A Computer: JPSHHBACKUP Description: In PerfDataSource, could not resolve counter LogicalDisk, Free Megabytes, C:. Module will be unloaded. One or more workflows were affected by this. Workflow name: UIGeneratedMonitor7618edcbec224a7492ba6b72b7f5a28c Instance name: jpshhbackup.joeys.de Instance ID: {92CDC6A4-F4F3-DD71-E707-4C17C85FC3D8} Management group: JPSHHSYS_MG Note: If the counter LogicalDisk is not present in Performance Monitor add it with diskperf -yv Commnand and reboot server. See: http://support.microsoft.com/kb/102020/en-us