OpsMgr, SCE And MOM Blog : New and upcoming KB Articles

Operations manager 2007 Sp1 / Essentials 2007 SP1 support for windows server 2008 announced

CliveEastwood — Sat, 26 Jul 2008 03:19:37 GMT

Windows Server 2008 support has been announced. Please see the following resources for more information

The Knowledgebase article KB953141 announces our support of OpsMgr SP1 and SCE SP1 running on Windows Server 2008

The above article discusses 4 required Windows Server 2008 hotfixes which may have to be installed depending on the OpsMgr/SCE role installed on Windows Server 2008

The above article also provide a link to a required OpsMgrSP1/SCESP1 hotfix rollup which is described in Knowledgebase article KB954049

The hotfixes referenced are all available from the Microsoft download center.

The Support Configurations details for Operations Manager 2007 SP1 have been updated to reflect supported Windows Server 2008 roles http://tnstage.dns.microsoft.com/en-us/library/bb309428.aspx

Management Pack Releases for Windows Server 2008 will take place shortly.

The hotfix provided in KB954049 can be installed on localized OpsMgrSP1/SCESP1 installations as it does not provide any localized fixes. The hotfix MSI installer is currently provided in English, localized versions will be provided in the coming weeks.

NOTES:

Please take careful consideration of the OpsMgrSP1/SCESP1 installation notes within KB954049 , particularly:

The OpsMgrSP1/SCESP1 hotfix must be applied after installation of OpsMgr/SCE on Windows Server 2008 or after in-place upgrade of the OS to Windows Server 2008 of an affected OpsMgr/SCE role. This will ensure correct performance counter registration on RMS, SCE Server, Management Server, Gateway server roles.
If User Account Control (UAC) is enabled on Windows Server 2008 when you apply the OpsMgrSP1/SCESP1 hotfix, you MUST execute SystemCenterOperationsManager2007-SP1-KB954049-X86-X64-ENU.MSI from an elevated command prompt. Failure to do so will not allow the display of the hotfix applicaton dialog once the MSI has completed installation of the staging bits on the server.
Read carefully the Known issues section of KB954049. There are a number of requirements and known issues, several still under investigation (Issues 6/7). As more information on Issues 6/7 becomes available and hotfixes developed the KB article will be updated and details provided.

KB951526 (Hotfix) - The Root Management Server (RMS) of System Center Operations Manager 2007 Service Pack 1 becomes unstable or unusable if a management pack is imported

CliveEastwood — Thu, 19 Jun 2008 21:16:43 GMT

The following Kb has been recently published and a hotfix is available. See http://support.microsoft.com/kb/951526

SYMPTOMS

Consider the following scenario:

•You import a management pack to monitor certain network devices in a Microsoft System Center Operations Manager 2007 Service Pack 1 environment.

•You perform a network device discovery by using Simple Network Management Protocol (SNMP).

In this scenario, you may receive one or both of the following error messages:
Error message 1

Health service host process has stopped working

Error message 2

Health service Host process encountered a problem and need to close

In this scenario, the OpsMgr Health Service is still running correctly. However, the Root Management Server (RMS) becomes unhealthy or unusable. Additionally, the following event is logged in the Operations Manager log on the server on which you perform the network device discovery:

Event Type: Error
Event Source: HealthService
Event Category: Health Service
Event ID: 4000
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
A monitoring host is unresponsive or has crashed. The status code for the host
failure was 2164195371.
Problem signature:
Problem Event Name: APPCRASH
Application Name: MonitoringHost.exe
Application Version: 6.0.6278.0
Application Timestamp: 47b71437
Fault Module Name: HealthServiceRuntime.dll
Fault Module Version: 6.0.6278.0
Fault Module Timestamp: 47b71433
Exception Code: c0000005
Exception Offset: 00003d9d
OS Version: 6.0.6001.2.1.0.16.7
Locale ID: 1033

CAUSE

A defect in the SNMP networking module causes the HealthService service to become unstable or to crash. Therefore, the Root Management Server becomes unstable or unusable.

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 (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

To apply this hotfix, you must have System Center Operations Manager 2007 Service Pack 1 installed

KB951380 (Hotfix) - Some computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1

CliveEastwood — Thu, 19 Jun 2008 21:10:27 GMT

The following KB has recently been published http://support.microsoft.com/kb/951380 and a hotfix is available.

SYMPTOMS

When you run a discovery operation in Microsoft System Center Operations Manager 2007 Service Pack 1, and a cluster node is discovered, some computer properties may not be collected for the cluster node. For example, the DNS host name, the security identifier (SID) and the Active Directory organizational unit of the cluster node may not be collected. Therefore, some Operations Manager workflows may not function correctly. For example, if the DNS host name is not collected in an Operations Manager 2007 environment that has the Microsoft Exchange Server 2007 Management Pack applied, the following event may be logged:

Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 10720
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health Service. This is a transient issue, the affected rule(s) will be unloaded and the Health Service will restart them when initialization is complete.

RESOLUTION

Hotfix information

http://support.microsoft.com/contactus/?ws=support (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

To apply this hotfix, you must have System Center Operations Manager 2007 Service Pack 1 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.

KB949969 Some data partition tables that exceed the data retention period are not groomed from the Audit Collection Services database in Operations Manager 2007

CliveEastwood — Fri, 13 Jun 2008 01:48:54 GMT

New KB http://support.microsoft.com/kb/949969/en-us and hotfix

SYMPTOMS

Consider the following scenario:

•
You use the Audit Collection Services (ACS) feature in Microsoft System Center Operations Manager 2007 to collect security events from managed computers.

•
You configure database grooming policies for the ACS database.

However, some data partition tables that exceed the data retention period are not groomed from the database as expected. Over time, the ACS database may run out of disk space.
When this problem occurs, you may discover that these partition tables have a status of 1.

CAUSE

This problem occurs for one or more of the following reasons:

•
When a partition is closing, ACS tries to calculate the last event insertion time for the partition. ACS uses the last event insertion time to determine whether the partition is still within the retention period. However, the calculation operation may time out if the partition is too large. In this situation, ACS saves an invalid time to the last event insertion time field.

•
ACS marks the partition status to 1 (This means that the partition status is "in transition") when a partition is closing. ACS sets the partition status to 2 (This means that the partition status is "closed") only after re-indexing is completed. However, the re-indexing operation may time out if the partition is too large. In this situation, the partition remains in the "in transition" status indefinitely.

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.
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, submit a request to 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 (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.

Hotfix installation instructions

To apply this hotfix, follow these steps:

1.
Copy the following file from the hotfix package to a local folder or to a shared folder. Then, run this file:

SystemCenterOperationsManager2007-SP1-KB949969-X86-X64-ENU.MSI

2.
By default, this hotfix is installed into the following folder:

%ProgramFiles%\System Center 2007 Hotfix Utility\Q949969

The Q949969 folder contains the following subfolders:

•
An x86 subfolder for x86 platforms

•
An x64 subfolder for x64 platforms

Open the x86 subfolder or the x64 subfolder, as appropriate for your situation.

3.
Locate the AdtSrvDll.dll file in the following folder:

%WINDIR%\system32\Security\AdtServer

4.
Verify that the version of the AdtSrvDll.dll file is greater than or equal to version 6.0.6278.0 and less than version 6.0.6278.7. To do this, right-click the AdtSrvDll.dll file in Windows Explorer, and then click Properties. The File version field on the Version tab displays the version of the file.
Note If the file version is greater than or equal to version 6.0.6278.7, this file already contains the current hotfix. If the file version is less than version 6.0.6278.0, you cannot apply this hotfix.

5.
On the ACS Collector server, stop the Operations Manager Audit Collection Service.

6.
Copy the following files from the Q949969 folder into the AdtServer folder that you located in step 3.

•
AdtSrvdll.dll

•
DbClosePartition.sql

•
DbCreatePartition.sql

When you do this, you replace the existing files with the hotfix files.

7.
On the server that hosts the ACS database or that has a connection to the ACS database, open SQL Server Management Studio.

8.
In SQL Server Management Studio, connect to the ACS database. By default, the ACS database is named "OperationsManagerAC."

9.
In SQL Server Management Studio, open a new query, and then run the following statements:

Use OperationsManagerAC
Update dtPartition Set Status = 2 Where Status = 1

10.
Verify that you receive the following message in the result pane:

(n row(s) affected)

11.
Restart the Operations Manager Audit Collection Service that you stopped in step 5.

Post-hotfix behavior

After you apply this hotfix, ACS uses the partition close time instead of the last event insertion time to determine whether a partition exceeds the retention period. In addition, when a partition is closing, the status of the partition is set from 0 directly to 2, instead of being set to 1.

Prerequisites

To apply this hotfix, you must have the following prerequisites installed on the computer:

•
System Center Operations Manager 2007 Service Pack 1

•
ACS Collector

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.

KB950853 - A memory leak occurs when you monitor Exchange Server 2007 by using the MOM 2007 agent in System Center Operations Manager 2007

CliveEastwood — Fri, 13 Jun 2008 01:45:07 GMT

Sorry this is one I failed to blog which released while I was at MMS http://support.microsoft.com/kb/950853/en-us .This hotfix is strongly recommended for for those running the Exchange 2007 MP together with http://support.microsoft.com/kb/951979/en-us

SYMPTOMS

Consider the following scenario:

•You import the Microsoft Exchange Server 2007 Management Pack for Operations Manager 2007 into a management group in Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1).

•Then, you install the Operations Manager 2007 agent on an Exchange Server 2007 computer to monitor Exchange rules and processes.

In this scenario, a memory leak occurs on the Exchange Server 2007 computer.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Operations Manager 2007 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Hotfix installation information

You must apply this hotfix on all Operations Manager Management Server computers. You can apply this hotfix from Windows Explorer or at a command prompt. This hotfix package includes both 32-bit and x64 file versions. When you apply this hotfix, it will install the files versions that are appropriate to your particular installation.
The computers that are running the agent are updated automatically. However, you must approve the update in the Pending Management folder. To do this, follow these steps:

1.
On the computer that is running the management server role, click Start, point to All Programs, point to System Center Operations Manager 2007, and then click Operations Console.

2.
Select Administration view, expand Administration, expand Device Management, and then click Pending Management.

3.
In the Pending Management folder, review and approve the agent computers on which you want to apply this hotfix.

Prerequisites

You must install Operations Manager 2007 Service Pack 1 before you apply this hotfix. To download the Operations Manager 2007 Service Pack 1 Upgrade Package, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=EDE38D83-32D1-46FB-8B6D-78FA1DCB3E85&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=EDE38D83-32D1-46FB-8B6D-78FA1DCB3E85&displaylang=en)

Restart requirement

You do not have to restart the computer after you apply this hotfix package. However all Operations Manager services will be automatically restarted.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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

CliveEastwood — Tue, 10 Jun 2008 20:00:10 GMT

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.

New KB Articles – Operations Manager 2007 / MOM 2005

CliveEastwood — Mon, 07 Apr 2008 18:41:44 GMT

The following new Operations Manager 2007 KB articles have been released:

KB949875 - When you run a task in the System Center Operations Manager 2007 Operations Console on a Russian version of Windows Server 2003, the task outputs are displayed in corrupted text - http://support.microsoft.com/kb/949875

KB945312 - The OpsMgr Health service may incorrectly display the health state of the cluster nodes in System Center Operations Manager 2007 - http://support.microsoft.com/kb/945312

NOTE: This hotfix is provided for OpsMgr RTM with the latest version of the Cluster MP (6.0.6277.0 >). See the Cluster 2003 MP Guide and folder KB945312 RTM ONLY QFE when the Clsuter MP MSI is extracted. This QFE does NOT apply to Operations Manager 2007 SP1.

KB946428 - The Health Service does not process configuration files, and events 7022 and 1220 are logged every 30 minutes on a domain controller on which you installed the Operations Manager 2007 agent - http://support.microsoft.com/kb/946428

The following new KB article for MOM 2005 has been released:

KB949874 - The MOM service may crash when you run the discovery process on many agent computers in MOM 2005 - http://support.microsoft.com/kb/949874

New Opsmgr and Essentials Kb articles

CliveEastwood — Mon, 17 Mar 2008 20:40:51 GMT

KB949451 - The ScheduleFilter module is removed from a rule in System Center Operations Manager 2007 - http://support.microsoft.com/kb/949451

KB949452 - Event 4618 is logged when you use the AdtSetup.exe program to update an Audit Collection Services installation in System Center Operations Manager 2007 - http://support.microsoft.com/kb/949452

KB949454 - Error message when you try to open a report from a link in the scheduled report e-mail notification in System Center Operations Manager 2007: "An internal error occurred on the report server" - http://support.microsoft.com/kb/949454

KB949449 - The Client Monitoring Configuration Wizard fails with an unknown error that occurs together with the 80FF002B code when you enable the client monitoring feature in System Center Operations Manager 2007 - http://support.microsoft.com/kb/949449

KB949455 - System Center Operations Manager 2007 Reporting installation fails on a Windows Server 2008 computer if IIS 6.0 Management Compatibility is not installed - http://support.microsoft.com/kb/949455

KB949453 - The state calculation may be delayed when a new group or a distributed application is created in System Center Operations Manager 2007 - http://support.microsoft.com/kb/949453

KB946426 - You are not prompted that a computer is shut down after the Maintenance Mode window expires in System Center Operations Manager 2007 - http://support.microsoft.com/kb/946426

KB949450 - You cannot add required permissions to the share when you run the "fix permissions" task in System Center Operations Manager 2007 - http://support.microsoft.com/kb/949450

KB948559 - AEM does not work when the management server action account is a low-permission account in System Center Operations Manager 2007 - http://support.microsoft.com/kb/948559

KB949448 - Error message in System Center Operations Manager 2007 or in System Center Essentials 2007: "The setup wizard was interrupted before System Center Operations Manager 2007 could be installed" or "The client has been disconnected from the server" - http://support.microsoft.com/kb/949448

KB946423 - How to install a System Center Essentials 2007 agent on a computer that is running ISA Server 2006 or ISA Server 2004- http://support.microsoft.com/kb/946423

KB946418 - Error message when you install the System Center Operations Manager 2007 reporting feature: "SRS Server Validation Error" - http://support.microsoft.com/kb/946418

KB942864 (Update) - How to use diagnostic tracing in System Center Operations Manager 2007 and in System Center Essentials 2007

CliveEastwood — Mon, 17 Mar 2008 18:20:47 GMT

I stated in a previous post that the existing trace KB article was undergoing a refresh due to changes in OpsMgr SP1 and SCE SP1. The updated article is now available http://support.microsoft.com/kb/942864

Details below:

INTRODUCTION

This article describes how to use diagnostic tracing in Microsoft System Center Operations Manager 2007 and in Microsoft System Center Essentials 2007.
Important We recommend that you perform diagnostic tracing only in association with a Microsoft Customer Support Services (CSS) representative. We recommend this because the generated traces contain information about the context of a text-based trace message. However, in Microsoft System Center Operations Manager 2007 and in Microsoft System Center Essentials 2007, this trace information is not in a human-readable format. After the traces are converted by a Microsoft CSS representative, human-readable text is available. However, this text contains only low-level information such as source-code file names, locations, source-code functions, and return codes. This information may be helpful if you have to troubleshoot a complex issue.
In System Center Essentials 2007 Service Pack 1 (SP1), in System Center Operations Manager 2007 SP1, and in later versions, trace message files (TMF) are supplied which allow for conversion of binary trace files to text. However, we strongly recommend that you perform diagnostic tracing only when it is required and only with the consultation of a Microsoft representative.

MORE INFORMATION

System Center Operations Manager 2007 and System Center Essentials 2007 implement a diagnostic tracing method that differs from earlier versions of Microsoft Operations Manager. This new tracing method creates binary files in which to store tracing information. Because this new tracing method is implemented at the Windows kernel level, it is highly efficient, and it can log tens of thousands of trace messages per second.
The following information discusses the tools that are available to start and to stop tracing if you are asked to do this by a Microsoft CSS representative. The following information also discusses the new functionality that is provided in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions.

Tracing tools location

The installation folder for each role, such as the Agent role, the Management Server role, or the Gateway role, contains a folder that is named Tools. The following files are located in the Tools folder:

•
StartTracing.cmd

•
StopTracing.cmd

•
TracelogSM.exe

•
TracingGuidsBid.txt

•
TracingGuidsUI.txt

•
TracingGuidsNative.txt

•
TracingReadMe.txt

System Center Essentials 2007 SP1 and System Center Operations Manager 2007 SP1 introduce the following additions:

•
FormatTracing.cmd

•
ViewRealtimeTracing.cmd

•
TraceFmtSM.exe

•
OpsMgrTraceTMF.cab

•
Default.tmf

•
System.tmf

To start tracing

Note In System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions, tracing is automatically started on both the Agent role and the Management Server role. Tracing will use error output only. Binary trace files are written to the SystemDrive\Temp\OpsMgrTrace folder. Before the tracing level for trace output can be changed, tracing must first be stopped.
To start diagnostic tracing, follow these steps:

1.
On the computer on which you want to start tracing, click Start, click Run, type cmd, and then click OK.

2.
At the command prompt, use the cd command to change to the Tools directory. For example, type the following command, and then press ENTER:

cd\Program Files\System Center Operations Manager 2007\Tools

3.
Type StartTracing LEVEL, and then press ENTER. In this command, replace LEVEL with the tracing level that you want. You must use uppercase characters to specify the tracing level. The following levels are available:

•
ERR

•
WRN

•
INF

•
VER

For example, type StartTracing WRN.

When you start tracing, the trace output is written to the following binary files:

•
MOMTraceNative.etl

•
MOMTraceBID.etl

•
MOMTraceUI.etl

These files are located in the SystemDrive\Temp folder.
Note In System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions, trace files (.etl) are located in the SystemDrive\Temp\OpsMgrTrace folder.

To stop tracing

To stop diagnostic tracing, follow these steps:

1.
Click Start, click Run, type cmd, and then click OK.

2.
At the command prompt, use the cd command to change to the Tools directory. For example, type the following command, and then press ENTER:

cd\Program Files\System Center Operations Manager 2007\Tools

3.
Type StopTracing.cmd, and then press ENTER.

After you stop diagnostic tracing, you can send the .etl files from the SystemDrive\Temp folder to the Microsoft CSS representative with whom you are working.
Note In System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions, trace files are located in the SystemDrive\Temp\OpsMgrTrace folder. Because TMFs are supplied with SP1, traces can be converted without having to send .etl files to Microsoft.

To convert existing traces to text format in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

To convert existing trace files to text tracing, you have to stop tracing first by using the StopTracing.cmd command.
Note Information within the converted traces is of a very low level detail (debug level). Therefore, the converted traces require knowledge of the source code and of the component that is being traced. We recommend that trace conversion be performed only when it is required by a Microsoft CSS representative.

1.
Click Start, click Run, type cmd, and then click OK.

2.
At the command prompt, use the cd command to change to the Tools directory. For example, type the following command, and then press ENTER:

cd\Program Files\System Center Operations Manager 2007\Tools

3.
Type FormatTracing.cmd, and then press ENTER.

The first time that the FormatTracing.cmd command is executed, the trace files that are required to convert traces are extracted to the SystemDrive\Program Files\System Center Operations Manager\Tools\TMF folder. Then, the FormatTracing.cmd batch file enumerates each trace file (*.etl) in the SystemDrive\Temp\OpsMgrTrace folder. Then, the TraceFMTSM.exe utility converts the files to text. The text output is written to a file of the same name with the extension .log in the SystemDrive\Temp\OpsMgrTrace folder. A summary (.sum) file is also written to the same location for each file that is converted. This file details each trace message event converted.

Viewing converted trace files in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

Trace files that are converted to text by using the FormatTracing.cmd batch file can be viewed by using a text editor, such as Notepad. By default, in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions, trace files are located in the SystemDrive\Temp\OpsMgrTrace folder.

Boot time tracing is enabled by default in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

On a typical Root Management Server (RMS) installation, three trace sessions begin when the HealthService service is started. By default, only error tracing is performed. Little information is written to the trace files. The default trace file location and names that are created are as follows:

Folder
File name
Description

system drive\Temp\OpsMgrTrace
TracingGuidsBID.etl
Trace output for Managed Code Components

system drive\Temp\OpsMgrTrace
TracingGuidsNative.etl
Trace output for Native Code Components

system drive\Temp\OpsMgrTrace
TracingGuidsUI.etl
Trace output for Managed code User Interface (OpsMgr UI)

Each session is enabled with circular tracing and has a maximum file size of 100 megabytes (MB). The typical .etl file size for a newly created .etl file is 16 kilobytes (KB).
Note Although an Operations Manager Role, such as an Agent role, does not contain managed or user interface tracing messages, the three default trace .etl files will be created by default when the HealthService service is started. By default, no trace sessions are started on a User Interface only role.

How to disable boot time tracing in System Center Essentials 2007 SP1 and in System Center Operations Manager 2007 SP1

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Three trace providers are started automatically on any role that contains the HealthService service. The trace files are written to the SystemDrive\Temp\OpsmgrTrace folder. Typically, the .etl files in this folder will be small, especially for the Agent role. However, for the RMS role, if the operations manager installation becomes unhealthy, one or more of these files could potentially grow to the maximum configured size of 100 MB each. These files include the following:

•
TracingGuidsBid.etl

•
TracingGuidsNative.etl

•
TracingGuidsUI.etl

•
previous .etl files

If you have to disable debug level tracing because of a small boot partition size, you can add a registry value to the computer that is running the Management Server role or the Agent role on which you want to disable tracing. To do this, follow these steps.
Note If tracing is disabled, this may affect future troubleshooting of Operations Manager because any low level tracing information will be lost. Future hotfixes, service packs, or product updates may remove the registry entry and enable tracing again. By default, this registry key does not exist. Default tracing is enabled if you remove this registry key or change its value to 0.

1.
Click Start, click Run, type regedit, and then click OK.

2.
Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Tracing

3.
In the details pane, double-click DisableAutoTracing.

4.
In the Value data field, type 1, and then click OK.

5.
Exit Registry Editor.

If you execute the StopTracing.cmd batch file from the Tools folder, the Operations Manager trace sessions will be stopped. The .etl files in the SystemDrive\Temp\OpsmgrTrace folder can be deleted if they are no longer required to regain disk space.

How to move the default location of trace file output in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

If an Operations Manager Server role or Agent role is installed on a computer where the boot partition space is limited, you may have to move the default location of trace files (*.etl). To do this, follow these steps:

1.
Create a new folder on a local disk that has sufficient capacity to house the files. Three default trace files at a maximum of 100 MB each and three previously-used trace files at a maximum of 100 MB each equals a total potential trace file capacity of 600 MB.

2.
Set at least the following NTFS permissions on the folder, SYSTEM = Full Control, Administrators = Full Control.

3.
Locate and open the StartTracing.cmd batch file in the Operations Manager/Essentials/Tools installation folder. Use a text editor, such as Notepad.

4.
In the StartTracing.cmd batch file, locate the SET OpsMgrTracePath statement. Replace the default value SystemDrive\Temp\OpsMgrTrace with the path of the new location. Delimit the path with speech marks (“) if the path contains a space character.

5.
Save the changes to the StartTracing.cmd file.

6.
To start tracing to the new folder, run the StopTracing.cmd batch file. Then, run the StartTracing.cmd batch file. After you run the StartTracing.cmd batch file, the following files are written to the new folder:

•
TracingGuidsBid.etl

•
TracingGuidsNative.etl

•
TracingGuidsUI.etl

7.
Before you use the FormatTracing.cmd command to convert traces to text, you must edit the FormatTracing.cmd command to change the OpsMgrTracePath variable to point to the new trace file folder.

Future hotfixes, service packs, or product updates may change the files in the Tools folder. This changes the functionality back to the default functionality. We recommend that you check for more changes after you perform updates.

How to view real time tracing in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

We recommend that you do not use the ViewRealTimeTracing.cmd batch file to view real time traces in a production environment without advice from Microsoft CSS. Viewing traces in real time, especially when you use Information trace level settings or Verbose trace level settings, may severely affect server performance.
The first time that the ViewRealTimeTracing.cmd file is executed, the trace files that are required to convert traces are extracted to the SystemDrive\Program Files\System Center Operations Manager\Tools\TMF folder. The ViewRealTimeTracing.cmd batch file then enumerates each trace session definition file (Tools\TracingGuids*.txt) in the Tools folder. Then, a separate instance of TraceFmtSM is started within a Command Prompt window. Output of trace sessions for Managed, Native, and UI Managed traces is output to each window.
The ViewRealTimeTracing.cmd batch file accepts a single, optional command line parameter (-ods). Supplying this parameter will additionally output trace data to a debugger.

New Operations Manager 2007 KB articles

CliveEastwood — Fri, 14 Mar 2008 00:40:57 GMT

KB949447 - You may have to restart the computer when you install the security update that Microsoft Knowledge Base article 933579 describes - http://support.microsoft.com/kb/949447

KB949446 - The mouse pointer disappears and the mouse rotation operation is unpredictable in System Center Operations Manager 2007 - http://support.microsoft.com/kb/949446

KB946437 - How to disable the use of certificates that are imported by using the MOMCertImport.exe tool in System Center Operations Manager 2007

CliveEastwood — Mon, 10 Mar 2008 19:44:30 GMT

KB946437 - How to disable the use of certificates that are imported by using the MOMCertImport.exe tool in System Center Operations Manager 2007 - http://support.microsoft.com/kb/946437

New Operations Manager KB Articles

CliveEastwood — Thu, 06 Mar 2008 23:56:59 GMT

KB946433 - Description of the mode that GSM modems must support to work with SMS notifications in System Center Operations Manager 2007 - http://support.microsoft.com/kb/946433

KB948730 - WMI does not work correctly after you install the Microsoft System Center Operations Manager 2007 agent on a Dell computer - http://support.microsoft.com/kb/948730

KB946435 - Error message when you configure Agent Exception Monitoring to use a remote file share in System Center Operations Manager 2007: "A file share could not be created" - http://support.microsoft.com/kb/946435

KB944443 - List of issues that are fixed in System Center Operations Manager 2007 Service Pack 1

CliveEastwood — Thu, 28 Feb 2008 07:13:15 GMT

Finally the edits for SP1 RTM have been made to http://support.microsoft.com/?id=944443

SUMMARY

This article lists the issues that are fixed in Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1).

INTRODUCTION

This article contains a list of Microsoft Knowledge Base (KB) articles that describe the issues that are fixed in System Center Operations Manager 2007 SP1. This article is primarily intended to help IT professionals and corporate helpdesk workers to support and to maintain a company’s computer system.

MORE INFORMATION

List of issues fixed

The following issues have been fixed in System Center Operations Manager 2007 SP1:

935898 (http://support.microsoft.com/kb/935898/) Error message when you try to access a Web page view in the System Center Operations Manager 2007 Web Console: "Requested value 'UrlViewType' was not found"

937470 (http://support.microsoft.com/kb/937470/) A notification subscription's Alert Criteria options do not work as expected in System Center Operations Manager 2007

935896 (http://support.microsoft.com/kb/935896/) When the Health Service (HealthService.exe) runs timed scripts in System Center Operations Manager 2007, high memory usage may occur

936838 (http://support.microsoft.com/kb/936838/) After a System Center Operations Manager 2007 agent sends discovery data to a management group, no rules are deployed for monitoring in later management groups

939799 (http://support.microsoft.com/kb/939799/) The System Center Operations Manager 2007 agent is unable to restart the health service after its monitored thresholds are exceeded

936481 (http://support.microsoft.com/kb/936481/) You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment

938505 (http://support.microsoft.com/kb/938505/) Some report information does not appear in Japanese in the Japanese version of System Center Operations Manager 2007

939364 (http://support.microsoft.com/kb/939364/) System Center Operations Manager 2007 cannot find some network devices by using the network device discovery process

939585 (http://support.microsoft.com/kb/939585/) Some SSL Monitoring monitors display an incorrect status or an incorrect name in System Center Operations Manager 2007

936219 (http://support.microsoft.com/kb/936219/) Error message when you try to install System Center Operations Manager 2007 Reporting: "The wizard was interrupted before Operations Manager 2007 could be installed"

938989 (http://support.microsoft.com/kb/938989/) Subscription notification objects in System Center Operations Manager 2007 may not be displayed correctly on a computer that uses a regional setting other than "English (United States)"

942865 (http://support.microsoft.com/kb/942865/) Error message when you try to generate a report in System Center Operations Manager 2007: "Cannot initialize report"

938626 (http://support.microsoft.com/kb/938626/) The Entity Health monitor for an Operations Manager 2007 management server displays "Critical" together with a Health Service threshold setting

938993 (http://support.microsoft.com/kb/938993/) You cannot deploy an agent by using the Discovery and Installation Wizard in System Center Operations Manager 2007

938991 (http://support.microsoft.com/kb/938991/) The SQL Server 2000 database engine health is not monitored in System Center Operations Manager 2007

938988 (http://support.microsoft.com/kb/938988/) You may be unable to delete a log file on a client computer in System Center Operations Manager 2007

936579 (http://support.microsoft.com/kb/936579/) The Operations Manager Audit Collection Service does not start and Event ID 4668 is logged after you install Audit Collection Server from a read-only source

943706 (http://support.microsoft.com/kb/943706/) The MonitoringHost.exe process on the System Center Operations Manager 2007 root management server may consume more than 2 gigabytes of memory

941985 (http://support.microsoft.com/kb/941985/) A management group that contains an Exchange Server computer may intermittently stop receiving new alerts in Microsoft System Center Operations Manager 2007

938507 (http://support.microsoft.com/kb/938507/) Report scheduling fails in System Center Operations Manager 2007 when the regional settings on the client computer differ from the regional settings on the server

938510 (http://support.microsoft.com/kb/938510/) You cannot obtain elevated user rights in management servers and in agents in System Center Operations Manager 2007 or System Center Essentials 2007 environments

939769 (http://support.microsoft.com/kb/939769/) You experience a delay in fetching "Actions for Tasks" and "Actions for Reports" for a selected row in System Center Operations Manager 2007

940224 (http://support.microsoft.com/kb/940224/) The Optimized Performance Counter Collection rule collects multiple values of 0 (zero) in System Center Operations Manager 2007

941307 (http://support.microsoft.com/kb/941307/) A health monitor may display state changes in an incorrect order in System Center Operations Manager 2007

941943 (http://support.microsoft.com/kb/941943/) The HealthServiceStore.edb file size grows to several gigabytes over time in an agent that is running System Center Operations Manager 2007

942168 (http://support.microsoft.com/kb/942168/) The Health service does not start after you install the RemotelyAnywhere program on the Root Management Server in System Center Operations Manager 2007

946429 (http://support.microsoft.com/kb/946429/) Error message when you try to view the AD Domains topology view in System Center Operations Manager 2007

946431 (http://support.microsoft.com/kb/946431/) You do not see the additional alert criteria that you selected when you view the properties of a subscription in Microsoft System Center Operations Manager 2007

945946 (http://support.microsoft.com/kb/945946/) Event ID 2115 is logged, and a management server generates an "unable to write data to the Data Warehouse" alert in System Center Operations Manager 2007

943211 (http://support.microsoft.com/kb/943211/) You cannot use Active Directory integration for untrusted domains in System Center Operations Manager 2007

941977 (http://support.microsoft.com/kb/941977/) You receive error messages when you try to edit the Web application monitoring settings in System Center Operations Manager 2007

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

941811 (http://support.microsoft.com/kb/941811/) A memory leak occurs if an agent of the release version of Microsoft System Center Operations Manager 2007 reports to System Center Operations Manager 2007 Service Pack 1 management servers

941557 (http://support.microsoft.com/kb/941557/) Management servers that are running the release version of System Center Operations Manager 2007 do not process the agent event data from an agent of System Center Operations Manager 2007 Service Pack 1

Operations Manager 2007 Service Pack 1 fixlist

CliveEastwood — Sat, 23 Feb 2008 03:14:00 GMT

This list will be an the update to http://support.microsoft.com/kb/944443/en-us (List of issues that are fixed in System Center Operations Manager 2007 Service Pack 1 Release Candidate). This article will be updated shortly to reflect the KB articles applying to the original release which are not fixed in SP1. For additional functionality/improvements please also see the What's New section of the Operations Manager Help online (soon to be published to the TechNet TechCenter too) - See OpsMgr2007.chm in the ProductDocumentation folder of the SP1 RTM expanded image.

Items in Red below are KB's awaiting publication (Soon I hope!). Sorry if the images are unclear. (2/24 - All Articles below are now available)

OpsMgr, SCE And MOM Blog : New and upcoming KB Articles

Operations manager 2007 Sp1 / Essentials 2007 SP1 support for windows server 2008 announced

KB951526 (Hotfix) - The Root Management Server (RMS) of System Center Operations Manager 2007 Service Pack 1 becomes unstable or unusable if a management pack is imported

SYMPTOMS

CAUSE

RESOLUTION

Hotfix information

Prerequisites

KB951380 (Hotfix) - Some computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1

SYMPTOMS

RESOLUTION

Hotfix information

Prerequisites

Restart requirement

Hotfix replacement information

KB949969 Some data partition tables that exceed the data retention period are not groomed from the Audit Collection Services database in Operations Manager 2007

SYMPTOMS

CAUSE

RESOLUTION

Hotfix information

Hotfix installation instructions

Post-hotfix behavior

Prerequisites

Restart requirement

Hotfix replacement information

KB950853 - A memory leak occurs when you monitor Exchange Server 2007 by using the MOM 2007 agent in System Center Operations Manager 2007

SYMPTOMS

RESOLUTION

Hotfix information

Hotfix installation information

Prerequisites

Restart requirement

Hotfix replacement information

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

SYMPTOMS

Problem 1

Problem 2

Problem 3

Problem 4

Problem 5

Problem 6

RESOLUTION

New KB Articles – Operations Manager 2007 / MOM 2005

New Opsmgr and Essentials Kb articles

KB942864 (Update) - How to use diagnostic tracing in System Center Operations Manager 2007 and in System Center Essentials 2007

MORE INFORMATION

Tracing tools location

To start tracing

To stop tracing

To convert existing traces to text format in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

Viewing converted trace files in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

Boot time tracing is enabled by default in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

How to disable boot time tracing in System Center Essentials 2007 SP1 and in System Center Operations Manager 2007 SP1

How to move the default location of trace file output in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

How to view real time tracing in System Center Essentials 2007 SP1, in System Center Operations Manager 2007 SP1, and in later versions

New Operations Manager 2007 KB articles

KB946437 - How to disable the use of certificates that are imported by using the MOMCertImport.exe tool in System Center Operations Manager 2007

New Operations Manager KB Articles

KB944443 - List of issues that are fixed in System Center Operations Manager 2007 Service Pack 1

SUMMARY

INTRODUCTION

MORE INFORMATION

List of issues fixed

REFERENCES

More new OpsMgr07 KB articles

Operations Manager 2007 Service Pack 1 fixlist