The Status Message Viewer

With the Status Message Viewer, you view status messages by querying the SMS site database through the SMS Provider. You can launch the Status Message Viewer from various places within the SMS Administrator console. For example, the status summaries contained in the SMS Administrator console show you the condition of your SMS site, components, packages, and advertisements. When you detect a problem at this level, you can start the Status Message Viewer to identify the problem more specifically.

To launch the Status Message Viewer, navigate to Component Status in the SMS Administrator console.


Systems Management Server>Site Database (site code - site name)>System Status>Site Status>site code - site name>Component Status

Select Component Status. When the component list appears in the details pane, select a component, right-click, and then click Show Messages. Each time you launch the Status Message Viewer, you must select which messages to view based on message severity: All, Errors, Warnings, or Informational. Select one of these items. The Status Message Viewer appears and displays the status messages for the selected component on the site system that you selected.

Status messages are also based on the queries you specify in the menus leading to the viewer. The different queries you can specify depend on the where you are in Site Status when you launch the viewer. For more information, see the "Interpreting System Status" section later in this chapter.

Alternatively, you can launch the Status Message Viewer from Package Status and Advertisement Status. Table 14.1 describes the Status Message Viewer columns.

Table 14.1 Status Message Viewer Columns

Column name



Error, warning, or informational.


Milestone, detail, or audit.


The time and date the status message was generated.

Site code

The site code where the status message was generated.


The computer name where the status message was generated.


The name of the SMS component that generated the status message.

Message ID

The message ID of the status message.


The text of the status message.

When you double-click a status message in the viewer, the Status Message Details dialog box appears with more details about the message, including the Process ID, Thread ID, message text, and optional message properties.

Table 14.2 summarizes the message viewer features that help you use the viewer.

Table 14.2 Status Message Viewer Features

By using this feature

You can do this


Change the column widths.

Add and remove columns and change their display order.


Copy status messages to your clipboard with tab- or comma- delimited columns to support paste to Excel and text editors.


Delete selected status messages from the SMS site database.

Filter on a Per Column Basis

Filter on a column basis by selecting the filter icon.

Filter on specific characteristics such as message severity, message type, and site code,.


Find specific status messages or all messages with specific characteristics such as message severity, message type, and site code.

Font Selection

Change the font type used to display status messages.

Multiple Viewers

Launch multiple status viewers to compare messages for troubleshooting purposes.

Multi-Selecting Rows

Select multiple rows in the Status Viewer by using the standard Shift + Select and Ctrl + Select methods.

Save and Print

Save and print status messages by using comma or tab delimiters and by using multi-select or All for options.

Saving status messages to files allows you to save specific sets of status messages that might be important beyond the routine, seven-day period. By default, SMS deletes most status messages after seven days. Due to the large number of status messages generated, it is important that you configure them to be deleted frequently.

Sort on a Per-Column Basis

Sort all messages based on a specific column by clicking on a column title. The messages appear sorted based on the column you select.

For More Information

Did you find this information useful? Please send your suggestions and comments about the documentation to