Microsoft KB Archive/896520

= You may receive an &quot;Old format or invalid type library error when processing MOM data&quot; message when the Microsoft Operations Manager (MOM) 2005 Management Server and the MOM 2005 database reside on the same computer =

Article ID: 896520

Article Last Modified on 11/16/2007

-

APPLIES TO


 * Microsoft Operations Manager (MOM) 2005
 * Microsoft SQL Server 2000 Service Pack 3

-





SYMPTOMS
When the Microsoft Operations Manager (MOM) 2005 Management Server and the MOM 2005 database reside on the same computer, you may receive the following error message every 24 to 120 hours:

Old format or invalid type library error when processing MOM data



CAUSE
This problem is caused by a memory leak that occurs in the Microsoft SQL Server shared memory protocol file (Dbmslpcn.dll). This file resides on the MOM 2005 Management Server. The Dbmslpcn.dll file contains the connection library protocols that the SQL Server client uses to connect to the MOM 2005 database that is hosted by SQL Server.

The SQL Server client can use the following three protocols to connect to the MOM 2005 database:
 * TCP
 * Named pipes
 * Shared memory

The SQL Server connection library typically contains these three protocols.

By default, a SQL Server client uses the shared memory protocol to connect to the MOM 2005 database when the following conditions are true:
 * The MOM 2005 Management Server is a SQL Server client.
 * The MOM 2005 Management Server resides on the computer that hosts the MOM 2005 database.

However, a memory leak may occur if the following conditions are true:
 * The Dbmslpcn.dll file that is used by the SQL Server client on the MOM 2005 Management Server is not the same version as the SQL Server Ssmslpcn.dll file.
 * The SQL Server client uses the shared memory protocol to connect to the MOM 2005 database.

Note When the SQL Server client and the MOM 2005 database reside on different computers, the TCP/IP or named pipes protocol is used to communicate.



WORKAROUND
To work around this problem, disable shared memory communication by using the Server Network Utility. To do this, follow these steps:  Verify that all instances of Microsoft SQL Server 2000 are version 8.0.818.0 or a later version. To do this, follow these steps:  Click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer. Select your SQL Server name and your authentication type, and then click OK. In the query input window on the Grids tab of the Query dialog box, type the following text, and then press the F5 key:

SELECT @@version

 Verify the version in the results box. If the version is earlier than 8.0.818.0, upgrade Microsoft SQL Server to version 8.0.818.0 or a later version. </li> Log on to the MOM 2005 Management Server by using an account that has administrative credentials.</li> Click Start, point to Programs, point to Microsoft SQL Server, and then click Server Network Utility.</li> In the Server Network Utility dialog box, click the General tab.</li> On the General tab, make sure that only the TCP/IP and Named Pipes protocols are listed in the Enabled protocols list, and then click OK.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in SQL Server 2000.

<div class="moreinformation_section">

MORE INFORMATION
For information about the most recent Microsoft SQL Server 2000 updates, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/sqlserver/bb331754.aspx

Keywords: kbtshoot kbprb KB896520

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.