OpsMgr, SCE And MOM Blog : Hotfix for Operations Manager 2007

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.

New Knowledge Base articles for Operations Manager 2007 / System Center Essentials 2007

CliveEastwood — Fri, 22 Feb 2008 23:32:48 GMT

Finally we have some content released I've been waiting for (better late than never). The KB article 944443 (List of issues that are fixed in System Center Operations Manager 2007 Service Pack 1 Release Candidate) will be updated shortly (crossing my fingers - not under my control) to reflect the list of changes in Service Pack 1 RTM. I'll post the fixlist separately as SP1 will likely hit the Web before the article gets re-published (not my fault, honest). (Yes, SP1 RTM is close, very close!)

KB948069 - Error message when you try to run reports in System Center Operations Manager 2007: "Cannot open Database 'OperationsManagerDW' requested by the login" - http://support.microsoft.com/kb/948069

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

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

KB938507 - 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 - http://support.microsoft.com/kb/938507

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

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

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

KB943706 - The MonitoringHost.exe process on the System Center Operations Manager 2007 root management server may consume more than 2 gigabytes of memory

CliveEastwood — Tue, 27 Nov 2007 01:15:13 GMT

New KB for OpsMgr07 http://support.microsoft.com/kb/943706 . This fix is included in the SP1 Release Candidate.

Updated Operations Manager MP's released to the Web - Windows Server 2000/2003 OS (6.0.5000.25) And DHCP (6.0.5000.33) MP

CliveEastwood — Mon, 01 Oct 2007 22:10:58 GMT

The following two Management packs have been updated:

Windows 2000/2003 http://www.microsoft.com/downloads/details.aspx?FamilyID=3529d233-5e3e-4b51-8f66-5d6f27005ec3&DisplayLang=en updated from 6.0.5000.0 to 6.0.5000.25

Issues that have been fixed

Monitor "Network Adapter Connection Health" is non-functional, looking for attribute that could be truncated: network adapter description is too large, multiple network adapters have the same description, enhanced monitoring of network adapter
Localizaton Issues: script or executable failed to run on the agent machine with Hungarian local, script or executable failed to run on the agent machine with French local

DHCP 2000/2003 MP http://www.microsoft.com/downloads/details.aspx?FamilyID=2694e87c-76e0-417b-ad0f-5897e46fff88&DisplayLang=en updated from 6.0.5000.0 to 6.0.5000.33

Issues that have been fixed

Backward Compatibility Script Error in ‘DHCP Server 2000 Scope Monitoring’ VBScript

Specifically

An error occurred on line 470 while executing script 'DHCP Server 2000 - Scope Monitoring' Source: Microsoft VBScript runtime error Description: Invalid procedure call or argument One or more workflows were affected by this. Workflow name: DHCP_Scope_Monitoring_1_Rule Instance name: Microsoft.Windows.Server.DHCP.Microsoft_Windows_2000_DHCP_Servers_Installation Instance ID: {F5EEB8EE-1C9F-DE78-9B38-46AE0B83B81D} Management group XXX

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

CliveEastwood — Fri, 31 Aug 2007 07:08:43 GMT

KB936838 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 has been released http://support.microsoft.com/kb/936838/en-us

This discusses an issue when an Operations Manager 2007 agent is multihomed to multiple management groups and failing to send discovery data, therefore unable to receive rules from that management group. A hotfix is available to correct this issue.

The hotfix may be requested via online submission via http://support.microsoft.com/kb/937470/en-us

KB937470 - A notification subscription's Alert Criteria options do not work as expected in System Center Operations Manager 2007

CliveEastwood — Fri, 31 Aug 2007 06:58:00 GMT

KB937470A notification subscription's Alert Criteria options do not work as expected in System Center Operations Manager 2007 has released http://support.microsoft.com/kb/937470/en-us

This article discusses a problem with the notification subscriptions alert criteria dialog in the UI and an available hotfix.

The hotfix may be requested via online submission via http://support.microsoft.com/kb/937470/en-us

KB939585 - Some SSL Monitoring monitors display an incorrect status or an incorrect name in System Center Operations Manager 2007

CliveEastwood — Fri, 24 Aug 2007 21:53:15 GMT

KB939585 Some SSL Monitoring monitors display an incorrect status or an incorrect name in System Center Operations Manager 2007 has been release and is available via http://support.microsoft.com/kb/939585/en-us

A hotfix is available if you are seeing the following symptoms :

SYMPTOMS

In Microsoft System Center Operations Manager 2007, you experience the following symptoms if you use the Web Application management pack template to monitor a Web site that is secured by using the Secure Socket Layer (SSL) protocol:

• The SSL Certificate Expired monitor displays a healthy status even if the certificate that the Web site uses has expired.

• The Certificate CN Invalid monitor displays a healthy status even if a common name of the certificate is not valid.

• In Health Explorer, Certificate CN Invalid incorrectly appears as the display name for the Untrusted CA monitor. In this situation, two Certificate CN Invalid monitors appear under the SSL Monitoring node. However, one of these monitors displays a description for the Untrusted CA monitor.

As discussed in the article the hotfix may be requested via online submission via http://go.microsoft.com/?linkid=6294451

KB938505 - Some report information does not appear in Japanese in the Japanese version of System Center Operations Manager 2007

CliveEastwood — Fri, 24 Aug 2007 03:19:12 GMT

KB938505 - Some report information does not appear in Japanese in the Japanese version of System Center Operations Manager 2007 has released and is available via http://support.microsoft.com/kb/938505/en-us

This discusses a hotfix available to the Japanese localized version of Operations Manager 2007. This hotfix may be requested by the Web form http://go.microsoft.com/?linkid=6294451

KB935896 -When the Health Service (HealthService.exe) runs timed scripts in System Center Operations Manager 2007, high memory usage may occur

CliveEastwood — Fri, 24 Aug 2007 03:13:29 GMT

KB935896 When the Health Service (HealthService.exe) runs timed scripts in System Center Operations Manager 2007, high memory usage may occur has release and is available via http://support.microsoft.com/kb/935896/en-us

This discusses a memory leak which can occur when running timed scripts within converted management packs (ie. utilizing the backward compatibility module). A hotfix is available for this issue. Although the KB article has not been updated to state the hotfix is available by Web submission, you can request the hotfix using the following web form http://go.microsoft.com/?linkid=6294451

KB939799 - The System Center Operations Manager 2007 agent is unable to restart the health service after its monitored thresholds are breached

CliveEastwood — Mon, 20 Aug 2007 07:51:15 GMT

KB939799 has been published discussing the problem with Private Bytes threshhold and Handle Count threshold ovrride issues (override is not applied correctly). A hotfix for this issue is now available which corrects this issue together with Healthservice restart issues which is a response to these rules which can fail to successfully restart the healthservice. For further information see the KB article here: http://support.microsoft.com/kb/939799/en-us

This article currently does not contain the link for online requests of the associated hotfix. However you may request the hotfix via online submission via this link http://go.microsoft.com/?linkid=6294451

SYMPTOMS

The Microsoft System Center Operations Manager 2007 agent monitors its processes to make sure that they do not consume too many system resources. When one of its processes does consume too many system resources, the agent tries to restart itself.
You may encounter one of the four symptoms that are mentioned in this section. These symptoms occur on the agent side if the following conditions are true:

•
The following processes are being monitored on the agent side:

•
HealthService.exe

•
MonitoringHost.exe

•
The following performance counters are being monitored for the processes that are mentioned in bullet point 1:

•
Process\Private Bytes

•
Process\Handle Count

Symptom 1

The health service shuts down successfully. However, the health service does not start successfully after its monitored thresholds are breached. When this occurs, one of the following events may be logged in the Application event log:

Event Type: Warning
Event Source: Health Service Script
Event Category: None
Event ID: 6026
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description: RestartHealthService.js : Restarting Health Service. Monitoring Host exceeded Process\Private Bytes threshhold.

Event Type: Warning
Event Source: Health Service Script
Event Category: None
Event ID: 6024
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description: RestartHealthService.js : Restarting Health Service. HealthService.exe exceeded Process\Handle Count or Process\Private Bytes exceeded threshold.

Event Type: Warning
Event Source: Health Service Script
Event Category: None
Event ID: 6025
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description: RestartHealthService.js : Restarting Health Service. MonitoringHost.exe exceeded Process\Handle Count threshold.

Symptom 2

The health service only restarts one time on Microsoft Windows 2000 agents if the thresholds of both monitors are configured to use a very low value. The expected behavior is that the health service repeatedly restarts.

Symptom 3

The health service on the agent restarts repeatedly if the following conditions are true:

•
Multiple management groups monitor this agent.

•
The monitored thresholds are breached.

Symptom 4

The overridden values for certain rules are not displayed in the Override properties dialog box. These rules are used to monitor the processes that are mentioned in this section.

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 System Center 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.

Prerequisites

No prerequisites are required.

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.

Hotfix installation instructions

This hotfix must be applied to each Systems Center Operations Manager 2007 Management Server-based computer.
To apply this hotfix, follow these steps:

1.
Copy the following file to a local folder or to a network shared folder:

SYSTEMCENTEROPERATIONS2007-RTM-KB939799-X86-X64-ENU.MSI

2.
Run the file that is mentioned in step 1 on each applicable computer.
Note You can run the file that is mentioned in step 1 from Windows Explorer, or you can run the file at a command prompt.

3.
Import the following management packs. If you use the Operations Console to import the management packs, they are imported in the correct order. If you import the management packs by using the command line or if you have problems when you use the Operations Console to import the management packs, import them in the following order:

a.
Microsoft.SystemCenter.Library.mp

b.
Microsoft.SystemCenter.2007.mp

Note The management packs will be extracted to the following folder:

%systemdrive%\ProgramFiles\System Center Management Packs\Microsoft System Center 2007 MP\

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.

System Center Operations Manager 2007, x86-based versions

File name
File version
File size
Date
Time
Platform

Microsoft.systemcenter.2007.mp
6.0.5000.20
122,880
29-Jun-2007
07:48
Not Applicable

Microsoft.systemcenter.library.mp
6.0.5000.20
241,664
29-Jun-2007
07:48
Not 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, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (http://support.microsoft.com/kb/824684/) Description of the standard terminology that is used to describe Microsoft software updates

KB935898 - 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"

CliveEastwood — Mon, 20 Aug 2007 07:32:23 GMT

KB935898 has now been published which refers to a hotfix available for the Web Console. Details here : http://support.microsoft.com/kb/935898/en-us

Note: http://go.microsoft.com/?linkid=6294451

Check out the link for online requests for this hotfix http://go.microsoft.com/?linkid=6294451 . You can now request the hotfix link be delivered by email by completing a simple web form.

SYMPTOMS

The Microsoft System Center Operations Manager 2007 Web Console raises an exception when you try to access a Web page view on the Monitoring page or on the My Workspace page. When this problem occurs, you receive the following error message in the Web Console:

Requested value 'UrlViewType' was not found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: Requested value 'UrlViewType' was not found.

This problem occurs because the URL view type is not supported in the System Center Operations Manager 2007 Web Console.

RESOLUTION

To resolve this problem, apply this hotfix on each computer that hosts the System Center Operations Manager 2007 Web Console.

Hotfix information

A supported hotfix is now 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 System Center Operations Manager 2007 service pack that contains this hotfix.
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)

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

System Center Operations Manager 2007, x86-based version

File name
File version
File size
Date
Time
Platform

microsoft.enterprisemanagement.operationsmanager.dataabstractionlayer.dll
6.0.5000.4
176,128
05-
17:09
x86

System Center Operations Manager 2007, x64-based version

File name
File version
File size
Date
Time
Platform

microsoft.enterprisemanagement.operationsmanager.dataabstractionlayer.dll
6.0.5000.4
176,128
06-
12:47
x86

momperfsnapshothelper.exe
6.0.5000.0
47,104
06-
12:46
x64

momperfsnapshothelperproxy.dll
6.0.5000.0
11,776
06-
12:46
x64

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 (http://support.microsoft.com/kb/824684/LN/) Description of the standard terminology that is used to describe Microsoft software updates

KB939364 - System Center Operations Manager 2007 cannot find some network devices by using the network device discovery process

CliveEastwood — Fri, 27 Jul 2007 18:54:32 GMT

The following KB article has been released http://support.microsoft.com/kb/939364/en-us documenting support for SNMPv1 device discovery with a new hotfix

SYMPTOMS

Microsoft System Center Operations Manager 2007 cannot find some network devices by using the network device discovery process. Therefore, you cannot manage these network devices in Operations Manager 2007.
This problem occurs even though the network devices respond to the "GET" packets that the Snmputil.exe tool sends.

CAUSE

This problem occurs because Operations Manager 2007 supports only version 2 of the SNMP protocol (SNMPv2). Devices that do not support SNMPv2 ignore the "GET" packets that Operations Manager sends. Therefore, the network device discovery process cannot detect these devices. For example, this situation occurs when the devices support only version 1 of the SNMP protocol (SNMPv1) or version 3 of the SNMP protocol (SNMPv3).
The Snmputil.exe tool uses both SNMPv1 and SNMPv2. These devices respond to the "GET" packets that the Snmputil.exe tool sends even if the devices support only SNMPv1.

RESOLUTION

To resolve this problem, apply the following hotfix. To do this, follow the steps in the "Hotfix installation instructions" section.
After you apply this hotfix, a new Simple Network Management Protocol (SNMP) Community version list appears in the network device discovery wizard. This list contains an SNMP v1 item and an SNMP v2 item. If you select SNMP v1 from the list, the network device discovery wizard uses SNMPv1 to detect network devices.

Hotfix information

A supported hotfix is now 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 System Center Operations Manager Service Pack 1 that contains this hotfix.
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)

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