Service Component on the Site Server, and Thread and Service Components Not on the Site Server

This flowchart documents how status messages are processed after they are generated by service components on the site server, or by thread or service components on site systems other than the site server. Server components (both service and thread) write information, warning, and error status messages that document their processing. Service components on the site server and thread and service components running on site systems use the same process for reporting status messages. The flowchart illustrates 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 computer that generated the status message. 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 a status message is not 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.
• Check the Status Reporting settings for server components. Verify that the settings are configured to report this status message, given 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.
• Check whether a *.svf file was created in the SMS\Inboxes\Statmgr.box \Statmsgs directory on the site server at the same time that the “STATMSG” entry was written to the log file. Note that if Status Manager is running, it may detect the *.svf file, process it, and delete it so quickly that you do not see it appear. To prevent this, you can stop Status Manager using the SMS Service Manager. Remember to restart Status Manager when you are finished troubleshooting. If you do not want to stop Status Manager, you can monitor its processing using the Windows NT Performance Monitor to verify that it received the *.svf file. To do this, start the Performance Monitor on the site server, click the Add Counter button (which looks like a +), select the SMS Status Messages object, select the Received counter, select the Component ==>  <ComponentName> instance, and click OK. Verify that the count increases by one just after the “STATMSG” entry is written to the log file.
• If the *.svf file was not created in the SMS\Inboxes\Statmgr.box\Statmsgs directory on the site server, verify that it was created in the %SystemRoot% \System32\SMSMsgs\XYZ directory on the server where the component is running. (XYZ is the name of the executable file for the component process. For example, for thread components, XYZ will be “Smsexec.”) The component creates the *.svf file in this directory when the site server is inaccessible or out of disk space.
• If the *.svf file was created in the %SystemRoot%\System32\SMSMsgs\XYZ directory on the server where the component is running, it will remain in that directory until the component attempts to report another status message. At that time, if the new status message is successfully written to a *.svf file in the SMS\Inboxes\Statmgr.box\Statmsgs directory on the site server, the component will move all of the *.svf files in the %SystemRoot%\System32 \SMSMsgs\XYZ directory to the SMS\Inboxes\Statmgr.box\Statmsgs directory. Note that when a *.svf file is moved, it will be given a new *.svf filename in the SMS\Inboxes\Statmgr.box\Statmsgs directory.

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 server where the component is running, 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 server where the component is running.