The first one is related to failures when sending to a child site, and the second is in regards to the SMS performance counter and is really more informational than anything.

Error message in the Sched.log file in SMS 2003 with Service Pack 2: "WARNING: Found duplicate Send Request ID already exists"

SYMPTOMS

You experience the following symptoms in a Microsoft Systems Management Server (SMS) 2003 site hierarchy:

CAUSE

This problem may occur if a duplicate send request ID is generated in SMS 2003. You may experience this problem if the following conditions are true:

Send request IDs can have a maximum number of 46,656 unique values before they restart. A send request that is sent to a remote site that has a slow link may take seven days to be processed or to be deleted.

Note The SMS Scheduler deletes active send requests that are over seven days old.

In a three-tier site hierarchy, send request IDs may reach the maximum number of unique values and restart as frequently as one time per week. Typically, duplicate send request IDs are located in the Sms\Inboxes\Schedule.box\Outboxes\lan folder. However, duplicate send requests IDs may also be located in the Sms\Inboxes\Schedule.box\Requests folder.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

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

Prerequisites

No prerequisites are required to install this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

STATUS

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

MORE INFORMATION

After you install this hotfix, SMS 2003 automatically generates a new send request ID when it detects duplicate send request IDs. This allows for the immediate processing of all the send requests in a routing request. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (http://www.kbAlertz.com/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

If you experience this symptom on a site that is running SMS 2003 with SP1, see the follow Microsoft Knowledge Base article:

http://www.kbalertz.com/Feedback.aspx?kbNumber=886685 (http://support.microsoft.com/default.aspx?scid=kb;en-us;886685)

Error message is logged in Systems Management Server 2003: "ERROR: Could not initialize the "Computer <ComputerName>" instance of the "SMS Status Messages" performance object"

View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure that you 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 (http://www.kbAlertz.com/Feedback.aspx?kbNumber=256986/) Description of the Microsoft Windows registry

SYMPTOMS

You experience the following symptoms on a Microsoft Systems Management Server (SMS) 2003 Service Pack 2 (SP2) site server:

CAUSE

This issue occurs if the SMS 2003 Status Manager component exceeds the maximum number of performance instances that are available for a performance object. This issue does not indicate that a problem exists with SMS 2003.

The SMS performance counter library is a new feature in SMS 2003 SP2. By default, this component has 256 kilobytes (KB) available from which to create instances of SMS performance objects. However, because SMS performance object instances are created per computer, this limit may be exceeded.

Note The block of memory that is used for the SMS performance counter library is shared by the SMSEXEC process and other processes that monitor performance counters, such as the Perfmon.exe counter.

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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this issue, increase the RAM that is available for use by the SMS performance counter library. To do this, follow these steps: