Event logged in the MOM Operator console: "Unable to start processing Request Sequence data file because a previous instance is already being processed" (924038)

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

When you click Events in the Microsoft Operations Manager (MOM) 2005 Operator console, you notice that the following event has been logged by the Web Sites and Services Management Pack: Event Type: Error
Event Source: Web Sites and Services MP
Event Category: None
Event ID: 3201
Date: 4/4/2006
Time: 5:55:00 PM
User: N/A
Computer: ComputerName
Description: Unable to start processing Request Sequence data file FileName.xml because a previous instance is already being processed. Please refer to product documentation for more information.

For more information, see Help and Support Center at http://support.microsoft.com.

CAUSE

This behavior occurs when the MOM 2005 Web Sites and Services request sequence interval is too short for the number of Web sites that are being monitored by the Web Sites and Services Management Pack. This behavior may also be caused by a network slowdown.

By default, the MOM 2005 Web Sites and Services request sequence is scheduled to run every two minutes. However, if the network is slow, or if there are lots of Web sites to monitor, it may take longer than two minutes to process the URL. In this case, the URL may not be successfully processed because a previous URL is still being processed.

WORKAROUND

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this behavior, you can increase the request sequence interval so that the URL can be successfully processed. To do this, change the MaximumConcurrentSequences value in the registry.

For more information about the MaximumConcurrentSequences registry value, see the Microsoft Operations Manager Web Sites and Services Management Pack Guide.

To download the Microsoft Operations Manager Web Sites and Services Management Pack Guide, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=53bc39b6-756b-4f01-b0d2-a8ca9751011f&DisplayLang=en