# Microsoft® Operations Manager (MOM) 2005 Service Pack 1 Release Notes

Last Updated: 07/01/2005

> ##### Important - Please read these release notes thoroughly before installing the MOM software or importing and using Management Packs.

## Documentation Roadmap and Additional Resources

### Documentation

You can find documentation for this release of MOM on the product CD and on the Microsoft Operations Manager Web site. Table 1 summarizes the type and location of the available documentation.

Table 1 MOM 2005 Documentation

Document | Location | Description
--- | --- | ---
RelNotes.htm | On the MOM product CD in the "...CDImage" folder for the product. | The release notes, which document the known issues at the time the MOM product CD was created.
AgentInstall.htm | On the MOM product CD in the "RelDocs" folder. | Instructions for manually installing MOM agents.
Install.htm | On the MOM product CD in the "RelDocs" folder. | Instructions for installing or upgrading to MOM 2005 SP1 in an environment of less than 200 managed computers in a single domain.
SupConfig.htm | On the MOM product CD in the "RelDocs" folder. | Information about the supported operating systems, hardware requirements, software requirements, installation combinations, and security configurations for MOM.
DataSheetRoadmap.htm | On the MOM product CD in the "RelDocs" folder. | Placeholder, not used.
Readme_WorkGroupEdition.htm | On the MOM product CD in the "...CDImage" folder for the Workgroup Edition of the product. | This document contains supplemental information that is specific to Microsoft Operations Manager 2005 Workgroup Edition SP1.
User Guides | On the Web at MOM 2005 Product Documentation. | This collection of documentation includes the following: Planning and Deployment Administration Security Management Pack Guides
Product Overview | On the Microsoft Operations Manager 2005 Product Overview. | This page includes links to the following: A demonstration of MOM 2005 An overview of Workgroup Edition MOM 2005 FAQ MOM 2005 Datasheet
MOM 2005 Solution Accelerators | On the MOM 2005 Web site. | This collection of solutions delivers additional benefits for Windows Server System environments that are managed by MOM 2005. Click the Solution Accelerators link in Related Products and Solutions to learn more about these solutions.

### Additional Resources

For general information about MOM, visit the Microsoft Operations Manager Web site. Additional documentation for this release of MOM can be found on the MOM Web Site.

Note - These documents might not be scheduled for release at the same time as the MOM product CD.

Contact Microsoft Product Support Services with specific questions.

## About this Service Pack

This service pack resolves several known issues with MOM 2005 and MOM 2005 Management Packs. This service pack:

- Incorporates all the fixes listed in Table 2.
- Addresses several Management Pack issues, which are summarized in Table 3.

Table 2 MOM 2005 SP1 Fixes

Knowledge Base Number | Title
--- | ---
883925 | The W3wp.exe process causes 100% CPU utilization on Management Servers in MOM 2005.
885416 | MOM 2005 agent logs an "existing connection was forcibly closed by the remote host" event.
885839 | The MOM 2005 Administrator Console crashes if you try to expand the the "Exchange 2000" rule group node in the Microsoft Operations Manager (MOM) 2005 Administrator console.
885841 | When you import a Management Pack in Microsoft Operations Manager MOM 2005, you may lose information that is contained in other Management Packs that reside in the same rule group.
887180 | A MOM 2000 SP1 hotfix (830595) introduces an unacceptable memory leak on Windows Server 2003 DCAM.
888304 | You receive a "Column 'IdComputer' does not belong to table" error message or a "Column 'IdTargetClass' does not belong to table" error message when you change regional and language options from English to Turkish on a computer that is running MOM 2005.
889017 | You receive an exception error when the MCF tries to insert alerts in MOM 2005, or event ID 10042 is written to the Application log when you use the MMPC.
889071 | Microsoft Operations Manager 2005 agent alerts are not processed when the Ignore Missing Heartbeats option is enabled.
889187 | MOM 2005 does not support NetBIOS domain names containing a period (.). The computer group is blank on any MOM agent (include the MOM server), and the attributes discovery seems not working.
890948 | "Generic failure" error message when you run a custom script that uses the UpdateContactTime method of the MSFT_Computer WMI class in Microsoft Operations Manager 2005.
| 891200 | The Operator Console State view shows a critical computer that has no alerts
891641 | The GetParentRuleGroup method does not return the correct rule group objects in Microsoft Operations Manager 2005.
891709 | The Microsoft Operations Manager Web console stops responding if the user belongs to many Active Directory user groups.
892096 | In a multiple tier deployment that uses MOM and HP Openview, the regional update to the alert occurs before the HP Openview reads the alert. As a result, the resolution state is overwritten and the alert is not forwarded.
892140 | Alerts that are in an inactive state on a source Microsoft Operations Manager 2005 Management Server appear as active on the destination Management Server.
892307 | The Application Log Provider may unexpectedly quit, and event 25257 is logged when the provider parses an IIS log file that contains Asian characters in MOM 2005.
894319 | In multiple tier environment there are missing alerts on the destination management group because alerts are erroneously suppressed into other alerts on the management group.
894464 | Provide version of the SetActionAccount utility that will allow you to supply the password via command-line instead of prompting during the installation.
895142 | In Microsoft Operations Manager (MOM) 2005, when you put a MOM agent in maintenance mode, responses may not immediately stop running on the Management Server. Additionally, when you remove an agent from maintenance mode, responses may not immediately start running on the Management Server.
895195 | You receive an "Access is denied" error message when you use the Install Agent Wizard in Microsoft Operations Manager 2005.
895324 | The Operator Console fails and displays the "MOM.UI.OPSCONSOLE.EXE.EXE - Common language runtime debugging services Application has generated an exception that cannot be handled" application exception message.
895951 | You receive an "UnauthorizedAccessException" error message when the MOM-to-MOM Product Connector tries to forward alert and discovery information in Microsoft Operations Manager 2005.
896861 | You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6.
896989 | You receive a "0x800706be" error message when you try to view the Computer Groups container in the MOM 2005 Administrator Console.
898466 | The override rule is not functioning dependably.
898921 | Issues that you may experience after you install MOM 2005 on a computer that is running Windows Server 2003 with SP1.
Fixed | Visual indicators in the Alerts view do not accurately reflect a computer's state when it is in maintenance mode.
Fixed | MOM licensing information is provided in MOM Reporting, but there is no way for customers to monitor license compliance. This service pack enables you to record the number of licenses acquired by providing this number during setup or by editing the Licenses global setting. The MOM Management Pack has a rule that warns when there is a possible non-compliance issue with licenses. See also: Table 3.

Table 3 MOM 2005 SP1 Management Pack Issues and Fixes

Management Pack | Title | Description
--- | --- | ---
Microsoft Business Security Analyzer (MBSA) | The English version of MBSA is installed on non-English builds of Windows | Prior to MOM 2005 SP1, the MBSASetupFile parameter of the "MBSA Install and Run" script incorrectly listed “MBSASetup-en.msi” as its value. This caused the installation of the English version of MBSA on non-English builds of Windows. The value for the parameter has been corrected, and the appropriate language version of MBSA will be installed on non-English builds of Windows.
Microsoft Operations Manager 2005 (MOM 2005) | The "MOM Database State Monitoring" and "MOM Agent Service Discovery" scripts might generate script errors | In some environments, the "MOM Agent Service Discovery" script might generate an error on line 14 and the "MOM Database State Monitoring" might generate an error on line 1252. Both of these script errors are fixed in this service pack.
| New authentication and MOM to MOM Product Connector related rules added to MOM 2005 SP | Two rules have been added to enable the detection of mutual authentication problems that affect Operations Manager Server and/or Agent communications. The new rules include "MOM Management Server mutual authentication problems", "MOM Management Server mutual authentication problems", "MMPC error forwarding a new invalid alert", and "MMPC error forwarding an invalid alert update".
| An alert might occur when computer discovery takes longer than 5 minutes | The alert “A script hung or exceeded its specified timeout” might incorrectly occur when computer discovery takes longer than five minutes. The rule has been updated for MOM 2005 SP1 to prevent an alert when this condition exists.
| There is no way to monitor MOM licensing compliance other than MOM Reporting | A new rule compares the number of managed computers against the value in the Licenses global setting. An alert is generated if there is a potential licensing non-compliance issue.
Microsoft SQL Server 2000 | The rule “A SQL job failed to complete successfully” doesn’t work on French versions of SQL Server 2000 | The criteria for the rule “A SQL job failed to complete successfully” is incorrect and fails to generate alerts when a job failure occurs on a French version of SQL Server 2000. The criteria for the rule has been fixed in this service pack.
| The threshold for the SQL Server 2000 Space Analysis script is ignored | The “SQL Server 2000 Space Analysis” script that is used by the “SQL Server Space Analysis” rule incorrectly ignores the value set for “TempLogErrorLevel” script parameter. The script is fixed, and MOM 2005 SP1 can use the script parameter correctly.
| The "Disk Read and Write Latency" view doesn’t list any counters | The criteria for the "Disk Read and Write Latency" view is incorrect, and as a result. none of the PhysicalDisk Counter instances are displayed. The view criteria is fixed in this service pack.
| Some reports fail when run on systems with non-US English regional settings | The "User Connections by Day" and "User Connections by Peak Hour" reports fail when run on a computer configured with non-US English regional settings. These reports are fixed and will run on systems that are running supported regional settings configurations for MOM 2005 SP1.
Microsoft Windows Server Base OS | The Operating System Storage Configuration might fail when attempting to sort columns | The Operating System Storage Configuration might fail when attempting to sort by the “Volume Name”, “Drive Free Space GB”, or “Drive Size GB” columns. The report is fixed in this service pack, and sorting by these columns works correctly.
| Used and Free space columns are missing from the Operating System Storage Configuration report | The “Used Space (GB)” and “Free Space (GB)” columns are missing in the Operating System Storage Configuration report. These columns have been added to the report for MOM 2005 SP1.
| The Memory Utilization rule might incorrectly generate alerts on Exchange Servers | Due to advanced memory management capabilities that enable Exchange Servers to utilize virtually all system memory, the “Performance Threshold Memory\Available Mbytes threshold exceeded” rule was designed with special consideration for Exchange Servers. The routine that enabled special handling for Exchange Servers does not work as expected and might incorrectly generate alerts on Exchange Servers. The relevant routines are fixed in this service pack, and the rule works as intended.
| The Microsoft Windows Storage State Monitoring script does not use the "MegaByteFreeSpaceThreshold" parameter | The “MegaByteFreeSpaceThreshold” parameter of the Microsoft Windows Storage State Monitoring script was designed to enable customers to generate alerts when any drive on the system reached a megabyte- based threshold value (for example, < 100 MB). In MOM 2005 SP1, this parameter is removed from the script because similar functionality can be implemented by using a combination of other script parameters. To generate megabyte-based thresholds, it is recommended that all percentage-based script parameters (for example, NonSystemDriveFreeSpacePercentageRed) be set to 100. It is recommended that megabyte-related script parameters (for example, NonSystemDriveFreeSpaceMegaByteRed) be set to the desired threshold value.
Microsoft Windows Internet Information Services (IIS) | IP addresses get blocked without warning | The rule “Security: Error 403: Forbidden Error - Alert” automatically blocks an IP address when 100 instances of a 403 event are generated by requests that come from the same IP address. Because the decision to block a specific IP address cannot be made without further investigation, the IP blocking response is removed for MOM 2005 SP1.
| Some reports fail when running on a computer with non-US English regional settings | The "Count of HTTP 500 Errors by Day" and "Count of HTTP 400 Errors by Day" fail when run on a computer configured with non-US English regional settings. These reports are fixed and will run on systems using supported regional settings for MOM 2005 SP1.

## Table of Contents

## Setup And Upgrade

- MOM 2005 Agent Cannot Co-Exist with NetIQ Security Manager 5.0 Agent
- Exchange 2000 Management Pack Error During Agent Setup
- How To Uninstall Management Servers After The MOM Database Has been Uninstalled
- MOM Setup Might Fail On Server Upgraded to Windows Server 2003
- Must Re-Add User to COM+ Roles After Upgrade to Windows Server 2003
- Installing Manual Agent on 64-bit Computer
- Prerequisite Checker Gives False Negative When Run on Non-Primary Node
- Password Or Username Field on Some Dialogs Shorter or Longer Than Windows Maximum Length for Passwords
- "The service is marked for deletion" Error During Agent Setup or Upgrade
- Registry Keys Remain After Uninstalling And Reinstalling the MOM Administrator Console
- MOM Server Setup Begins to Roll-Back When It Cannot Connect to MOM Database Due to Network Problems
- Cannot Upgrade from Unsupported MOM 2000 SP1 Configurations of Stand Alone Web Console or Separated DAS and CAM
- MOM Reporting Setup Requires Computer Name For MOM Database Server Instance
- MOM 2005 Reporting Setup Fails If SSL Is Enabled On SQL Reporting Services
- Upgrade Fails If Using A Very Long Directory Name - Error Code: -2147024774
- Installing MOM Using Non ASCII Path
- Cannot Install MOM 2005 Reporting if Default Web Site on Reporting Services Server or ReportServer Services Is Stopped
- MOM Cannot Be Installed on a Passive Node
- Silent Agent Install Requires MPHelper Objects Install
- Removing Agent From MOM Database Installed By MOMCreateDB.exe Removes MOM Registry Hive
- Event 21081 After Upgrade From MOM 2000 SP1 With ManualMC.txt
- Installing MOM Reporting Database on 64-Bit Computer
- "There was an error accessing the SQL Server Reporting Services Server through WMI" Error During Reporting Setup
- Prerequisite Checker Says "ASP is not enabled"
- "The remote MOM database must be a valid MOM database" Error During Management Server or UI Uninstall
- Setup Fails - SetLicenseInformation Error In Setup Log
- MOMCreateDB.Exe: No Log is Presented When Setup Fails
- Push-Install Agent to ISA Server 2004 Fails with "RPC Server Unavailable" Error
- Setup Fails With "Failed to create MOM DAS COM+ Components" Error
- Upgrade Fails When Using a Non-Default Agent Data Directory
- Changing Windows Installer Default Settings Might Cause MOM Setup to Fail
- Setup Fails With "Account verification" Error
- MOM Reporting Setup Fails With an Exception
- "Service could not be started" Dialog During Management Server Setup
- Upgrade Might Fail if Less Than 50% Free Space in OnePoint Database
- [NEW] "The Management Server Could Not Be Contacted" Message Appears when Installing a MOM 2005 Agent for a MOM 2005 SP1 Management Server
- [NEW] After a Manual Agent Installation is Rejected, Subsequent Manual Installations of the Same Agent Do Not Appear in the Administrator Console's Pending Actions View
- [NEW] Known Issues Related to Running MOM Components on a 64-bit Computer
- [NEW] MOM 2005 Reporting Installation Error When Installing on Windows Server 2003 SP1
- [NEW] MOM 2005 SP1 Update Behavior When MOM 2005 Agents are in Pending Uninstall Mode
- [NEW] Installing the MOM 2005 SP1 Update on a MOM Management Server that Already Has an Agent Installed Will Cause a Management Server Failure
- [NEW] In a Multiple Tier Configuration that Uses Alert Forwarding, Alerts May Not Be Forwarded to the Destination Management Group After MOM 2005 SP1 is Installed on the Destination Management Server
- [NEW] Warning Events 1004 and 1001 are Generated by the MsiInstaller When an Agent is Upgraded to MOM 2005 SP1
- [NEW] Agent Installer Log Files are Not Copied to the MOM Server After a Push Install Fails
- [NEW] A Custom Application May Not Work if it References a MOM Assembly That Was Patched Prior to MOM 2005 SP1 with a QFE
- [NEW] In Some Cases, the Prerequisite Checker May Generate an ASP.NET Error Even if ASP.NET is Installed and Running
- [NEW] In a SQL Server Cluster, the Prerequisite Checker Works Only on the Active Node of the Cluster
- [NEW] Specific Steps are Required When Installing the MOM 2005 SP1 Update on a SQL Server Cluster or Special Database Configuration
- [NEW] If the MCF Assembly is Loaded During an Upgrade from MOM 2005 RTM to MOM 2005 SP1, the Installation will be Interrupted and an Error Message is Displayed
- [NEW] When Installing MOM Reporting, You Might Get an "Error 401:Unauthorized error while creating datasource" Message and the Reporting Installation Will Fail.

## Management Packs

- Pre-Filter Rules Not Supported in Versions After MOM 2005
- Microsoft Active Directory Management Pack Installation Might Not Update OOMADS.DLL
- Remove Active Directory Management Pack Helper Objects Before Removing MOM Agent
- Duplicated and Non-Functional Views After Upgrading IIS Management Pack
- Record Notification Group Changes Before Re-Import or Upgrade to Management Pack
- SQL Server Replication Monitoring May Not Work As Expected
- Override Setting Does Not Work For Collection Rules
- Check for Updated Management Packs on the MOM Web Site
- Additional Information About Management Packs Available in Management Pack Guides
- Active Directory Management Pack Script Might not Work Properly on a Manually-Installed Agent
- "Download mssecure.cab from http://www.microsoft.com" Task Should Be Run Only From A File Transfer Server
- "AD Replication Connection Objects" Report Failing
- Upgrading Base Operating System or DNS Management Pack Will Remove Existing Rules and Groups
- Upgrading Custom Rules with MOM 2000 SP1 Attributes Might Break Computer Groups
- [NEW] Computers that Were Manually Added to a Computer Group’s Include and Exclude Lists Remain in the Lists After an Associated Product is Upgraded

## Security

- "Reject Manually Installed Agents" Setting Requires Mutual Authentication
- Password Field on Some Dialogs Shorter or Longer Than Windows Maximum Length for Passwords
- File Transfer Failing with "Access Denied" Error
- Cannot Remove SC DW DTS Group - "Unknown Active Directory object" Error

## Reporting

- "Agent Uptime by Computer" Report Does Not Return Correct Information On An IA64 Computer
- How To Remove Reports After Upgrading MOM Reporting From Beta 3 or the Release Candidate
- DTS Job Times Out With "System.Data.SqlClient.SqlException" Event
- Date Format is Always UE English Regardless of Browser Settings
- [NEW] New Parameters Have Been Added for Running the DTS Job from the Command Line

## Operator Console

- Some Tasks or Functions Not Working After Removing Agent From Consoles-Only Computer

## Administrator Console

- Importing MOM 2000 SP1 Licenses Does Not Work
- "Recursive reference chain" Error When Creating Computer Groups
- Some Tasks or Functions Not Working After Removing Agent From Consoles-Only Computer
- Performance Recommendation: Change Rule Change Polling For Large-Scale Environments
- Software Updates Might Not Be Applicable in a Multihomed Environment
- [NEW] On MOM 2005, the Administrator Console May Fail After Windows Server 2003 is Upgraded to Service Pack 1
- [NEW] Under Certain Conditions, Manually Installed MOM 2005 Agents Cannot be Updated by a MOM 2005 SP1 Management Server
- [NEW] Multihoming an Existing MOM 2005 SP1 Agent to a MOM 2005 Management Group Does Not Work
- [NEW] Calculating Group Membership May Fail When Using the Administrator Console to Connect to a Different Management Server
- [NEW] To Push Install Agents in MOM 2005 SP1, Windows Installer 3.1 or Later Is Required on the Destination Computers

## Web Console

- Web Console Website Cannot Start
- Need To Grant NETWORK_SERVICE Rights To Run The Web Console On A Windows Server 2003 Domain Controller
- “You are not authorized to view this page” Error when Opening the Web Console

## Product Connector and MOM Connector Framework

- [NEW] Computer Group Membership is Not Complete in the Destination Management Group
- [NEW] Invalid Alert Objects
- [NEW] Concurrent Updates to Alerts

## Accessibility

- Report Contents are not Visible In High-Contrast Mode

## MOM 2005 Workgroup Edition

- Items Left After Upgrade

# Setup and Upgrade

Back to Table of Contents

### MOM 2005 Agent Cannot Co-Exist with NetIQ Security Manager 5.0 Agent

The MOM 2005 agent cannot be installed on a computer that already has a NetIQ Security Manager agent, and visa-versa.

WORKAROUND: None.

Back to Table of Contents

### Exchange 2000 Management Pack Error During Agent Setup

If you get an error during MOM agent or server setup that states "The Microsoft Exchange Messaging and Collaboration Services component is not installed on this Exchange 2000 Server. The installation program may be running on an Exchange 2000 Server administrator-only computer" with event number 10005 and source="MsiInstaller", you can ignore this error. You will get this error every time you install a MOM agent or server on a computer which does not have Exchange 2000 installed.

WORKAROUND: None.

Back to Table of Contents

### How To Uninstall Management Servers After The MOM Database Has been Uninstalled

If you need to uninstall Management Servers after you have already uninstalled the MOM Database, you must use the Remove option in Add or Remove Programs or the Remove option on the Change menu if running MOMServer.MSI.

WORKAROUND: None.

Back to Table of Contents

### MOM Setup Might Fail On Server Upgraded to Windows Server 2003

If you upgrade a server from Windows 2000 to Windows Server 2003 and then attempt to install MOM components on that server, the setup might fail. This is because the MDAC files are not updated during the server upgrade process to version 2.8.

WORKAROUND: Before installing the MOM components, update the MDAC components to version 2.8. The MDAC setup can be obtained from Microsoft Download Center.

Back to Table of Contents

### Must Re-Add User to COM+ Roles After Upgrade to Windows Server 2003

If you install MOM on a computer and then upgrade the operating system from Windows 2000 to Windows Server 2003 the DAS service might not work properly. To fix this problem either uninstall MOM and re-install it (this option is not available if there is a MOM Database on the computer) or re-add the COM+ roles for MOM.

To re-add the MOM COM+ roles:

1. In Component Services, navigate to Computers / My Computer (or <computername>) / COM+ Applications / Microsoft Operations Manager Data Access Server / Roles.
2. For each of the roles, add the computer's local Administrators group as a User.

Note - When selecting to add a new user, the default does not include to search for groups. Choose the Object Types button and select Groups before attempting to add the Administrators.

WORKAROUND: None.

Back to Table of Contents

### Installing Manual Agent on 64-bit Computer

To install a MOM agent on a 64-bit computer you cannot install it from setup.exe, but you must use the MOMAgent.msi from the ia64 directory on the MOM 2005 CD.

WORKAROUND: None.

Back to Table of Contents

### Prerequisite Checker Gives False Negative When Run on Non-Primary Node

If you run the MOM 2005 Prerequisite Checker on a non-primary node in a cluster, the results will be inaccurate. To get accurate results, run the Prerequisite Checker on the Active node.

WORKAROUND: Run the Prerequisite Checker on the primary node.

Back to Table of Contents

### "The service is marked for deletion" Error During Agent Setup or Upgrade

If during agent install or uninstall, while updating agent settings, or during a MOM agent upgrade from the Release Candidate to MOM 2005, setup might fail and you might receive the following error:

> Error Code: -2147023293
> Error Description: Fatal error during installation. Microsoft Installer Error Description: Product: Microsoft Operations Manager 2005 Agent -- Internal Error 25222. -2147023824, The specified service has been marked for deletion. For more information, see Windows Installer log file "C:\Program Files\Microsoft Operations Manager 2005\AgentLogs\<computername>AgentInstall.LOG" on the Management Server.

WORKAROUND: To solve this problem try solution number 1 first and, if it does not work, try solution number 2:

1. From the command line run "sc create MOM binPath= "%Program Files%\Microsoft Operations Manager 2005\MOMService.exe" DisplayName= MOM" then push-install an agent to this computer.
2. If the MOM Service still exists and is in a Disabled state, you must restart the computer to complete setup.

Note - The sc.exe utility is only available on Windows Server 2003. On Windows 2000 you will need to download the Windows 2000 Resource Kit which has the sc.exe utility.

Back to Table of Contents

### Registry Keys Remain After Uninstalling And Reinstalling The MOM Administrator Console

If you uninstall the MOM Administrator console, registry values for HKEY_CURRENT_USER and HKEY_USERS are not removed from the registry. When you reinstall the Administrator console, the consoles will try to connect to the Management Server specified in the residual key values. The following registry keys that are not deleted:

> HKEY_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager
> HKEY_CURRENT_USER\Software\Mission Critical Software
> HKEY_USERS\<SID>\Software\Microsoft\Microsoft Operations Manager

WORKAROUND: Manually delete the registry keys before reinstalling the Administrator console.

Note - You will have to search through all of the user subkeys under the HKEY_USERS hive and manually delete the registry subkey Software\Microsoft\Microsoft Operations Manager.

Back to Table of Contents

### MOM Server Setup Begins to Roll-Back When It Cannot Connect To MOM Database Due to Network Problems

When you attempt to install or upgrade MOM 2005 on a computer that is not connected or has lost connection to the network, or in a Workgroup, setup will begin to roll-back if it cannot connect to the MOM Database. This is normal behavior and if this happens, use the following workaround.

WORKAROUND: Retry setup when the computer can connect, use an account that is a member of the local administrators group to install, or flush the cached credentials before installing. To flush the cached credentials, use ipconfig /flushdns.

Back to Table of Contents

### Cannot Upgrade from Unsupported MOM 2000 SP1 Configurations of Stand Alone Web Console or Separated DAS and CAM

If you attempt to upgrade a computer with a standalone Web console from MOM 2000 SP1 to MOM 2005, setup will fail because the DAS is required. No upgrade path is supported for a DAS only or CAM only computer.
WORKAROUND: Convert the machine to a full MOM 2000 SP1 DCAM, either by uninstalling the standalone DAS or CAM and then reinstalling a full DCAM, or by installing a DCAM alongside the standalone Web console, in order to be in a supported upgrade configuration.

Back to Table of Contents

### MOM Reporting Setup Requires Computer Name For MOM Database Server Instance

When the MOM Reporting setup program prompts for the MOM Database Server Instance, you must provide the Computer Name of the computer where the MOM database is installed. Using an alias will cause setup to fail.
WORKAROUND: Enter the actual computer name.

Back to Table of Contents

### MOM 2005 Reporting Setup Fails If SSL Is Enabled On SQL Reporting Services

MOM 2005 Reporting setup will fail, and SQL Server Reporting Services will not function properly, if you enable SSL on the IIS Default Web Site after installing SQL Server Reporting Services. To prevent this problem, always enable SSL on the IIS Default Web Site before installing SQL Server Reporting Services.
WORKAROUND - If you have enabled SSL the on the Default Web Site after installing SQL Server Reporting Services you can fix resulting problems by following these steps:

1. On the MOM 2005 Reporting Server, change the configuration file: %SYSTEMDRIVE%\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.Config. Change the value for "SecureConnectionLevel" to 0.
2. Install MOM 2005 Reporting.
3. On the MOM 2005 Reporting Server, change the configuration file: %SYSTEMDRIVE%\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.Config. Change the value for "SecureConnectionLevel" to 3.
4. Open SQL Server Enterprise Manager and navigate to the OnePoint database. In the navigation pane, click Tables.
5. In the details pane, locate the ReportingSettings table.
6. Edit the ReportingSettings table and change the URLs from http:// to https://
7. Restart the ReportServer service.

Back to Table of Contents

### Upgrade Fails If Using A Very Long Directory Name - Error Code: -2147024774

If you attempt to upgrade from MOM 2000 SP1 and you specify an install directory with a very long name (approximately 200 character or more) the upgrade will fail and the SP1 installation will be left in a partially uninstalled state.
WORKAROUND Do not specify a very long install directory when upgrading.

Back to Table of Contents

### Installing MOM Using Non ASCII Path

MOM setup will fail if you use non-ASCII characters in the installation path and the Windows system locale is not set to the language you are using.
WORKAROUND: Either use only ASCII characters in the installation path, or switch Windows to the appropriate system locale and run setup again.

Back to Table of Contents

### Cannot Install MOM 2005 Reporting if Default Web Site on Reporting Services Server or ReportServer Services Is Stopped

To install MOM 2005 Reporting you must make sure that SQL Server Reporting Services is running and the that Internet Information Services Default Web Site is also running.
WORKAROUND: None.

Back to Table of Contents

### MOM Cannot Be Installed on a Passive Node

The Passive node of a Windows Server Cluster checkbox on the SQL Server Database Instance page of the MOM 2005 setup wizard might be misunderstood to mean that you can install MOM on a passive (non-active) cluster node. MOM cannot be installed on a passive cluster node. To perform the MOM install, each node must be made the active node of the cluster before running setup on that node. This checkbox is used to indicate if the computer you are running setup on is a secondary cluster node, meaning the MOM Database has been installed previously on another cluster node.
WORKAROUND: None.

Back to Table of Contents

### Silent Agent Install Requires MPHelper Objects Install

If you do a silent agent installation, the Active Directory Management Pack Helper Objects and Exchange 2000 Management Pack Helper Objects will not install automatically. If the Active Directory Management Pack has been deployed, the OOMADS.msi located in the support tools folder will also need to be installed on the manual agent machine. If the Exchange Management Pack has been deployed and the manual agent resides on an Exchange 2000 server, the ExchMPObj.msi located in the support tools folder on the MOM CD will also need to be installed.
WORKAROUND: None.

Back to Table of Contents

### Removing Agent From MOM Database Installed By MOMCreateDB.exe Removes MOM Registry Hive

If you remove a MOM agent from a MOM Database Server where the MOM Database was installed using the MOMCreateDB.exe, the agent removal will remove the registry keys for the MOM Database under HKLM\Software\Microsoft\Microsoft Operations Manager. MOM Reporting will not be able to installed on this instance until the issue is fixed.
WORKAROUND: Re-install the agent.

Back to Table of Contents

### Event 21081 After Upgrade From MOM 2000 SP1 With ManualMC.txt

If you upgrade a MOM 2000 SP1 DCAM to a MOM 2005 Management Server and you first delete all the Managed Computer Rules (MCRs) and you have a ManualMC.txt file with at least one entry in it, you might receive event 21081 during the upgrade process. If you do, you must create a rule for each Management Server in the management group.
WORKAROUND: Create a rule for the Management Server(s) as follows:

> Rule Type: Include
> Domain Name: <MOM Server's Domain Name has to be specified>
> Computer Name: Contains Substring <Management Server Name>
> Computer Type: Servers and Clients
> Initial Management Mode: Agent-Managed

Note - the rule must be a "Contains Substring" rule and not a "Equals" rule.

Back to Table of Contents

### Installing MOM Reporting Database on 64-Bit Computer

To install MOM 2005 Reporting Database on a 64-bit computer, you must run msiexec from the command line. The command syntax is as follows, fill in the parameters in <parameter>:

> <InstallationDrive>:\>msiexec /i <PathToMOMReportingMSI.exe>:\momreporting.msi /qb /l*v repsetup.log

> DB_SIZE="1000"

> SQLSVR_INSTANCE="<SqlServerInstanceName>"

> TASK_USER_ACCOUNT="<UserName1>"

> TASK_USER_PASSWORD="<Password1>"

> TASK_USER_DOMAIN="<DomainName1>"

> REPORTING_USER="<UserName2>"

> REPORTING_PASSWORD="<Password2>"

> REPORTING_DOMAIN="<DomainName2>"

> MOM_DB_SERVER="<MOMDatabaseServerName\Instance>"

> ALLUSERS=1

> PREREQ_COMPLETED=1

> AUTOMATICALLY_DETECT_ROSETTA_VDIRS=0

> REPORT_SERVER_VDIR=ReportServer

> REPORT_MANAGER_VDIR=Reports

> ROSETTA_SERVER="<SQLServerReporitngServicesServerName>"

> - DB_SIZE represents the size of the database which contains the data and log files. The log file will be automatically sized to be a percentage of the data file.
> - UserName1, Password1, and DomainName1 refer to the user account used for the DTS job that transfers data from the MOM Database to the MOM Reporting Database.
> - UserName2, Password2, and DomainName2 refer to the user account used for the MOM Reporting functionality. Typically this is the same account as the MOM DAS account.

WORKAROUND - None.

Back to Table of Contents

### "There was an error accessing the SQL Server Reporting Services Server through WMI" Error During Reporting Setup

If you receive this error while installing MOM 2005 Reporting, the cause might be one or more of the following:

- There is a firewall between the MOM Reporting Database Server and the SQL Server Reporting Services Server. If so, then clear the Automatically detect virtual directories check box and try to run setup again.
- The ReportServer service is missing, this can happen if SQL Server Reporting Services is installed while the default Web Site is stopped.
- The SQL Server Reporting Services Server service is not started. If so, start it.
- The Windows Management Instrumentation service is not started. If so, start it.
- If the SQL Server Reporting Services computer is remote there could be a network connectivity issue.
- The account you are logged on with does not have sufficient permissions to the SQL Server Reporting Services computer.

WORKAROUND - Fix the problem and restart MOM Reporting Setup.

Back to Table of Contents

### Prerequisite Checker Says "ASP.NET is not enabled"

If the MOM Prerequisite Report sates "ASP.NET is not enabled", then you will have to enable ASP.NET before installing the MOM component.

To enable ASP.NET using the IIS Manager :

1. In Internet Information Services (IIS) Manager, expand Computer Name, and then click Web Service Extensions.
2. If the ASP.NET v1.1.4322 extension appears in the results pane, select it and click Allow.
3. If the ASP.NET v1.1.4322 extension does not appear in the right pane, click Add a new Web Service Extension.
4. In the Extension name text box, type "ASP.NET v1.1.4322".
5. Click Add, and then click Browse.
6. Locate %WINDIR%\Microsoft.NET\Framework\v1.1.4322\Aspnet_isapi.dll.
7. Click Open, and then click OK.
8. Select the Set extension status to Allowed check box, and then click OK.

To enable ASP.NET using the command line :

1. Using the command line window, navigate to %WINDIR%\Microsoft.NET\Framework\v1.1.4322\.
2. Run the following command: aspnet_regiis -i

WORKAROUND - Enable ASP.NET by using either the IIS Manager or the command line and start MOM setup.

Back to Table of Contents

### "The remote MOM database must be a valid MOM database" Error During Management Server or Console Uninstall

Uninstalling the MOM Database before uninstalling (unsung the Modify option in Add Or Remove Programs) the Management Servers or the Consoles will cause the Management Server or Console uninstalls to fail with the error: "The remote MOM database must be a valid MOM database."

WORKAROUND - Use the Remove option in Add Or Remove Programs on the Management Server or Console computer to uninstall them.

Back to Table of Contents

### Setup Fails - SetLicenseInformation Error In Setup Log

If setup fails and no error appears, look in the Server MSI log at %TEMP%\momserverlog If the log contains the entry:

> MSI (s) (98:10): Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI26.tmp, Entrypoint: SetTracingOptions
> SetLicenseInformation: LicenseSetMaxNodes() failed. Error Code: 0x8000401A

This setup failure might be caused by access permission settings in COM Security. These settings might be set to deny access to the account being used to install MOM.

WORKAROUND - To investigate and possibly fix this problem, do the following:

For Windows 2000

1. Open the Component Service snap-in.
2. Navigate to My Computer, right click the folder and click Properties.
3. In the My Computer Properties dialog, on the Default Security tab, click Edit Default, under Access Permissions.
4. On the Registry Value Permissions dialog, make sure the account used to install MOM and view the Access Permissions assigned to it.
5. If you do not see the account, you must add it by clicking Add.
6. Click OK and retry setup.

For Windows Server 2003

1. Open the Component Service snap-in.
2. Navigate to My Computer, right click the folder and click Properties.
3. In the My Computer Properties dialog, on the Default COM Security tab, click Edit Default, under Access Permissions.
4. On the Access Permissions dialog, on the Default Security tab, select the account used to install MOM and view the Access Permissions assigned to it.

Note - If you are using the account you logged onto the computer to install MOM, this account is "SELF".

1. Make sure that the account you are installing MOM under has Allow access in the dialog.
2. If you do not see the account, you must add it by clicking Add.
3. Click OK and retry setup.

Back to Table of Contents

### MOMCreateDB.Exe: No Log is Presented When Setup Fails

If setup fails when you are using the MOMCreateDB.exe tool, the tool prompts you if you want to see a setup log. The tool presents no log when you reply "Yes".

WORKAROUND - None.

Back to Table of Contents

### Push-Install Agent to ISA Server 2004 Fails with "RPC Server Unavailable" Error

If you try to push-install a MOM 2005 agent to a computer running Microsoft Internet Security and Acceleration Server (ISA) 2004, the install might fail with an "RPC server unavailable" error.

WORKAROUND - To solve this problem, you can do either of the following:

Instead of using the Management Server's Action Account, try supplying credentials when push-installing the agent. IF this does not work, manually install the agent.

OR

Disable the "Enforce Strict RPC compliance" setting and open the RPC port on the ISA 2004 server during the agent push. For more information, see the ISA 2004 documentation.

Back to Table of Contents

### Setup Fails With "Failed to create MOM DAS COM+ Components" Error

If you partially remove a previous MOM installation manually, for example if you are upgrading from MOM 2000 SP1 to MOM 2005, and you leave the DAS COM+ components, you will get the "Failed to create MOM DAS COM+ Components" error during MOM 2005 setup.

This can also happen if you have NetIQ Operations Manager 3.30 DAS COM+ components on the computer.

WORKAROUND - You must completely remove the OnePointActiveOpsDas and MOMDasLocator components before you can install or upgrade to MOM 2005.

Back to Table of Contents

### Upgrade Fails When Using a Non-Default Agent Data Directory

If you are upgrading MOM 2000 SP1 where you have the agent data directory at a non-default location, the MOM Service might not be able to start because the ACLs on the non-default directory might not be properly configured. MOM setup does not change the ACLs on this directory.

Note - This only happens if the MOM Service is configured to run as Network Service on Windows Server 2003. Local System has sufficient permissions.

The default location for this directory is: %InstallDrive%\Documents and Settings\All Users\Application Data\Microsoft\Microsoft Operations Manager\<management group.

WORKAROUND - You must add an ACL for NETWORK_SERVICE = Full Control.

Back to Table of Contents

### Changing Windows Installer Default Settings Might Cause MOM Setup to Fail

If you changing the Windows Installer default settings before running the MOM Setup, the Prerequisite Checker might not detect these changes and MOM setup might fail.

WORKAROUND - None.

Back to Table of Contents

### Setup Fails With "Account verification" Error

If you install and then re-install the Management Server on a Windows Server 2003 SP1 computer and MOM setup might fail with the following error:

> "Account verification error. Setup is unable to validate the account you provided. To change the account information, click Back."

WORKAROUND - Log off and then log back on and retry MOM setup.

Back to Table of Contents

### MOM Reporting Setup Fails With an Exception

If you try to install MOM Reporting on a computer that does not have the .NET Framework version 1.1 or higher, setup might fail with an exception.

WORKAROUND - Make sure you install the .NET Framework 1.1 before installing MOM Reporting. You can get the .NET Frameworks from http://go.microsoft.com/fwlink/?LinkId=31654.

Back to Table of Contents

### "Service could not be started" Dialog During Management Server Setup

If you see a dialog that states that the MOM Service or the MOM Connector (MOMConn) Service could not be started, click OK to finish setup and then manually start the service after setup has completed.

WORKAROUND - Manually start the service after setup has completed.

Back to Table of Contents

### Upgrade Might Fail if Less Than 50% Free Space in OnePoint Database

If you are upgrading MOM 2000 SP1 to MOM 2005 and the OnePoint database has less than 50% free space available, the upgrade might fail.

WORKAROUND - To avoid this problem run the preupgrade2000.sql script on the OnePoint database before upgrading. The script is in the Upgrade Tools directory on the MOM 2005 CD.

Note - If you get the "Failed to import management packs Error Code: -2147286928" error during MOM 2005 setup, this might also be caused by the problem above. To fix this, run the script above and retry setup.

Back to Table of Contents

### "The Management Server Could Not Be Contacted" Message Appears when Installing a MOM 2005 Agent for a MOM 2005 SP1 Management Server

If mutual authentication is turned off when a MOM 2005 agent is installed, the agent setup program generates the following error message, "The Management Server Could Not Be Contacted". This message is misleading because the setup program does finish successfully and the agent is installed. Agent installation will appear in the Administration/Computers/Pending Actions view for approval, as it does when mutual authentication is enabled.

WORKAROUND: None.

Back to Table of Contents

### After a Manual Agent Installation is Rejected, Subsequent Manual Installations of the Same Agent Do Not Appear in the Administrator Console's Pending Actions View

After a manual agent installation has been rejected in the Administrator console, subsequent manual installations of the same agent are not shown in the Pending Actions view.

WORKAROUND: Stop and restart the MOM Service on the management server.

Back to Table of Contents

### Known Issues Related to Running MOM Components on a 64-bit Computer

The MOM 2005 Web console and MOM Connector Framework (MCF) require ASP.NET 1.1, which is a 32-bit application. Even if ASP.NET 1.1 is installed on a 64-bit computer, you must configure IIS 6.0 to run in 32-bit mode.

IIS 6.0 supports both 32-bit mode and 64-bit mode. However, IIS 6.0 does not support running both modes at the same time on a 64-bit version of Windows.

For more information about configuring IIS to run 32-bit ASP.Net applications and running 32-bit applications on 64-bit Windows (IIS 6.0), refer to the following KB article: http://go.microsoft.com/fwlink/?linkid=47028

WORKAROUND: Configure IIS 6.0 to run as the 32-bit version.

Back to Table of Contents

### MOM 2005 Reporting Installation Error When Installing on Windows Server 2003 SP1

This issue is caused by installing SQL Server Reporting Services on Windows Server 2003 SP1.

WORKAROUND: Follow the instructions in the SQL Reporting Services KB article (number 896861) to fix the issue.

Back to Table of Contents

### MOM 2005 SP1 Update Behavior When MOM 2005 Agents are in Pending Uninstall Mode

When you run the setup program for the MOM 2005 SP1 update on MOM 2005 agent-managed computers, any computers whose agents are in pending uninstall mode remain in that mode. If you reject the pending uninstall after installing the update, the computers are still agent managed and are not updated to MOM 2005 SP1. When Computer Discovery is run again, the agents are put back into pending uninstall mode.

Note the following behavior:

- Creating a managed computer rule for computers that were in pending uninstall mode and running computer discovery does not put them into a pending upgrade state. You need to run update agent settings.
- Running Update Agent Settings updates the agents on these computers, and after a short delay, the agent version number is updated in the Administrator console.

Back to Table of Contents

### Installing the MOM 2005 SP1 Update on a MOM Management Server that Already Has an Agent Installed Will Cause a Management Server Failure

Installing the MOM 2005 SP1 update on a MOM management server that already has an agent installed updates the agent but not the MOM management server. This partial update results in a MOM management server failure. The following workarounds are available:

WORKAROUND 1: Perform the following steps:

1. Stop MOM service on the management server.
2. Navigate to Administrative Tools/Component Services/Component Services/Computers/My Computer/COM+ Applications. Right-click Microsoft Operations Manager Data Access Server, and select Apply the service pack update again. Wait for the service to stop.
3. Start MOM service.
4. Apply the service pack update again.

WORKAROUND 2: Restart the server computer, and then install the service pack update again.
Note: For both of the preceding workarounds, the update wizard will run twice, once for the agent and once for the server.

Back to Table of Contents

### In a Multiple Tier Configuration that Uses Alert Forwarding, Alerts May Not Be Forwarded to the Destination Management Group After MOM 2005 SP1 is Installed on the Destination Management Server

When you install the MOM 2005 SP1 upgrade on a destination management server that has the MOM Connector Framework (MCF) installed, EventID 10015 (source: MOM-to-MOM Product Connector) may be generated on a source management server when an attempt is made to forward an alert to this destination management server. When this occurs, the alert is not forwarded successfully.

WORKAROUND: Restart the World Wide Web Publishing Service (W3SVC) on all destination management servers after installing MOM 2005 SP1.

Back to Table of Contents

### Warning Events 1004 and 1001 are Generated by the MsiInstaller When an Agent is Upgraded to MOM 2005 SP1

The following warning events are logged when an agent is upgraded to MOM 2005 SP1. These events do not indicate a failure and can be ignored.

Event Type: Warning
Event Source: MsiInstaller
Event ID: 1004
Description:
Detection of product '{F692770D-0E27-4D3F-8386-F04C6F434040}', feature 'MOMXAgent', component '{3DD5588C-CFE0-41BD-BBEF-E08FE0310C2B}' failed. The resource 'D:\Program Files\Microsoft Operations Manager 2005\MBSA 1.2\MBSASetup.msi' does not exist.

Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{F692770D-0E27-4D3F-8386-F04C6F434040}', feature 'MOMXAgent' failed during request for component '{D52536A1-50CA-4CA3-BC54-4747BB448AE3}'

WORKAROUND: None.

Back to Table of Contents

### Agent Installer Log Files are Not Copied to the MOM Server After a Push Install Fails

The agent installer log files are not copied back to the MOM server after specifying a non-valid password for the agent action account when using a low-privilege MOM server action account. This occurs because the MOM server’s Action Account does not get added to the ACL on the AGENTLOGS directory. The following alert is created:

Source: Microsoft Operations Manager
Category: MOM Server
EventID: 21083
User: <MOM server action account>
Computer: <MOM server name>
Description: The MOM Server failed to install agent on remote computer <agent fqdn>.
Error code: -2147023293
Error Description: Fatal Error during installation.
Microsoft Installer Error Description: No Description Available.

WORKAROUND: You must edit the ACL on the AgentLogs directory to give Read+Write access to the Action Account on the management server. Follow these steps:

1. Using the Windows Explorer, right-click the AGENTLOGS directory and select Sharing and Security.
2. Click the Security tab.
3. Click Add, and enter the MOM Server’s Action Account; then click OK.
4. Select the MOM Server’s Action Account, clear all check boxes except Allow Write, and then click Apply.

Back to Table of Contents

### A Custom Application May Not Work if it References a MOM Assembly That Was Patched Prior to MOM 2005 SP1 with a QFE

Several QFEs were released for MOM 2005 that shipped new versions of the following MOM assemblies:

- Microsoft.Mom.Sdk.dll
- MomConnectorFrameworkV2.dll

This affects custom applications that specifically reference a QFE version of the MOM SDK or the MOM Connector Framework. In this scenario, installing MOM 2005 SP1 Beta on the MOM management server that hosts the application causes the application to fail. This is caused by the QFE assembly version numbers not being included in the policy file for the new assemblies.

WORKAROUND: It is necessary to edit the policy file that is in the GAC to include the QFE version numbers. Follow these steps:

- For the MOM SDK policy file, edit the file policy.5.0.Microsoft.Mom.Sdk.config in the directory %windir%\assembly\GAC\policy.5.0.Microsoft.MOM.Sdk\5.0.2845.0__31bf3856ad364e35 directory. Replace oldVersion="5.0.2749.0" with oldVersion=" 5.0.2749.0-5.0.2749.11", and then save the file.
- For the MOM Connector Framework policy file, edit the file policy.5.0.MomConnectorFramework.config that is in the directory %windir%\assembly\GAC\policy.5.0.MomConnectorFramework\5.0.2845.0__31bf3856ad364e35 directory. Replace oldVersion="5.0.2749.0" with oldVersion=" 5.0.2749.0-5.0.2749.1", and the save the file.

After you change these configuration files, restart any application that uses these assemblies.

Back to Table of Contents

### In Some Cases, the Prerequisite Checker May Generate an ASP.NET Error Even if ASP.NET is Installed and Running

This issue is caused by the installation order of .NET Framework and Internet Information Services (IIS). For example, if you install .NET Framework 1.1 and then IIS, the prerequisite check fails because ASP.NET is not registered with IIS.

The prerequisite checker will fail to detect ASP.NET when the following conditions exist:

1. ASP.NET is disabled. To resolve this issue, enable ASP.NET in Services.
2. ASP.NET does not exist. To resolve this issue, install ASP.NET. You can install ASP.NET by:
   - Installing .NET Framework 1.1.
   - In Windows Server 2003, use Add or Remove Programs to Add/Remove Windows Components.
3. ASP.NET is not registered with IIS. To resolve this issue, do one of the following:
   - Uninstall, and then reinstall .NET Framework 1.1.
   - Use the command window to register ASP.NET. Navigate to %SYSTEMROOT%\microsoft.net\framework\v.1.1.4322. At the command prompt, run the aspnet_regiis -i command.
   - Add ASP.NET to the Web Service Extensions list:
     1. Click Start, pick Settings, and then click Control Panel.
     2. Double-click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.
     3. In the navigation pane, expand Computer Name, and then click Web Service Extensions.
     4. In the details pane, click Add a new Web service extension.
     5. In the Extension name text area, type ASP.NET v1.1.4322.
     6. Click Add to open the Add file property page, and then click Browse.
     7. Locate the Aspnet_isapi.dll in the Windows directory under \Microsoft.NET\Framework\v1.1.4322.
     8. Click Open and then click OK.
     9. Click to select the Set extension status to Allowed check box, and then click OK.

Back to Table of Contents

### In a SQL Server Cluster, the Prerequisite Checker Works Only on the Active Node of the Cluster

When you run the prerequisite checker against a SQL Server cluster, the checker works only on the active node of the cluster.

WORKAROUND: None.

Back to Table of Contents

### Specific Steps are Required When Installing the MOM 2005 SP1 Update on a SQL Server Cluster or Special Database Configuration

The type of MOM Database installation that you are using determines which steps are required to install the MOM 2005 SP1 update.

#### MOM Database install from MSI on a cluster (most common to Active/Passive clusters)

In this cluster configuration, you apply the service pack update running setup.exe to use the MSI installer.

For illustration purposes, the setup procedure is based on the following configuration:

- ServerA--the MOM management server with the MOM consoles installed.
- ServerB--hosts the MOM operational database. This computer is also the active node of the SQL Server cluster.

To install the service pack update, perform the following steps:

1. Install the service pack update on ServerB. If there is a MOM agent also installed on this computer, the agent update is applied first, followed by the server update.
2. Install the update on ServerA. If there were managed agents, they need to be updated through the Administrator Console's Pending Actions view. If there was an agent also installed on ServerB, this agent will be listed in the Pending Actions view. You can safely reject the pending action for it because it was already updated in step 1.

#### MOM Database install from MOMCreateDB.exe (most common to Active/Active clusters)

In this type of environment, if MOMCreateDB.exe was used to create the database, you must use MOMRunScript.exe to install the service pack update.

Note: To verify that your database installation was installed by using MOMCreateDB.exe, open Add or Remove Programs and verify that there is not a registered product for Microsoft Operations Manager 2005. (You may have an entry for Microsoft Operations Manager 2005 Agent, but this does not affect the database upgrade.)

To install the service pack update, perform the following steps:

1. Ensure that all SQL instances that contain the MOM 2005 RTM OnePoint database are active on a single node.
2. Copy the Support Tools folder for x86 or ia64 (as appropriate) to the computer where you want to install the service pack update.
3. On the computer where you want to run the update, open cmd.exe and navigate to the Support Tools folder.
4. At the command prompt, run MOMRunScript.exe /databasename:OnePoint /sqlscript:”[localdirectory]\build_mom2005_sp1.sql” /updateno:SP1.
5. The script in step 4 will locate all the SQL instances that the update will run against and generate a user interface. When you are ready to install the service pack, click Update.
6. When the update is finished, a pop-up will appear that indicates whether or not the update was successful.

Note: An error may appear that indicates that the registry could not be updated. If the Microsoft Operations Manager\2.0\ registry key exists, it will update the UpdatesInstalled key. If the node that the service pack update was run on is not the same node that the product was originally installed on, this key will not exist. Because this registry for MOMCreateDB is not a blocking issue, you can ignore this error.

Back to Table of Contents

### If the MCF Assembly is Loaded During an Upgrade from MOM 2005 RTM to MOM 2005 SP1, the Installation will be Interrupted and an Error Message is Displayed

If the MCF assembly is loaded by aspnet_wp.exe/w3wp.exe during the upgrade from MOM 2005 RTM to MOM 2005 SP1, the following error message is displayed:

"The installer has insufficient privileges to access this directory: D:\Program Files\Microsoft Operations Manager 2005\WebService\bin. The installation cannot continue. Log on as administrator or contact your system administrator."

This error is caused by ASP.NET caching, which keeps the handle to Webservice/bin dir open, which prevents files from getting replaced.

WORKAROUND:

- Restart the W3SVC service on the management server before starting the upgrade from MOM 2005 RTM to MOM 2005 SP1. If you do this, the installation is not interrupted and the error message is not displayed.
- If you've already started the upgrade and the error message pop-up is displayed, click Retry to continue. This action releases the open handle and allows the upgrade to finish.

Back to Table of Contents

### When Installing MOM Reporting, You Might Get an "Error 401:Unauthorized error while creating datasource" Message and the Reporting Installation Will Fail.

This error is caused by a security setting in Windows Server 2003 Service Pack 1.

WORKAROUND: A workaround is available and documented in KB article number 896861, which is available at http://support.microsoft.com.

# Management Packs

Back to Table of Contents

### Pre-Filter Rules Not Supported in Versions After MOM 2005

Pre-Filtering rules have been removed from all Management Packs shipping on the MOM 2005 CD and will not be created for, or supported in, versions of MOM after MOM 2005. Existing pre-filter rules will be supported in MOM 2005 however you are advised not to use this type of rule to avoid upgrade issues from MOM 2005 to future versions of MOM.

WORKAROUND: None.

Back to Table of Contents

### Microsoft Active Directory Management Pack Installation Might Not Update OOMADS.DLL

In some cases the OOMADS.DLL may not update during installation of the AD MP. This will result in one or more of the alerts listed below:

- Script Based Test Failed to Complete
- Topology Discovery did not fully discover topology - the Site Link diagram may be incomplete
- AD Client Side - Script Based Test Failed to Complete

WORKAROUND: To resolve this problem, do the following on the computer experiencing the problem:

1. Stop the MOM Service.
2. Run the OOMADS.MSI installation program from the Support Tools directory on the MOM 2005 CD.
3. Start the MOM Service.

Back to Table of Contents

### Remove Microsoft Active Directory Management Pack Helper Objects Before Removing MOM Agent

If you are removing the Microsoft Active Directory Management Pack Helper Objects (OOMADS.DLL), you must remove it before removing the MOM agent. To Remove the Helper Objects, use Add or Remove Programs.

WORKAROUND: None.

Back to Table of Contents

### Duplicated and Non-Functional Views After Upgrading IIS Management Pack

Several Views will be duplicated and remain after you upgrade the Microsoft Internet Information Services Management Pack from MOM 2000 SP1. These views can be manually deleted.

Alert Views / Microsoft Windows Internet Information Services / Internet Information Services 4.0 and 5.0 /

- Health Monitoring / All Open Alerts From Web Servers
- Health Monitoring / Web Page Not Found Alerts
- Intrusion Detection / Access Denied Alerts
- Intrusion Detection / Possible Buffer Attack Alerts
- Intrusion Detection / Unauthorized User Alerts

Performance Views / Microsoft Windows Internet Information Services / Internet Information Services 4.0 and 5.0 /

- Performance Monitoring / IIS 5 Web Server Uptime
- Performance Monitoring / Web Server Throughput

Computers and Groups / Microsoft Windows Internet Information Services / Internet Information Services 4.0 and 5.0 / Discovery

- Computers Running IIS

Event Views / Microsoft Windows Internet Information Services / Internet Information Services 6.0 /

Important: Check each view's properties before deleting any of the views listed below. Only delete the views that do not reference "Microsoft Windows 2003 IIS*Servers" computer group.

- Configuration Issues
- Logging Issues
- Application Pool Diagnostics / Worker Process Error
- Application Pool Diagnostics / Worker Process Recycle Events

WORKAROUND: Manually delete the duplicated and non-functional views listed above using the MOM Operator console. To remove a view, navigate to the specified location, right-click on the view and click Delete.

Back to Table of Contents

### Record Notification Group Changes Before Re-Import or Upgrade to Management Pack

If you alter the membership or structure of the Notification Groups for any Management Pack and then either re-import or upgrade the Management Pack, the changes will be overwritten.

WORKAROUND: Record any changes to the Notification Groups and re-populate these after re-importing or upgrading the Management Pack.

Back to Table of Contents

### SQL Server Replication Monitoring May Not Work As Expected

The Microsoft SQL Server Management Pack replication monitoring script may generate failed login errors when attempting to monitor replication. For each SQL Server instance on a monitored SQL Server, the management pack attempts to verify the Replication Distributor database which may not exist on all servers involved in replication or may use a name other than 'distribution'.

For each failure, the Management Pack will raise the event "18456 : Login failed for user 'loginAccountName'" each time the Replication Monitoring script runs (by default this is every 30 minutes).

WORKAROUND: Disable the “Microsoft SQL Server\SQL Server 2000\State Monitoring and Service Discovery\SQL Server 2000 Replication Monitoring” rule to prevent failed login events occurring.

Back to Table of Contents

### Management Pack Import Fails with "Error 25203. Failed to import management packs"

If you try to install two MOM 2005 Management Server at, or near, the same time on two computers, the setup will fail with the "Error 25203. Failed to import management packs. Error Code: -2147467259 (Unspecified error)" error.

WORKAROUND: Retry MOM setup and install one computer at a time.

Back to Table of Contents

### Override Setting Does Not Work For Collection Rules

The Enable rule-disable overrides for this rule setting does not work for event collection rules.

WORKAROUND: To get the same functionality, use an event processing rule, but do not configure it to raise alerts. You can then enable overrides on that rule.

Back to Table of Contents

### Check for Updated Management Packs on the MOM Web Site

The Management Packs available on the MOM 2005 CD will be updated periodically. These updates are freely available and can be downloaded from the MOM Web site - http://go.microsoft.com/fwlink/?linkid=6727. Before importing Management Packs, check to see if there is an updated version of the Management Pack.

WORKAROUND: Not Applicable.

Back to Table of Contents

### Additional Information About Management Packs Available in Management Pack Guides

Additional and detailed information about Management Packs can be found within the relevant Management Pack guide. These guides include detailed information about importing, configuring, and tuning, as well as additional release notes for, the Management Pack. The Management Pack guides can be found on the MOM Web site - http://go.microsoft.com/fwlink/?linkid=6727.

WORKAROUND: Not Applicable.

Back to Table of Contents

### Active Directory Management Pack Script Might not Work Properly on a Manually-Installed Agent

If you are running a MOM 2005 agent on an Active Directory server, such as a Domain Controller, and scripts in the Active Directory Management Pack are failing, this might be caused by the agent control setting.

WORKAROUND: Change the agent Control setting to "Full".

Back to Table of Contents

### "Download mssecure.cab from http://www.microsoft.com" Task Should Be Run Only From An MBSA File Transfer Server

You must run the "Download mssecure.cab from http://www.microsoft.com" Task on a File Transfer Server. The Task will fail if run on a computer that is not a File Transfer Server.

Note - This task is different than the "Download mssecure.cab from File Transfer Server" task, which can be run on a computer that is not a File Transfer Server.

WORKAROUND: Not Applicable.

Back to Table of Contents

### "AD Replication Connection Objects" Report Failing

If the "AD Replication Connection Objects" report is failing to run, this might be caused by an update to the SQL Server Reporting Services. The update changes the SQL Server Reporting Services version from 8.00.760 ( the SP3 version) to 8.00.859. The report only works with SQL Server version 8.00.760 ( the SP3 version).

WORKAROUND: None.

Back to Table of Contents

### Upgrading Base Operating System or DNS Management Pack Will Remove Existing Rules and Groups

When upgrading the MOM 2000 Windows Base Operating System or DNS Management Packs to the MOM 2005 version all previous rules and groups will be deleted. This will include any customized or user created rules and groups.

WORKAROUND: Copy rules and groups you would like to preserve to a custom rule group outside the Management Pack. Upgrade the Management Pack to the MOM 2005 version. Optionally copy the rules back into a suitable place within the upgraded rule group structure.

Back to Table of Contents

### Upgrading Custom Rules with MOM 2000 SP1 Attributes Might Break Computer Groups

When upgrading MOM 2000 SP1 Management Packs to the MOM 2005 version, custom Computer Group rules with MOM 2000 SP1 Attributes might not upgrade correctly, because Attributes were not maintained across versions. If these Computer Groups do not function correctly they must be changed to work.

WORKAROUND: Recreate the required MOM 2000 SP1 computer Attributes for your custom Computer Groups.

Back to Table of Contents

### Computers that Were Manually Added to a Computer Group’s Include and Exclude Lists Remain in the Lists After an Associated Product is Upgraded

When a Computer Group based on a product version (for example, Microsoft SQL Server 2000) is maintained using the Include and Exclude lists, the relevant managed nodes will continue to be members of the Computer Group after the product is upgraded. For example, if you manually added computers to the Microsoft SQL Server 2000 Include and Exclude lists, the relevant managed nodes would continue to be members of the Computer Group even after SQL Server is upgraded from SQL Server 2000 to SQL Server 2005.

WORKAROUND: Update the appropriate Computer Group Include and Exclude lists after upgrading the application.

# Security

Back to Table of Contents

### "Reject Manually Installed Agents" Setting Requires Mutual Authentication

The "Reject Manually Installed Agents" setting requires Mutual Authentication to work properly. If you enable this setting, you must also enable Mutual Authentication.

WORKAROUND: None.

Back to Table of Contents

### Password or Username Field on Some Dialogs Shorter or Longer Than Windows Maximum Length for Passwords

The following dialogs in MOM 2005 have password or username entry fields that are either shorter or longer than the maximum allowed by Windows.

Password Fields (Windows allows 128 characters):

> Install/Uninstall Agents Wizard - Management Server Action Account page: 38 characters

> Install/Uninstall Agents Wizard - Agent Action Account page: 38 characters

> Setup Wizard - DAS Account page: 80 characters.

> Update Agent Settings dialog - Management Server Action Account: 256 characters

> Update Agent Settings dialog - Agent Action Account: 256 characters

> Uninstall Agents dialog - Management Server Action Account: 256 characters

Username Fields (Windows allows 256 characters):

> Setup Wizard - DAS Account page: 80 characters.

WORKAROUND: Be aware that the password is truncated to match the shorter length.

Back to Table of Contents

### File Transfer Failing with "Access Denied" Error

If File Transfers are failing with the error below, this might be caused by the BUILTIN\Users group not having READ access to the C:\ drive.

> The agent <domain/computername> could not add remote file: http://<server>/MBSA/mssecure.cab, local file: C:\Program Files\Microsoft Operations Manager 2005\Downloaded Files\Critical Infrastructure\mssecure.cab to BITS job MOM_File_Transfer_Job_Critical Infrastructure{53BA5370-7C10-44A3-A648-D2F490D60761}. Error description: Access is denied.

WORKAROUND: Make sure that the BUILTIN\Users group has READ access to the C:\ drive.

Back to Table of Contents

### Cannot Remove SC DW DTS Group - "Unknown Active Directory object" Error

The MOM DB install creates the "SC DW DTS" NT group but does not uninstall it when the MOM DB component was uninstalled (no other components on the box). When the SC DW DTS group is clicked to remove the group an error dialog is displayed "Unknown Active Directory object". This error dialog prevents its deletion.

WORKAROUND: To remove the group close and then open Computer Management, then the delete option will be available again.

# Reporting

Back to Table of Contents

### "Agent Uptime by Computer" Report Does Not Return Correct Information On An IA64 Computer

The "Agent Uptime by Computer" report does not return correct information for "System Uptime" on an IA64 computer.

WORKAROUND: None.

Back to Table of Contents

### How To Remove Reports After Upgrading MOM Reporting From Beta 3 or the Release Candidate

Some reports are left after upgrading MOM Reporting from Beta 3 or Release Candidate to final version of MOM 2005. You must remove these reports manually by doing the following:

1. Log onto the Reporting Server with sufficient rights to modify reports.
2. Navigate to the report folder and select the checkbox beside each of the reports.
3. Click Delete.
4. Do this for each of the report folders and reports listed below:

Microsoft Operations Manager
- MOM Monthly Capacity Planning
- MOM Monthly Capacity Planning Detail
- Service Discovery Failures Detail
- Service Discovery Failures Summary
- Management Group Health
Operational Health Analysis
- Alerts by Severity By Computer
- Computer Group Membership
- Event Count by Agent by Day
- Events By Severity By Computer
- Events By Severity By Computer Group
- Most Common Alerts by Rule Group
Microsoft Windows Base Operating System\Reliability
- Application Hangs by Application
- Application Hangs by Computer
- Application Hangs by Event
Microsoft Windows Base Operating System\Performance History
- Performance History Memory-Committed Bytes
- Performance History Memory-Cache Bytes
- Performance History Memory-Percent Committed Bytes In Use
- Performance History Memory-Demand Zero Faults per Sec
- Performance History Memory-Page Faults per Sec
- Performance History Memory-Pages Input per Sec
- Performance History Memory-System Cache Resident Bytes
- Performance History Memory-Transition Faults per Sec
- Performance History Process-Handle Count
- Performance History Process-Page File Bytes
- Performance History Process-Private Bytes
- Performance History Process-Virtual Bytes
- Performance History Processor-Percent DPC Time
- Performance History Processor-Percent Privileged Time
- Performance History Server-Pool Paged Failures

WORKAROUND: Manually remove the reports listed above.

Back to Table of Contents

### DTS Job Times Out With "System.Data.SqlClient.SqlException" Event

If you are running the Reporting DTS job and you have timeouts with this Event text:

> "System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion
> of the operation or the server is not responding."

You need to get this hotfix: http://go.microsoft.com/fwlink/?LinkId=47030

WORKAROUND: Install the update.

Back to Table of Contents

### Date Format is Always UE English Regardless of Browser Settings

Many of the Management Pack reports might display dates in US - English format as opposed to a format that is consistent with the locale of the browser in which they are viewed.

WORKAROUND: None.

Back to Table of Contents

### New Parameters Have Been Added for Running the DTS Job from the Command Line

The following parameters have been added to the command line for running the DTS job:

- /chunksize: Chunk size in days. High volume data will be transferred in increments of the chunk size, enabling transfer of high-volume data with limited log space. Specifying 0 will not chunk the data. (Default = 1 day.)
- /maxchunks: Maximum number of chunks to create when chunking is enabled. (Default = 10 chunks.)
- /usesqlauth: Indicates use SQL Authentication. SQL Authentication should not be used and was added only to support the MSN scenario. (Default is to use Windows Authentication.)
- /srcsqllogin: Source SQL Login. Used to connect to the source database. Used only for SQL Authentication.
- /srcsqlpwd: Source SQL Password. Used to connect to the source database. Used only for SQL Authentication.
- /dwsqllogin: Data warehouse SQL Login. Used to connect to the data warehouse database. Used only for SQL Authentication.
- /dwsqlpwd: Data warehouse SQL Password. Used to connect to the data warehouse database. Used only for SQL Authentication.

To use the new SQL Authentication switch, you have to configure the source and destination SQL Server login accounts for the DTS job. Configure these accounts as follows.

To set up the account on the MOM Database computer:

1. Open SQL Enterprise Manager, and connect to the SQL Server instance where the MOM Database (OnePoint) is installed.
2. Expand Console Root/Microsoft SQL Servers/SQL Server Group<SQL Server Instance>/Security, and right-click Logins.
3. Pick New Login.
4. On the General tab, type the login name that you want to use for DTS in the Name field.
5. Enable SQL Server Authentication, and type the password that you want to use for the login.
6. Select OnePoint from the Database list.
7. Click the Database Access tab.
8. Click the Permit check box for OnePoint database. This action populates the available database roles for the OnePoint database.
9. Find SC DW DTS in the Database roles for ‘OnePoint’ list, and click the Permit check box for this role.
10. Click OK to save your configuration, and exit the dialog.
11. You will be prompted to confirm the password for the login in the Confirm Password dialog. Enter the password you used in step 5, and click OK. A OnePoint database user with the same name and password is automatically created.

To set up the account on the MOM Reporting Database computer:

1. Open SQL Enterprise Manager and connect to the SQL Server instance where the MOM Reporting Database (SystemCenterReporting) is installed.
2. Expand Console Root/Microsoft SQL Servers/SQL Server Group<SQL Server Instance>/Security, and right-click Logins.
3. Pick New Login.
4. On the General tab, type the login name that you want to use for DTS in the Name field.
5. Enable SQL Server Authentication, and type the password that you want to use for the login.
6. Select SystemCenterReporting from the Database list.
7. Click the Server Roles tab.
8. Click the check boxes for Security Administrators and Setup Administrators
.
9. Click the Database Access tab.
10. Click the Permit check box for the OnePoint database. This action populates the available database roles for the OnePoint database.
11. Find SC DW DTS in the Database roles for ‘OnePoint’ list, and click the Permit check box for this role.
12. Click OK to save your configuration, and exit the dialog.
13. You will be prompted to confirm the password for the login in the Confirm Password dialog. Enter the password you used in step 5, and click OK. A OnePoint database user with the same name and password is automatically created.
14. Expand Console Root/Microsoft SQL Servers/SQL Server Group<SQL Server Instance>/Databases/SystemCenterReporting/Users.
15. Right-click the login name that you created in step 4, and pick Properties.
16. In the Permit in Database Role list, click the check boxes for db_securityadmin and db_ddladmin and then click OK.

You are finished creating the logins and permissions that are required by DTS. However, you still have to ensure that the SQL Server installation that hosts both the OnePoint and SystemCenterReporting databases allows Windows Authentication and SQL Server Authentication. Use the following steps for both database instances to ensure that authentication is configured correctly:

1. Open SQL Enterprise Manager, and connect to the SQL Server instance that hosts the databases.
2. Right-click on the SQL Server instance, and pick Properties.
3. Click the Security tab, and verify that SQL Server and Windows authentication is enabled. If this is not enabled, click the radio button and then click OK.
4. Restart SQL Server so that the new changes take effect.

Note: To use the new accounts, you have to use the following command line switches:

- /usesqlauth
- /srclogin
- /srcpwd
- /dwlogin
- /dwpwd

# Operator Console

Back to Table of Contents

### Some Tasks or Functions Not Working After Removing Agent From Consoles-Only Computer

If you remove the MOM agent from a computer that only has the Administrator and/or Operator console installed on it, some Tasks and functions might not work correctly.

WORKAROUND: Uninstall and re-install the console(s).

# Administrator Console

Back to Table of Contents

### Importing MOM 2000 SP1 Licenses Does Not Work

MOM 2000 SP1 licenses cannot not displayed or imported from the MOM 2005 Administrator console. The console appears to import these licenses, but does not.

WORKAROUND: None.

Back to Table of Contents

### "Recursive reference chain" Error When Creating Computer Groups

IF you receive the "Recursive reference chain" error when creating Computer Groups, this means that the Computer Group references itself at some point. This can happen if you use Computer Group names that are the same as existing Computer Groups except that they have extra spaces in the name.

WORKAROUND: Use unique Computer Group names and be sure to correctly spell Computer Group names.

Back to Table of Contents

### Performance Recommendation: Change Rule Change Polling For Large-Scale Environments

If you are running MOM in a large-scale environment (more than 200 managed computers) you can gain performance by lengthening the Rule Change Polling setting to a larger value, for example, 12 to 24 hours.

WORKAROUND: Not Applicable.

Back to Table of Contents

### Software Updates Might Not Be Applicable in a Multihomed Environment

On a managed computer where the computer is multihomed with two different versions of MOM, such as the Release Candidate and the RTM version, MOM Software Updates might indicate in the Pending Actions folder that an update must be done on the managed computer but the updates might not actually be required or even applicable.

WORKAROUND: Reject the Software Update.

Back to Table of Contents

### On MOM 2005, the Administrator Console May Fail After Windows Server 2003 is Upgraded to Service Pack 1

After you upgrade Windows Server 2003 to Service Pack 1, the MOM Administrator console may fail when you click Management Packs/Computer Groups in the navigation pane. When affected by this issue, the Administrator Console may fail with “The remote procedure call failed” error message. This will occur when the MOM 2005 Management Server is running on a server that has Microsoft Windows Server 2003 Service Pack 1 installed.

WORKAROUND: Obtain and install the following hotfix: Q896989. You can download a copy from: http://go.microsoft.com/fwlink/?LinkId=47046

Back to Table of Contents

### Under Certain Conditions, Manually Installed MOM 2005 Agents Cannot be Updated by a MOM 2005 SP1 Management Server

If you manually install a MOM 2005 agent after updating the management server to MOM 2005 SP1, the management server will detect the MOM 2005 agent but cannot apply the MOM 2005 SP1 update. This is by design.

WORKAROUND: Manually install MOM 2005 SP1 on the computer where the MOM 2005 agent is installed.

Back to Table of Contents

### Multihoming an Existing MOM 2005 SP1 Agent to a MOM 2005 Management Group Does Not Work

When you attempt to configure multihoming for an existing MOM 2005 SP1 agent from a MOM 2005 management group, you get the following error:

Error Code: -2147023258
Error Description: Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

WORKAROUND: None

Back to Table of Contents

### Calculating Group Membership May Fail When Using the Administrator Console to Connect to a Different Management Server

In scenarios where you use the Administrator console to connect to a different management server, calculating group membership may fail. This happens when you use a Fully Qualified Domain Name (FQDN) to connect to the management server. The following error message is generated:

Incorrect function.
Result code: 8000ffff

WORKAROUND: Use the NetBIOS name of the computer that you want to connect to.

Back to Table of Contents

### To Push Install Agents in MOM 2005 SP1, Windows Installer 3.1 or Later Is Required on the Destination Computers

In MOM 2005 SP1, push installing agents requires Windows Installer 3.1 or later on the computers that are the destination for the push install.

To determine which version of Windows Installer is installed on a destination computer, do the following:

1. Log on to the destination computer.
2. Issue the following command from the command prompt: MSIEXEC.EXE /?

You can download the latest version of the Windows Installer from the following locations: http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en or from the Microsoft Windows Update Web site.

WORKAROUND: None

# Web Console

Back to Table of Contents

### Web Console Website Cannot Start

If setup provides a warning that the web console website could not start, port 1272 may already be in use by another application or service.

WORKAROUND: If the port is already being used, use the following steps to activate the Web console:

Reconfigure any Web application or Site that is using port 1272 and start the MOM Web console website from IIS. For information about how to do this, see the Internet Information Services help.
OR:

Configure the Web console port using Global Settings in the Administrator console to an unused port, and restart the website from IIS.

Back to Table of Contents

### Need To Grant NETWORK_SERVICE Rights To Run The Web Console On A Windows Server 2003 Domain Controller

If you install MOM 2005 Web Console on a domain controller the Web console will not work because of access rights on the computer.

WORKAROUND: Add an ACL entry for the NETWORK_SERVICE and grant NETWORK_SERVICE full access right to the “%Systemroot%\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files" directory.

Back to Table of Contents

### “You are not authorized to view this page” Error when Opening the Web Console

This error may occur when you open the Web console from the Administrator console on a computer that has Windows Server 2003 installed. This error may also occur when typing "http://computername:1272" in the URL bar of the IE browser window.
This error is caused by the sequence in which the MOM 2005 prerequisites are installed on the server. If the .NET Framework Common Language Runtime is installed before IIS, the default.aspx file is not added to the list of default file names to resolve under a directory.

WORKAROUND: Use the following steps to add default.aspx:

1. Open Computer Management (Start/Settings/Control Panel/Administrative Tools).
2. Right-click Internet Information Services (IIS) Manager and select Properties.
3. Click Edit and select the Documents tab.
4. Click Add.
5. Type in "default.aspx".
6. Save the filename and close Properties.

# Product Connector and MOM Connector Framework

Back to Table of Contents

### Computer Group Membership is Not Complete in the Destination Management Group

When two or more MOM management groups are connected using the MOM to MOM Product Connector (MMPC), computer grouping will not function correctly in the destination management group. By default, computers in the source management group(s) will not appear in the majority of computer groups in the destination management group.

This is caused by Computer type information not getting forwarded to the destination management group. Most computer groups use this information to determine computer group membership. The computer type can be Server, Client, Domain Controller, Unknown or Cluster Virtual Server. Computers from the source management group will be of type Unknown in the destination management group. Since most computer groups do not include this type in their definition, these computers will be excluded even if the computer group formula finds a match.

WORKAROUND: Each computer group definition in the destination management group that you want to have populated with computers from the source management group should be changed to include the Unknown computer type.

Note: The exception to this workaround is any Domain Controller computer group. For these computer groups, setting the definition to match Unknown computers will result in all computers from the source management group being included in the computer group. For these computer groups, the domain controllers should be added to the included computers by name.

Back to Table of Contents

### Invalid Alert Objects

MOM 2005 SP1 introduces stricter validation of alerts that are forwarded using the MOM to MOM Product Connector (MMPC). An invalid alert can be generated in the source management group in a MOM script using the ScriptContext objects.

This type of alert will be rejected if it is forwarded to a destination management group to avoid an attempt to insert an invalid alert. When this occurs, an event is logged in the application event log of the source management server that is attempting to forward the alert.

An event with ID 10078 and a source of Microsoft to MOM Connector will be raised for each alert that could not be forwarded. The description will contain the GUID of the alert with problems. If it is an alert update that has failed, event 10079 will be logged instead, again containing the GUID of the alert that could not be updated. The MOM management pack that is included in MOM 2005 SP1 has two new rules to alert on these events.

Back to Table of Contents

### Concurrent Updates to Alerts

It is possible that an update occurs to an alert in both the source and destination management groups during the same polling period. The default behavior in the MMPC is for the update in the source management group to overwrite the update from the destination management group. This behavior is the same in MOM 2005 SP1, but you can alter the behavior so that the destination management group alert update takes precedence when a concurrent update occurs.

WORKAROUND: To change alert precedence:

- On each MOM server in the source management group, create a REG_DWORD value named TopTierConflictResolution under the registry key HKLM\Software\Mission Critical Software\MomConn path. A nonzero value will result in the destination management group taking precedence, while a zero value or absence of the registry value will result in the source management group taking precedence.
  Note: This value does not exist by default; to change the default behavior, the value must be added using REGEDIT.
- After you've configured the value, you must restart the MOM to MOM connector service on each MOM server where you changed the registry value.

# Accessibility

Back to Table of Contents

### Report Contents are not Visible In High-Contrast Mode

The contents of reports are not visible if you are using high-contrast mode on your display.

WORKAROUND: Turn off high-contrast mode by doing the following:

1. In Internet Explorer, click Tools and select Internet Options.
2. In the Internet Options dialog, on the General tab, click the Accessibility button.
3. In the Accessibility dialog, select the Ignore colors specified on Web pages checkbox and click OK.

# MOM 2005 Workgroup Edition

Back to Table of Contents

### Items Left After Upgrade

Setup will leave the following items after you upgrade from MOM 2005 Express Beta 3 (build 2358) to MOM 2005 Workgroup Edition. You can safely remove these.

> SQL Login: %computername%\SC DW DTS

> Windows Group: SC DW DTS

Setup will leave the following registry hive after you upgrade a UI only MOM 2005 Express Beta 3 (build 2358) or MOM 2005 Express RC2 (build 2642) to MOM 2005 Workgroup Edition. No action on this item is necessary.

> Registry hive: HKEY_LOCAL_MACHINE\Software\Mission Critical Software\OnePoint\Configurations]

WORKAROUND: None.

## Release Notes Copyright Information

Information in this document, including URL and other Internet web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document might be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft might have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 1994-2005 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries/regions.

The names of actual companies and products mentioned herein might be the trademarks of their respective owners.