OpsMgr, SCE And MOM Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of Use

New KB951979 (SP1 Hotfix): Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed

New KB951979 (SP1 Hotfix): Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed

  • Comments 1
  • Likes

The following hotfix has been released for Operations Manager 2007 SP1 containing four management pack updates. These correct a number of issues seen after SP1 upgrade. See http://support.microsoft.com/kb/951979/en-us for full details.

These management packs will not be posted on the Management pack catalog and are only available as a hotfix at this time. See the link in the KB  article to request this hotfix.

 

Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed

SYMPTOMS


Consider the following scenario. You are using a management server that has Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1) installed. This management server also has certain management packs installed. In this scenario, the following problems occur.

Problem 1


The management server cannot collect the CSDVersion property from Windows Vista-based client computers. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 31876
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Data item returned no information for parameter '$Data/Property[@Name='CSDVersion']$'
This usually indicates that the query is incorrect.

Problem 2


The management server cannot collect operating system properties from Windows 2000 Service Pack 4-based client computers. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 10409
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Object enumeration failed Query: 'SELECT Version,Caption,BuildNumber,CSDVersion,ServicePackMajorVersion,ServicePackMinorVersion,SerialNumber,InstallDate,SystemDrive,WindowsDirectory,TotalVisibleMemorySize FROM Win32_OperatingSystem' HRESULT: 0x80041017 Details: Invalid query One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DiscoverWindowsOSProperties Instance name: InstanceName Instance ID: {Instance ID} Management group: GroupName


Problem 3


The HandleCountThreshold agent monitor does not restart the HealthService service on the Microsoft Exchange Server agent even when the HandleCountThreshold value has been exceeded. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Script
Event Category: None
Event ID: 6026
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
RestartHealthService.js : Restarting Health Service. Monitoring Host exceeded Process\Private Bytes threshold.

Problem 4


Audit Collection Services (ACS) events cannot be collected correctly. Additionally, Operations Manager displays the following error message:
An error occurred while performing a database operation. The error code was {0}

Problem 5


Incorrect warnings are raised for Performance Data Source Module when some services in the system are disabled. Additionally, Operations Manager displays the following error message:
Performance Module could not find a performance counter
Back to the top

Problem 6


Cluster discovery does not work correctly when the Virtual Server Name is a substring of the Physical Server Name.

RESOLUTION


Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451)
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Hotfix installation instructions
To apply this hotfix, follow these steps:1. Copy the SystemCenterOperationsManager2007-SP1-KB951979-X86-X64-ENU.msi file from the hotfix package to a local folder or to a shared folder.
2. Run the SystemCenterOperationsManager2007-SP1-KB951979-X86-X64-ENU.msi file.
3. Locate the hotfix utility folder for the hotfix. By default, the folder has the following path:
%ProgramFiles%\System Center 2007 Hotfix Utility\Q951979
4. Import the following management packs from the hotfix utility folder:

• Microsoft.SystemCenter.2007.mp (version 6.0.6278.19)
• Microsoft.SystemCenter.ACS.Internal.mp (version 6.0.6278.19)
• Microsoft.SystemCenter.Internal.mp (version 6.0.6278.19)
• Microsoft.Mom.BackwardCompatibility.mp (version 6.0.6278.19)

Prerequisites
To apply this hotfix, you must have System Center Operations Manager 2007 SP1 installed.
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.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment