Microsoft KB Archive/938441

= The appropriate tables and stored procedures are not created successfully when you install the Windows Key Management Service Management Pack for Microsoft Operations Manager 2005 =

Article ID: 938441

Article Last Modified on 7/31/2007

-

APPLIES TO


 * Microsoft Operations Manager (MOM) 2005

-



SYMPTOMS
After you install the Microsoft Windows Key Management Service (KMS) Management Pack for Microsoft Operations Manager (MOM) 2005, the management pack does not work.

If you perform troubleshooting steps, you experience the following symptoms:  When you examine the SystemCenterReporting database in Microsoft SQL Server, you notice that the KMS Management Pack-related tables and KMS Management Pack-related stored procedures have not been created successfully.  If you run the InstallKMSReports.bat file from the folder in which the management pack files were installed, the output is generated to the following two text files as expected:  InstallOutFile.txt InstallOutFile2.txt

However, when you examine these text files, you notice that the following error information has been logged: [Shared Memory]SQL Server does not exist or access denied. [Shared Memory]ConnectionOpen (Connect) 

This problem occurs if the SystemCenterReporting database is located on a named instance of SQL Server. If the SystemCenterReporting database is located on the default instance of SQL Server, this problem does not occur.



CAUSE
This problem occurs because the following two batch files do not correctly create the tables and stored procedures when the SystemCenterReporting database is located on a named instance of SQL Server:
 * InstallKMSReports.bat
 * KMSReportTableJob.bat



WORKAROUND
To work around this problem, modify the batch files that are listed in the &quot;Cause&quot; section to specify the named instance of SQL Server. To do this, follow these steps: <ol> Open the InstallKMSReports.bat file in a text editor. For example, open the file in Notepad.</li>  Modify the two Osql.exe statements to specify the named instance of SQL Server. For example, consider the following statements.

Original Osql.exe statements osql.exe -E -d SystemCenterReporting osql.exe -E -S %1 -d SystemCenterReporting Modified Osql.exe statements osql.exe -E -S .\<instance_name> -d SystemCenterReporting osql.exe -E -S %1\<instance_name> -d SystemCenterReporting Note In this code, replace <instance_name> with the name of the instance of SQL Server. </li> Save the file, and then open the KMSReportTableJob.bat file.</li>  Modify the Osql.exe statement to specify the named instance of SQL Server. For example, consider the following statements.

Original Osql.exe statement osql.exe -E -d SystemCenterReporting Modified Osql.exe statement osql.exe -E -S .\<instance_name> -d SystemCenterReporting Note In this code, replace <instance_name> with the name of the instance of SQL Server. </li> Save the file, and then exit the text editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information about how to obtain the KMS Management Pack, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=F500D97B-8648-49B8-AF7C-C65A47E83256&displaylang=en

Keywords: kbtshoot kbprb KB938441

-

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

© Microsoft Corporation. All rights reserved.