Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 938441 - Last Review: July 31, 2007 - Revision: 1.0
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
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.
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
To work around this problem, modify the batch files that are listed in the "Cause" section to specify the named instance of SQL Server. To do this, follow these steps:
- Open the InstallKMSReports.bat file in a text editor. For example, open the file in Notepad.
- Modify the two Osql.exe statements to specify the named instance of SQL Server. For example, consider the following statements.
Original Osql.exe statementsosql.exe -E -d SystemCenterReporting
osql.exe -E -S %1 -d SystemCenterReporting
osql.exe -E -S .\<instance_name> -d SystemCenterReporting
osql.exe -E -S %1\<instance_name> -d SystemCenterReporting
- Save the file, and then open the KMSReportTableJob.bat file.
- Modify the Osql.exe statement to specify the named instance of SQL Server. For example, consider the following statements.
Original Osql.exe statementosql.exe -E -d SystemCenterReporting
osql.exe -E -S .\<instance_name> -d SystemCenterReporting
- Save the file, and then exit the text editor.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to obtain the KMS Management Pack, visit the following Microsoft Web site:
APPLIES TO
- Microsoft Operations Manager (MOM) 2005
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate