The Inbox Manager component generates many Status ID 3600 messages in Systems Management Server 2.0 (889429)


The information in this article applies to:

  • Microsoft Systems Management Server 2.0

SYMPTOMS

The Microsoft Systems Management Server (SMS) 2.0 Inbox Manager component generates many Status ID 3600 messages in the SMS Administrator console. The following errors appear in the SMS\Logs\Inboxmgr.log file: 
Copying D:\SMS\inboxes\offerinf.box\XXXSYSTM.che to D:\CAP_XXX\offerinf.box\XXXSYSTM.che, Failed, Win32 Error = 2 ~Cannot copy directory D:\SMS\inboxes\offerinf.box\ to D:\CAP_XXX\offerinf.box\, Win32 error = 0 
STATMSG: ID=3600 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_INBOX_MANAGER" SYS=server name SITE=XXX PID=532 TID=2444 GMTDATE=Tue Nov 04 13:47:11.612 2003 ISTR0="\\server name\SMS_XXX\inboxes\offerinf.box" ISTR1="MSWNET:["SMS_SITE=XXX"]\\server name\CAP_XXX\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Skipping D:\CAP_XXX\offerinf.box\XXXzxl5q.INS, no need to copy.
Skip copying zero sized file D:\SMS\inboxes\offerinf.box\offerinf.tok to D:\CAP_XXX\offerinf.box\offerinf.tok, ignore sharing violation error.
Failed to copy D:\SMS\inboxes\offerinf.box\XXXSYSTM.che to D:\CAP_XXX\offerinf.box\XXXSYSTM.che because of sharing violation.
Cannot copy directory D:\SMS\inboxes\offerinf.box\ to D:\CAP_XXX\offerinf.box\, Win32 error = 0
STATMSG: ID=3600 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_INBOX_MANAGER" SYS=server name SITE=XXX PID=1996 TID=1652 GMTDATE=Mon Nov 03 17:02:43.984 2003 ISTR0="\\server name\SMS_XXX\inboxes\offerinf.box" ISTR1="MSWNET:["SMS_SITE=XXX"]\\server name\CAP_XXX\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Waiting for changes in inbox definition, inbox rules and inbox replication files, max wait = 900 seconds
File or directory change detected in <\\server name\SMS_XXX\inboxes\offerinf.box>
Established connection to MSWNET:["SMS_SITE=XXX"]\\server name\CAP_XXX Created lock file <\\server name\CAP_XXX\offerinf.box\inboxlck.tok>.
Note XXX is the SMS site code.

CAUSE

This problem occurs because the SMS Inbox Manager component tries to copy a temporary file that does not exist. The SMS Offer Manager component creates a temporary XXXsystm.che file in the Offerinf.box folder when the component is updating client *.ins files. The SMS Inbox Manager component tries to copy the *.che file after the SMS Offer Manager component deletes the file.

WORKAROUND

To work around this problem, use one or more of the following methods:
  • Increase the warning and critical threshold value for the SMS Inbox Manager component. By increasing the threshold value, you can prevent the component from reaching warning or critical status as frequently. To configure a threshold value, follow these steps:
    1. Start the SMS Administrator console.
    2. Expand the Site Database (site code - site name)\Site Hierarchy\site code - site name\Site Settings container, and then click Status Summarizers.
    3. Right-click Component Status Summarizer, and then click Properties.
    4. Click the Thresholds tab, and then click a message type in the Message type list.
    5. Double-click SMS_INBOX_MANAGER, increase the threshold value for the Warning and Critical messages, and then click OK.
    6. Repeat steps 4 through 5 for each message type.
  • Reduce the activity on the client access point (CAP) by adding additional CAPs or by decreasing the frequency of client-to-CAP communication. To reduce client-to-CAP communication, follow these steps:
    1. In the SMS Administrator console, expand Site Settings, and then click Client Agents.
    2. Double-click Advertised Programs Client Agent, increase the value in minutes before the client will look for new programs, and then click OK.
    3. Double-click Hardware Inventory Client Agent, increase the inventory schedule, and then click OK.
    4. Double-click Software Inventory Client Agent, increase the inventory schedule, and then click OK.
    5. Under Site Settings, click the Discovery Methods container, double-click Heartbeat Discovery, increase the Heartbeat schedule, and then click OK.
  • Reconfigure connection cycles to reduce CAP traffic.
For more information about best design practices for SMS 2.0, review the SMS 2.0 "Site Design Best Practices" document. To obtain this document, visit the following Microsoft Web site:

http://www.microsoft.com/smserver/techinfo/deployment/20/deploysms/bstprac.asp



For more information about sizing SMS 2.0 in your organization, review the Systems Management Server 2.0 Server Sizing in an Organization white paper. To obtain this white paper, visit the following Microsoft Web site:

http://www.microsoft.com/technet/prodtechnol/sms/sms2/sizing.mspx

For more information about planning your SMS site, review the Microsoft Systems Management Server Planning Guide. To obtain this guide, visit the following Microsoft Web site:

http://www.microsoft.com/resources/documentation/sms/2/all/proddocs/en-us/default.mspx


For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

317249 How to troubleshoot event ID 2021 and event ID 2022

245080 Receiving multiple instances of event ID 2022

STATUS

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

This problem is fixed in Microsoft Systems Management Server 2003.
Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbtshoot kbSMSTopazFix kbCAP kbInboxMgr kberrmsg kbnetwork kbusage kbSysSettings kbPerformance KB889429 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.