| Message ID | Severity | Message |
|---|---|---|
|
1200 |
Informational |
In the last %1 hours, SMS Status Manager processed %2 status messages. Of these, %3 were written to the site database, %4 were replicated to the parent site, %5 were reported as Windows NT events on the site server, and %6 were passed as command-line parameters to external programs. During this time, SMS Status Manager received %7 corrupt files that contained one or more status messages that could not be processed. Also during this time, Status Manager used %8 hours of CPU time, which represents a %9 percent utilization of the total CPU time available for the period. SMS Status Manager periodically reports this message for your convenience; you can ignore it if you’re not interested in monitoring SMS Status Manager’s processing performance. SMS Status Manager will report this message again in %10 hours. |
|
1201 |
Informational |
SMS Status Manager successfully initialized the “SMS Status Messages” performance object. Every time SMS Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure Status Manager’s processing performance by monitoring this performance object with the Windows NT Performance Monitor. For example, you can monitor the total number of status messages written to the site database by SMS Status Manager by monitoring the “_Total” instance of the “Written To SMS Database” counter. SMS Status Manager resets all of the counts when it is restarted, and the counts cannot be viewed when SMS Status Manager is not running. |
|
1202 |
Warning |
Due to an internal error, SMS Status Manager could not initialize the “SMS Status Messages” performance object. You can measure SMS Status Manager’s processing performance by monitoring this performance object with the Windows NT Performance Monitor. This problem will not affect SMS Status Manager’s ability to process status messages, but it will prevent you from viewing this performance object. You can ignore this problem if you do not need to view this performance object. Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
1203 |
Informational |
SMS Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. The summarizer distills the stream of status messages into a high-level summary, which you can view under the System Status node of the SMS Administrator console. You can monitor the performance of the in-memory queue in the Windows NT Performance Monitor by selecting the “SMS In-Memory Queues” performance object, and then selecting the instance for this summarizer. For example, the “Total Objects Enqueued” counter tells you how many status messages SMS Status Manager has forwarded to the summarizer. The counts are reset when both SMS Status Manager and the summarizer are restarted, which typically occurs when SMS Executive is restarted. The counts cannot be viewed when SMS Status Manager and the summarizer are both not running. |
|
1204 |
Informational |
SMS Status Manager will no longer forward status messages to the summarizer component %1 because the summarizer was disabled. The summarizer distills a stream of status messages into a high-level summary, which you can view under the System Status node of the SMS Administrator console. If you reenable the summarizer in the SMS Administrator console, SMS Status Manager will resume forwarding messages to the summarizer. |
|
1205 |
Error |
Due to an internal error, SMS Status Manager could not initialize an in-memory queue to forward status messages to the summarizer component %1. The summarizer distills the stream of status messages into a high-level summary, which you can view under the System Status node of the SMS Administrator console. Until this problem is fixed, the high-level summary will be inaccurate or not available. Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
1209 |
Warning |
SMS Status Manager has created %1 instances of the “SMS Status Messages” performance object, which is the maximum allowed number of instances. Every time SMS Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure SMS Status Manager’s processing performance by monitoring this performance object with the Windows NT Performance Monitor. Because the maximum limit was reached, SMS Status Manager will not create any more instances of this performance object. SMS Status Manager builds the list of instances as it receives status messages. You can reset the list by restarting SMS Status Manager. |
|
1210 |
Warning |
SMS Status Manager was instructed by a status filter rule to execute program and command-line arguments %1 upon receipt of a status message that satisfied the criteria specified by the status filter rule, but the program and command-line arguments are invalid. (Note that for display purposes, the program and command-line arguments were truncated to %2 characters in this message.) Possible cause: The program and command-line arguments are blank or contain an invalid escape sequence. Solution: Correct the value of the Program box on the Actions tab of the status filter rule Properties page in the SMS Administrator console. The valid escape sequences are listed in an appendix of the SMS 2.0 Administrator’s Guide. (Note that you are not limited to %2 characters in the Program box.) |
|
1211 |
Warning |
SMS Status Manager was instructed by a status filter rule to execute program %1 with command-line arguments %2 upon receipt of a status message that satisfied the criteria specified by the status filter rule. (Note that for display purposes, the program and command-line arguments were truncated to %3 characters in this message.) Status Manager failed to execute the program. Possible cause: The status filter rule specifies a program that is invalid or does not exist. Solution: Correct the value of the Program box on the Actions tab of the status filter rule Properties page in the SMS Administrator console. (Note that you are not limited to %3 characters in the Program box.) Be sure to explicitly specify the path to the program. For example, specify “c:\Winnt\System32\Net.exe” instead of just “Net.exe”. |
|
1212 |
Warning |
SMS Status Manager was instructed by a status filter rule to execute program %1 with command-line arguments %2 upon receipt of a status message that satisfied the criteria specified by the status filter rule. (Note that for display purposes, the program and command-line arguments were truncated to %3 characters in this message.) Status Manager successfully started the program, but the program was still running after 60 seconds. Possible cause: The status filter rule specifies a program that runs interactively and the program will not exit until it receives user input. This would happen, for example, if you specified “Notepad.exe” as the program. Solution: First correct the status filter rule to specify a program that runs to completion without requiring user input; this is done by editing the Program box on the Actions tab of the Status Filter Rule Properties page in the SMS Administrator console. (Note that you are not limited to %3 characters in the Program box.) Then verify that the old program is not still running on the site server using the Windows NT Task Manager. If the old program is still running, use End Process in Task Manager to stop it. Possible cause: The status filter rule specifies a program that takes a long time to run. Solution: Ignore this message, but consider changing the status filter rule to specify a program that runs quickly. Slow programs, when executed frequently, will slow down the rate at which SMS Status Manager can process status messages, and might cause a large number of running processes to build up on your site server. If too many processes build up, the general performance of the site server might be affected. |
|
1213 |
Warning |
SMS Status Manager received a status message reported by component %1 running on computer %2, and the time stamp on the message is more recent than the current system time on the site server. Possible cause: The system clock on computer %2 is %3 or more seconds ahead of the site server’s system clock. Solution: Synchronize the system clock of computer %2 with the site server’s system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. SMS Status Manager will process status messages with improper time stamps when the site server’s system clock surpasses the improper time stamps. For example, this status message will not be processed for %3 seconds. SMS Status Manager will continue to report this problem every 24 hours until you fix it. |
|
1214 |
Warning |
SMS Status Manager received a status message with an invalid time stamp. The status message was reported by component %1 running on computer %2. Possible cause: The system clock on computer %2 is not synchronized with the site server’s system clock. Most likely, the system clock on computer %2 is set to some date greater than 2035 or less than 1970. Solution: Synchronize the system clock of computer %2 with the site server’s system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. When SMS Status Manager receives status messages with invalid time stamps, it will stamp these messages with the current system time on the site server. The messages will then be processed successfully, but their time and date might not be truly representative of when they were reported in real time. SMS Status Manager will continue to report this problem every 24 hours until you fix it. |