OnePoint Service CPU Utilization Peaks When Monitoring Multiple IIS Sites (305972)



The information in this article applies to:

  • Microsoft Operations Manager 2000

This article was previously published under Q305972

SYMPTOMS

The OnePoint service may cause CPU utilization to both peak for longer amounts of time than what is typical (at a lower than normal priority) and consume large amounts of memory on servers that run Microsoft Operations Manager (MOM) rules that manage Microsoft Internet Information Server (IIS) log files by using the Application Log provider. By default, there are over 50 rules in the IIS Processing Rule group that use the IIS log files.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office Manager 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

814529 How to Obtain the Latest Microsoft Operations Manager 2000 Service Pack



The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time      Version   Size     File name
   ---------------------------------------------------------------
   18-DEC-2001  14:17:36  4.0.9.66  660,208  Eemapplogprovider.dll
				

Installing The Hotfix

Note You can use the following method only for Intel-based computers that are running Windows 2000.

Apply this hotfix to each computer that hosts a MOM Consolidator (CAM) and a manually installed MOM agent.

To apply this hotfix:
  1. Copy the hotfix program (Q305972.exe) to a local shared folder on your computer or to a shared drive on your network.
  2. Run the Q305972.exe program on each computer that meets the predefined criteria. Follow the instructions that are provided in the hotfix installer.
  3. Restart your computer.
Note If you run the Q305972.exe file while the MOM Administrator console is open, you must restart the MOM Consolidator (CAM) server. It is therefore recommended that you shut down the MOM Administrator console before you install the hotfix.

When you install this hotfix on a MOM Consolidator (CAM) server, the installation engine causes an agent update to all currently managed servers. This process involves the following steps:
  • At the next scheduled Managed Computer scan, the list of agent computers that must be updated appear in the Pending Installation folder in the Configuration snap-in. If necessary, you can immediately start the Managed Computer scan.
  • On the MOM Consolidator (CAM) computer, the deployment of the updated agents must be approved.
  • The deployment of the updated agent occurs for each managed node only after the deployment is approved in the Pending Installation folder.

STATUS

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

This problem was first corrected in Microsoft Microsoft Operations Manager 2000 Service Pack 1.

MORE INFORMATION

In the MOM base management pack (Microsoft Operations Manager\Agent\Performance Processing Rules) there is a "Threshold Process-Private Bytes-OnePointService Agent" rule. By default, this rule restarts the OnePoint service on the agent if the Windows NT-based Process/Private Bytes/OnePointService performance counter exceeds 50 megabytes (MB) in size.

When you manage a large number of IIS virtual sites on the same server, the OnePoint Process Private bytes could increase beyond the default 50 MB threshold and continue to be in typical limits. To prevent the OnePoint service from being restarted, increase the threshold value for the "Threshold Process-Private Bytes-OnePointService Agent" rule. Depending on the environment (for example, the number of IIS sites being managed, site activity, and so on), a more appropriate threshold value may be in the range of 70 MB to 100 MB in size.

Modification Type:MajorLast Reviewed:4/7/2006
Keywords:kbQFE KBHotfixServer kbOpMan2000SP1Fix kbbug kbfix kbService KB305972