Thread Component on the Site Server

Thread Component on the Site Server documents how status messages are processed after they are generated by thread components on the site server, including how status messages are reported to Status Manager for processing and how status messages are logged to the Windows NT Application Event Log.

The actions illustrated in this flowchart take place on the site server. For information about how status messages are processed by Status Manager on the site server, see Figure 23.4, “Status Manager”, later in this chapter.

Troubleshooting Tips

If status messages are not being properly reported to Status Manager for processing:

• On the server where the component is running, examine SMS\Logs\<Component>.log. Verify that the log file contains an entry generated at the time you believe a status message should be generated that begins with “STATMSG” as shown in the following example:

  STATMSG: ID=2808 SEV=I LEV=M SOURCE="SMS Server"COMP="SMS_SITE_CONTROL_MANAGER" SYS=SPIKE SITE=S9K PID=461 TID=441GMTDATE=Mon Dec 07 20:39:15.906 1998ISTR0="C:\SMS\inboxes\sitectrl.box\incoming\9EOR03Q7.CT1"ISTR1="SMS_INBOX_MANAGER" ISTR2="smsservice" ISTR3="SPIKE"ISTR4="1998 12 1 07 20 38 53 000" ISTR5="" ISTR6="" ISTR7="" ISTR8=""ISTR9="" NUMATTRS=0 $$<SMS_SITE_CONTROL_MANAGER><Mon Dec 0712:39:15.906 1998 Pacific Standard Time><thread=441 (0x1B9)>

  • Note the value of “SEV=X” in the “STATMSG” log file entry. X specifies the severity of the status message where “I” is Informational, “W” is Warning, and “E” is Error.
  • Note the value of “LEV=X” in the “STATMSG” log file entry. X specifies the level of the status message where “M” is Milestone and “D” is Detail.
• Examine the Status Reporting settings for server components. Verify that the settings are configured to report this status message, based on its severity and level. If the settings are not configured to report this status message, it will not be reported to Status Manager.

  Systems Management Server   Site Database (site code - site name)      Site Hierarchy         site code - site name            Site Settings               Component Configuration                  Status Reporting

• Check whether the next log file entry after the “STATMSG” log file entry begins with the text “CServerStatusReporter.” If it does, the component may have encountered a problem reporting the status message to Status Manager, and the problem will be explained in the log file.
• Verify that at the time the “STATMSG” entry was written to the log file, the status message was placed into the in-memory queue of status messages that flows from the thread components to Status Manager. To do this, start the Windows NT Performance Monitor, click the Add Counter button (which looks like a +), select the SMS In-Memory Queues object, select the Total Objects Enqueued counter, select the Status Messages from SMS_EXECUTIVE to SMS_STATUS_MANAGER instance, and click OK. Now verify that the count increases by one just after the “STATMSG” entry is written to the log file.

If status messages are not being reported to the Windows NT Application Event Log and the Status Reporting settings are configured for them to be reported:

• On the site server, examine SMS\Logs\<Component>.log. Verify that the log file contains an entry beginning with “STATMSG” that was generated at the time you believe a status message should be generated.
  • Note the value of “SEV=X” in the “STATMSG” log file entry. X specifies the severity of the status message where “I” is Informational, “W” is Warning, and “E” is Error.
  • Note the value of “LEV=X” in the “STATMSG” log file entry. X specifies the level of the status message where “M” is Milestone and “D” is Detail.
• Examine the Status Reporting settings for server components. Verify that the settings are configured to log this status message to the Windows NT Application Event Log, based on its severity and level. If the settings are not configured to log this status message, it will not be logged to the event log.

  Systems Management Server   Site Database (site code - site name)      Site Hierarchy         site code - site name            Site Settings               Component Configuration                  Status Reporting

• Check whether the next log file entry after the “STATMSG” log file entry begins with the text “CServerStatusReporter.” If it does, the component may have encountered a problem logging the status message to the Windows NT Application Event Log, and the problem will be explained in the log file.
• Using the Windows NT Event Viewer, verify that at the time the “STATMSG” entry was written to the log file, the status message was logged to the Windows NT Application Event Log on the site server.