Knowledge Base

SMS: Status Message Flood from Child or Secondary Servers

Article ID: 297870

Article Last Modified on 10/27/2006

APPLIES TO

Microsoft Systems Management Server 2.0 Standard Edition
Microsoft Systems Management Server 2.0 Service Pack 1
Microsoft Systems Management Server 2.0 Service Pack 2
Microsoft Systems Management Server 2.0 Service Pack 3

This article was previously published under Q297870

SYMPTOMS

Systems Management Server (SMS) version 2.0 child or secondary sites may cause a "storm" of status messages to be sent to the primary site. Specifically, Site Control Manager may repeatedly create 10 status messages each second. The following information is an example of one iteration of the problem:

------
Processing delta site control file 
"C:\SMS\inboxes\sitectrl.box\incoming\8B4NFYM5.CT1"...
the delta site control file 
"C:\SMS\inboxes\sitectrl.box\incoming\8B4NFYM5.CT1" contains a record 
submitted by server component SMS_SITE_CONTROL_MANAGER running as user 
SMSService on computer CAIXATEST on Fri Apr 20 21:21:42 GMT.

TATMSG: ID=2808 <Rest of text deleted for readability>
WARNING: The "Site Definition" item in a record contained in delta site 
control file "C:\SMS\inboxes\sitectrl.box\incoming\8B4NFYM5.CT1" specifies
an invalid public key for decrypting the SMS service account and password.
This record and the remaining records in the file are unusable.

TATMSG: ID=2847 <Rest of text deleted for readability>
Deleted file "C:\SMS\inboxes\sitectrl.box\incoming\8B4NFYM5.CT1".
WARNING: Aborted processing of delta site control file 
"C:\SMS\inboxes\sitectrl.box\incoming\8B4NFYM5.CT1".  
TATMSG: ID=2800 <Rest of text deleted for readability>
TATMSG: ID=508 <Rest of text deleted for readability>
TATMSG: ID=2804 <Rest of text deleted for readability>
------

The preceding iteration takes less than a second to complete. Typically two iterations each second occur, which equals 10(5*2) status messages a second. 10*60*60 equals 360,000 status messages an hour.

CAUSE

This problem can occur if both of the following conditions exist:

The time zone has been changed.
The system Microsoft Windows NT Cryptography key has been reset.

NOTE: As of June 28, 2001, Microsoft NetMeeting with Remote Desktop sharing enabled is known to reset the Windows NT Cryptography key. However, other programs may also reset the key and satisfy the second condition for this problem to occur.

RESOLUTION

To resolve this problem, obtain the latest service pack for Systems Management Server version 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

288239 SMS: How to Obtain the Latest Systems Management Server 2.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Systems Management Server 2.0 Service Pack 4.

Additional query words: prodsms sitectrl

Keywords: kbhotfixserver kbqfe kbbug kbenv kbfix kbserver kbsitecomp kbsms200presp4fix kbstatsum KB297870

Microsoft KB Archive/297870

Contents