A hotfix is available that fixes two issues with management packs in System Center Operations Manager 2007

Article translations Article translations
Article ID: 974254 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Issue 1

You try to create many groups in a single management pack or to import a management pack that contains many groups. However, the operation fails and the following event is logged in the Operations Manager log:

Source: OpsMgr SDK Service
Event ID: 26319
Description:
An exception was thrown while processing UpdateManagementPack for session id uuid:[UUID];id=<number>.
Exception Message: The creator of this fault did not specify a Reason.
Full Exception:
System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.ManagementPackException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to : Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Incorrect syntax near 'MTV_AllDatabasesGroup_:'.
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 0.
).

For example, this problem may occur when you use the OpsMgr SDK Service to create more than 397 groups in a single management pack. This example includes when you import a management pack and when you use the OpsMgr SDK Service to create the groups programmatically.

Issue 2

When you import a management pack or create a management pack from a management pack template, the following exception may be generated in the Operations Manager Operations Console:

Date: Date_and_Time
Application: System Center Operations Manager 2007
Application Version: 6.0.6278.0
Severity: Error
Message:

: Processing the template failed. See inner exception for details.
Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Too many table names in the query. The maximum allowable is 256.
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = n, current count = n.
: Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Too many table names in the query. The maximum allowable is 256.
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = n, current count = n

Additionally, the following events are logged in the Operations Manager log that is located on the Root Management Server.

Event ID 33333

Source: DataAccessLayer
Event ID: 33333
Description:
Data Access Layer rejected retry on SqlError:
Request: MPInfra_p_ManagementPackInstall -- (ManagementPackXML=<ManagementPack xmlns:xsd="URL" xmlns:xsl="URL" ContentReadable="t...), (ManagementPackXMLUpdateFragment=<ManagementPack xmlns:xsd="URL" xmlns:xsl="URL" ContentReadable="t...), (RunTimeXML=<ManagementPack xmlns:xsd="URL" xmlns:xsl="URL" ContentReadable="t...), (MPKeyToken=), (RETURN_VALUE=0)
Class: n
Number: n
Message: Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 0.

Event ID 26319

Source: OpsMgr SDK Service
Event ID: 26319
Description:
An exception was thrown while processing UpdateManagementPack for session id uuid<guid>;id=n.
Exception Message: The creator of this fault did not specify a Reason.
Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.ManagementPackException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to : Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Database error. [MPInfra_p_ManagementPackInstall] failed with exception:
Too many table names in the query. The maximum allowable is 256.
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = n, current count = n.).

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

This hotfix requires System Center Operations Manager 2007 Service Pack 1.

Installation instructions

This hotfix must be applied to each computer that hosts a Microsoft Operations Manager 2007 Database Server role.

Installation of this hotfix requires two separate procedures:
  1. Extract the hotfix files by running the installation file.
  2. Use Microsoft SQL Server Management Studio to run commands that are saved in a TSQL file against the Operations Manager database.
Note We recommend that you back up the Operations Manager database before you apply this hotfix.

Procedure 1: Extract the hotfix files

On any computer that has SQL Server Management Studio installed and that can connect to the Operations Manager Database Server, follow these steps to extract the management pack files:
  1. Copy the SystemCenterOperationsManager2007-SP1-KB974254-X86-X64-ENU.MSI file to either a local folder or a network shared folder.
  2. Run the SystemCenterOperationsManager2007-SP1-KB974254-X86-X64-ENU.MSI file. By default, the files are extracted into the following folder:
    Program Files\System Center Hotfix Utility\Q974254
    Note You can specify a different location during installation.
Procedure 2: Use SQL Server Management Studio to run SQL commands

Use Microsoft SQL Server Management Studio to run commands that are saved in a TSQL file against the Operations Manager Database Server database. To do this, follow these steps:
  1. Log on to the computer that hosts the Operations Manager 2007 Database Server database role as a user who has the database owner rights ("dbo" rights) to the Operations Manager 2007 database. Or, log on to a computer that hosts SQL Server Management Studio as a user who has the appropriate "dbo" rights to the Operations Manager 2007 database to perform the database update remotely.
  2. Start the SQL Server Management Studio.
  3. In the Connect to Server dialog box, connect to the Operations Manager 2007 Database Server.
  4. Click New Query on the toolbar.
  5. On the SQL Editor toolbar, select the Operations Manager database from the Available databases drop-down list. For example, select the OperationsManager database.
  6. On the File menu, point to Open, click File, and then open the ViewCreateSprocs.sql file that you extracted in procedure 1.
  7. When the file is open, click Execute on the SQL Editor toolbar.
  8. Check the Messages pane to confirm that the Transact-SQL commands have completed successfully.
  9. Repeat steps 4 through 8 to run the Transact-SQL commands in the AutoTableCreation.sql file.
  10. Exit the SQL Server Management Studio.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Autotablecreation.sqlNot Applicable3,84018-Jun-200909:07Not Applicable
Viewcreatesprocs.sqlNot Applicable15,60218-Jun-200909:07Not Applicable

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 974254 - Last Review: October 7, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft System Center Operations Manager 2007 Service Pack 1, when used with:
    • Microsoft System Center Operations Manager 2007
Keywords: 
kbsurveynew kbbug kbfix kbqfe KB974254

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com