Table of Contents



Symptoms

When running System Center Operations Manager 2007, the Operations Manager SDK Service may fail with the following error:

Event Type: Error
Event Source: OpsMgr SDK Service
Event Category: None
Event ID: 26380
Date: <date>
Time: <time>
User: N/A
Computer: computerName
Description:
The System Center Operations Manager SDK Service failed due to an
unhandled
exception
.
The service will attempt to restart.

You may also find information similar to the following:

System.TypeLoadException: Method 'SetupAlertsByCriteriaAndMonitoringClassReaderWithProperties' in type 'Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess' from assembly 'Microsoft.Mom.Sdk.ServiceDataLayer, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have an implementation.
at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService.AsyncStartCallback(Object notUsed)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="OpsMgr SDK Service" />
<EventID Qualifiers="49152">26380</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-06-22T08:20:38.000000000Z" />
<EventRecordID>6577561</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>RMS</Computer>
<Security />
</System>
<EventData>
<Data>System.TypeLoadException: Method 'SetupAlertsByCriteriaAndMonitoringClassReaderWithProperties' in type 'Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess' from assembly 'Microsoft.Mom.Sdk.ServiceDataLayer, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have an implementation.
at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService.AsyncStartCallback(Object notUsed)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)</Data>
</EventData>
</Event>

Note that if you restart the service it will start but fail again approximately 10 seconds later.

Cause

This can be cause by one or both of the following:

1. The System Center Operations Manager 2007 R2 Authoring console was installed on a System Center Operations Manager 2007 SP1 RMS server. This is an unsupported configuration.

2. The SDK assembly files are corrupt or the wrong version.

Resolution

To resolve this issue follow the steps below:

1. Remove the System Center Operations Manager 2007 R2 Authoring console if it was installed on a System Center Operations Manager 2007 SP1 RMS server.

2. Download and install the .NET Framework 2.0 Software Development Kit:

- For OpsMgr 2007 x86 see http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-c96d69c35dec&DisplayLang=en

- For OpsMgr 2007 x64 see http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1aef6fce-6e06-4b66-afe4-9aad3c835d3d

Run the commands below to re-install the SDK assembly files. Note that the gacutil.exe tool will be in C:\Program Files (x86)\Microsoft.NET\SDK\v2.0\Bin or C:\Program Files (x64)\Microsoft.NET\SDK\v2.0\Bin:

gacutil.exe /i "C:\Program Files\System Center Operations Manager 2007\SDK Binaries\Microsoft.EnterpriseManagement.OperationsManager.Common.dll" /f

gacutil.exe /i "C:\Program Files\System Center Operations Manager 2007\SDK Binaries\Microsoft.EnterpriseManagement.OperationsManager.dll" /f

The commands above register the Assembly cache with the correct DLL files.

3. Restart the OpsMgr SDK Service.