%11SMS management point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. %12 Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the computer running SQL Server site system is turned on, connected to the network, and functioning properly. Possible cause: Management point does not have sufficient access rights to the SQL server site system. Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: Network problems are preventing the management point from properly accessing the SQL Server. Solution: Investigate and correct any problems with your network. Possible cause: The management point having problems is at a secondary site, and SQL access account being used was recently reset by the parent site. Solution: This can automatically repair itself after one hour , as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you can stop and start the SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration. Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.%0
SMS Inventory Data Loader is updating database statistics for all inventory-related tables. By default, statistics are updated ...
SMS Inventory Data Loader requested a resynchronization for machine "%1" because a hardware inventory file was sent without ...
SMS Inventory Processor failed to process inventory RAW file %1.%12 Possible cause: The file might be corrupt. Solution: ...
SMS Inventory Processor failed to process MIF file %1.%12 Possible cause: The MIF file is not formatted correctly. Solution: ...
SMS management point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. ...
SMS NDS Logon Discovery Manager detected that there is no NetWare NDS redirector installed on the site server. SMS NDS Logon ...
SMS NDS Logon Discovery Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is ...
SMS NDS Logon Discovery Manager failed to read file "%1", which contains the configuration of SMS NDS Logon Server Manager.%12 ...
SMS NDS Logon Discovery Manager failed to update the configuration of SMS NDS Logon Server Manager.%12 Solution: Review the ...