The Offer Status Summarizer reports a "3812 Warning" error message after receiving a status 10000 message from a Systems Management Server 2003 Legacy Client (886108)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

When the Microsoft Systems Management Server (SMS) 2003 Offer Status Summarizer tries to process a status 10000 message that was sent from an SMS 2003 Legacy Client, the SMS 2003 Offer Status Summarizer may report the following error message:
3812 Warning SMS_OFFER_STATUS_SUMMARIZER
SMS Offer Status Summarizer cannot process a status message because it has an invalid message ID 10000.
The message ID must be within the range 10000 to 10099. As a result, the Advertisement Status summary data in the SMS Administrator console may be inaccurate. The message was reported by component "SMS System Offer Data Provider (ODP)" on computer "ComputerName" at site TWO on <date> <time>.

Please refer to the Microsoft Knowledge Base for more information.
Additionally, the Offersum.log file, located in the \SMS\Logs folder on the SMS 2003 site server, may contain a warning message that is similar to the following:
Warn>: The status message was reported by component "SMS System Offer Data Provider (ODP)" with message ID 10000 which is not within the valid range of message IDs for that component (10000 to 10099).
The message will be ignored.

CAUSE

This problem typically occurs when the .ofr advertisement file on a Client Access Point (CAP) is missing, corrupted, or missing required data. When this problem occurs, the advertisement does not run and is not displayed.

RESOLUTION

To resolve this problem, use one of the following methods:
  • Change any values in the specified advertisement in the SMS Administrator console. For example, add comments in the Comments dialog box or change the priority. This forces the SMS Offer Manager to update the advertisement files. You must wait for the SMS Inbox Manager to replicate the change to the CAPs throughout the site before refreshing the list of advertised programs on the client. To verify that the advertisement has been replicated to the CAP, follow these steps:
    1. Log on to the primary site server computer using an account that has administrative permissions.
    2. Click Start, point to Programs, point to Systems Management Server, and then click SMS Administrator Console.
    3. In the SMS Administrator Console, expand Site Database (SiteCode-SiteName), expand System Status, and then click Advertisement Status.
    4. Make sure that the advertisement appears in the details pane.
  • Copy an uncorrupted version of the .ofr AdvertisementID file from the Sms\Inboxes\Offerinf.box folder of the parent site to the Sms\Inboxes\Offermgr.box\Incoming folder where AdvertisementID is the Advertisement ID of the advertised package.

    This overwrites the file in the Sms\Inboxes\Offermgr.box folder and processing proceeds normally.
  • Remove the corrupted .ofr AdvertisementID file in the Sms\Inboxes\Offermgr.box folder. To identify the corrupted .ofr AdvertisementID file, compare the .ofr files to those at the parent site in the Sms\Inboxes\Offerinf.box folder. After you remove the file, copy the .ofr AdvertisementID file for the advertisement from the Sms\Inboxes\Offermgr.box folder to the Sms\Inboxes\Offermgr.box\Incoming folder.

    This triggers an advertisement evaluation cycle. Although this enables other advertisements to be processed, the corrupted advertisement must be re-created to be processed successfully.
If the problem persists, look for disk problems on the CAP or for other external causes of file corruption.
Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbtshoot kbprb KB886108 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.