%11SMS 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.%12 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.%0
SMS Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. %12 ...
SMS SQL Backup service on the SQL server %1 did not start the SMS database backup. SMS SQL Backup service might not be running ...
SMS SQL Backup service on the SQL server %1 failed to backup the SMS database %2. The error reported by the service is %3. ...
SMS SQL Monitor could not start the SMS Backup service on server %1.%12 Possible cause: You changed the service setting for ...
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) ...
SMS SQL Monitor failed to execute database maintenance SQL command "%1".%12 Possible cause: The SQL command contains syntax ...
SMS SQL Monitor failed to execute database maintenance task "%1".%12 Possible cause: A SQL Server problem prevented this ...
SMS SQL Monitor failed to install trigger "%1" in the SMS site database.%12 Possible cause: Either table "%2" or column "%3" ...
SMS SQL Monitor is executing database maintenance SQL command/task "%1". You can configure the execution schedule for this ...