Table 26.20 SMS SQL Monitor (Message IDs 2400 to 2412)

Message ID	Severity	Message
2400	Error	SMS SQL Monitor failed to copy file smsxp.dll from the \SMS\bin\i386 directory (or \SMS\bin\alpha if this is an Alpha computer) to its required place in the\Winnt\system32 directory. Smsxp.dll must exist in the system32 directory for all SMS triggering operations to function, such as notification to the server components of a new package or collection. Possible cause: The file %1 exists, but it is corrupt. Solution: Delete the file, and then stop and restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: The file is being read from a remote computer (the site server) that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The file smsxp.dll exists, but something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file’s permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
2401	Warning	SMS SQL Monitor failed to execute database maintenance task %1. Possible cause: A SQL Server problem prevented this task from running. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Most database maintenance tasks are designed to optimize database performance. If a task fails once, the effect on the system will be small and you can ignore the failure. But if a task fails repeatedly you should investigate and fix the problem.
2402	Error	SMS SQL Monitor failed to execute database maintenance SQL command %1. Possible cause: The SQL command contains syntax errors. Solution: Manually execute the command using the Microsoft SQL Server ISQL/w application, and fix any problems you discover. When you are satisfied the command runs successfully in ISQL/w, correct it in the SMS Administrator console. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the Smsdbmon.log for SQL Server error logs.
2404	Informational	The database maintenance SQL task %1 completed successfully. The task deleted %2 items from the SMS site database.
2405	Informational	SMS SQL Monitor is installing trigger %1 for table %2 and actions %3 in the SMS site database. Server components such as SMS Hierarchy Manager, SMS Collection Evaluator, and SMS Discovery Data Manager instruct SMS SQL Monitor to install SQL triggers. Then, when certain kinds of data are added to, changed in, or removed from the SMS site database, the SQL triggers notify SMS SQL Monitor. In turn, SMS SQL Monitor notifies the appropriate server components.
2406	Informational	SMS SQL Monitor is removing trigger %1 from the SMS site database. Server components such as SMS Hierarchy Manager, SMS Collection Evaluator, and SMS Discovery Data Manager instruct SMS SQL Monitor to install SQL triggers. Then, when certain kinds of data are added to, changed in, or removed from the SMS site database, the SQL triggers notify SMS SQL Monitor. In turn, SMS SQL Monitor notifies the appropriate server components. This trigger is being removed because it is no longer needed.
2407	Error	SMS SQL Monitor failed to install trigger %1 in the SMS site database. Possible cause: Either table %2 or column %3 of table %2 does not exist in the SMS site database. Solution: If you modified table %2, restore it to its original, unmodified state. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
2408	Informational	SMS SQL Monitor is executing database maintenance SQL command/task %1. You can configure the execution schedule for this SQL command/task in the SMS Administrator console under Site Database -> Site Hierarchy -> site code - site name -> Site Settings -> Database Maintenance -> SQL Commands or Tasks.
2409	Informational	The Delete Aged Collected Files database maintenance task completed successfully. The task deleted %1 collected files and %2 directories.
2410	Informational	The Rebuild Indexes database maintenance task successfully re-created index %1 on table %2 in the SMS site database. The Rebuild Indexes task periodically re-creates the indexes in the SMS site database to provide optimal query performance.
2411	Informational	The Rebuild Indexes task has dropped index %1 on table %2 in the SMS site database. The Rebuild Indexes task periodically recreates the indexes in the SMS site database to provide optimal query performance. The task will drop an index when the index has a density of less than 0.50, which indicates that it is not selective enough to improve query performance.
2412	Informational	The Monitor Keys and Recreate Views database maintenance task has detected less than 100 values left for key %1 and has rolled it over to %2.