%11Database Notification Monitor failed to copy file smsxp.dll from the \SMS\bin\i386 directory to its required place in the\Windows\system32 directory. Smsxp.dll must exist in the system32 directory for all 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 Database Notification Monitor. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager 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 else 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 service can access the file. If you ignore this problem, ConfigMgr will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.%0
Data Corruption Warning If the site being introduced into the hierarchy is using a site code that was previously used within ...
Data gathering failed because the specified source hierarchy is not a supported version for migration to the destination ...
Data gathering failed because the specified source hierarchy is not a supported version for migration to the destination ...
Database Notification Monitor could not start the SMS Backup service on server %1.%12 Possible cause: You changed the service ...
Database Notification Monitor failed to copy file smsxp.dll from the \SMS\bin\i386 directory to its required place in the\Windows\system32 ...
Database Notification Monitor failed to execute database maintenance SQL Server command "%1".%12 Possible cause: The SQL ...
Database Notification Monitor failed to execute database maintenance task "%1".%12 Possible cause: A SQL Server problem prevented ...
Database Notification Monitor failed to install trigger "%1" in the site database.%12 Possible cause: Either table "%2" or ...
Database Notification Monitor is executing database maintenance SQL Server command/task "%1". You can configure the execution ...