SMS server state messages
List of SMS server State Messages. This list was originally posted into Microsoft TechNet by Klaus Bilger. Click here to view the TechNet article.
| MessageID | MessageString | Severity |
|---|---|---|
| 10000 | Failed to initialize. Please refer to cloudusersync.log for further details. | Error |
| 10001 | Got exception on method call %1. Please refer to cloudusersync.log for further details. Exception: %2 | Error |
| 10002 | CloudUserSync - delta sync to cloud failed. Please refer to cloudusersync.log for further details. | Error |
| 10003 | CloudUserSync - consistency check to cloud failed. Please refer to cloudusersync.log for further details. | Error |
| 10004 | CloudUserSync - full sync to cloud failed. Please refer to cloudusersync.log for further details. | Error |
| 10005 | CloudUserSync - Duplicate principal names found for users in cloud collection. Some users were not enabled for cloud services. Please refer to cloudusersync.log for further details. | Warning |
| 10006 | CloudUserSync - Empty principal names found for users in cloud collection. Some users were not enabled for cloud services. Please refer to cloudusersync.log for further details. | Warning |
| 10007 | CloudUserSync - A large number of users has been selected for delta sync. Ensure that these are previously unsynced users. Please refer to cloudusersync.log for further details. | Warning |
| 1001 | The Active Directory forest designed to store the Configuration Manager health state references has not been extended with the Configuration Manager 2007 schema extensions. The error encountered was %1. Solution: Either extend the schema for the currently designated Active Directory forest, or configure Network Access Protection to store the health state references in a different Active Directory forest that has the Configuration Manager 2007 schema extensions. For more information about extending the schema, see the Help topic How to Extend the Active Directory Schema for Configuration Manager. For more information on configuring the location of the health state references, see the Help topic How to Specify the Location of the Health State Reference. | Error |
| 1002 | The Active Directory (AD) Cache Client failed to search the AD Forest for NAP-related Configuration Manager Health Information. The error encountered was %1. | Error |
| 1003 | The file cache store in the System Health Validator point failed to initialize properly. The error encountered was %1. | Error |
| 1004 | The File Cache Store update failed. This will potentially cause the Configuration Manager System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1. | Error |
| 1005 | The File Cache Store could not be persisted to disk properly. This will potentially cause the Configuration Manager System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1. | Error |
| 1006 | The Configuration Manager System Health Validator Registry Settings failed to get loaded properly. This will prevent the Configuration Manager System Health Validator Service from functioning properly. The error encountered was %1. | Error |
| 1007 | Changes to Configuration Manager System Health Validator Registry Settings failed to get processed properly. This might prevent the Configuration Manager System Health Validator Service from functioning as desired. The error encountered was %1. | Error |
| 1008 | The Configuration Manager System Health Validator Service failed to initialize properly. The error encountered was %1. | Error |
| 1009 | The AD Cache Client failed to initialize properly. The error encountered was %1. | Error |
| 10100 | The APNs account cert has expired, follow the Request Apple Notification Service CSR process to request a new APNs account cert. | Error |
| 10101 | An update is required for Windows Intune integration with Configuration Manager. More information on the update can be found here: %1. | Error |
| 1013 | Site Component Manager detected that this component should be installed on this site system. Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds. | Informational |
| 1014 | Site Component Manager is installing this component on this site system. | Informational |
| 1015 | Site Component Manager successfully installed this component on this site system. | Informational |
| 1016 | Site Component Manager failed to install this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in %1 minutes. To force Site Component Manager to immediately retry the installation, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 1017 | Site Component Manager detected that this component should be reinstalled on this site system. Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds. | Informational |
| 1018 | Site Component Manager is reinstalling this component on this site system. | Informational |
| 1019 | Site Component Manager successfully reinstalled this component on this site system. | Informational |
| 1020 | Site Component Manager failed to reinstall this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in %1 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 10201 | Certificate Registration Point is responding to HTTP requests. | Informational |
| 10202 | Certificate Registration Point is not responding to HTTP requests. The error encountered was %1. Please refer to crpctrl.log for further details. | Error |
| 10203 | Network Device Enrollment Service %1 is responding to HTTPS requests. | Informational |
| 10204 | Network Device Enrollment Service %1 is not responding to HTTPS requests. The error encountered was %1. Please refer to crpctrl.log for further details. | Error |
| 10205 | Certificate is issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. Certificate is valid till %6. | Informational |
| 10206 | Certificate deployed to machine/device %1 (GUID:%2) for user %3 with thumbprint %4 has expired. This certificate was issued against CI Id %5. | Informational |
| 10207 | Certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4 was revoked successfully. This certificate was issued against CI Id %5. | Informational |
| 10208 | Certificate Registration Point failed to revoke certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. The error encountered was %6. | Error |
| 10209 | Certificate is renewed for machine/device %1 (GUID:%2) for user %3. Old thumbprint of the certificate is %4. New thumbprint of the certificate is %5. This certificate was issued against CI Id %6. New certificate is valid till %7. | Informational |
| 1021 | Site Component Manager detected that this component should be deinstalled from this site system. Site Component Manager will attempt to deinstall the component every %1 minutes. Site Component Manager will abort the deinstallation if it fails to succeed after %2 minutes. | Informational |
| 10210 | Certificate Registration Point failed to renew certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. The error encountered was %6. | Error |
| 1022 | Site Component Manager is deinstalling this component from this site system. | Informational |
| 1023 | Site Component Manager successfully deinstalled this component from this site system. | Informational |
| 1024 | Site Component Manager failed to deinstall this component from this site system. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the deinstallation in %1 minutes. To force Site Component Manager to immediately retry the deinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 1025 | Site Component Manager failed to deinstall this component from this site system. | Error |
| 1026 | Site Component Manager is configuring site system "%1" to receive Configuration Manager Server Components. | Informational |
| 1027 | Site Component Manager successfully configured site system "%1" to receive Configuration Manager Server Components. Site Component Manager will now begin installing the components on the site system. | Informational |
| 1028 | Site Component Manager failed to configure site system "%1" to receive Configuration Manager Server Components. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager cannot install any Configuration Manager Server Components on this site system until the site system is configured successfully. Site Component Manager will automatically retry this operation in %2 minutes. To force Site Component Manager to immediately retry this operation, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 1029 | Site Component Manager is reconfiguring site system "%1" to receive Configuration Manager Server Components. | Informational |
| 1030 | Site Component Manager successfully reconfigured site system "%1" to receive Configuration Manager Server Components. Site Component Manager will now begin reinstalling the components on the site system. | Informational |
| 10301 | The Certificate Manager failed to revoke the certificate (Cert Serial Number: %1) issued to the device/requester %2/%3 on the Certification Authority %4. Possible cause: The central site server does not have permission to revoke certificate on this Certification Authority. Action to take: Make sure that the site server has the permission to revoke certificates on the Certification Authority or ask the CA administrator to revoke the certificate manually. Possible cause: The certification authority is not reachable or not working properly. Action to take: Ensure that the certification authority is reachable and functional. | Error |
| 1031 | Site Component Manager failed to reconfigure site system "%1" to receive Configuration Manager Server Components. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager cannot reinstall any Configuration Manager Server Components on this site system until the site system is reconfigured successfully. Site Component Manager will automatically retry this operation in %2 minutes. To force Site Component Manager to immediately retry this operation, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 1032 | Site Component Manager detected that all Configuration Manager Server Components have been deinstalled from site system "%1". Site Component Manager is removing remaining accounts, files, and registry keys associated with the Configuration Manager Server Components from the site system. | Informational |
| 1033 | Site Component Manager successfully removed all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1". | Informational |
| 1034 | Site Component Manager failed to remove all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1". Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry this operation in %2 minutes. To force Site Component Manager to immediately retry this operation, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 1035 | Site Component Manager failed to remove all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1". | Error |
| 1036 | Site Component Manager could not access site system "%1" due to an unexpected failure within the network abstraction layer (NAL). Solution: To examine the exact failure, turn on logging for Site Component Manager using the Configuration Manager Service Manager, wait for Site Component Manager to retry this operation, and review the log messages for Site Component Manager. Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1037 | Site Component Manager could not access site system "%1". Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to connect to the site system. Solution: Verify that the Site Server's computer$ account has administrator rights on the remote site system. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend on using it as a site system any more. Solution: Remove this site system from the list of site systems for this site. The list appears in the Site Systems node of the Administrator console. | Error |
| 1038 | Site Component Manager detected that site system "%1" is not running the Microsoft Windows Server operating system. Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to your Configuration Manager documentation to determine the required version. Possible cause: You accidentally configured the site to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager Console. | Error |
| 1039 | Site Component Manager detected that the site server does not contain the binary files for the platform (processor architecture) of site system "%1". Possible cause: When installing this site, you did not specify that the binary files for this site system's platform should be installed on the site server. Solution: Use Configuration Manager Setup to modify the configuration of this site. When asked to select the server platforms for this site, select this site system's platform. Possible cause: You accidently configured the site to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager Console. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing to the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1040 | Site Component Manager detected that site system "%1" is based on an Intel x86 or compatible platform (processor architecture). | Informational |
| 1041 | Site Component Manager detected that site system "%1" is based on the Alpha platform (processor architecture). | Informational |
| 1042 | Site Component Manager could not detect which version of the Microsoft Windows Server operating system is running on site system "%1". Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to your ConfigMgr Documentation to determine the required version. Possible cause: You accidentally configured the site to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager Console. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1043 | Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2, which is not a supported operating system for this version of SMS. Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to your ConfigMgr Documentation to determine the required version. Possible cause: You accidentally configured the site to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager Console. | Error |
| 1044 | Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3, which is not a supported operating system for this version of Configuration Manager. Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to your ConfigMgr Documentation to determine the required version. Possible cause: You accidentally configured the site to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager Console. | Error |
| 1045 | Site Component Manager detected that site system "%1" is running the Microsoft Windows Workstation operating system, which is not a supported operating system for this version of SMS. Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to your ConfigMgr Documentation to determine the required version. Possible cause: You accidentally configured the site to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager Console. | Error |
| 1046 | Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2. | Informational |
| 1047 | Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3. | Informational |
| 1048 | Site Component Manager detected that site system "%1" is currently in use by ConfigMgr site %2. Possible cause: You accidentally configured this site system as part of this site and as part of site %2. Solution: Remove this site system from the list of site systems for this site or for site %2. | Error |
| 1049 | Site Component Manager could not find an NTFS partition on site system "%1" to hold the Configuration Manager Server Components' files. Possible cause: The site system does not contain an NTFS partition. Solution: Using the Windows Disk Administrator, create an NTFS partition on the site system, or convert an existing FAT partition to NTFS. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. Configuration Manager requires these shares. Please re-enable these shares using the Windows Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the accounts are properly configured to allow the site server to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1050 | Site Component Manager could not create the Configuration Manager Server Components' installation directory "%2" on site system "%1" or set the correct permissions on the directory. Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. Configuration Manager requires these shares. Please re-enable these shares using the Windows Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the accounts are properly configured to allow the site server to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1051 | Site Component Manager created the Configuration Manager Server Components' installation directory "%2" on site system "%1". Site Component Manager selected this partition because it was the NTFS partition with the most free space. | Informational |
| 1052 | Site Component Manager could not create the "%2" account on site system "%1". Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When Site Component Manager installs services on the site system, it will configure them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system. | Error |
| 10526 | ;The worker for syncing licensed applications from the Windows Store for Business failed to initialize properly on the Service Connection Point. | Error |
| 10527 | Successfully completed sync and download if application of licensed applications for registered tenant from the Windows Store for Business. | Informational |
| 10528 | Failed to sync licensed applications from the Windows Store for Business. | Error |
| 10529 | Failed to download package content or license blob for licensed application(s) from the Windows Store for Business. | Error |
| 1053 | Site Component Manager created the "%2" account on site system "%1". When Site Component Manager installs services on the site system, it will configure them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system. | Informational |
| 10530 | Failed to authenticate with Azure Active Directory. For more information, view the WsfbSyncWorker.log for the SMS_CLOUDCONNECTION component. Possible cause: The Azure Active Directory app defined for Windows Store for Business to sync with is not configured as the management tool in Windows Store for Business for your tenant. Solution: Select and activate the Azure Active Directory application as the management tool in the Windows Store for Business web portal. Possible cause: The secret key used for the Windows Store for Business management tool is expired. Solution: Remove the Windows Store for Business account in the Configuration Manager console, then add it again with the correct information. Possible cause: The machine where the SMS_CLOUDCONNECTION component is installed does not have access to AAD. Solution: If needed, set the proxy to enable redirection to Azure Active Directory in the Service connection point role. You may have to reinstall the role to change the proxy settings. Solution: Open up the address/port for smsexec.exe to access on the server. Possible cause: The Azure Active Directory app defined for Windows Store for Business to sync with has been deleted from Azure Active Directory. Solution: Remove the Windows Store for Business account in the Configuration Manager console, then add it again with the correct information. | Error |
| 1054 | Site Component Manager could not verify that the "%2" account exists on site system "%1". Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When Site Component Manager installs services on the site system, it will configure them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system. | Error |
| 1055 | Site Component Manager could not read the Network Connection account data, which is stored in the installation directory on the site server. Possible cause: The data is corrupt. Possible cause: Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1056 | Site Component Manager could not write Network Connection account data to the installation directory "%2" on site system "%1". Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: Ensure that the default drive letter shares are enabled. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1057 | Because site system "%1" might have malfunctioned, as a safety measure Site Component Manager will attempt to reconfigure it to receive Configuration Manager Server Components and reinstall all of the Configuration Manager Server Components on it. This attempt will occur in %2 minutes. | Informational |
| 1058 | Site Component Manager could not remove the "%2" account from site system "%1". Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1059 | Site Component Manager removed the "%2" account from site system "%1". | Informational |
| 1060 | Site Component Manager could not remove the Configuration Manager installation directory "%2" on site system "%1". Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: Enable the default drive letter shares on the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1061 | Site Component Manager removed the Configuration Manager Server Components' installation directory "%2" on site system "%1". | Informational |
| 1062 | Site Component Manager detected that the service account has changed, and will now reinstall all of the Configuration Manager Server Components that are installed on the site server. | Informational |
| 1063 | Site Component Manager was instructed by Configuration Manager Setup to shut down the site in preparation for a site upgrade, modification, or reset operation. Site Component Manager will now stop all of the Configuration Manager Server Components on all of the site systems, mark all of these components for reinstallation, and then stop itself. Site Component Manager will reinstall all of the components when it is restarted by Configuration Manager Setup at the end of the site upgrade, modification, or reset operation. | Informational |
| 1064 | Site Component Manager is stopping all of the Configuration Manager Server Components on site system "%1". | Informational |
| 1065 | Site Component Manager will not stop any Configuration Manager Server Components on site system "%1" because no Configuration Manager Server Components are installed on the site system. | Informational |
| 1066 | Site Component Manager will now try again to stop all of the Configuration Manager Server Components on site system "%1", as requested by Configuration Manager Setup. | Informational |
| 1067 | Site Component Manager will now cease trying to stop all of the Configuration Manager Server Components on site system "%1", as requested by Configuration Manager Setup. The Configuration Manager Server Components were not properly deinstalled from the site system. Solution: Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 1068 | Site Component Manager was instructed by Configuration Manager Setup to deinstall the site. Site Component Manager will now deinstall all of the Configuration Manager Server Components from all of the site systems. | Informational |
| 1069 | Site Component Manager is deinstalling all of the Configuration Manager Server Components from site system "%1". | Informational |
| 1070 | Site Component Manager will not deinstall any Configuration Manager Server Components from site system "%1" because no Configuration Manager Server Components are installed on the site system. | Informational |
| 1071 | Site Component Manager will now try again to deinstall all of the Configuration Manager Server Components from site system "%1", as requested by Configuration Manager Setup. | Informational |
| 1072 | Site Component Manager will now cease trying to deinstall all of the Configuration Manager Server Components from site system "%1", as requested by Configuration Manager Setup. The Configuration Manager Server Components were not properly deinstalled from the site system. Solution: Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 1073 | Site Component Manager could not detect how much disk space was available in the "%1" directory on this site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to connect to the site system. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1074 | Site Component Manager cannot install this component on this site system because %1 bytes are required on the drive containing the "%2" directory, but only %3 bytes are available. Solution: Make at least %1 available on the drive containing the "%2" directory. | Error |
| 1075 | Site Component Manager detected that %1 bytes are required by this component on the drive containing the "%2" directory, and that %3 bytes are available. Site Component Manager will proceed with the installation of this component. | Informational |
| 1076 | Site Component Manager could not copy file "%1" to "%2". Site Component Manager reports this error when it fails to: 1. Create the destination directory, if it does not already exist. 2. Assign the proper directory permissions to the destination directory. 3. Copy the source file to the destination directory. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1077 | Site Component Manager could not copy file "%1" to "%2". Site Component Manager reports this error when it fails to: 1. Create the destination directory, if it does not already exist. 2. Copy the source file to the destination directory. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. | Error |
| 1078 | Site Component Manager copied file "%1" to "%2". | Informational |
| 1079 | Site Component Manager did not copy file "%1" to "%2", because the source file is not a newer version than the destination file. | Informational |
| 1080 | Site Component Manager detected that the %1 service was installed on site system "%2", but Site Component Manager could not deinstall the service. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Site Component Manager uses the %1 service to install Configuration Manager Server Components, and cannot install component %3 until the existing %1 service can be deinstalled. If this problem persists and you cannot fix it, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1081 | Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3". Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Configuration Manager cannot install component %4 until the %1 service can be installed. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1082 | Site Component Manager could not start the %1 service on site system "%2" to install component %4 with the service logging on as account "%3". Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. | Error |
| 1083 | Site Component Manager successfully used the %1 service to run the following program on site system "%2": %3 %4 %5 The program failed for the following reason: %6 Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Site Component Manager cannot install component %7 until the program runs successfully. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1084 | Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3". Possible cause: You deleted account "%3" or changed its password, but forgot to notify SMS. Solution: Use Configuration Manager Setup to modify the installation of the site. Specify the correct account and password in Configuration Manager Setup. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the iste to administer the site system. Possible cause: The Microsoft Visual C++ 2008 SP1 runtime libraries are not installed. Solution: Install the Microsoft Visual C++ 2008 SP1 Redistributable Package from the Microsoft Download Center. | Error |
| 1085 | Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3". Possible cause: You deleted account "%3" or changed its password, but forgot to notify SMS. Solution: Use Configuration Manager Setup to modify the installation of the site. Specify the correct account and password in Configuration Manager Setup. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Possible cause: The account "%3" is disabled. Solution: Enable the account. Possible cause: The Microsoft Visual C++ 2008 SP1 runtime libraries are not installed. Solution: Install the Microsoft Visual C++ 2008 SP1 Redistributable Package from the Microsoft Download Center. | Error |
| 1086 | Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3". Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. Possible cause: The Microsoft Visual C++ 2008 SP1 runtime libraries are not installed. Solution: Install the Microsoft Visual C++ 2008 SP1 Redistributable Package from the Microsoft Download Center. | Error |
| 1087 | Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3". Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. If advanced security verify the site server machine account is properly configured to allow the site to administer the site system. Possible cause: The Microsoft Visual C++ 2008 SP1 runtime libraries are not installed. Solution: Install the Microsoft Visual C++ 2008 SP1 Redistributable Package from the Microsoft Download Center. Possible cause: The account "%3" is disabled. Solution: Enable the account. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1088 | Site Component Manager installed the %1 service on site system "%2". The service will log on as account "%3". | Informational |
| 1089 | Site Component Manager started the %1 service on site system "%2". | Informational |
| 1090 | Site Component Manager could not stop the %1 service on site system "%2". Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 10901 | Failed to populate WSfB application metadata into database. | Error |
| 10902 | Sync Summary is update in database successfully. | Informational |
| 1091 | Site Component Manager could not deinstall the %1 service from site system "%2". Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1092 | Site Component Manager stopped the %1 service on site system "%2". | Informational |
| 1093 | Site Component Manager deinstalled the %1 service from site system "%2". | Informational |
| 1094 | Site Component Manager installed this component as a thread of the SMS Executive service on this site system. | Informational |
| 1095 | Site Component Manager started this component on this site system. | Informational |
| 1096 | Site Component Manager stopped this component on this site system. | Informational |
| 1097 | Site Component Manager deinstalled this component as a thread of SMS Executive on this site system. | Informational |
| 1098 | Site Component Manager could not start this component on this site system because the SMS Executive service is not running. Solution: Review the status messages reported by SMS Executive on this site system, and fix any problems it is experiencing. | Error |
| 1099 | Site Component Manager signaled this component on this site system to stop, but it did not stop after 60 seconds. | Error |
| 11001 | Failed to install ConfigMgr Update (%1). Please refer to the cmupdate.log for details. | Error |
| 11002 | ConfigMgr Update (%1) has installed successfully. Please refer to the cmupdate.log for details. | Informational |
| 1104 | SMS Executive detected that this component stopped unexpectedly. Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly. Solution: Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1105 | SMS Executive is next scheduled to start this component on "%1". | Informational |
| 1106 | SMS Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the component, enable the component in the Configuration Manager Console and adjust its schedule to an appropriate setting. | Informational |
| 1107 | SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component is scheduled to run so frequently that it cannot complete its work before the next scheduled run time. Solution: Adjust the component's schedule in the Configuration Manager Console so that it will not run so frequently. Possible cause: The component is running for an abnormally long time. Solution: Examine the other status messages reported by the component. If the component is experiencing a problem, correct it. | Warning |
| 1108 | SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function. Possible cause: The DLL was somehow corrupted or deleted. Solution: Restore the DLL by manually copying it from your installation media to \"%1\". Possible cause: The file "%1" 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 ConfigMgr component can access the file. Possible cause: The DLL depends on another DLL, which does not exist or cannot be found via the PATH environment variable. Solution: Determine all of the DLLs that this DLL depends on (using Depends.exe from the Win32 SDK) and insure they exist and can be found via the PATH environment variable for the user account that the SMS_EXECUTIVE service runs under. | Error |
| 1109 | SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported by \"%1\" using the Win32 GetProcAddress() function. Possible cause: The DLL was somehow corrupted or deleted. Solution: Restore the DLL by manually copying it from your installation media to \"%1\". Possible cause: This is a defective DLL that is part of an add-on product to Microsoft Configuration Manager. The DLL is defective because it does not export a ThreadMain() function. Solution: Contact the manufacturer of this product for more information. | Error |
| 1200 | In the last %1 hours, 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 Events on the site server, and %6 were passed as command-line parameters to external programs. During this time, 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. Status Manager periodically reports this message for your convenience; you can ignore it if your not interested in monitoring Status Manager's processing performance. Status Manager will report this message again in %10 hours. | Informational |
| 1201 | Status Manager successfully initialized the "SMS Status Messages" performance object. Every time 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 Performance Monitor. For example, you can monitor the total number of status messages written to the site database by Status Manager by monitoring the "_Total" instance of the "Written To SMS Database" counter. Status Manager resets all of the counts when it is restarted, and the counts cannot be viewed when Status Manager is not running. | Informational |
| 1202 | Due to an internal error, Status Manager could not initialize the "SMS Status Messages" performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. This problem will not affect 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 ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 1203 | 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 Configuration Manager Console. You can monitor the performance of the in-memory queue in the Windows 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 Status Manager has forwarded to the summarizer. The counts are reset when both Status Manager and the summarizer are restarted, which typically occurs when SMS Executive is restarted. The counts cannot be viewed when Status Manager and the summarizer are both not running. | Informational |
| 1204 | 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 Configuration Manager Console. If you reenable the summarizer in the Configuration Manager Console, Status Manager will resume forwarding messages to the summarizer. | Informational |
| 1205 | Due to an internal error, 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 Configuration Manager Console. Until this problem is fixed, the high-level summary will be inaccurate or not available. Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 1209 | Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number of instances. Every time 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 Performance Monitor. Because the maximum limit was reached, Status Manager will not create any more instances of this performance object. Status Manager builds the list of instances as it receives status messages. You can reset the list by restarting Status Manager. | Warning |
| 1210 | 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 Configuration Manager Console. (Note that you are not limited to %2 characters in the Program box.) | Warning |
| 1211 | 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 Configuration Manager 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". | Warning |
| 1212 | 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 Configuration Manager 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 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 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. | Warning |
| 1213 | 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 Server documentation or the Microsoft Knowledge Base for further information. 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. Status Manager will continue to report this problem every 24 hours until you fix it. Status Manager will not report this problem if the system clock of computer "%2" is less than five minutes ahead of the site server's system clock. | Warning |
| 1214 | 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 Server documentation or the Microsoft Knowledge Base for further information. When 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. Status Manager will continue to report this problem every 24 hours until you fix it. | Warning |
| 1215 | 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 Server documentation or the Microsoft Knowledge Base for further information. 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. Status Manager will continue to report this problem every 24 hours until you fix it. Status Manager will not report this problem if the system clock of computer "%2" is less than %4 seconds ahead of the site server's system clock. This interval is configurable in the site control file. Please refer to the Microsoft Knowledge Base for further information. | Warning |
| 1300 | Network Discovery is starting. | Informational |
| 1301 | Network Discovery is retrieving information about previously discovered devices and networks from CIM Object Manager. This process can take a long time when many devices are being discovered. | Informational |
| 1302 | Network Discovery protocol modules are initializing. | Informational |
| 1303 | Network Discovery is starting protocol operations. Network Discovery is querying network devices to discover devices related to the specified configuration. | Informational |
| 1304 | Network Discovery is stopping protocol operations. | Informational |
| 1305 | Network Discovery is stopping the Network Discovery protocol modules. | Informational |
| 1306 | Network Discovery is storing currently discovered devices and networks in CIM Object Manager, which can take a long time when many devices are being discovered. | Informational |
| 1307 | Network Discovery is exporting devices and networks to the Discovery Data Manager. This process can take a long time when many devices are being discovered. | Informational |
| 1308 | Network Discovery has stopped. | Informational |
| 1309 | Network Discovery failed to connect to a DHCP server due to insufficient access. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. Possible cause: The site server does not have sufficient rights to read data from the DHCP server Solution: Ensure that the site server computer account has sufficient permission to read configuration information from the DHCP server. | Error |
| 1310 | Network Discovery failed to connect to a DHCP server due to a connection error. (Network Discovery can communicate only with Microsoft DHCP servers; if you do not use these servers, you can ignore this error.) Solution: If you are using Microsoft DHCP servers, then refer to the specific error string for details. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. | Error |
| 1311 | Network Discovery failed to perform a WinSock operation. Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. | Error |
| 1312 | Network Discovery failed to perform a WinSock operation relating to multicast membership. Network Discovery will not discover other routers on your local subnet by listening for OSPF packets. However, if Network Discovery can detect your default gateway using SNMP, it will find those routers anyway. Possible cause: Some other network software on the server is preventing Network Discovery from joining the OSPF multicast group. Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. | Warning |
| 1313 | Network Discovery did not have time to finish. Therefore, the information in the site database is not as complete as it should be. Solution: Increase the duration of the discovery. In the Network Discovery Properties dialog box, on the Schedule tab, select a schedule and open the Schedule dialog box. Note that the duration of the discovery is the amount of time spent performing protocol transactions, not the overall time Network Discovery performs processing. | Warning |
| 1314 | Network Discovery failed to connect to CIM Object Manager. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager. Possible cause: CIM Object Manager is not installed on this computer. Solution: Install CIM Object Manager by running Sms\bin\i386\wmicore.exe. | Error |
| 1315 | Network Discovery detected CIM Object Manager, but could not establish a connection to it. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager. Possible cause: This computer has an incompatible version of CIM Object Manager, or there was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe. | Error |
| 1316 | Network Discovery failed to read information from CIM Object Manager. Network Discovery cannot continue. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe. | Error |
| 1317 | Network Discovery failed to read information from CIM Object Manager. Network Discovery will continue, but slowly. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe. | Warning |
| 1318 | Network Discovery failed to write information to CIM Object Manager. Network Discovery cannot continue. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe. | Error |
| 1319 | Network Discovery failed to write information to CIM Object Manager. Network discovery will continue, but slowly. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe. | Warning |
| 1320 | Network Discovery failed to execute a query from CIM Object Manager. Network discovery will continue, but slowly. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF. Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe. | Warning |
| 1321 | Network Discovery failed to communicate with some SNMP devices because of an internal problem with SNMP resources. Network Discovery will continue, but slowly. The discovery duration might have to elapse before discovery can finish fully. Possible cause: Too many SNMP-related applications are running on this computer. Solution: Close some SNMP-related applications. Possible cause: An internal error. Solution: Re-run Network Discovery. If that does not work, reboot. If that does not work, contact your network administrator. | Error |
| 1322 | Network Discovery failed to export a device to the Discovery Data Manager. Therefore, discovered devices will not appear in the site database. Possible cause: There is not enough free disk space on the Configuration Manager Site Server. Solution: Free some disk space and re-run Network Discovery. | Error |
| 1323 | Network Discovery failed to export a network to the Discovery Data Manager. Therefore, discovered devices will not appear in the site database. Possible cause: There is not enough free disk space on the Configuration Manager Site Server. Solution: Free some disk space and re-run Network Discovery. | Error |
| 1324 | Network Discovery failed to enumerate the computers on one or more domains. Possible cause: The specified domains do not exist. Solution: Re-specify domains; go to the Network Discovery Properties dialog box, Domains tab. Possible cause: Domain access problems exist. Solution: Contact your network administrator. | Informational |
| 2300 | Distribution Manager is beginning to process package "%1" (package ID = %2). | Informational |
| 2301 | Distribution Manager successfully processed package "%1" (package ID = %2). | Informational |
| 2302 | Distribution Manager failed to process package "%1" (package ID = %2). Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it. | Error |
| 2303 | Distribution Manager refreshed package "%1" on distribution point "%2". | Informational |
| 2304 | Distribution Manager is retrying to distribute package "%1". Wait to see if the package is successfully distributed on the retry. | Informational |
| 2305 | Distribution Manager failed to process package "%1" without a source directory. Possible cause: The Source directory is not specified. Solution: Verify that you have specified the package source directory on the Data Source tab in the Package Properties dialog box in the Configuration Manager Console. Retry Interval is %2 minutes, number of retries left is %3. | Error |
| 2306 | The source directory "%1" for package "%2" does not exist. Solution: Make sure you have specified a valid package source directory on the Data Source tab in the Package Properties dialog box in the Configuration Manager Console. If you specify a local path, it must be a local path on the site server. If you specify a path on a network drive, verify that the path exists and that the path is typed correctly. Retry Interval is %3 minutes, number of retries left is %4. | Error |
| 2307 | Distribution Manager failed to access the source directory "%1" for package "%2". Possible cause: Distribution Manager does not have sufficient rights to the package source directory. Solution: Verify that the site server computer account has at least Read access to the directory you specify as the package source directory. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Retry Interval is %3 minutes, number of retries left is %4. | Error |
| 2308 | Distribution Manager failed to remove the previously compressed copy for package "%1" located at "%2". Possible cause: The site server computer account does not have sufficient access rights to delete file "%2". Solution: Verify that the file's permissions will permit the site server computer account to delete it. | Error |
| 2309 | Distribution Manager failed to compress package "%1" from "%2" to "%4". The file that failed the compression is "%3". Possible cause: The drive containing file "%4" does not have enough free disk space. Solution: Verify that there is enough free disk space. Possible cause: If the package source directory "%2" is on a remote machine, that machine is turned off, not connected to the network, or not functioning properly. Solution: Verify that the machine containing the package source directory is turned on, connected to the network, and functioning properly. Verify that the network itself is functioning properly. Possible cause: The site server computer account does not have sufficient access rights to the package source directory "%2" or the file "%3". Solution: Verify that the site server computer account has read access to the package source directory and the problem file. | Error |
| 2310 | Distribution Manager compressed package "%1" from "%2" to "%3". | Informational |
| 2311 | Distribution Manager successfully created or updated package "%1". | Informational |
| 2312 | Distribution Manager failed to update the distribution source for package "%1". Possible cause: Distribution Manager cannot update the package data in the site database. 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 the site can access the site database. 5. Verify that the 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 Configuration Manager Console. If the problem persists, check the SQL Server error logs. Possible cause: Low disk space on the drive containing the package source files. Solution: Make more space available on that drive. Possible cause: The package source files are being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The package source files exist, but something else has changed the permissions or attributes of the files or the directory containing them. Solution: Restore the files' permissions or attributes so that the site can access the files. Possible cause: The package source files exist, but they are corrupt. Solution: Delete the files and replace them with backup copies. 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. Retry Interval is %2 minutes, number of retries left is %3. | Error |
| 2313 | Distribution Manager failed to remove package "%1" from "%2". Possible cause: The share type or the share name have been changed since the package was created. Solution: Verify that the share defined for this package is accessible to Distribution Manager running on the site server and that the name of the share has not been changed. If users are currently accessing the share, disconnect them before making any changes to the share. If the package distribution point is located on a Windows computer, you can force users to disconnect by clicking on the "Disconnect users from distribution points" box in the Data Access tab of the Package Properties dialog box. Retry Interval is %3 minutes, number of retries left is %4. | Error |
| 2314 | Distribution Manager removed package "%1" from "%2" due to changes in the share type or the share name. | Informational |
| 2315 | Distribution Manager deleted the compressed image of package "%1" at "%2". | Informational |
| 2316 | Distribution Manager failed to delete the compressed image of package "%1" at "%2". Possible cause: The site server computer account does not have sufficient access rights to file "%2". Solution: Verify that the site server computer account has delete access to the file. | Error |
| 2317 | Distribution Manager is refreshing package "%1" on distribution point "%2". | Informational |
| 2318 | Distribution Manager failed to distribute package "%1". Possible cause: The specified share is a hidden Windows NT drive share or a hidden Windows NT admin share. Solution: Specify a different share name on the Data Access tab of the Package Properties dialog box in the Configuration Manager Console. Retry Interval is %2 minutes, number of retries left is %3. | Error |
| 2319 | Distribution Manager failed to decompress package "%1" from "%2". Possible cause: The compressed image "%2" is either missing or corrupt. Distribution Manager will attempt to recover the package by requesting a new compressed package image from the site that sent it. | Error |
| 2320 | There is not enough free disk space on the site server to decompress package "%1". Possible cause: At least %2 megabytes of free disk space are required. Solution: Allocate more free disk space for the site server. | Error |
| 2321 | Distribution Manager failed to decompress package "%1" from "%2" to "%3". The file that failed to decompress is "%4". Possible cause: The drive containing directory "%3" does not have enough free disk space. Solution: Verify that there is enough free disk space. | Error |
| 2322 | Distribution Manager decompressed package "%1" from "%2" to "%3". | Informational |
| 2323 | Distribution Manager failed to connect to the distribution point. Possible cause: Distribution Manager cannot access the distribution point machine because of access permissions issues. Solution: Make sure that the site server machine account or Site System Installation account has administrative permissions on the distribution point machine. Retry Interval is %1 minutes, number of retries left is %2. | Error |
| 2324 | Distribution Manager failed to find or create the defined share or folder (%3) on distribution point "%1" for distributing package "%2". Possible cause: Windows NT distribution points might not have at least one available NTFS drive. Solution: Verify that there is at least one NTFS drive with enough free disk space to store the package. Then, verify that the distribution point directory exists, has the proper permissions, and is accessible. Retry Interval is %4 minutes, number of retries left is %5. | Error |
| 2325 | Distribution Manager failed to create subdirectories on distribution point "%1" for distributing package "%2". Possible cause: Distribution Manager does not have sufficient rights to create subdirectories on the distribution point. Solution: In the Configuration Manager Console, create a new site system connection account or verify that an existing account has sufficient privileges. | Error |
| 2326 | Distribution Manager failed to save package status for package "%1" to the site database. 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 the site server can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. 6. If the problem persists, check the SQL Server error logs. Retry Interval is %2 minutes, number of retries left is %3. | Error |
| 2327 | Distribution Manager failed to update the package properties on distribution points for package "%1". Solution: Verify that there is enough free disk space on the site server to update the package. Retry Interval is %2 minutes, number of retries left is %3. | Error |
| 2328 | Distribution Manager failed to copy package "%1" from "%2" to "%3". Possible cause: Distribution Manager does not have sufficient rights to read from the package source directory or to write to the destination directory on the distribution point. Solution: In the Configuration Manager Console, verify that the Site System Installation accounts have sufficient privileges to the source and destination directories. Possible cause: The distribution point might not be accessible to Distribution Manager running on the site server. Solution: If users are currently accessing the package files on the distribution point, disconnect the users first. If the package distribution point is located on a Windows NT computer, you can force users to disconnect by clicking on the "Disconnect users from distribution points" box in the Data Access tab of the Package Properties dialog box. Possible cause: The distribution point does not have enough free disk space to store the package. Solution: Verify that there is enough free disk space. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Retry Interval is %4 minutes, number of retries left is %5. | Error |
| 2329 | Distribution Manager copied package "%1" from "%2" to "%3". | Informational |
| 2330 | Distribution Manager successfully distributed package "%1" to distribution point "%2". | Informational |
| 2331 | Distribution Manager successfully removed package "%1" from distribution point "%2". | Informational |
| 2332 | Distribution Manager failed to remove package "%1" from distribution path "%2". Possible cause: The distribution point might not be accessible to Distribution Manager running on the site server. Solution: If users are currently accessing the package files on the distribution point, disconnect the users first. Retry Interval is %3 minutes, number of retries left is %4. | Error |
| 2333 | Distribution Manager is preparing to send the compressed image of package "%1" to child site "%2". | Informational |
| 2334 | Distribution Manager created a 1.x style instruction to send package "%1" to 1.x child site "%2". | Informational |
| 2335 | Distribution Manager instructed Scheduler and Sender to send package "%1" to child site "%2". | Informational |
| 2336 | Distribution Manager failed to create a 1.x style instruction to send package "%1" to 1.x child site "%2". Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. | Error |
| 2337 | Distribution Manager failed to instruct Scheduler to send package "%1" to child site "%2". Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. Retry Interval is %3 minutes, number of retries left is %4. | Error |
| 2338 | Distribution Manager created a 1.x style instruction to send package definition for package "%1" to 1.x child site "%2". | Informational |
| 2339 | Distribution Manager instructed Scheduler and Sender to send the package information for package "%1" to child site "%2". | Informational |
| 2340 | Distribution Manager failed to create a 1.x style instruction to send the package definition for package "%1" to 1.x child site "%2". Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. | Error |
| 2341 | Distribution Manager failed to send the package information for package "%1" to child site "%2". Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. | Error |
| 2342 | Distribution Manager is starting to distribute package "%1" to distribution point "%2". | Informational |
| 2343 | There is not enough free disk space to copy package "%1" to "%2". Solution: Verify that "%2" has at least %3 kbytes of free disk. | Error |
| 2344 | Failed to create virtual directory on the defined share or volume on distribution point "%1". Possible cause: Distribution Manager requires that IIS base components be installed on the local Configuration Manager Site Server in order to create the virtual directory. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS). Solution: Verify that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server. | Error |
| 2345 | Failed to delete virtual directory on the defined share or volume on distribution point "%1". Possible cause: The IIS base components may not be installed on the local Configuration Manager Site Server or IIS Web Services may not be installed on the Distribution Point Server. Solution: Verify that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server. | Error |
| 2346 | Distribution Manager failed to distribute package "%1". Possible cause: The specified share is a hidden share. Solution: Specify a different share name on the Data Access tab of the Package Properties dialog box in the Configuration Manager Console. Retry Interval is %2 minutes, number of retries left is %3. | Error |
| 2347 | Distribution Manager upgraded the hidden file ISAPI on the distribution point but was unable to load the file because the original ISAPI was in use. To load the new ISAPI please restart IIS on computer "%1". | Warning |
| 2348 | Distribution Manager failed to decompress package "%1" from "%2". Possible cause: The compressed image "%2" is either missing or corrupt. Distribution Manager will not attempt to recover the package. Please update the package to repair the compressed image | Error |
| 2349 | The WebDAV server extensions are disabled on the distribution point "%1". As a result, clients will not be able to use BITS support on the distribution point. To enable BITS support, enable the WebDAV server extension from the Web Service Extensions node in the Internet Information Services (IIS) administrative tool. | Error |
| 2350 | Distribution Manager instructed Scheduler and Sender to send a forwarding request to site "%2", requesting that site to forward package "%1" to site "%3". | Informational |
| 2351 | Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") is greater than the version requested ("%4"). Possible cause: A package update has recently been triggered. The package source site has been recently recovered. Possible workaround: If the package has been recently updated, verify that sites "%2" receive the package directly from package source site. If package source site has been recently recovered, verify that all recovery steps for this package have been followed. | Warning |
| 2352 | Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") is lower than the version requested ("%4"). Possible cause: A package update has recently been triggered. This site "%5" has been recently recovered. Possible workaround: If the package has been recently updated, verify that sites "%2" receive the package directly from package source site. If this site has been recently recovered, verify that all recovery steps for this package have been followed. | Error |
| 2353 | Failed to configure ports in IIS on the defined share or volume on distribution point "%1". Possible cause: Distribution Manager requires that IIS base components be installed on the local Configuration Manager Site Server in order to configure the ports. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS). Solution: Verify that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server. | Error |
| 2354 | Failed to validate package status file "%1" received from Distribution Point %2 for package %3. Possible cause: For content prestaging, the remote distribution point package is not enabled for prestaging. The package being prestaged on the remote distribution point is not enabled for prestaging. The source version of the package extracted on the remote prestaged distribution point or distributed to the remote distribution point does not match with the current version of the package on the site server. Solution: Verify that both the remote distribution point as well as the package is enabled for prestaging. Ensure that the latest version of the package is being extracted/distributed on/to the remote distribution point. | Error |
| 2355 | Package "%1" is not assigned to any standard distribution points for site "%2". Branch distribution points require the package to be assigned to at least one standard distribution point . The branch distribution point downloads package content from a standard distribution point from the site where the branch distribution point client is assigned. | Warning |
| 2356 | Distribution Manager failed to instruct Package Transfer manager to send package "%1" to distribution point "%2". Solution: Verify that the site server has available memory and that there is enough free disk space to create the send job. Retry Interval is %3 minutes, number of retries left is %4. | Error |
| 2357 | Distribution Manager instructed Package Transfer manager to send package "%1" to distribution point "%2". | Informational |
| 2358 | "%1" server ("%2") is a 32-bit system. Multicast or File Streaming are not supported distribution point features on 32-bit system. These features can not be enabled on this distribution point. | Warning |
| 2359 | Distribution Manager failed to find a drive on distribution point "%1" on system "%2" which has characteristics appropriate for storing shared folders used by distribution point. Possible cause: Windows NT distribution points might not have at least one available NTFS drive. Solution: Verify that there is at least one NTFS drive with enough free disk space to store the packages. | Error |
| 2360 | Distribution Manager failed to verify drive specified by user on distribution point "%1" on system "%2". Possible cause: The distribution point might not have specified volume or the speicified volume is not NTFS drive or it does not have enough free space. Solution: Verify that selected drive is of NTFS type with enough free disk space to store the packages. | Error |
| 2361 | Distribution Manager failed to access the source directory "%1" for content "%2" (content ID = %3). Possible cause: Distribution Manager does not have sufficient rights to the source directory. Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory. Possible cause: There is not enough disk space available on the site server. Solution: Verify that there is enough free disk space available on the site server. Retry Interval is %4 minutes, number of retries left is %5. | Error |
| 2362 | Distribution Manager successfully installed IIS component of operating system to distribution point "%1". | Informational |
| 2363 | Distribution Manager has not tried to install IIS component of operating system to distribution point "%1" because its operating system is older than Windows Server 2008. Manual installation of IIS component of operating system to distribution point might be needed. Please ensure RDC is also enabled. | Informational |
| 2364 | Distribution Manager installed IIS component of operating system to distribution point "%1". Installation process ended with an exit code of %2. Reboot of machine "%1" is needed to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings. | Informational |
| 2365 | Distribution Manager attempted to run a tool to install IIS component of operating system to distribution point "%1". The tool returned non-zero error code %2. Reboot or manual installation of IIS might be required to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings and RDC is enabled. | Informational |
| 2366 | Distribution Manager attempted to run a tool to install IIS component of operating system to distribution point "%1". Reboot or manual installation of IIS might be required to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings. | Informational |
| 2367 | Package "%1" content was successfully imported from a prestaged content file to distribution points on site server "%2" (%3). | Informational |
| 2368 | An error occurred during the import of content from a prestaged content file to distribution points on site server "%1" (%2). | Warning |
| 2369 | WDS is not installed on distribution point "%1".The PXE service point will not be available. | Informational |
| 2370 | Distribution Manager failed to install distribution point %1 on computer %2. Possible cause: Distribution Manager does not have sufficient rights to the computer. Solution: Verify that the site server computer account is an administrator on the distribution point computer. | Error |
| 2371 | Distribution Manager is waiting for package %1 content to be prestaged on the distribution point %2. You must manually prestage the package %1 on the distribution point before the content will be available. | Informational |
| 2372 | The content files for package %1 have not yet arrived from the source site %2. Distribution Manager will try again later to distribute the content. | Informational |
| 2373 | PXE is %1 on distribution point %2 | Informational |
| 2374 | Multicast is %1 on distribution point %2 | Informational |
| 2375 | Created virtual directories on the defined share or volume on distribution point "%1" successfully. | Informational |
| 2376 | Distribution Manager created a snapshot for content %1 successfully. | Informational |
| 2380 | Start to evaluate package "%1" on distribution point "%2". | Informational |
| 2381 | An evaluation task is running. Put package "%1" to wait queue on distribution point "%2". | Informational |
| 2382 | The hash of package "%1" is invalid on distribution point "%2". Please redistribute the package. | Error |
| 2383 | Failed to validate package "%1" on distribution point "%2". The package may not be present or may be corrupt. Please redistribute it. | Warning |
| 2384 | Package "%1" on distribution point "%2" has been verified successfully. | Informational |
| 2385 | Following file(s) of package "%1" on distribution point "%2" are missing. %3 | Error |
| 2386 | All content on distribution point "%1" has been verified. | Informational |
| 2387 | The hash of the migrated package "%1" is incorrect in the database. Please update the package on the Configuration Manager 2007 site and then migrate the package again. | Informational |
| 2388 | Failed to retrieve the package list on the distribution point %1. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure. | Warning |
| 2389 | Failed to copy the package "%1" from "%2" into the content library on the distribution point server "%3". | Warning |
| 2390 | The migrated packages on the distribution point server "%1" have been successfully copied into the content library on the server. | Informational |
| 2391 | Distribution Manager failed to connect to the distribution point %1. Check your network and firewall settings. | Error |
| 2392 | Distribution Manager has not tried to install IIS component of operating system to distribution point "%1". You should install and configure IIS manually. Please ensure RDC is also enabled. | Warning |
| 2393 | Successfully retrieved and validated the package list from the distribution point %1. | Informational |
| 2394 | A reboot is required on the distribution point %1. | Warning |
| 2397 | Detail will be available after the server finishes processing the messages. | Informational |
| 2398 | Starting to process content | Informational |
| 2399 | Successfully completed the installation or upgrade of the distribution point on computer "%1". | Informational |
| 2400 | Database 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. 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. | Error |
| 2401 | Database Notification 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. 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. | Warning |
| 2402 | Database Notification Monitor failed to execute database maintenance SQL Server command "%1". Possible cause: The SQL Server 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 in the Configuration Manager 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the Smsdbmon.log for SQL Server error logs. | Error |
| 2404 | The database maintenance SQL Server task "%1" completed successfully. The task deleted %2 items from the site database. | Informational |
| 2405 | Database Notification Monitor is installing trigger "%1" for table "%2" and actions "%3" in the site database. Server components such as Hierarchy Manager, Collection Evaluator, and Discovery Data Manager instruct Database Notification Monitor to install SQL Server triggers. Then, when certain kinds of data are added to, changed in, or removed from the site database, the SQL Server triggers notify Database Notification Monitor. In turn, Database Notification Monitor notifies the appropriate server components. | Informational |
| 2406 | Database Notification Monitor is removing trigger "%1" from the site database. Server components such as Hierarchy Manager, Collection Evaluator, and Discovery Data Manager instruct Database Notification Monitor to install SQL triggers. Then, when certain kinds of data are added to, changed in, or removed from the site database, the SQL Server triggers notify Database Notification Monitor. In turn, Database Notification Monitor notifies the appropriate server components. This trigger is being removed because it is no longer needed. | Informational |
| 2407 | Database Notification Monitor failed to install trigger "%1" in the site database. Possible cause: Either table "%2" or column "%3" of table "%2" does not exist in the 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 2408 | Database Notification Monitor is executing database maintenance SQL Server command/task "%1". You can configure the execution schedule for this SQL Server command/task in the Configuration Manager console under Administration / Overview / Site Configuration / Sites -> Site Maintenance. | Informational |
| 2409 | The Delete Aged Collected Files database maintenance task completed successfully. The task deleted %1 collected files and %2 directories. | Informational |
| 2410 | The Rebuild Indexes database maintenance task successfully recreated index "%1" on table "%2" in the site database. The Rebuild Indexes task periodically recreates the indexes in the site database to provide optimal query performance. | Informational |
| 2411 | The Rebuild Indexes task has dropped index "%1" on table "%2" in the site database. The Rebuild Indexes task periodically recreates the indexes in the 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. | Informational |
| 2412 | 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". | Informational |
| 2413 | The Software Metering File Usage Summarization task has completed, %1 rows have been added to the summary tables. | Informational |
| 2414 | The Software Metering Data Monthly Usage Summarization task has completed, %1 rows have been added or updated in the summary tables. | Informational |
| 2415 | The Clear Install Flag for Undiscovered Clients task has completed, %1 rows have been updated in system discovery tables. | Informational |
| 2416 | Database Notification Monitor could not start the SMS Backup service on server %1. Possible cause: You changed the service setting for the SMS Backup service, but forgot to notify SMS. Solution: Use Configuration Manager Setup to modify the installation of the site. Possible cause: Database Notification Monitor does not have sufficient access rights to administer the site server. Solution: Verify that the server connection accounts are properly configured to allow the Database Notification Monitor to administer the site server. | Warning |
| 2417 | The Delete Inactive Client Discovery Data task has completed, %1 inactive clients have been removed from the database. | Informational |
| 2418 | The Delete Obsolete Client Discovery Data task has completed, %1 obsolete clients have been removed from the database. | Informational |
| 2419 | The Client Access License Usage Data Summarization task has completed, %1 rows have been added or updated in the summary table. | Informational |
| 2420 | The task "%1" is configured to run today, but it could not run within the scheduled time. Possible cause: The task has been enabled recently or updated to run today, but this occurred after the end of the scheduled time. Or, other tasks that were scheduled to run today did not complete before the end of the scheduled time, preventing this task from starting. Solution: Allow more time for this task to run, or schedule this task to run at another day or time. You can configure the schedule for this task in the Configuration Manager console under Administration / Overview / Site Configuration / Sites -> Site Maintenance. | Warning |
| 2421 | Database Notification Monitor succeed to start task Reset AMT Computer Passwords. | Warning |
| 2422 | Database Notification Monitor succeed to start task Evaluate Provisioned AMT Computer Certificates. | Warning |
| 2423 | Database Notification Monitor succeed to run task 'Delete Expired Bookmarks'. %1 bookmarks have been removed. | Informational |
| 2424 | Database Notification Monitor succeed to run task 'Delete Expired Activities'. %1 activities have been removed. | Informational |
| 2425 | Database Notification Monitor succeed to run task 'Delete Expired Activity Facts'. %1 activity facts have been removed. | Informational |
| 2426 | Database Notification Monitor successfully ran task 'Delete Obsolete Alerts'. %1 alerts have been removed. | Informational |
| 2427 | The database maintenance SQL Server task "%1" completed successfully. %2 catalog rows have been added. | Informational |
| 2428 | The database maintenance SQL Server task "%1" completed successfully. %2 Software rows have been added to summary table. | Informational |
| 2429 | The database maintenance SQL Server task "%1" completed successfully. %2 Targeting rows have been changed. | Informational |
| 2500 | Collection Evaluator failed to enumerate collections. 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 the site can access the site database. 5. Verify that the 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 Configuration Manager Console. If the problem persists, check the SQL Server error logs. | Error |
| 2504 | Collection Evaluator failed to find collection "%1". Collection Evaluator received a .udc (update collection) or .adc (create collection) file for a collection that does not exist. Possible cause: The collection was deleted shortly after being created or updated, but Database Notification Monitor and Collection Evaluator processed the create or update file out of sequence. Solution: None needed. The create or update file will simply not be processed for the nonexistent collection. | Warning |
| 2507 | Collection Evaluator failed to delete collection "%1". 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2511 | Collection Evaluator failed to update the membership of collection "%1". 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2519 | Collection Evaluator failed to enumerate members of collection "%1" at site "%2". 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2521 | Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source is the site database. On secondary sites, it is \Sms\inboxes\colleval.box.) Possible cause on primary sites: 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. Possible cause on secondary sites: The file in \Sms\inboxes\colleval.box is corrupt. Solution: Delete the file, and then stop and restart Collection Evaluator. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2523 | Collection Evaluator failed to enumerate membership rules for collection "%1". 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2524 | Collection Evaluator failed to write to file "%1". Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart Collection Evaluator. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2530 | Collection Evaluator failed to update collection "%1" in the collection source. (On primary sites, this is the site database. On secondary sites, this is \Sms\inboxes\colleval.box.) Possible cause: Low disk space on the disk drive of the site server inbox. Solution: Make more space available on that drive. | Error |
| 2531 | Collection Evaluator failed to retrieve a SQL Server command from the collection membership rule. Possible cause: An SMS Provider failure occurred while inserting the WBEM Query Language (WQL) string into the SQL Server database, or the rule was added improperly. Solution: Recreate the rule in the Configuration Manager Console and save it. If the WQL string had been stored correctly, it should remain after it was resaved, and the proper SQL string should be stored in the database. | Error |
| 2532 | Collection Evaluator failed to connect to the site database. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2533 | Collection Evaluator failed to enumerate discovery architectures because it cannot retrieve the discovery architecture list from the database. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2535 | Collection "%1" has no name. Collection Evaluator cannot continue processing the collection without a name. Solution: Add a name by editing the collection in the Configuration Manager Console. | Error |
| 2542 | Collection Evaluator failed to update the query rule "%1" of collection "%2" (%3). Possible cause: Inventory or Resource classes referenced in the query do not exist at this site, resulting in a SQL error. Solution: Enable the collection of the missing Inventory or Resource information at this site.n 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Warning |
| 2543 | Collection Evaluator failed to evalute some of the query rules for collection "%1" (%2). Possible cause: Inventory or Resource classes referenced in the query do not exist at this site, resulting in a SQL error. Solution: Review the immediately preceding status messages from this component about query rule failures. Enable the collection of the missing Inventory or Resource information at this site. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Warning |
| 2545 | Collection Evaluator successfully processed new Collection Settings %1. | Informational |
| 2546 | Collection Evaluator successfully processed Update to Collection Settings %1. | Informational |
| 2547 | Collection Evaluator successfully removed Collection Settings Policy for Collection %1. | Informational |
| 2548 | Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 2549 | Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings will be retried %2 times on the next processing cycles. Solution: Review the previous status messages and logs for further clarification about this problem. | Warning |
| 2550 | Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings has been retried %2 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 2551 | Collection Evaluator failed to process Collection Settings Replication File %1 as Collection %2 referenced object of type %3 does not exists. This Collection Settings Replication file has been retried %4 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 2552 | Collection Evaluator failed to process Collection Settings Replication File %1. This Collection Settings Replication file has been retried %2 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 2553 | Policy Provider failed to process Machine Settings for Machine %1. This Machine Settings will be retried on the next processing cycles. Solution: Review the previous status messages and logs for further clarification about this problem. | Warning |
| 2554 | Policy Provider failed to process Machine Settings changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 2555 | Collection Evaluator successfully processed %1 client updates for collection %2. Original clients number: %3, added: %4, deleted: %5. | Informational |
| 2556 | The query rule for the collection "%1" generated a high number of records (%2). Solution: Consider optimizing the query rule for this collection. | Warning |
| 2557 | Policy Provider failed to process User Settings changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 2600 | Discovery Data Manager failed to synchronize this site's deletions with all secondary site databases. When discovery data is deleted, the deletion must be propagated to all secondary sites. In addition, any licenses associated with the deleted resources must be revoked. Because secondary site data is not synchronized, more licenses will be used than is necessary. Possible cause: SQL Server problem on this site or one or more secondary sites. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2601 | Discovery Data Manager failed to connect to the discovery database. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2602 | Discovery Data Manager is removing references from deleted site "%1". | Informational |
| 2603 | Discovery Data Manager is beginning the process of sending discovery data to the new parent site. (This happens whenever a site attaches to a new parent site.) | Informational |
| 2604 | Discovery Data Manager failed to send discovery data to the new parent site. Discovery Data Manager will retry, resuming where it left off. | Warning |
| 2605 | Discovery Data Manager failed to move the new parent site notification file to the Data Loader inbox. Possible cause: Low disk space on the disk drive of the Data Loader inbox. Solution: Make more space available on that drive. | Error |
| 2606 | Discovery Data Manager has tried ten times to send the discovery database to the new parent site, and Discovery Data Manager has been unsuccessful each time. Discovery Data Manager is giving up. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2607 | Discovery Data Manager has successfully sent the discovery database to the parent site. | Informational |
| 2608 | Discovery Data Manager failed to send file "%1" to site "%2". Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive. | Error |
| 2609 | Discovery Data Manager failed to enumerate discovery architectures. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2610 | Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site. Possible cause: Low memory. Solution: Stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2611 | Discovery Data Manager has detected a change in assignment rules. Discovery Data Manager will not process discovery data records (DDRs) until it completes the rule refresh operation. | Informational |
| 2612 | Discovery Data Manager failed to complete the rule refresh process. Possible cause: Refer to the previous Discovery Data Manager message. | Error |
| 2613 | Discovery Data Manager failed to read the serial number from the parsed discovery data record (DDR) "%1". Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2614 | Discovery Data Manager failed to read the new discovery item from the parsed discovery data record (DDR) "%1". Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2615 | Discovery Data Manager failed to parse the new discovery item data from the parsed discovery data record (DDR) %1. Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2616 | Discovery Data Manager failed to insert the new item from file "%1" into the data source. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2617 | Discovery Data Manager failed to write the serial number record to file "%1". Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive. | Error |
| 2618 | Discovery Data Manager failed to write the item key record to file "%1". Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive. | Error |
| 2619 | Discovery Data Manager failed to write item buffer to file "%1". Discovery Data Manager is attempting to send a discovery data record (DDR) to another site or registered consumer, but is unable to write the data for the new item. Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive. | Error |
| 2620 | Discovery Data Manager failed to format discovery data into file "%1". Possible cause: Low memory. Solution: Stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2621 | Discovery Data Manager failed to enumerate properties for architecture "%1". 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2622 | Discovery Data Manager failed to process file "%1" because it cannot detect any Name properties. Discovery Data Manager requires that all discovery data records (DDRs) report at least one field that is defined as a Name candidate. The three default architectures--User, User Group, and System--all have one or more defined Name fields. Either this DDR is not of one of those three architectures, or it is an invalid DDR. Possible cause: an Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. Possible cause: Something other than ConfigMgr created the DDR, and no value was specified as the Name. Solution: Every discovery item needs to have some value that can be identified as the name of the resource. In System DDRs, for example, one of the following values is used as the Name: NetBIOS Name, Resource Names, IP Addresses, IPX Addresses, or MAC Addresses. If none of these are available, or if you have created a DDR of a new architecture, then pick a property and flag it as the Name by ORing decimal 64 in the property's Flags column. | Error |
| 2623 | Discovery Data Manager failed to insert discovery data because the site is out of client access licenses. Solution: Increase the number of client access licenses. | Error |
| 2624 | Discovery Data Manager failed to read the current site's .ncf (assignment rule) file. Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2625 | Discovery Data Manager failed to read the .ncf (assignment rule) file for site "%1". Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2626 | Discovery Data Manager failed to open the .ncf (assignment rule) file for site "%1". Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Error |
| 2627 | Discovery Data Manager failed to read the site control file for site "%1". Because the site database maintains the site control files for this site and all sites beneath it, Discovery Data Manager reads site control files only from the site database. 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 the site can access the site database. 5. Verify that the 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 Configuration Manager Console. If the problem persists, check the SQL Server error logs. | Error |
| 2628 | Discovery Data Manager failed to write the .ncf (assignment rule) file "%1". Discovery Data Manager will retry writing this file during its next processing cycle. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. | Warning |
| 2629 | Discovery Data Manager failed to copy the .ncf (assignment rule) file "%1" to Asstdata.box, the point of replication to client access points (CAPs). Discovery Data Manager will retry copying this file during its next processing cycle. Possible cause: Low disk space on the disk drive containing Asstdata.box. Solution: Make more space available on that drive. | Warning |
| 2630 | During a refresh, Discovery Data Manager detected that assignment rules had changed. Therefore, Discovery Data Manager is stopping the refresh now, but will perform it later. | Informational |
| 2631 | Discovery Data Manager failed to create a full refresh file to send to the secondary site. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. | Error |
| 2632 | Discovery Data Manager failed to notify all consumers that a full refresh has occurred and that users need to refresh their data store. Possible cause: Because these notifications are done by a file, there is probably low disk space on one or more destination disk drives. Solution: Make more space available on those disks. | Error |
| 2633 | Discovery Data Manager failed to send file "%1" to site "%2". Possible cause: Low disk space on site "%2". Solution: Make more space available on the disk drive containing \Sms\inboxes on site "%2". | Error |
| 2634 | Discovery Data Manager will resume processing because it has successfully completed assignment-rule processing. | Informational |
| 2635 | While parsing discovery data record (DDR) "%1", Discovery Data Manager found a blank Architecture field, which makes "%1" a bad DDR. Possible cause: Something other than ConfigMgr created the DDR, and no value was specified as the Architecture. Solution: Re-create the DDR, specifying an architecture as part of the discovery item format. Possible cause: an Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 2636 | Discovery Data Manager failed to process the discovery data record (DDR) "%1", because it cannot update the data source. Possible cause: On a Primary site, it is probably a 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 the site can access the site database. 5. Verify that the 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 Configuration Manager Console. If the problem persists, check the SQL Server error logs. Possible cause: On a secondary site, Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server. Solution: Make more space available on the site server. | Error |
| 2637 | Discovery Data Manager is updating statistics in all tables in the site database, which helps ensure optimal performance of SQL Server 6.5. | Informational |
| 2638 | Discovery Data Manager has interpreted discovery data record (DDR) "%1" as a delete request. Therefore, Discovery Data Manager is deleting item "%2" of architecture "%3". DDR "%1" contains an old item, but not a new item. | Informational |
| 2639 | Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%3" which has reported a new hardware identifier of "%2". %4 existing records sharing this hardware identifier have been marked as obsolete. The data in these records has been superseded by the data in the new record. Possible cause: The operating system and ConfigMgr client have been reinstalled on this computer. | Informational |
| 2640 | Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%2" which has reported a new SMS ID of "%3". An existing record with the previous SMS identifier has been marked as obsolete. The data in this record has been superseded by the data in the new record. Possible cause: The hardware properties of this client have changed substantially, and the client has generated a new SMS identifier. | Informational |
| 2641 | Discovery Data Manager failed to process a client registration request for computer with the identity "%1" and with the SMS identifier "%2" because the SMS identifier has already been registered for another client. | Error |
| 2642 | Configuration Manager has detected a record that might be conflicting with the following client record in the site database: %1. Possible cause: %1 has been imaged, recovered from backup, or migrated to a new computer. Solution: In the Configuration Manager console, under Computer Management, in the Conflicting Records node, right click %1 and then choose one of the following options: Merge to match the conflicting record with the existing record, New to create a new client record, or Block to block this record from being a client. | Informational |
| 2700 | Inventory Data Loader failed to read the delta MIF file "%1" and will move the file to the BADMIFs directory. Possible cause: The file is invalid or corrupt. Solution: Do nothing. The file will be moved to the BADMIFs directory where it will be checked for corruption. Any formatting errors will be logged in Dataldr.log. If there are no formatting errors, there might have been a memory error, in which case the MIF will be retried. | Error |
| 2701 | Inventory Data Loader encountered a SQL Server problem and is stopping the MIF processing thread. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2702 | Inventory Data Loader failed to process the delta MIF file "%1" because the file does not have a corresponding discovery record. Inventory Data Loader has moved this file to the Orphans directory as file "%2" and will retry processing it within 10 minutes. Possible cause: Discovery Data Manager is not running. Solution: Stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Warning |
| 2703 | Inventory Data Loader failed to process the delta MIF file "%1" and has moved it to "%2." Possible cause: The file attempted to update inventory information in the site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun. | Error |
| 2703 | Inventory Data Loader failed to process the delta MIF file "%1" and has moved it to "%2." Possible cause: The file attempted to update inventory information in the site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun. | Warning |
| 2704 | Inventory Data Loader is updating database statistics for all inventory-related tables. By default, statistics are updated to optimize database performance after a certain number of MIF files have been processed. This message indicates that this milestone has been achieved. You can edit this value in the Configuration Manager Console, under Component Configuration, Data Processing and Storage Properties. | Informational |
| 2705 | Inventory Data Loader has finished processing %1 MIF files and is terminating the MIF file processing thread. Each time the processing cycle completes, Inventory Data Loader generates this message to report the number of MIF files it has processed. | Informational |
| 2706 | Inventory Data Loader has quit trying to update inventory after failing 10 times. Inventory Data Loader detected that the parent site was changed to a new site, and then Inventory Data Loader tried to send all inventory to the new parent through the inventory update process. However, Inventory Data Loader tried this process 10 times and failed each time. Solution: Review the immediately preceding status messages from this component for more details. 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. | Error |
| 2707 | Inventory Data Loader failed to send inventory to the new parent site, but it will retry %1 more times before quitting. If you want more information, review the immediately preceding status messages from this component, or look in dadaldr.log. 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. | Warning |
| 2708 | Inventory Data Loader detected that the parent site has changed to a new site, and now Inventory Data Loader is trying to send all inventory to the new parent through the inventory update process. | Informational |
| 2709 | The Inventory Data Loader inventory update process has initialized the inventory update status file, which controls the inventory update process's ability to restart. | Informational |
| 2710 | The Inventory Data Loader has detected that the inventory update process has already been completed. Therefore, Inventory Data Loader is not starting the inventory update process. If this information is incorrect, delete the status file Inv_stat.dat to force the inventory update process to restart. | Informational |
| 2711 | The Inventory Data Loader inventory update process will use the directory %1. Inventory Data Loader will create delta MIF files in this folder to send to the parent site. | Informational |
| 2712 | The Inventory Data Loader inventory update process failed to write the MIF file for machine %1 of architecture %2. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 2713 | The Inventory Data Loader inventory update process has finished successfully. All inventory has been sent to the parent site. | Informational |
| 2714 | Inventory Data Loader has requested a resynchronization for site %1. Inventory Data Loader requests resynchronization when it receives an Update or Delete request for a nonexistent group. | Informational |
| 2715 | Inventory Data Loader has detected a resynchronization request for agent %1. When an agent is specified, the resynchronization is planned only for items reported by that agent. A resynchronization indicates that the current MIF file represents all inventory for the current machine. If any inventory is present in the database that does not occur in the MIF file, Inventory Data Loader deletes it (unless, as with an agent resynchronization, it was reported by a different agent). If many resynchronizations occur, it indicates that inventory was lost at some point. | Informational |
| 2716 | Inventory Data Loader is going to widen attribute %2 of group %1 from %3 to %4. Inventory Data Loader has received a MIF file that contains a referenced attribute that exceeds the current maximum length. Inventory Data Loader will attempt to widen the column before it inserts the data. | Informational |
| 2717 | Inventory Data Loader has added group %1 to architecture %2. Inventory Data Loader found a group that it had not found before and successfully added the group to the inventory database. | Informational |
| 2718 | Inventory Data Loader has added the architecture %1. Inventory Data Loader found an architecture that it had not found before and successfully added it to the inventory database. A custom MIF file, either from this site or from one beneath it, caused this action. | Informational |
| 2719 | Inventory Data Loader failed to process the file %1 because it is larger than the defined maximum allowable size of %2. Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size (the default is 5 MB), and wait for Inventory Data Loader to retry the operation. | Error |
| 2720 | Inventory Data Loader has detected that a resource with GUID %1 needs to be resynchronized, but the resource will not be resynchronized because the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Resynchronize Clients on the resource computer has been turned off. Data will not be processed for this resource until it has been resynchronized. Possible cause: Inventory Data Loader detected a MIF file (from the resource with GUID %1) that contains an update request for data that is not in the site database. Therefore, Inventory Data Loader wants to request a resynchronization, or full MIF file, from that resource. Solution: On the resource with GUID %1, set the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Resynchronize Clients to 1 (true). | Warning |
| 2721 | Inventory Data Loader failed to compile %1. The failing MOF file has been moved to %2, and the last successfully compiled version has been restored. Possible cause: The file has been edited with changes that are not valid for MOF file syntax. Solution: Review the last set of changes to the file for adherence to MOF file syntax. | Error |
| 2722 | Inventory Data Loader has requested a resynchronization for machine %1. Inventory Data Loader requests resynchronization when it receives an Update or Delete request for a nonexistent group. | Informational |
| 2723 | Inventory Data Loader requested a resynchronization for machine "%1" because a hardware inventory file was sent without a public key information. | Informational |
| 2724 | Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Will switch to single-threaded operation after exceeding %3. | Warning |
| 2725 | Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Switching to single-threaded operation for the next %3 minutes. | Warning |
| 2800 | Site Control Manager is beginning to process delta site control file "%1". Configuration Manager Server Components and SMS Provider clients (such as the Configuration Manager Console) submit delta site control files to change the configuration of the site. A delta site control file contains one or more required changes to the actual site control file ("%2" at this site). The actual site control file contains the site configuration currently in use. The site is successfully reconfigured only after Site Control Manager receives and processes a delta site control file and then updates the actual site control file with the new configuration data. | Informational |
| 2801 | Site Control Manager successfully processed delta site control file %1. | Informational |
| 2802 | Site Control Manager could not completely process delta site control file %1. Possible cause: Some site configuration change requests contained in the file might not have been applied to the actual site control file; consequently, the site might not be fully reconfigured. Solution: Site Control Manager will try to process the file again the next time a new delta site control file arrives at "%2" or the next time Site Control Manager is restarted, whichever comes first. You can force Site Control Manager to try to process the file again by stopping and restarting Site Control Manager using the Configuration Manager Service Manager application. | Warning |
| 2803 | A non-critical problem occurred while Site Control Manager was processing delta site control file %1. Possible cause: The file could be unnecessarily processed again, or it might temporarily seem that the site has not been fully reconfigured. Solution: Both of these problems will be resolved the next time a new delta site control file arrives at "%2" for processing, or the next time Site Control Manager is restarted, whichever comes first. You can force this to occur immediately by stopping and restarting Site Control Manager using the Configuration Manager Service Manager application. | Warning |
| 2804 | Site Control Manager aborted the processing of delta site control file %1. Possible cause: The delta site control file contained a corrupt or invalid site configuration change request. Any successfully processed site configuration change requests in this file will remain in effect (i.e., those changes will not be "undone" from the actual site control file). However, the corrupt site configuration change request and all subsequent site configuration change requests in this file, were not made to the site configuration. Solution: If the file was submitted by a ConfigMgr server component, the component will detect that the change was not made and will submit a new delta site control file, usually within a few minutes. If the file was submitted by the SMS Provider on behalf of one of its clients (such as the Configuration Manager Console), Hierarchy Manager will eventually detect that the change was not made and submit a new delta site control file. If the file was submitted by the SMS Provider at the current site, Hierarchy Manager should submit a new file within 24 hours. If the file was submitted by the SMS Provider at a parent site, it could take longer than 24 hours. You can cause a new file to be submitted immediately by stopping and restarting Hierarchy Manager at the site that submitted the file using the Configuration Manager Service Manager application. Hierarchy Manager will continue to submit new delta site control files until all outstanding site configuration change requests have been made. | Warning |
| 2805 | The delta site control file %1 contains a corrupt site configuration change request. This site configuration change request and the remaining site configuration change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2806 | The delta site control file %1 contains a site configuration change request that is missing a "%2" item, or that item is corrupt or invalid. The site configuration change request cannot be processed without this item. Possible cause: This site configuration change request and the remaining change requests in the file are unusable. Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 2807 | The delta site control file %1 contains a site configuration change request submitted by the "%2" SMS Provider client running as user "%3" on computer "%4" at site "%5" at "%6". The site configuration change request was assigned the serial number %7 at site "%5". Site Control Manager uses this serial number to ensure that it does not process the same site configuration change request from an SMS Provider client (such as the Configuration Manager Console) more than once. When an SMS Provider client submits a delta site control file containing a site configuration change request, Hierarchy Manager at the site submitting the file will report status message 3307. You can track the time on message 3307 and this one to determine when the site configuration change request was submitted and when it actually went into effect. | Informational |
| 2808 | The delta site control file %1 contains a site configuration change request submitted by the server component "%2" running as user "%3" on computer "%4" at "%5". | Informational |
| 2809 | Site Control Manager will ignore this site configuration change request ("%1" from site "%2"). This change request was already processed as part of an older delta site control file. Hierarchy Manager at site "%2" will continue to submit this site configuration change request until it receives a copy of the new actual site control file from site "%3" that confirms the change was successfully processed. If you find that Hierarchy Manager continues to submit this site configuration change request for an extraordinarily long time, there might be a problem with Hierarchy Manager at any of the sites between and including sites "%2" and "%3". Or, if "%2" and "%3" are different sites, there might be a communication problem between them or any sites between them. If you suspect this is happening, check for Warning and Error status messages from Hierarchy Manager, Replication Manager, Scheduler, and the Sender components at these sites. | Informational |
| 2810 | Site Control Manager created the temporary file "%1". In a moment, Site Control Manager will rename this file to %2, and it will become the new actual site control file. | Informational |
| 2811 | Site Control Manager created serial number %2 of the actual site control file %1. This creation occurred in response to a site configuration change request contained in delta site control file %3. The other Configuration Manager Server Components will detect that a new actual site control file is available, read it, and reconfigure themselves accordingly. | Informational |
| 2812 | Site Control Manager created serial number %2 of the actual site control file %1 as a result of processing delta site control file %3. No changes were made to the site configuration. | Informational |
| 2813 | Site Control Manager added a "%1" item named "%2" to the actual site control file %5. This addition occurred as a result of a site configuration change request in delta site control file %4. The change will take effect in serial number %3 of the actual site control file. | Informational |
| 2814 | Site Control Manager modified the properties of the "%1" item named "%2" in the actual site control file %7. This modification occurred as a result of a site configuration change request in delta site control file %6. The change will take effect in serial number %5 of the actual site control file. You can compare the file %3 with the file %4 to determine which properties changed. | Informational |
| 2815 | Site Control Manager deleted the "%1" item named "%2" from the actual site control file %5. This deletion occurred as a result of a site configuration change request contained in delta site control file %4. The change will take effect in serial number %3 of the actual site control file. | Informational |
| 2816 | The actual site control file %1 does not exist. Solution: The Configuration Manager Server Components cannot function without this file. Site Control Manager will shut down SMS Executive immediately. Contact Microsoft for help in restoring the actual site control file. | Error |
| 2817 | This computer "%1" is not the site server (%2). Solution: Site Control Manager can run only on the site server. Site Control Manager will shut down immediately. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 2818 | The actual site control file %1 does not contain a "%2" item. Solution: The Configuration Manager Server Components cannot run without this item. Site Component Manager will shut down SMS Executive immediately. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 2819 | Site Control Manager will maintain copies of the %1 most recent actual site control files in the directory "%2". The actual site control file %3 contains the configuration currently in use at this site. You can compare the files in the "%2" directory with each other to determine how the site configuration has changed over time. Each file is named ????????.ct0, where ???????? is the actual site control file serial number in hexadecimal format. For example, actual site control file 20 would be named 00000014.ct0. Also, if the current actual site control file %3 ever becomes corrupted or is ever accidentally deleted, you can restore it from one of the versions in the "%2" directory. Contact Microsoft for help before attempting to restore "%3" from one of these versions. | Informational |
| 2820 | Site Control Manager wrote a copy of the actual site control file %1 to %2. In a moment, Site Control Manager will move this file into the Hierarchy Manager inbox ("%3") for processing. | Informational |
| 2821 | Site Control Manager could not write a copy of the actual site control file %1 to %2. Consequently, Hierarchy Manager will not be notified that the site configuration has changed, and it might appear that the site has not been fully reconfigured. Solution: Site Control Manager will submit a new copy of the actual site control file to Hierarchy Manager the next time a new delta site control file is processed at "%3", or the next time Site Control Manager is restarted, whichever comes first. You can force this to occur immediately by stopping and restarting Site Control Manager using the Configuration Manager Service Manager application. | Warning |
| 2822 | The "%1" item in a site configuration change request in delta site control file %2 does not identify the change request as being valid. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2823 | The "%1" item in a site configuration change request in delta site control file %2 does not specify which site should receive the change request. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2824 | The "%1" item in a site configuration change request in delta site control file %2 specifies that the change request should be submitted to site "%3" instead of this site ("%4"). This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2825 | The "%1" item in a site configuration change request in delta site control file %2 does not specify which site submitted the change request. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2826 | The "%1" item in a site configuration change request in delta site control file %2 does not specify which computer submitted the change request. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2827 | The "%1" item in a site configuration change request in delta site control file %2 does not specify which user submitted the change request. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2828 | The "%1" item in a site configuration change request in delta site control file %2 does not specify which component submitted the change request. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2829 | The "%1" item in a site configuration change request in delta site control file %2 was submitted by a server component at site "%3", instead of this site ("%4"). This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2830 | The "%1" item in a site configuration change request in delta site control file %2 specifies a site type that does not match the current site's type. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2831 | The "%1" item in a site configuration change request in delta site control file %2 does not specify a site code. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2832 | The "%1" item in a site configuration change request in delta site control file %2 specifies a site code (%3) that does not match the current site's code (%4). This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2833 | The "%1" item in a site configuration change request in delta site control file %2 does not specify a site name. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2834 | The "%1" item in a site configuration change request in delta site control file %2 specifies a site name ("%3") that does not match the current site's name ("%4"). This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2835 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site server. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2836 | The "%1" item in a site configuration change request in delta site control file %2 specifies a site server name ("%3") that does not match the name of the current site server ("%4"). This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2837 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the domain of the site server. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2838 | The "%1" item in a site configuration change request in delta site control file %2 specifies a site server domain (%3) that does not match the site server's domain (%4). This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2839 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server's platform. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2840 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server installation directory. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2841 | The "%1" item in a site configuration change request in delta site control file %2 specifies a site server installation directory ("%3") that does not match the current site's installation directory ("%4"). This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2842 | The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the service account. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2843 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the service account. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2844 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of the service account. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2845 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the service account. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2846 | The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting the service account and password. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2847 | The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting the service account and password. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2848 | The "%1" item in a site configuration change request in delta site control file %2 specifies an service account name and/or password that cannot be decrypted with the specified public key. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2849 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting the address accounts and passwords. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2850 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL Server in use at this site. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2851 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site database. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2852 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator account. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2853 | The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the SQL administrator account. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2854 | The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting the SQL administrator account and password. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2855 | The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account name and/or password that cannot be decrypted with the specified public key. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2864 | The "%1" item in the actual site control file %2 does not contain a "%3" item named "%4", or that item is corrupt. As a result, the Configuration Manager Server Components might not be using the site system connection accounts you created in the Configuration Manager Console and might be unable to access some site systems. Solution: Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 2865 | Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager. This is the new actual site control file that contains the current configuration of this site. If this is a primary site, Hierarchy Manager will update this site's database with the copy. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy, updating each parent site's database. | Informational |
| 2866 | Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat site control file. Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration. Site Control Manager will then submit a heartbeat site control file to Hierarchy Manager at "%3". | Informational |
| 2867 | Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat site control file. Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration. | Informational |
| 2868 | Site Control Manager is configured so that no more heartbeat site control files will be submitted to Hierarchy Manager. Possible cause: If the site is functioning properly, this configuration will not produce any problems. However, if inter-site communication problems interrupt the proper replication of site control files and replicated site control files are lost, the site hierarchy might take a long time to recover or might not recover at all. During this time, parent sites might not have the most up-to-date configuration of this site. Solution: If this happens, you can either reconfigure Site Control Manager to submit heartbeat site control files again, or you can cause it to immediately submit a heartbeat site control file by stopping and restarting Site Control Manager using the Configuration Manager Service Manager application. | Warning |
| 2869 | The schedule at which Site Control Manager submits heartbeat site control files to Hierarchy Manager has changed. The next heartbeat site control file will be submitted at "%1". Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the heartbeat site control file up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration. | Informational |
| 2870 | The "%1" item in a site configuration change request in delta site control file %2contains a full version that's older than the current full version. This site configuration change request and the remaining change requests in the file are unusable. Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 3000 | Client Configuration Manager failed to read the site control file for site "%1." Solution: Do nothing. If CCM has just started, it will retry every hour, but if CCM has already read the site control file, it will continue to use the old data. Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than ConfigMgr 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. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run a site reset and reset the current installation. 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. | Error |
| 3001 | Client Configuration Manager failed to read the site identification values from the registry in \HKLM\Software\Microsoft\SMS\Identification key. Solution: Reboot. If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 3002 | Client Configuration Manager failed to connect to the registry of site server %1. Solution: Reboot. If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 3003 | Client Configuration Manager failed to read the account information for site %1. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run a site reset on the current installation. If you ignore this problem, CCM will continue using any Client Push Installation account that is available (if specified), but client installations might not be successful. | Error |
| 3004 | Client Configuration Manager failed to read the component item "%1" from the site control file on the server "%2". Possible cause: The file is being read from a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than ConfigMgr 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. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run a site reset on the current installation. 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. If you ignore this problem, CCM will continue using previously read information, but client installations might not be successful. | Error |
| 3005 | Client Configuration Manager failed to create a thread. Possible cause: The computer is low on memory or other resources. Solution: Reboot. | Error |
| 3006 | Client Configuration Manager failed to establish inbox "%1" on the site server. Solution: Do nothing. Client Configuration Manager will retry in the next interval (the default is one minute). Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 3008 | Client Configuration Manager failed to create an inbox rule to copy files "%1" from inbox "%2" to inbox "%3." Solution: Do nothing. Client Configuration Manager will retry in the next interval. Possible cause: The registry is full. Solution: Allocate more space for the registry. Possible cause: The computer is low on memory or other resources. Solution: Reboot, or stop and restart the SMS Executive. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 3009 | Client Configuration Manager reports that queue "%1" contains %2 Client Configuration Requests (CCRs), which exceeds the queue's threshold. Possible cause: If the Incoming queue threshold (default 100) or the Processing queue threshold (default 150) is being exceeded, there might suddenly be many clients needing installation, in which case simply be aware that it will take a while to get them all installed. However, it is more likely that this error means Client Configuration Manager is not processing CCRs properly. Solution: Stop and restart Client Configuration Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. Possible cause: If the Retry queue's threshold (default 150) is being exceeded, there is probably a client access problem. Solution: Verify that the site server computer account or (if specified) the Client Push Installation account have the required privileges, as specified in the ConfigMgr Documentation. | Warning |
| 3010 | In the past %3 hours, Client Configuration Manager has made %1 unsuccessful attempts to install the ConfigMgr client "%2". CCM will continue to attempt to install this client. Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the site server computer account or (if specified) the Client Push Installation account have the required privileges, as specified in the ConfigMgr Documentation. | Warning |
| 3011 | Client Configuration Manager failed to complete the ConfigMgr installation on client "%1". In the past %3 hours, CCM has made %2 unsuccessful attempts. Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the site server computer account or (if specified) the Client Push Installation account have the required privileges, as specified in the ConfigMgr Documentation. | Error |
| 3012 | Client Configuration Manager failed to complete its periodic account maintenance cycle. Possible cause: Network problems. Solution: Do nothing. Client Configuration Manager will retry in the next interval (the default is 30 days). This error will not cause problems with the operation of the site. The account maintenance cycle merely deletes obsolete domain accounts. | Error |
| 3013 | The Client Push Installation account list has been reset to a single account. Possible cause: Additional accounts were deleted. Solution: Add more Client Push Installation accounts for this site. | Warning |
| 3014 | Client Configuration Manager cannot connect to the machine "%1". Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the site server computer account or (if specified) the Client Push Installation account has the required privileges, as specified in the ConfigMgr Documentation. Possible cause: A Client Push Installation account was not specified, the account is not valid, is disabled, or has an expired password. Solution: Ensure one or more valid and active Client Push Installation accounts are specified in the Configuration Manager console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines. | Warning |
| 3015 | Client Configuration Manager cannot find machine "%1" on the network. Possible cause: The client is offline. Solution: Verify that the client is connected to the network. | Warning |
| 3016 | Client Configuration Manager cannot install a client to machine "%1", because it is not a supported platform for this action. Refer to the ConfigMgr documentation for the list of supported platforms. | Warning |
| 3017 | Client Configuration Manager cannot install a client to machine "%1", because it is a domain controler. CCM is currently configured to not install to domain controllers. | Warning |
| 3019 | Client Configuration Manager cannot install the client to machine "%1". This platform is not supported. Refer to the ConfigMgr documentation for the list of supported platforms. | Warning |
| 3200 | Inventory Processor failed to process MIF file %1. Possible cause: The MIF file is not formatted correctly. Solution: Check the inboxes\invproc\BADMIFs directory for the MIF. Determine what the error is, correct it, and resubmit the file. | Error |
| 3201 | Inventory Processor failed to process inventory RAW file %1. Possible cause: The file might be corrupt. Solution: The file will be moved to the inboxes\invproc.box\BADRAWs directory. Regenerate the RAW file by reinstalling the client. Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 3300 | Site "%1" (%2) is trying to report to a site that already reports to site "%1". This configuration is illegal because it creates a "loop" in the site hierarchy. Solution: Configure the site hierarchy properly; it must not contain loops. See the ConfigMgr documentation for information on how to create a proper site hierarchy. | Error |
| 3301 | Site "%1" (%2) has the same site code as another site. Possible cause: Hierarchy Manager has detected that a child site has the same site code as this site or another child site. Solution: Each site must have a unique site code. Deinstall the child site and reinstall it using a unique site code. | Error |
| 3302 | The parent site for this site cannot be changed from site "%1" (%2). Possible cause: You attempted to configure this site to report to a different parent site, but you attempted this using an Configuration Manager Console that was not connected to this site's database. Solution: To change configure this site to report to a different parent site, use an Configuration Manager Console that is connected to the this site's database. If this site is a secondary site, use Configuration Manager Setup to configure this site to report to a different parent site. | Error |
| 3303 | Hierarchy Manager cannot connect to the site database. 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 the site server computer account can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. 6. If the problem persists, check the SQL Server error logs. | Error |
| 3304 | Hierarchy Manager cannot save site information to the site database for site "%1". 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 the site server computer account can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. 6. If the problem persists, check the SQL Server error logs. | Error |
| 3305 | Hierarchy Manager detected that site code "%1" is already in use by existing site "%2". Possible cause: Site "%3" is using the same site code as another site. Solution: Each site must have a unique site code. Deinstall one of these sites and reinstall it using a unique site code. | Error |
| 3306 | Hierarchy Manager successfully processed "%1", which represented the site control file for site "%2" (%3). If this site is a primary site, Hierarchy Manager stored this site control file in the site database. If this site reports to a parent site, Hierarchy Manager instructed Replication Manager to replicate this file to the parent site at high priority. | Informational |
| 3307 | Hierarchy Manager detected that a change was requested by this site to the configuration of site "%1". Hierarchy Manager created a delta site control file for this request. If this site is site "%1", Hierarchy Manager submitted this file to Site Control Manager at this site. If site "%1" is a child site, Hierarchy Manager instructed Replication Manager to deliver the file to Site Control Manager at site "%1" at high priority. | Informational |
| 3308 | Hierarchy Manager cannot reinstall the Site Component Manager. Possible cause: Due to an OS error, the Site Component Manager is marked for deletion. Solution: Perform a site reset and then reboot the site server to recover from this error. | Error |
| 3309 | Hierarchy Manager reinstalled Site Component Manager. Site Component Manager will now reinstall all of the other server components at this site. | Informational |
| 3310 | Hierarchy Manager has initiated remote installation of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components. | Informational |
| 3311 | Hierarchy Manager has initiated remote upgrade of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components. | Informational |
| 3312 | Hierarchy Manager has initiated remote deinstallation of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components. | Informational |
| 3313 | Hierarchy Manager failed to execute site maintenance task "%1". Possible cause: Service containing the maintenance task, %1, is not installed or in not running. Solution: Check the status of the service containing the maintenance task. | Warning |
| 3317 | Hierarchy Manager cannot add machine account %1 for secondary site %2 to the address group %3, this must be done manually. | Warning |
| 3318 | Hierarchy Manager cannot add address account %1 for secondary site %2 to the address group %3, this must be done manually. | Warning |
| 3320 | The secondary site upgrade failed because either the prerequisite checker has not been run without errors on secondary site %1 in the past seven days or it has not been run at all. Follow the corrective steps that are required for the failed prerequisite rules to pass. You must restart the secondary site upgrade after the prerequisite checker has been re-run and passed without errors. | Error |
| 3321 | Hierarchy Manager detected that this site's client computer communication method is set to allow HTTPS only. | Informational |
| 3322 | Hierarchy Manager cannot remove the computer account of site system %1 from database role %2. This needs to be done manually. | Warning |
| 3323 | Hierarchy Manager detected that this site's client computer communication method is set to allow either HTTPS or HTTP. | Informational |
| 3324 | Hierarchy Manager detected that the public key of this site in the site control file is no longer valid and has updated it with the new public key. The password of all the accounts need to be reset through the Configuration Manager Console. The bootmedia CDs created on the site may also need to be recreated. Please refer to your Configuration Manager documentation or the Microsoft Knowledge Base for further information. | Warning |
| 3330 | Hierarchy Monitoring detected that the SQL Server %1 machine certificate is still valid. | Informational |
| 3331 | Hierarchy Monitoring detected that the SQL Server %1 machine certificate has missed. | Warning |
| 3332 | Hierarchy Monitoring detected that the SQL Server %1 machine certificate has missed. It is failed to remediate with Error %2. | Error |
| 3333 | Hierarchy Monitoring detected that the SQL Server %1 machine certificate has been remediated. | Informational |
| 3334 | Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate is still valid. | Informational |
| 3335 | Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has missed. | Warning |
| 3336 | Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has been expired. | Warning |
| 3337 | Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has missed or is expired, and failed to remediate with Error %2. | Error |
| 3338 | Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has been remediated. | Informational |
| 3339 | Hierarchy Monitoring detected that the SQL Server %1 Port %2 still valid. | Informational |
| 3340 | Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been changed to %3. | Warning |
| 3341 | Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been changed to %3, and failed to remediate with Error %4. | Error |
| 3342 | Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been remediated from %3. | Informational |
| 3343 | Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 still valid. | Informational |
| 3344 | Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been changed to %3. | Warning |
| 3345 | Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been changed to %3, and failed to remediate with Error %4. | Error |
| 3346 | Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been remediated from %3. | Informational |
| 3347 | Hierarchy Monitoring detected that all ConfigMgr SQL Server Roles are still valid. | Informational |
| 3348 | Hierarchy Monitoring detected that the following ConfigMgr SQL Server Roles [%1] are missing. | Warning |
| 3349 | Hierarchy Monitoring detected that the following ConfigMgr SQL Server Roles [%1] are missing. | Error |
| 3350 | The following missing ConfigMgr SQL Server Roles [%1] have been added back. | Informational |
| 3351 | Hierarchy Monitoring detected that the ConfigMgr SQL Server ports %1 are still active on Firewall exception. | Informational |
| 3352 | Hierarchy Monitoring detected that the ConfigMgr SQL Server ports %1 are not active on Firewall exception. | Warning |
| 3353 | Hierarchy Monitoring detected that the ConfigMgr SQL Server %2 ports %1 are not active on Firewall exception. | Error |
| 3354 | Hierarchy Monitoring has added the ConfigMgr SQL Server ports %1 into the Firewall exception. | Informational |
| 3355 | Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 still valid. | Informational |
| 3356 | Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is missing. | Warning |
| 3357 | Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is missing. | Error |
| 3358 | Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is valid after remediation. | Informational |
| 3359 | Hierarchy Monitoring detected that the ConfigMgr Database file location is still valid. | Informational |
| 3360 | Hierarchy Monitoring detected that the ConfigMgr Database file location is invalid. | Warning |
| 3361 | Hierarchy Monitoring detected that the ConfigMgr Database file location is invalid. | Error |
| 3362 | Hierarchy Monitoring detected that the ConfigMgr Database File Disk still has enough free space. | Informational |
| 3363 | Hierarchy Monitoring detected that the Database File Disk (%1) is short of space. | Warning |
| 3364 | Hierarchy Monitoring detected that the Database File Disk (%1) is running out of space. | Error |
| 3365 | Hierarchy Monitoring detected that the Database File Disk still has enough free space. But there is no alert configured. Please use Site System properties to configure alerts. | Informational |
| 3366 | Hierarchy Manager cannot search the Active Directory. Possible cause: Active Directory problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the Active Directory computer. 3. Verify that Active Directory services are running. 4. Verify that the site server computer account can access the Active Directory. 5. If the problem persists, check the Active Directory error logs. | Error |
| 3367 | Hierarchy Manager detected that the feature data is invalid for feature (%1). The feature exposure state will be set to false now. | Error |
| 3400 | Scheduler does not have an address defined at site "%2" for site "%1". Files cannot be sent from site "%2" to site "%1" until an address is defined. Solution: Define a valid address at site "%2" for site "%1" in the Configuration Manager Console under Site Hierarchy -> %2 -> Site Settings -> Addresses. | Error |
| 3401 | Scheduler has data to send to site "%1", and addresses defined at site "%2" for site "%1", but none of them are available for sending at this time. Solution: If you purposefully configured the addresses this way, ignore this message. Otherwise, modify the addresses' scheduling in the Configuration Manager Console under Site Hierarchy -> %2 -> Site Settings -> Addresses. | Warning |
| 3402 | Scheduler at site %1 has received package %2 version %3 and has instructed the Sender to send the package to the following sites: %4. | Informational |
| 3500 | The sender cannot connect to remote site "%1" over the LAN. Possible cause: Remote site server "%2" might not be connected to the LAN. Solution: Verify that site server "%2" is connected to the LAN and functioning properly. Possible cause: Share "%3" might not be accessible. Solution: Verify that share "%3" is visible and that the address connection account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network. | Error |
| 3501 | The sender cannot connect to site "%1" over RAS. Possible cause: Remote site server "%2" might be down. Solution: Verify that remote site server "%2" is connected to the network and functioning properly. Possible cause: Remote site server "%2" might not be running RAS Server Service. Solution: Verify that remote site server "%2" is running RAS Server Service. Possible cause: The phone book entry "%3" in the default phone book might not contain the correct information. Solution: Verify that the phone book entry "%3" contains valid information. Possible cause: Share "%4" might not be accessible. Solution: Verify that share "%4" is visible and that the address connection account has the necessary permissions to access the share. For a detailed explanation of the RAS error code, see the Windows NT documentation. | Error |
| 3502 | The address to site "%1" is invalid. Possible cause: The destination site server name is missing. Solution: Define a valid address in the Configuration Manager Console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses. | Error |
| 3503 | The address to site "%1" is invalid. Possible cause: The destination share name is missing. Solution: Define a valid address in the Configuration Manager Console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses. | Error |
| 3504 | The sender cannot install secondary site "%1" on server "%2". Possible cause: The targeted installation directory "%3" does not reside on an NTFS partition. Solution: Select an NTFS partition for the installation directory or convert the current partition to NTFS. | Error |
| 3505 | The sender cannot install secondary site "%1" on server "%2" because the sender cannot create the Bootstrap initialization file "%3". Possible cause: The site server computer account for site "%1" might not have the appropriate privileges to create the initialization file Solution: Verify that the account has Administrator privileges to server "%2". Possible cause: There is not enough free disk space on server "%2". Solution: Make more space available on the destination drive. | Error |
| 3506 | The sender cannot install secondary site "%1" on server "%2" because it cannot retrieve the encryption public key. Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 3507 | The sender cannot install secondary site "%1" on server "%2" because it cannot query the status of the Configuration Manager Bootstrap service on server "%2". Possible cause: The computer account for site "%1" might not have the appropriate privileges to server "%2". Solution: Make sure the service account has Administrator privileges to server "%2". | Error |
| 3508 | The sender cannot install secondary site "%1" on server "%2" because it cannot stop the Configuration Manager Bootstrap service on server "%2". Possible cause: The computer account for site "%1" might not have the appropriate privileges to server "%2". Solution: Make sure the account has Administrator privileges to server "%2". | Error |
| 3509 | The sender cannot install, upgrade, or deinstall secondary site "%1" on server "%2". Possible cause: The server is running Windows %3 %4, but this does not meet the minimum installation requirements for an Configuration Manager Site Server. Solution: Install a version of Windows that meets the installation requirements. Please refer to your ConfigMgr Documentation for more information. | Error |
| 3510 | The sender cannot install secondary site "%1" on server "%2". Possible cause: The server is already in use as a site system for another site. Solution: Install secondary site "%1" on a different server. | Error |
| 3511 | The sender cannot install secondary site "%1" on server "%2" because the sender could not copy the Configuration Manager Bootstrap service file from "%3" to "%4". Possible cause: The computer account for site "%1" might not have the appropriate privileges to create the destination file. Solution: Verify that the account has Administrator privileges to server "%2". Possible cause: There is not enough free disk space on server "%2". Solution: Make more space available on the destination drive. | Error |
| 3512 | The sender cannot install secondary site "%1" on server "%2" because the sender failed to install the Configuration Manager Bootstrap service. Possible cause: The site server computer account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the "Log on as a service" right on server "%2". | Error |
| 3513 | The sender cannot install secondary site "%1" on server "%2" because the sender cannot start the Configuration Manager Bootstrap service. Possible cause: The site server computer account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the "Log on as a service" right on server "%2". | Error |
| 3514 | The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the installation of secondary site "%2" by running Configuration Manager Setup with a script that specifies the installation parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1". | Informational |
| 3515 | The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the upgrade of secondary site "%2" by running Configuration Manager Setup with a script that specifies the upgrade parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1". | Informational |
| 3516 | The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the deinstallation of secondary site "%2" by running Configuration Manager Setup with a script that specifies the deinstallation parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1". | Informational |
| 3517 | Sender failed to send files to destination site %1. Make sure the address account has full access to directory "%2" on the destination site server and the destination site server has sufficient free disk space on the ConfigMgr installation drive. | Error |
| 3518 | %1 failed to start. Possible cause: Server "%2" might not be running RAS Server Service. Solution: Verify that server "%2" is running RAS Server Service. | Error |
| 3522 | The sender cannot install secondary site "%1" on server "%2" because some fatal error occured in Configuration Manager Bootstrap service running on secondary site server. Please review smssetup.log on the secondary site server for troubleshooting the problem. The smssetup.log is located at the root of the system drive. Once the problem is resolved, delete the secondary site object in the Configuration Manager Administrator's Console and rerun the secondary site creation wizard. | Error |
| 3523 | The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", started Configuration Manager Setup successfully. | Informational |
| 3524 | The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", failed to start Configuration Manager Setup. Please check the logs on secondary site. | Error |
| 3525 | The Configuration Manager Setup running on secondary site "%1" on server "%2" has completed. | Informational |
| 3526 | The Configuration Manager Setup running on secondary site "%1" on server "%2", failed. Please check the logs on secondary site. | Error |
| 3527 | The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", started package decompression. | Informational |
| 3528 | The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", completed successfully. | Informational |
| 3529 | The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", failed to connect to parent site. Possible cause: Either connection to the parent site is unavailable or the sender address provided is not correct. Solution: If the secondary site does not show up even if the connection is there, please reinstall the site with correct sender address. | Warning |
| 3530 | The sender cannot connect to remote site "%1" over the LAN. Possible cause: Remote site server "%2" might not be connected to the LAN. Solution: Verify that site server "%2" is connected to the LAN and functioning properly. Possible cause: Share "%3" might not be accessible. Solution: Verify that share "%3" is visible and that the site server machine account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network. | Error |
| 3531 | Sender is currently sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed. | Informational |
| 3532 | Sender encountered errors while sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed. | Warning |
| 3533 | Sender has successfully sent software distribution package %1 version %2 to site %3. | Informational |
| 3600 | Inbox Manager cannot copy files from "%1" to "%2". Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network. | Warning |
| 3601 | Inbox Manager cannot create directory "%1" with the desired security rights on server "%2". Possible cause: The destination drive is full. Solution: Make more space available on that drive. | Error |
| 3603 | Inbox Manager cannot create directory "%1" with the desired security rights on site system "%2". (The site system is shown here as a network abstraction layer (NAL) path.) Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network. | Error |
| 3604 | Inbox Manager Assistant running on the client access point "%1" cannot connect to site server "%2". Possible cause: The site server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site server is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing Inbox Manager Assistant from properly accessing the site server. Solution: Investigate and correct any problems with your network. | Error |
| 3605 | Inbox Manager cannot create the client access point on site system "%1". Possible cause: Site system "%1" does not have any drives or volumes that support file and directory permissions. For example, the FAT file system does not support permissions, but the NTFS file system does. Solution: Choose a site system that supports file and directory permissions. | Error |
| 3606 | SMS Inbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds. Possible cause: Site server "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site server "%4" has a high backlog of files in its inboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further. | Warning |
| 3607 | SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds. Possible cause: Site system "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site system "%4" has a high backlog of files in its outboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further. | Warning |
| 3700 | Software Inventory Processor successfully processed %1 software inventory files. | Informational |
| 3701 | Software Inventory Processor failed to process software inventory file "%1," and has moved it to "%2." Possible cause: The file attempted to update inventory information in the site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the subsequent message 3703, which indicates the resynchronization has begun. | Error |
| 3701 | Software Inventory Processor failed to process software inventory file "%1," and has moved it to "%2." Possible cause: The file attempted to update inventory information in the site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the subsequent message 3703, which indicates the resynchronization has begun. | Warning |
| 3702 | Software Inventory Processor is terminating its processing cycle due to a 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 the site can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. | Error |
| 3703 | Software Inventory Processor requested a resynchronization for machine "%1" because an attempt was made to update inventory information in the site database that does not already exist. | Informational |
| 3704 | Software Inventory Processor has removed the oldest revision of collected file "%1" for resource "%2". The maximum revision number for a collected file has been reached, so the oldest copy has been replaced by the most recent copy. | Informational |
| 3705 | Software Inventory Processor is updating database statistics. By default, statistics are updated to optimize SQL Server database performance after every 500 software inventory files have been processed. You can edit this value in the Configuration Manager Console, under Component Configuration, Data Processing and Storage Properties. | Informational |
| 3706 | Software Inventory Processor was unable to store collected file "%1" for resource "%2". Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. | Warning |
| 3707 | Software Inventory Processor failed to process software inventory file "%1" because the file does not have a corresponding discovery record. Software Inventory Processor has moved this file to the Orphans directory as file "%2" and will retry processing it later. When Software Inventory Processor receives a software inventory file, it acquires the unique numeric ID for the file it is processing from the discovery data in the site database. If this cannot be found, a discovery data record (DDR) is generated, and the software inventory file is temporarily moved to the Orphans directory, where Software Inventory Processor retries the file every 10 minutes. Possible cause: Discovery Data Manager is not running. Solution: Stop and restart Discovery Data Manager. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components. | Warning |
| 3708 | Software Inventory Processor failed to process the file %1 because it is larger than the defined maximum allowable size of %2. Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_SOFTWARE_INVENTORY_PROCESSOR\Max File Size (the default is 5 MB), and wait for Software Inventory Processor to retry the operation. | Error |
| 3709 | Software Inventory Processor requested a resynchronization for machine "%1" because a software inventory file was sent without a public key information. | Informational |
| 3800 | Received more than 10 NULL status message pointers from the Offer Status Queue. | Error |
| 3801 | Unable to create a file to store the replication data at %1. | Error |
| 3802 | Unable to open the incoming %1 replication file. | Error |
| 3803 | While initializing, no records of the proper type were found in the data store. | Error |
| 3804 | Received a status message from site %1, but this is site %2. Ignoring message. | Informational |
| 3805 | The Offer summary %1,%2 has not been heard from for %3 days. This summary has been marked for deletion. | Informational |
| 3806 | Failed to send the replication file. Will try again later. | Warning |
| 3807 | Interval %1 not found in OfferSummaryDetail record. | Warning |
| 3808 | No data store was found at %1 to initialize from. | Warning |
| 3809 | The file %1 is not the correct type of replication file for this summarizer, deleting the file. | Warning |
| 3810 | Unable to create a file to store the summary data. Will try again in %1 seconds. | Warning |
| 3811 | Unable to send changed records to the data store. Will try again in %1 seconds. | Warning |
| 3812 | Offer Status Summarizer cannot process a status message because it has an invalid message ID %1. The message ID must be within the range 10000 to 10099. As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information. | Warning |
| 3813 | Offer Status Summarizer cannot process a status message because it does not contain a deployment ID. As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message (ID %1) was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information. | Warning |
| 3814 | Offer Status Summarizer cannot process a status message because it contains the invalid deployment ID "%6". As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message (ID %1) was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information. | Warning |
| 3900 | SMS Offer Manager successfully processed new deployment %1. | Informational |
| 3901 | SMS Offer Manager successfully removed deployment %1. | Informational |
| 4000 | Replication Manager successfully instructed Scheduler to send files to site "%1". | Informational |
| 4001 | Replication Manager received files from the "%1" component at a child site, but that component is not enabled at the current site. Replication Manager will throw away these files. Solution: Either enable component "%1" at the current site, or reconfigure it at all child sites to not replicate to the current site. | Warning |
| 4200 | Server Discovery Agent failed to read the necessary registry information. Possible cause: The registry information is not available yet. Solution: Server Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 4201 | Server Discovery Agent failed to read the location of the outbox. Possible cause: The information necessary to complete the initialization is not available now. Solution: Windows NT Server Discovery Agent is waiting for the information to become available and will retry at its next interval. | Warning |
| 4202 | Server Discovery Agent read the system roles and found %1 server role entries in the site control file. Windows NT Server Discovery Agent identified %2 unique servers in the server roles and generated %3 discovery data records (DDRs) and %4 errors while attempting to create DDRs. | Informational |
| 4400 | Despooler successfully stored the compressed binaries for package "%1" at "%2". | Informational |
| 4401 | Despooler failed to decompress package "%1" from "%2". Possible cause: The compressed image "%2" is either missing or corrupt. Solution: Distribution Manager will attempt to recover the package by requesting a new compressed package image from the site that sent it. | Error |
| 4402 | Despooler failed to merge delta to the compressed package "%1". Possible cause: The destination drive is full. Solution: Make more space available on that drive. Despooler will attempt to merge the delta again during its next retry interval | Error |
| 4403 | Obsolete. | Error |
| 4404 | Despooler received an instruction and package file from site %1 that contains that site's public key, however the despooler cannot find a valid public key to verify the signature of the package. Because this site does not allow unsigned key exchange between sites, the instruction cannot be processed and will be retried. Solution: Extend the Active Directory schema to allow ConfigMgr sites to publish their public keys into AD, or use the preinst.exe tool to manually replicate the public keys, or change the site property site connection setting in the Administrator UI to allow unsigned key exchange between sites. | Error |
| 4405 | Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site replication data, however the despooler does not have the public key to verify the signature of the package. The instruction cannot be processed and will be retried. Solution: Extend the Active Directory schema to allow sites to publish their public keys into AD, or use the preinst.exe tool to manually replicate the public keys. | Error |
| 4406 | Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site replication data, however either the signature on the package or the hash algorithm ID used for the signature is not valid, the despooler will delete the instruction and the package file. | Error |
| 4407 | Despooler successfully received the compressed image for package %1 version %2. | Informational |
| 4500 | Sent a replication file to %1. | Informational |
| 4501 | A replication file has been created, the replication file is %1. | Informational |
| 4502 | Processing the incoming replication file %1. | Informational |
| 4503 | The file %1 is not a replication file for this summarizer, deleting the file. | Informational |
| 4504 | Unable to decrypt the SQL Server login user name and/or password. | Warning |
| 4505 | Unable to find this summarizer's component section in the site control file. | Warning |
| 4506 | Unable to open the site control file. | Warning |
| 4507 | Unable to read the site configuration. | Warning |
| 4508 | An error occurred while setting or resetting a change notification for the site control file. | Warning |
| 4509 | An error occurred while setting or resetting a change notification for the summarizer's inbox. | Warning |
| 4510 | Unable to create the status message queue. | Warning |
| 4511 | Failed to send a replication file to site %1. | Warning |
| 4512 | The data store %1 was not found. | Warning |
| 4513 | .Could not read all of the records in the file %1. The error code is %2. | Warning |
| 4514 | Unable to write changed records to the data store. | Warning |
| 4515 | Unable to initialize the summarizer. The returned error code is %1. | Error |
| 4516 | The site properties are not set in the registry. | Error |
| 4517 | The error %1 has occurred while initializing the status message queue. | Error |
| 4518 | The summarizer cannot continue and is stopping. The exit code is %1. | Error |
| 4519 | The reset request list %1 is too old. It was sent on %2 from %3, by user %4, on system %5, at site %6. | Informational |
| 4520 | Reset specific tally intervals as requested from %1, by user %2, on system %3, at site %4. | Informational |
| 4600 | Component Status Summarizer detected that the list of Component Status Display Intervals specified in the site control file has changed. Component Status Summarizer will reconfigure itself to use the new set of Display Intervals. | Informational |
| 4601 | Component Status Summarizer detected that entry "%1" of the Component Thresholds property list in the site control file is corrupt. Possible cause: The site control file entry does not contain a component name. Solution: Component Status Summarizer will ignore this entry, which might result in the Status column of the Component Status display in the Configuration Manager Console being improperly set for a particular component. This problem might be the result of a code defect. If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 4602 | Component Status Summarizer received a status message from component "%1", running on computer "%2", but there is no record of this component in the site control file. Possible cause: Component Status Summarizer will now begin tracking the status of this component as if it were properly listed in the site control file. If this component is a ConfigMgr component, it could mean the component should have been deinstalled sometime in the past by Site Component Manager. Solution: Investigate whether or not the component should really be installed and running on this computer. If it should not be installed, the problem might be the result of defective code. If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 4603 | Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Informational status messages during the Component Status Threshold Period. Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Informational status messages for the component. Solution: Component Status Summarizer will set the component's status to Critical in the Component Status summary in the Configuration Manager Console. | Informational |
| 4604 | Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status messages during the Component Status Threshold Period. Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Warning status messages for the component. Solution: Component Status Summarizer will set the component's status to Critical in the Component Status summary in the Configuration Manager Console. | Informational |
| 4605 | Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status messages during the Component Status Threshold Period. Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Error status messages for the component. Solution: Component Status Summarizer will set the component's status to Critical in the Component Status summary in the Configuration Manager Console. | Informational |
| 4606 | Component Status Summarizer detected that component "%1" running on computer "%2" has reported %3 or more Informational status messages during the Component Status Threshold Period. Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Informational status messages for the component. Solution: If the component's status is not already set to Warning, Component Status Summarizer will set the component's status to Warning in the Component Status summary in the Configuration Manager Console. | Informational |
| 4607 | Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status messages during the Component Status Threshold Period. Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Warning status messages for the component. If the component's status is not already set to Warning, Component Status Summarizer will set the component's status to Warning in the Component Status summary in the Configuration Manager Console. | Informational |
| 4608 | Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status messages during the Component Status Threshold Period. Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Error status messages for the component. Solution: If the component's status is not already set to Warning, Component Status Summarizer will set the component's status to Warning in the Component Status summary in the Configuration Manager Console. | Informational |
| 4609 | Component Status Summarizer set the status of component "%1", running on computer "%2", to Critical. Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examining the status messages that the component reports. 2. Correcting the problem. 3. Instructing Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the Configuration Manager Console. When the counts are reset, Component Status Summarizer will change the status of the component to OK. This might take some time if site "%3" is a child site. 4. Delete any unwanted status messages from the site database, if necessary. 5. Monitor the component occasionally to verify that the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the Configuration Manager Console. Possible cause: The component is flooding the status system by rapidly reporting the same message repeatedly. Solution: Diagnose and control the flood of status messages by: 1. Verifying that the component is actually flooding the status system. View the status messages reported by the component and verify that the same message is continually reported every several minutes or seconds. 2. Noting the Message ID of the flooded status message. 3. Creating a Status Filter Rule for site "%3" that instructs Status Manager to discard the flooded status message when component "%1" on computer "%2" reports it. 4. Verifying that your sites' databases were not filled up by the flooded status message. Delete any duplicate status messages from the site database, if necessary. 5. Refer to the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 4610 | Component Status Summarizer set the status of component "%1" running on computer "%2" to Warning. Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examine the status messages that the component reports. 2. Correcting the problem. 3. Instructing Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the Configuration Manager Console. When the counts are reset, Component Status Summarizer will change the status of the component to OK. This might take some time if site "%3" is a child site. 4. Deleting any unwanted status messages from the site database, if necessary. 5. Monitor the component occasionally to verify the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the Configuration Manager Console. Possible cause: The component is "flooding" the status system by rapidly reporting the same message repeatedly. Solution: Diagnose and control the flood of status messages by: 1. Verifying that the component is actually flooding the status system. View the status messages reported by the component, and verify that the same message is continually reported every several minutes or seconds. 2. Noting the Message ID of the flooded status message. 3. Creating a Status Filter Rule for site "%3" that instructs Status Manager to discard the flooded status message when component "%1" on computer "%2" reports it. 4. Verifying that your sites' databases were not filled up by the flooded status message. Delete any duplicate status messages from the site database, if necessary. 5. Refer to the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 4611 | Component Status Summarizer reset the status of component "%1", running on computer "%2", to OK. Component Status Summarizer will automatically reset a component's status to OK every time the Component Status Threshold Period elapses and a new Threshold Period begins. For example, if the Threshold Period is "Since 12:00:00 AM", Component Status Summarizer will reset the component's status to OK every 24 hours at midnight. At this time, the counts of status messages reported by the component for the Threshold Period will be reset to zero. Solution: Component Status Summarizer will also reset a component's status to OK when an administrator manually resets the counts of status messages reported by the component for the Threshold Period. Solution: Component Status Summarizer will also reset a component's status to OK when an administrator adjusts the Component Status Thresholds to be higher than the current counts of status messages reported by the component. | Informational |
| 4612 | Component Status Summarizer has not received a status message from component "%1", running on computer "%2", in %3 hours. Possible cause: There is no record of this component in the site control file. Solution: The Component Status Summarizer will assume the component was deinstalled and will remove it from the Component Status summary. | Warning |
| 4613 | Component Status Summarizer received a status message that was reported by component "%1", running on computer "%2" at site "%3", which is not the site where Component Status Summarizer is running. Possible cause: Component Status Summarizer is designed to process only status messages reported by components at the site where Component Status Summarizer is running. Solution: Component Status Summarizer will ignore this status message. Possible cause: This problem might be the result of defective software. Solution: If you suspect a software defect, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 4614 | Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4615 | Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4616 | Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4617 | Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4618 | Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "%9" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". Possible cause: "%9" is a custom Display Interval you have configured the Component Status Summarizer to use. Component Status Summarizer cannot display a an unencrypted version of "%9" in a status message. Solution: If you wish to decode "%9" into something more readable, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 4619 | Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4620 | Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4621 | Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4622 | Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4623 | Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "%9" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". "%9" is an encrypted version of the custom Display Interval you configured the Component Status Summarizer to use. Component Status Summarizer cannot display an unencrypted version of "%9" in a status message. | Informational |
| 4624 | Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4625 | Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4626 | Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4627 | Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". | Informational |
| 4628 | Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "%9" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". "%9" is an encrypted version of the custom Display Interval that you configured the Component Status Summarizer to use. Component Status Summarizer cannot display an unencrypted version of "%9" in a status message. | Informational |
| 4629 | Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Online. | Informational |
| 4630 | Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Failed. Possible cause: This component has failed to generate a heartbeat within its heartbeat interval or has reported with its heartbeat that it is in a failure state. Solution: Verify that the condition persists by examining compmon.log and then check the component's log file. | Informational |
| 4631 | Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Degraded. Possible cause: This component has with its heartbeat that it is in a degraded state. Solution: Verify that the condition persists by examining the component's log file and performance counters. | Informational |
| 4632 | Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Offline. Possible cause: This component is under maintenance or shutdown. Solution: Verify that maintenance is not being performed at this time and the component is running. If the component is not running, restart it using Configuration Manager Service Manager. | Informational |
| 4633 | Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Unknown. Possible cause: This component does not have an Availability State, it could not be accessed or it has not been updated. Solution: Verify that the Site Server can connect to the registry of the server on which this component resides. | Informational |
| 4700 | Site System Status Summarizer could not access storage object "%1" on site system "%2". Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object. Solution: Verify that the accounts are properly configured to allow the site to connect to the site system and access the storage object. Possible cause: Network problems are preventing Site System Status Summarizer from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend to use it as a site system any more. Solution: Remove the site system from the list of site systems used by this site; this list appears in the Site Systems node of the Configuration Manager Console. Possible cause: You accidentally deleted the storage object or took the storage object out of service. Solution: The site components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other site components to verify that this occurs properly. Site System Status Summarizer will now set the storage object's status to Critical in the Site System Status summary in the Configuration Manager Console. When you correct the problem and Site System Status Summarizer successfully accesses the storage object, Site System Status Summarizer will set the storage object's status to OK, providing that the storage object has sufficient free space. | Informational |
| 4701 | Site System Status Summarizer still cannot access storage object "%1" on site system "%2". Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object. Solution: Verify that the accounts are properly configured to allow the site to connect to the site system and access the storage object. Possible cause: Network problems are preventing Site System Status Summarizer from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend on using it as a site system any more. Solution: Remove the site system from the list of site systems used by this site; this list appears under Site Systems in the Configuration Manager Console. Possible cause: You accidentally deleted the storage object or took the storage object out of service. Solution: The components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other site components to verify that this occurs properly. The storage object has been inaccessible since "%3". When you correct the problem and Site System Status Summarizer successfully accesses the storage object, Site System Status Summarizer will set the storage object's status to OK, providing that the storage object has sufficient free space. | Informational |
| 4702 | Site System Status Summarizer successfully accessed storage object "%1" on site system "%2". Possible cause: The storage object had been inaccessible since "%3". Solution: If the storage object has sufficient free storage space, Site System Status Summarizer will now restore the status of the storage object to OK in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4703 | Site System Status Summarizer could not access the "%1" database on site database Server "%2". Possible cause: The site database Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the Configuration Manager Console. Solution: Verify that the SQL Server account in the Configuration Manager Console contains the correct user name and password, and that the account has sufficient access rights to the site database Server. Possible cause: Network problems are preventing Site System Status Summarizer from connecting to the site database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your ConfigMgr site. Site System Status Summarizer will now set the status of the "%1" database to Critical in the Site System Status summary in the Configuration Manager Console. When you correct the problem and Site System Status Summarizer successfully accesses the database, Site System Status Summarizer will set the status of the "%1" database to OK, providing that the database has sufficient free space. | Informational |
| 4704 | Site System Status Summarizer still cannot access the "%1" database on site database Server "%2". Possible cause: The site database Server is turned off, not connected to the network, or not functioning properly. Solution: verify that the site database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the Configuration Manager Console. Solution: Verify that the SQL Server account in the Configuration Manager Console contains the correct user name and password, and that the account has sufficient access rights to the site database Server. Possible cause: Network problems are preventing Site System Status Summarizer from connecting to the site database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your ConfigMgr site. The database has been inaccessible since "%3". When you correct the problem and Site System Status Summarizer successfully accesses the database, Site System Status Summarizer will set the status of the database to OK, providing that the database has sufficient free space. | Informational |
| 4705 | Site System Status Summarizer successfully accessed the "%1" database on SQL Server "%2". Possible cause: The database had been inaccessible since "%3". Solution: If the database has sufficient free space, Site System Status Summarizer will now restore the status of the database to OK in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4706 | Site System Status Summarizer could not access the transaction log for the "%1" database on SQL Server "%2". Possible cause: The site database Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the Configuration Manager Console. Solution: Verify that the SQL Server account in the Configuration Manager Console contains the correct user name and password, and that the account has sufficient access rights to the site database Server. Possible cause: Network problems are preventing Site System Status Summarizer from connecting to the site database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your ConfigMgr site. Site System Status Summarizer will now set the status of the transaction log to Critical in the Site System Status summary in the Configuration Manager Console. When you correct the problem and Site System Status Summarizer successfully accesses the transaction log, Site System Status Summarizer will set the status of the transaction log to OK, providing that the transaction log has sufficient free space. | Informational |
| 4707 | Site System Status Summarizer still cannot access the transaction log for the "%1" database on SQL Server "%2". Possible cause: The SQL Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SQL Server computer is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the Configuration Manager Console. Solution: Verify that the SQL Server account in the Configuration Manager Console contains the correct user name and password, and that the account has sufficient access rights to the SQL Server computer. Possible cause: Network problems are preventing Site System Status Summarizer from connecting to the SQL Server computer. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your ConfigMgr site. The transaction log has been inaccessible since "%3". When you correct the problem and Site System Status Summarizer successfully accesses the transaction log, Site System Status Summarizer will set the status of the transaction log to OK, providing that the transaction log has sufficient free space. | Informational |
| 4708 | Site System Status Summarizer successfully accessed the transaction log for the "%1" database on SQL Server "%2". The transaction log had been inaccessible since %3. Providing that the transaction log has sufficient free space, Site System Status Summarizer will now restore the status of the transaction log to OK in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4709 | Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is above the Free Space Thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to OK in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4710 | Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is less than or equal to the Warning Free Space Threshold of %4 KB. Possible cause: The storage object is almost full. Solution: Make more space available on the storage object by deleting unneeded files. Possible cause: The Warning Free Space Threshold is set too high for this storage object. Solution: Decrease the Warning Free Space Threshold in the Configuration Manager Console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to Warning in the Site System Status summary in the Configuration Manager Console. | Warning |
| 4711 | Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is less than or equal to the Critical Free Space Threshold of %4 KB. Possible cause: The storage object is almost full. Solution: Make more space available on the storage object by deleting unneeded files. Possible cause: The Critical Free Space Threshold is set too high for this storage object. Solution: Decrease the Critical Free Space Threshold in the Configuration Manager Console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to Critical in the Site System Status summary in the Configuration Manager Console. | Error |
| 4712 | Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the database. Site System Status Summarizer will now set the status of the database to OK in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4713 | Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Warning Free Space Threshold of %4 KB. Possible cause: The database is almost full. Solution: Make more space available in the database by deleting unneeded data. Possible cause: The database is too small. Solution: Increase the size of the database using SQL Enterprise Manager. Possible cause: The Warning Free Space Threshold is set too high for the database. Solution: Decrease the Warning Free Space Threshold in the Configuration Manager Console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the database. Site System Status Summarizer will now set the status of the database to Warning in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4714 | Site System Status Summarizer detected that the database "%1" on site database server "%2" has %3 KB of free space, which is less than or equal to the Critical Free Space Threshold of %4 KB. Possible cause: The database is almost full. Solution: Make more space available in the database by deleting unneeded data. Possible cause: The database is too small. Solution: Increase the size of the database using SQL Enterprise Manager. Possible cause: The Critical Free Space Threshold is set too high for the database. Solution: Decrease the Critical Free Space Threshold in the Configuration Manager Console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the database. Site System Status Summarizer will now set the status of the database to Critical in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4715 | Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the transaction log. Site System Status Summarizer will now set the status of the transaction log to OK in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4716 | Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Warning Free Space Threshold of %4 KB. Possible cause: The transaction log is too small. Solution: Increase the size of the transaction log using SQL Enterprise Manager. Possible cause: The Warning Free Space Threshold is set too high for the transaction log. Solution: Decrease the Warning Free Space Threshold in the Configuration Manager Console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the transaction log. Site System Status Summarizer will now set the status of the transaction log to Warning in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4717 | Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Critical Free Space Threshold of %4 KB. Possible cause: The transaction log is too small. Solution: Increase the size of the transaction log using SQL Enterprise Manager. Possible cause: The Critical Free Space Threshold is set too high for the transaction log. Solution: Decrease the Critical Free Space Threshold in the Configuration Manager Console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the transaction log. Possible cause: A software defect caused the transaction log to fill up completely. Solution: investigate why the transaction log is full (see the SQL Server documentation for details). If you suspect a software defect, contact Microsoft for more information. Stop and start SQL Server to empty the transaction log. Site System Status Summarizer will now set the status of the database to Critical in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4718 | Site System Status Summarizer has not been able to access the storage object "%1" on Site Object "%2" for %3 hours. Site System Status Summarizer will now assume that you no longer intend to use the storage object and will no longer monitor the storage object. | Informational |
| 4719 | Site System Status Summarizer detected that the storage object "%1" on Branch Distribution Point site system "%2" has %3 KB of free storage space, which is less than or equal to the Critical Free Space Threshold of %4 KB. Possible cause: The storage object is almost full or the storage status has not yet been received from the Branch Distribution Point. Solution: Verify that the messages from the Branch Distribution Point are successfully received. Make more space available on the storage object by deleting unneeded files. Possible cause: The Critical Free Space Threshold is set too high for this storage object. Solution: Decrease the Critical Free Space Threshold in the Configuration Manager Console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to Critical in the Site System Status summary in the Configuration Manager Console. | Informational |
| 4720 | Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Online. | Informational |
| 4721 | Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Failed. Possible cause: This Configuration Manager Server Role is unable to function. Solution: Verify that no security or configuration problems exist and that all related components are running. | Informational |
| 4722 | Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Degraded. Possible cause: This Configuration Manager Server Role is experiencing a severe impact to its performance and or partial loss of functionality. Solution: Check the overall CPU, Memory and Disk performance on this server. Solution: Verify that no security or configuration problems exist that could be impacting availability of this role. | Informational |
| 4723 | Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Offline. Possible cause: This Configuration Manager Server Role is under maintenance or shutdown. Solution: Verify that maintenance is not being performed at this time and that all related components are running. | Informational |
| 4724 | Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Unknown. Possible cause: This Configuration Manager Server Role does not have an Availability State, it could not be accessed or it has not been updated. Solution: Verify that the Site Server can connect to the registry of the site system. | Informational |
| 4900 | Site Component Manager is deinstalling all Configuration Manager Server Components from site system "%1". | Informational |
| 4901 | Site Component Manager successfully deinstalled all Configuration Manager Server Components from site system "%1". | Informational |
| 4902 | Site Component Manager failed to deinstall all Configuration Manager Server Components from site system "%1". Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry this operation in %2 minutes. To force Site Component Manager to immediately retry this operation, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 4903 | Site Component Manager failed to deinstall all Configuration Manager Server Components from site system "%1". | Error |
| 4904 | Site Component Manager successfully installed the performance counters for this component on this site system. | Informational |
| 4905 | Site Component Manager failed to install the performance counters for this component on this site system. Possible cause: The site system's registry is full. Solution: Increase the size of the site system's registry. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in Site Component Manager's log file "sitecomp.log" and the perfsetup.log on the site system. | Error |
| 4906 | Site Component Manager successfully removed the performance counters for this component from this site system. | Informational |
| 4907 | Site Component Manager failed to remove the performance counters for this component from this site system. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in Site Component Manager's log file "sitecomp.log" and the perfsetup.log on the site system. | Error |
| 4908 | Site Component Manager could not add machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3". Possible cause: The site server's machine account might not have administrative access to the SQL Server computer. Solution: Manually add the machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3". | Error |
| 4909 | Configuration Manager could not locate the "System Management" container in Active Directory (%1). Nor could it create a default container. This will prevent Site Component Manager and Hierarchy Manager from updating or adding any objects to Active Directory. Possible cause: The site server's machine account might not have the correct rights to update active directory. Solution: Either give the Service Account rights to update the domain's System Container, or manually create the "System Management" container in this domain's Active Directory system container, and give the site server computer account full rights to that container (and all children objects.) | Error |
| 4910 | Configuration Manager created a default "System Management" container in Active Directory (%1). This will be used to publish all necessary Active Directory objects for this site. | Informational |
| 4911 | Configuration Manager successfully created the object "%1" in Active Directory (%2). | Informational |
| 4912 | Configuration Manager cannot update the already existing object "%1" in Active Directory (%2). Possible cause: The site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site server's machine account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: The Active Directory object "%1" has been moved to a location outside of the "System Management" container, or has been lost. Solution: Delete the object from its current location, and let the site create a new object. Possible cause: The Active Directory schema has not been extended with the correct ConfigMgr Active Directory classes and attributes. Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended. The schema can be extended with the tool "extadsch.exe" from the installation media. | Error |
| 4913 | Configuration Manager cannot create the object "%1" in Active Directory (%2). Possible cause: The site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site server's machine account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: Another Active Directory object named "%1" already exists somewhere outside of the "System Management" container Solution: Locate the other object with the same name, and delete the object from its current location. Then allow the site to create a new object. Possible cause: The Active Directory schema has not been extended with the correct ConfigMgr Active Directory classes and attributes. Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended. The schema can be extended with the tool "extadsch.exe" from the installation media. | Error |
| 4914 | Configuration Manager successfully deleted the object "%1" from Active Directory (%2). | Informational |
| 4915 | Configuration Manager cannot delete the object "%1" in Active Directory (%2). Possible cause: The site server's machine accountmay not have full control rights for the "System Management" container in Active Directory Solution: Give the site server's machine account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: The Active Directory object "%1" has been moved to a location outside of the "System Management" container Solution: Manually delete the object from its current location. | Error |
| 4918 | Configuration Manager cannot update the dNSHostName property for the existing object "%1" in Active Directory (%2). This property is used to publish fully qualified host names in Active Directory. Possible cause: The Active Directory schema has not been extended with latest version of the ConfigMgr Active Directory classes and attributes. Solution: Ensure the schema has been extended with the latest version of the ConfigMgr Active Directory classes and attributes. The schema can be extended with the tool "extadsch.exe" from the installation directory on the Configuration Manager Site Server that reported this message. | Warning |
| 4919 | Site Component Manager successfully installed the COM access registry keys for this component on this site system. | Informational |
| 4920 | Site Component Manager failed to install the COM access registry keys for this component on this site system. Possible cause: The site system's registry is full. Solution: Increase the size of the site system's registry. Possible cause: Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in Site Component Manager's log file "sitecomp.log" and the comregsetup.log on the site system. | Error |
| 4921 | Site Component Manager successfully removed the COM access registry keys for this component from this site system. | Informational |
| 4922 | Site Component Manager failed to remove the COM access registry for this component from this site system. Possible cause: Site Component Manager does not have administrator rights to this site system. Solution: Verify that the either the site server computer account or the Site System Installation account is a member of the local Administrators group on the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in Site Component Manager's log file "sitecomp.log" and the comregsetup.log on the site system. | Error |
| 4923 | SMS System Health Validator %1 encountered an error. ErrorCode = %2. | Error |
| 4924 | Site Component Manager failed to add machine account %1 to the user group %2, this must be done manually. | Warning |
| 4925 | Site Component Manager detected that this component's binaries should be recopied on this site system. Site Component Manager will attempt to recopy the component binaries every %1 minutes until the action succeeds. | Informational |
| 4926 | Site Component Manager is recopying the binaries of this component on this site system. | Informational |
| 4927 | Site Component Manager successfully recopied the binaries of this component on this site system. | Informational |
| 4928 | Site Component Manager failed to recopy the binaries of this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the recopy in %1 minutes. To force Site Component Manager to immediately retry the recopy, stop and restart Site Component Manager using the Configuration Manager Service Manager. | Error |
| 4950 | Site Component Manager failed to install this component, because it can't configure Microsoft Internet Information Services (IIS). Possible cause: Microsoft Internet Information Services (IIS) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Internet Information Services (IIS), and verify that the World Wide Web Service is running. Possible cause: Site Component Manager does not have sufficient access rights to administer and configure Microsoft Internet Information Services (IIS) on this site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Site Component Manager cannot install component %1 until Microsoft Internet Information Services (IIS) is installed and configured correctly. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further information. | Error |
| 4951 | Site Component Manager failed to install this component, because the Microsoft Installer File for this component (%1) could not install. Refer to the %2, the %3, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information. | Error |
| 4952 | Site Component Manager failed to install this component because at least one file necessary for installation is missing. Refer to the component's installation log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information. | Error |
| 4956 | Site Component Manager successfully installed this component, However a reboot is required to complete the installation. Possible cause: Some files could not be replaced because they were in use by another process Solution: Reboot the machine to complete the installation. The component %1 may not be fully operational until a reboot. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further information. | Error |
| 4957 | Site Component Manager failed to install this component, because it either can't find or configure Internet Information Services Background Intelligent Transfer Service (BITS) Server Extensions. Possible cause: Background Intelligent Transfer Service (BITS) is not installed or running. Solution: Use Add/Remove Programs to install Background Intelligent Transfer Service (BITS) . Possible cause: Site Component Manager does not have sufficient access rights to administer and configure Background Intelligent Transfer Service (BITS) on this site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Site Component Manager cannot install component %1 until Background Intelligent Transfer Service (BITS) is installed and configured correctly. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further information. | Error |
| 4958 | Site Component Manager failed to install this component, because it couldn't determine the the name of the IIS anonymous user account. Possible cause: The account is not configured correctly in IIS. Solution: Configure the account in IIS. Site Component Manager cannot install component %1 until this account is configured correctly. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further information. | Error |
| 4959 | Site Component Manager successfully installed this component. However the SQL Server Principal Name (SPN) could not be validated in Active Directory. Possible cause: The MSSQL Service is running under a user account, instead of the computer account. In this case, SQL does not publish its own SPN. Solution: Manually publish the SQL Server SPN in Active Directory. The component %1 will operate correctly. However remote site systems requiring access to SQL Server (i.e. management points) might not be able to access the SQL database. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further information. | Error |
| 4960 | Site Component Manager failed to install this component, because the designated Web Site of Internet Information Services is not running or started. Possible cause: The designated Web Site is in the Stopped or Paused state. Solution: Start the designated Web Site using the Internet Services Manager. Possible cause: The World Wide Publishing Service is in the Stopped or Paused or Disabled state. Solution: Start the World Wide Publishing Service on the machine. Site Component Manager cannot install component %1 until the designated Web Site is started. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further information. | Error |
| 4961 | Site Component Manager failed to install this component. The Distributed Transaction Coordinater Service (DTC) is not running. This service is needed to complete the Management Point installation. Please start the service, and try again. | Error |
| 4962 | Site Component Manager failed to install this component. The Task Scheduler Service is not running. This service is needed to complete the Management Point installation. Please start the service, and try again. | Error |
| 4963 | MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory. Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. | Error |
| 4964 | Site Component Manager failed to install this component, because Secure Sockets Layer (SSL) is not configured properly on the Internet Information Server. Possible cause: No Server Certificate is attached to the designated Web Site. Solution: Refer to ConfigMgr Documentation regarding how to create and attach a proper Server Certificate to the designated Web Site. Possible cause: The Server Certificate is invalid or expired. Solution: Refer to ConfigMgr Documentation regarding how to create and attach a proper Server Certificate to the designated Web Site. | Error |
| 4965 | Site Component Manager failed to install this component, because it can't configure Microsoft Network Policy Server (NPS). Possible cause: Microsoft Network Policy Server (NPS) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Network Policy Server (NPS). Possible cause: Site Component Manager does not have sufficient access rights to administer and configure Microsoft Network Policy Server (NPS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow Configuration Manager to administer the site system. Site Component Manager cannot install component %1 until Microsoft Network Policy Server (NPS) is installed and configured correctly. Refer to the documentation or the Microsoft Knowledge Base for further information. | Error |
| 4966 | Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3, which is not a supported operating system for System Health Validator point. Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to the Configuration Manager Documentation Library to determine the required version. Possible cause: You accidentally configured Configuration Manager to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager console. | Error |
| 4967 | Site Component Manager failed to install this component, because it can't configure Microsoft Windows Deployement Services (WDS). Possible cause: Microsoft Windows Deployment Services (WDS) is not installed. Solution: Use Add/Remove Programs to install Windows Deployment Services (WDS). Possible cause: Site Component Manager does not have sufficient access rights to configure Microsoft Windows Deployment Services (WDS) on this site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. Site Component Manager cannot install component %1 until Microsoft Windows Deployment Services (WDS) is installed. Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further information. | Error |
| 4968 | Site Component Manager failed to install this component, because it either can't find or configure WSUS. Possible cause: WSUS service is not installed or running. Solution: Use Add/Remove Programs to install WSUS. | Error |
| 4969 | Site Component Manager failed to install WSUS role on server %1. Refer to the ConfigMgr Documentation and the Microsoft Knowledge Base for further information. | Error |
| 4970 | Site Component Manager failed to install component %1 on server %2. The WebDAV server extension is either not installed or not configured properly. Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow "All users" read access to "All content". Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" and "Allow Custom Properties" is set to false. | Error |
| 4971 | Site Component Manager failed to install component %1 on server %2. The WCF is not activated. Solution: Make sure WCF is activated. | Error |
| 4972 | Site Component Manager failed to install component %1 on server %2. The IIS Windows Authentication component is not installed. Solution: Make sure IIS Windows Authentication component is installed. | Error |
| 4973 | Site Component Manager failed to install component %1 on server %2. The IIS ASP.NET component is not installed. Solution: Make sure IIS ASP.NET component is installed. | Error |
| 4974 | Site Component Manager failed to install component %1 on server %2. The IIS ASP.NET is not registered correctly. Solution: Review Microsoft Technet article located at: http://support.microsoft.com/kb/306005 to resolve the issue. | Error |
| 4975 | Site Component Manager failed to install component %1 on server %2. The .NET Framework 3.5 is not installed. Solution: Make sure .NET Framework 3.5 is installed. | Error |
| 4976 | Site Component Manager failed to install component %1 on server %2. The .NET Framework 4.0 Full Profile is not installed. Solution: Make sure .NET Framework 4.0 Full Profile is installed. | Error |
| 4977 | Site Component Manager failed to install component %1 on server %2. SCEPInstall.exe returns error %3. | Error |
| 4978 | Site Component Manager failed to install component %1 on server %2. The .NET Framework 4.5 Full Profile is not installed. Solution: Make sure .NET Framework 4.5 Full Profile is installed. | Error |
| 4979 | Site Component Manager successfully installed a prerequisite component. However a reboot is required to complete the installation. | Error |
| 500 | This component started. | Informational |
| 5000 | Site Backup was unable to open control file "%1". Site backup did not occur. Possible cause: Wrong name specified or permissions to "%1" are incorrect. Solution: Verify that a readable backup control file named "%1" exists. | Error |
| 5001 | Site Backup stopped the "%1" executable on the local computer. | Informational |
| 5002 | Site Backup could not stop the "%1" executable on the local computer. Possible cause: "%1" is an interactive Windows application and is waiting for user confirmation of the stop request. Solution: Manually stop this application. | Error |
| 5003 | Site Backup started the "%1" executable on the local computer. | Informational |
| 5004 | Site Backup could not start the "%1" executable on the local computer. Possible cause: "%1" does not exist in the specified location on the local computer. Solution: Verify that an executable "%1" exists on the local computer. Also specify its full path in the backup control file. | Error |
| 5005 | Site Backup stopped the %1 service on site system %2. | Informational |
| 5006 | Site Backup could not stop the %1 service on site system %2. Possible cause: Site Backup does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system. If this problem persists, refer to the ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 5007 | Site Backup started the %1 service on site system %2. | Informational |
| 5008 | Site Backup could not start the %1 service on site system %2. Possible cause: Site Backup does not have sufficient access rights to administer the site system. Solution: Verify that the site server computer accounthas administrative rights on the site system. If this problem persists, refer to the ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 5009 | Site Backup successfully backed up file system object %1 to %2. | Informational |
| 501 | This component was signalled to stop by an administrator or the operating system. The component will complete any processing it is doing and stop at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to stop. | Informational |
| 5010 | Site Backup was unable to back up file system object %1 to %2. Possible cause: %1 is not readable, or %2 is not writable. Solution: Adjust file attributes and/or permissions of %1 and/or %2. Possible cause: The destination directory %2 did not already exist, and Site Backup was unable to create it. Solution: Verify that a regular file with the same name as %2 or one of its parent directories does not exist, or replace %2 with an existing directory. Possible cause: %1 or %2 are on remote computers that Site Backup does not have sufficient access rights to administer. Solution: Verify that the site server computer accounthas administrative rights on the site system. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. Possible cause: Source %1 being copied to %2 may cause a recursive operation Solution: Verify that destination folder does not exist within the source folder. | Warning |
| 5011 | Site Backup successfully backed up registry key %1 to %2. | Informational |
| 5012 | Site Backup was unable to back up registry key %1 to %2. Possible cause: Site Backup was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, Verify that the site server computer accounthas administrative rights on the site system ; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. Possible cause: %2 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %2 and/or its directory. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. | Warning |
| 5013 | Site Backup successfully backed up %1 database %2 to %3. | Informational |
| 5014 | Site Backup was unable to back up %1 database %2 to %3. Possible cause: %3 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %3 and its directory. 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 the site server can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. 6. If the problem persists, check the SQL Server error logs. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. | Warning |
| 5015 | Site Backup successfully ran command line "%1", which completed with exit status %2. | Informational |
| 5016 | Site Backup was unable to run command line "%1" (error #%2). Possible cause: "%1" does not exist at the specified location or is not in the system path. Solution: Install "%1" at the specified location, or add its directory to the system path. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. | Warning |
| 5017 | Site Backup reported that the backup control data ended unexpectedly at line %1. This problem might cause part of the site backup to be skipped. Possible causes: the backup control file was truncated or contains a syntax error. Solution: Verify completeness of the backup control file and fix any errors. | Error |
| 5018 | Site Backup is ignoring the invalid definition on line %1 of the backup control file. This problem may cause part of the site backup to be skipped. Possible cause: The backup control file contains a syntax error on line %1. Solution: Fix any errors in the backup control file. | Error |
| 5019 | Site Backup is ignoring the invalid section starting on line %1 of the backup control file. This problem might cause part of the site backup to be skipped. Possible cause: The backup control file contains an invalid section name on line %1. Solution: Verify that line %1 specifies a valid section name. Possible cause: The section starting at line %1 contains no valid definitions. Solution: If the section contains invalid definitions, correct any errors. If the section contains no definitions, remove the section or add at least one definition. Possible cause: The backup control file contains a syntax error on or before line %1. Solution: Fix any errors in the backup control file. | Error |
| 502 | This component stopped. | Informational |
| 5020 | Site Backup stopped the %1 ConfigMgr client application on the local computer. | Informational |
| 5021 | The %1 ConfigMgr client application on the local computer did not respond to Site Backup's stop request. Possible cause: %1 is not a ConfigMgr client application and so cannot respond to a "close" event. Solution: Stop this application manually or as a standard executable. Possible cause: %1 was not running. Solution: Remove the "clientapp %1" definition from the backup control file. | Warning |
| 5022 | Site Backup could not stop the %1 ConfigMgr client application on the local computer. Possible cause: %1 does not exist on the local computer. Solution: Verify that there are no errors in the "clientapp %1" definition, or remove the definition from the backup control file. | Error |
| 5023 | Site Backup started the %1 ConfigMgr client application on the local computer. | Informational |
| 5024 | Site Backup could not start the %1 ConfigMgr client application on the local computer. Possible causes: %1 is not in the system path or does not exist on the local computer. Solution: Verify that a ConfigMgr client application "%1" exists on the local system. Either add its directory to the system path, or specify its full path in the backup control file. | Error |
| 5025 | Site Backup was run, but the %1 token had no value. Site backup did not occur. Possible cause: The current site's "Backup Configuration Manager Site Server" Maintenance Task has no value set for its "Backup Destination" field. Solution: Set the "Backup Destination" field using the Configuration Manager Console. | Error |
| 5026 | Site Backup was run, but the backup destination directory ( %1 ) is invalid. Site backup did not occur. Possible cause: The current site's "Backup Configuration Manager Site Server" Site Maintenance Task has invalid value set for its "Backup destination" field or "Backup destination" exists inside the Configuration Manager root folder or Backup was unable to create this directory. Solution: Set a valid location to the "Backup destination" field using the Configuration Manager Console Make sure "Backup destination" does not exist inside the Configuration Manager root folder. Check the privileges for proper rights | Error |
| 5027 | Site Backup found syntax errors on the following lines:%1 in backup control file. Site backup did not occur. Possible cause: There are syntax errors or unsupported commands that need to be removed. Solution: Edit backup control file and remove syntax errors on the given lines. | Error |
| 5028 | The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information. Possible cause: %1 is/are missing from their predefined location. Solution: Please copy the unavailable tools to their designated folder. | Warning |
| 5029 | Unable to verify the installation of the service : %1 This service will not be stopped or restarted. Possible cause: if %1 is a service then it is not installed or cannot be reached. Solution: Check the name and location of the Service and make sure that service is installed and the machine is reachable. | Warning |
| 503 | This component was signalled to pause by an administrator. The component will complete any processing it is doing and pause at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to pause. Once the component has paused, it will not do any more processing until the administrator signals it to resume processing. | Informational |
| 5030 | Maximum sleep time is 15 minutes. Time given in Backup Control File exceeds this limit so it is being reset to this maximum limit. | Warning |
| 5031 | Token Symbol (%1) already defined. First value (%2) will be used. Possible cause: %1 is either a built-in symbol or already defined in Backup Control file. Solution: If it is a built-in symbol, it cannot be redefined, remove added definition from backup control file otherwise use only a single definition. | Warning |
| 5032 | Site Backup was unable to back up registry key %1 to %2. Possible cause: Site Backup was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, Verify that the site server computer accounthas administrative rights on the site system ; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. Possible cause: %2 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %2 and/or its directory. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. | Error |
| 5033 | Site Backup was unable to back up %1 database %2 to %3. Possible cause: %3 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %3 and its directory. 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 the site server can access the site database. 5. Verify that the site database, transaction log, and tempdb are not full. If the problem persists, check the SQL Server error logs. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. | Error |
| 5034 | Site Backup could not start the "%1" executable on the local computer. Possible cause: "%1" is not found in the specified location. Solution: Verify that the executable "%1" exists on the local computer. Please specify its full path in the backup control file. | Warning |
| 5035 | Site Backup completed successfully with zero errors but still there could be some warnings. | Informational |
| 5036 | Site Backup tried to stop the %1 service on site system %2. This service is already stopped. | Informational |
| 5037 | Site Backup tried to stop the %1 executable. This executable is already stopped. | Informational |
| 5038 | Site Backup service was stopped manually. Backup operation is not completed. | Warning |
| 5039 | %1 utility initiated by Site Backup did not complete in timely fashion. Terminating this utility. You may need to get its generated information manually. | Warning |
| 504 | This component was signalled to resume processing by an administrator. | Informational |
| 5040 | Site Backup successfully initiated command file "%1". | Informational |
| 5041 | Site Backup was unable to initiate command file "%1" . Possible cause: Unable to find command shell to execute this file. Solution: Install command shell (CMD.EXE) in the system directory. Possible cause: Command shell failed to execute this file. Solution: Verify that CMD.EXE or "%1" are not corrupted. | Warning |
| 5042 | Site Backup did not find command file "%1" at its predefined location. Command file "%1" not launched. | Informational |
| 5043 | Site Backup was unable to back up file system object %1 to %2. Possible cause: %1 is not readable, or %2 is not writable. Solution: Adjust file attributes and/or permissions of %1 and/or %2. Possible cause: The destination directory %2 did not already exist, and Site Backup was unable to create it. Solution: Verify that a regular file with the same name as %2 or one of its parent directories does not exist, or replace %2 with an existing directory. Possible cause: %1 or %2 are on remote computers that Site Backup does not have sufficient access rights to administer. Solution: Verify that the site server computer accounthas administrative rights on the site system. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. Possible cause: Source %1 being copied to %2 may cause a recursive operation Solution: Verify that destination folder does not exist within the source folder. Possible cause: Source %1 contains some file(s) that is opened exclusively by some application. Solution: Retry backup again. | Error |
| 5044 | Site Backup failed to initialize the VSS services. Aborting the backup operation. Please verify that the VSS services are up and running. | Error |
| 5045 | Site Backup could not find the SMS Writer in the list of writers provided by the VSS. Aborting the backup operation. Please verify that the SMS Writer service is up and running. | Error |
| 5046 | Site Backup failed while reading the VSS writers meta data. Aborting the backup operation. | Error |
| 5047 | Site Backup failed while creating the snapshot using the VSS services. Aborting the backup operation. | Error |
| 5048 | Site Backup failed while trying to copy the files to the destination. Backup operation is not completed. Possible Cause: The Volume Shadow Copy Service may not have sufficient disk space to create the shadow copy of the site backup snapshot information. Check the storage associations for the drives containing Configuration Manager data and ensure that they are configured to use a volume with free space equivalent to at least 50% of the size of the Configuration Manager data. The backup destination should not be on the source volume, and the storage association should refer to a different volume than the source volume. | Error |
| 5049 | Site Backup could not connect to the registry on the SQL Server machine. Aborting the backup operation. Verify that the site server computer accounthas administrative rights on the SQL Server . | Error |
| 505 | Server %1 is unreachable or down.%2 | Error |
| 5050 | Site Backup could not find the registry entries on the SQL Server machine. SMS SQL Backup service might not be running on the SQL Server machine. | Error |
| 5051 | Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the site database. It cannot start the new backup until the previous backup task is completed. | Error |
| 5052 | SMS SQL Backup service on the SQL Server %1 failed to backup the site database %2. The error reported by the service is %3. Backup operation is not completed. | Error |
| 5053 | SMS SQL Backup service on the SQL Server %1 did not start the database backup. SMS SQL Backup service might not be running on the SQL Server machine. | Error |
| 5054 | SMS SQL Backup service on the SQL Server %1 successfully backed up the site database. | Informational |
| 5055 | Site Backup task is starting. This task will interact with the windows VSS services and the appropriate writers to create a volume snapshot and then back up the required files to the specified destination. | Informational |
| 5056 | Site Backup is starting to copy the files from the snapshot. | Informational |
| 5057 | Site Backup has successfully completed copying the files from the snapshot. | Informational |
| 5058 | SQL Server Backup path is empty or invalid. For remote SQL Server scenarios you should provide either a UNC path for entire backup or provide a local path on the site server for site backup and a local path on the SQL Server for the SQL backup. For the site database backup to succeed, you must update the SQL Server backup location in the Backup Configuration Manager maintenance task properties in the Configuration Manager Console. | Error |
| 5059 | Site Backup failed to copy the files from the snapshot. | Error |
| 506 | Copied file "%1" to "%2". | Informational |
| 5060 | Site Backup failed. The error reported by the service is %1. Backup operation is not completed. Please see smsbkup.log for more information. | Error |
| 507 | Moved file "%1" to "%2". | Informational |
| 508 | Deleted file "%1".%2 | Informational |
| 509 | Locked file "%1".%2 | Informational |
| 510 | Unlocked file "%1".%2 | Informational |
| 5100 | Policy Provider successfully created a policy and a policy assignment based on package %1 (%2), program %3 and deployment %4 (%5). | Informational |
| 5101 | Policy Provider successfully updated the policy and the policy assignment that were created from package %1 (%2), program %3 and deployment %4 (%5). | Informational |
| 5102 | Policy Provider successfully removed policy %1 and the related policy assignment. | Informational |
| 5103 | Policy Provider successfully created a settings policy and a settings policy assignment. | Informational |
| 5104 | Policy Provider successfully updated a settings policy and a settings policy assignment. | Informational |
| 5105 | Policy Provider successfully created a metering policy and a metering policy assignment. | Informational |
| 5106 | Policy Provider successfully updated a metering policy and a metering policy assignment. | Informational |
| 5107 | Policy Provider successfully created a policy and a policy assignment based on Distribution Point %1 (%2). | Informational |
| 5108 | Policy Provider successfully updated the policy and the policy assignment that were created from Distribution Point %1 (%2). | Informational |
| 5109 | Policy Provider successfully created a policy and a policy assignment based on package %1. | Informational |
| 511 | Created directory "%1".%2 | Informational |
| 5110 | Policy Provider successfully updated the policy and the policy assignment that were created from package %1. | Informational |
| 5111 | The site server signing certificate with hashcode '%1' is missing in the Certificate Store. | Error |
| 5112 | The site server signing certificate will expire in %1 day(s). Please ensure that this certificate is renewed for the proper operation of the ConfigMgr site. | Warning |
| 5113 | The site server signing certificate has expired %1 day(s) ago. Please replace/renew the certificate. The Policies at this Site will be re-signed by the Site Server using the new signing certificate. | Error |
| 5114 | The site server signing certificate has changed. The Policy at this Site will be re-signed by the Site Server using the new signing certificate. | Informational |
| 5115 | Policy Provider has failed to sign one or more policy assignments. It will retry this operation automatically. | Error |
| 5116 | Policy Provider successfully signed all policy assignments with the new Site Server Signing Certificate. | Informational |
| 5117 | The hashing algorithm has changed. The Policy at this Site will be re-signed by the Site Server. | Informational |
| 5118 | Policy Provider has noted that the Program: %1 (Package ID: %2) is set to only run on one or more deprecated platforms that are no longer supported. The deployment (ID: %3)will not run on clients until the platform requirements are corrected. | Error |
| 5119 | Policy Provder has detected policy changes for Collection %1. %2 are added. %3 are deleted. | Informational |
| 512 | Removed directory "%1".%2 | Informational |
| 513 | Set the current directory for this process to "%1".%2 | Informational |
| 514 | Opened a change notification handle for directory "%1".%2 | Informational |
| 515 | Could not open a change notification handle for directory "%1" because the directory is on a remote computer.%2 | Informational |
| 516 | Closed the change notification handle for directory "%1".%2 | Informational |
| 517 | Could not open file "%1" for reading.%2 | Warning |
| 518 | Could not open file "%1" for reading and writing.%2 | Warning |
| 519 | Could not read from file "%1".%2 | Warning |
| 520 | Could not write to file "%1".%2 | Warning |
| 5200 | Active Directory System Discovery Agent failed to read the necessary registry information. Possible cause: The registry information is not available yet. Solution: Active Directory System Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 5201 | Active Directory System Discovery Agent failed to read the location of the outbox. Possible cause: The information necessary to complete the initialization is not available now. Solution: Active Directory System Discovery Agent is waiting for the information to become available and will retry at its next interval. | Warning |
| 5202 | Active Directory System Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory System Discovery Agent identified %2 systems in the AD Containers and generated %3 system discovery data records (DDRs) and %4 errors while attempting to create DDRs. | Informational |
| 5203 | Active Directory System Discovery Agent reported errors for %1 objects. DDRs were generated for %2 objects that had errors while reading non-critical properties. DDRs were not generated for %3 objects that had errors while reading critical properties. Possible cause: The site server might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. | Warning |
| 5204 | Active Directory System Discovery Agent failed to bind to container %1. Error: %2. Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried. | Error |
| 521 | Could not copy file "%1" to "%2". | Warning |
| 522 | Could not move file "%1" to "%2". | Warning |
| 523 | Could not delete file "%1".%2 | Warning |
| 524 | Could not lock file "%1".%2 | Warning |
| 525 | Could not create directory "%1".%2 | Warning |
| 526 | Could not remove directory "%1".%2 | Warning |
| 527 | Could not set the current directory for this process to "%1".%2 | Warning |
| 528 | Could not open a change notification handle for directory "%1".%2 | Warning |
| 529 | Could not wait on a change notification handle for directory "%1".%2 | Warning |
| 530 | Could not open file "%1" for reading.%2 | Error |
| 5300 | Active Directory User Discovery Agent failed to read the necessary registry information. Possible cause: The registry information is not available yet. Solution: Active Directory User Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 5301 | Active Directory User Discovery Agent failed to read the location of the outbox. Possible cause: The information necessary to complete the initialization is not available now. Solution: Active Directory User Discovery Agent is waiting for the information to become available and will retry at its next interval. | Warning |
| 5302 | Active Directory User Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory User Discovery Agent identified %2 users in the AD Containers and generated %3 user discovery data records (DDRs) and %4 errors while attempting to create DDRs. | Informational |
| 5303 | Active Directory User Discovery Agent reported errors for %1 objects. DDRs were generated for %2 objects that had errors while reading non-critical properties. DDRs were not generated for %3 objects that had errors while reading critical properties. Possible cause: The site server might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. | Warning |
| 5304 | Active Directory User Discovery Agent failed to bind to container %1. Error: %2. Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried. | Error |
| 531 | Could not open file "%1" for reading and writing.%2 | Error |
| 532 | Could not read from file "%1".%2 | Error |
| 533 | Could not write to file "%1".%2 | Error |
| 534 | Could not copy file "%1" to "%2". | Error |
| 535 | Could not move file "%1" to "%2". | Error |
| 5350 | Active Directory Security Group Discovery Agent failed to read the necessary registry information. Possible cause: The registry information is not available yet. Solution: Active Directory Security Group Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 5351 | Active Directory Security Group Discovery Agent failed to read the location of the outbox. Possible cause: The information necessary to complete the initialization is not available now. Solution: Active Directory Security Group Discovery Agent is waiting for the information to become available and will retry at its next interval. | Warning |
| 5352 | Active Directory Security Group Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory Security Group Discovery Agent identified %2 security group(s) in the AD Containers and generated %3 security group discovery data records (DDRs). | Informational |
| 5353 | Active Directory Security Group Discovery Agent reported warnings for %1 object(s). DDRs were generated for %2 object(s) that had warning(s) while reading non-critical properties. DDRs were not generated for %3 object(s) that had warnings while reading critical properties. Possible cause: OU name or Security Group name may contain at least a Unicode character which has conversion problem between Unicode and your system ANSI locale(e.g. Korean characters in English System Locale). The site server might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. | Warning |
| 5354 | Active Directory Security Group Discovery Agent failed to bind to container %1. Error: %2. Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried. | Error |
| 536 | Could not delete file "%1".%2 | Error |
| 537 | Could not lock file "%1".%2 | Error |
| 538 | Could not create directory "%1".%2 | Error |
| 539 | Could not remove directory "%1".%2 | Error |
| 540 | Could not set the current directory for this process to "%1".%2 | Error |
| 5400 | MP File Dispatch Manager running on the management point "%1" cannot connect to site server "%2". Possible cause: The site server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site server is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing MP File Dispatch Manager from properly accessing the site server. Solution: Investigate and correct any problems with your network. Refer to Configuration Manager documentation for more information. | Error |
| 5401 | MP File Dispatch Manager cannot copy files from "%1" to "%2". Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: MP File Dispatch Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing MP File Dispatch Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network. | Warning |
| 541 | Could not open a change notification handle for directory "%1".%2 | Error |
| 5410 | MP common layer cannot read the registry configuration when processing %1. Possible cause: The corruption of the registry or an installation problem. Solution: Check the registry entries for MP or reinstall MP. | Error |
| 5411 | MP has experienced out of memory condition when processing %1. Possible cause: Temporary spike in processing requests. Solution: If the condition persists check the logs to identify the cause and if necessary install NLB. | Warning |
| 5412 | MP has incurred an unexpected error when processing %1. Possible cause: Unforeseen system error. Solution: Check the logs to pinpoint the source of the problem and the reason for the condition. If unsuccessful raise the issue to Microsoft support. | Error |
| 5413 | MP has discarded a report when processing %1. Possible cause: Corruption or invalid user definition. Solution: Check the logs to identify the cause. If the problem is persistent raise the issue with Microsoft support | Warning |
| 5414 | MP could not complete a task when processing %1. Check the logs for clues. Possible cause: Out of disk space. Solution: Increase the disk space, remove unprocessable files. | Error |
| 5415 | MP cannot load the hardware inventory class mapping table when processing %1. Possible cause: MP cannot communicate with the SQL data base. Solution: Check the network connection between MP and the machine hosting the site database. Possible cause: The site database is not initialized properly or corrupted. Solution: Check the data for consistency. Recreate the hardware definition tables if necessary. | Warning |
| 5416 | MP needs to reload the hardware inventory class mapping table when processing %1. The MP hardware inventory manager cannot find a WMI class definition in the mapping table when processing a report. This should only happen if new definitions beyond those known to the site are added to the collected classes. Possible cause: Inconsistent way the new definitions have been introduced. Solution: Check that the mapping tables contain the information consistent with the hardware definition tables and that the definitions have been propagated properly. Possible cause: Corruption of the data base. Solution: Check the consistency of the data base. | Warning |
| 5417 | MP could not process a message itself or spawn a task for message processing and discarded the message when processing %1. This is benign. Possible cause: Temporary spike in processing requests. Solution: If the condition persists, check the logs to identify the cause and if necessary install NLB. | Warning |
| 5418 | MP could not find some class or property definitions when processing %1 as they are apparently missing in sms_def.mof. Unknown classes and properties have been ignored and a MIF file generated with all the classes and properties that could be found. Possible cause: This might indicate that the report has become obsolete due to a new HW inventory policy or that a customer's private definitions haven't been properly propagated to the sms_def.mof at the PSS. Solution: See if the missing classes or properties are genuinely missing in the current sms_def.mof and find out why the client put them in the xml report. | Warning |
| 5419 | MP retry component gave up on a report when processing %1 and moved it to the bad report directory. Possible cause: The file was too old to start with due to propagation problems. Solution: Ignore. Possible cause: MP's cache of class definitions could not be reloaded for a long time. Solution: Fix the network connection or SQL data base replication problem for the affected MP. | Warning |
| 542 | Could not wait on a change notification handle for directory "%1".%2 | Error |
| 5420 | Management Point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SQL Server is turned on, connected to the network, and functioning properly. Possible cause: Management point does not have sufficient access rights to the database. Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of 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. | Error |
| 5421 | The Management Point was repaired. | Informational |
| 543 | Parsed site control file "%1", serial number %2. | Informational |
| 5430 | MP failed to register with the local WINS server. Possible cause: WINS server is not running. Solution: Make sure that the WINS server on the local network is up and running. Possible cause: MP's IP configuration has an invalid address of the WINS server. Solution: Supply a valid WINS IP address. | Warning |
| 5431 | MP failed to unregister from the local WINS server. Possible cause: WINS server is not running. Solution: Make sure that the WINS server on the local network is up and running. Manually delete that MP's entry from the WINS server Possible cause: The MP's entry at the WINS server is missing. Solution: Ignore the issue. | Warning |
| 5432 | MP could not write out CCM setting to WMI. Possible cause: MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP | Error |
| 5433 | MP could not update its settings to the new values. Possible cause: MP may be overloaded. Solution: Reapply the setting at a later time. | Error |
| 5434 | Some or all of the MP Component Managers could not be started. Possible cause:MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP Possible cause: MP may be overloaded. Solution: Manually start the SMS Agent Host service on the MP. | Error |
| 5435 | Some or all of the MP Component Managers could not be stopped. Possible cause:MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP Possible cause: MP may be overloaded. Solution: Manually start the SMS Agent Host service on the MP. | Error |
| 5436 | MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is %1, %2. Possible cause: Management point encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (msdbrole_MP) in the SQL Server database. 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. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5437 | MP Control Manager detected NLB MP is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: MP encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow Management Point access. Verify the account used by the MP to connect to the SQL Server is a member of the SMS_SiteSystemToSQLConnection_ 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. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5438 | MP Control Manager detected MP is not responding to HTTP requests. The http error is %1. Possible cause: MP service is not started or not responding. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5439 | MP Control Manager detected NLB MP is not responding to HTTP requests. The http error is %1. Possible cause: MP service is not started or not responding on all MP physical machines. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 544 | Wrote delta site control file "%1".%2 | Informational |
| 5441 | The SMS Agent Host (CCMEXEC) was unable to update certificate information in the Active Directory. | Error |
| 5442 | The SMS Agent Host (CCMEXEC) successfuly updated certificate information in the Active Directory. | Informational |
| 5443 | MP has rejected a message from client %2 because it was not signed using the hash algorithm that is required by this site. Possible causes: This Client is running on a Operating System that does not support the hash algorithm required by this site (or) Client is earlier than Configuration Manager 2012 or did not use the hash algorithm required by this site. | Warning |
| 5444 | MP has rejected policy request from %2 because this SMSID is marked as blocked. | Warning |
| 5445 | MP has rejected registration request due to failure in client certificate (Subject Name: %2) chain validation. If this is a valid client, Configuration Manager Administrator needs to place the Root Certification Authority and Intermediate Certificate Authorities in the MP?s Certificate store or configure Trusted Root Certification Authorities in primary site settings. | Warning |
| 5446 | MP has rejected the request because %2 certificate has expired. | Warning |
| 5447 | MP has rejected a message from %2 because the signature could not be validated. If this is a valid client, it will attempt to re-register automatically so its signature can be correctly validated. | Warning |
| 5448 | MP has rejected a policy request from %2 because this client is not approved. | Warning |
| 5449 | MP has rejected a message from Client %2 because it was not signed. Possible causes: The Client is earlier than Configuration Manager 2012 or did not sign the message as required by the management point. | Warning |
| 545 | Could not read site control file "%1".%2 | Error |
| 5450 | MP has rejected registration request from %2 because the Client Certificate has insufficient key length. Possible causes: The Client is earlier than Configuration Manager 2012 or did not generate or use a client certificate that meets the key length requirement. | Warning |
| 546 | Could not parse site control file "%1", the file contains a syntax error or it is improperly formatted or corrupt.%2 | Error |
| 5460 | MP Control Manager verified that Management Point is responding to HTTP requests. | Informational |
| 5461 | MP Control Manager verified that Device Management Point is responding to HTTP requests. | Informational |
| 5462 | MP Control Manager verified that Device Management Point Proxy is responding to HTTP requests. | Informational |
| 547 | Could not parse site control file "%1", the file does not contain an end-of-file (EOF) marker.%2 | Error |
| 548 | Site control file "%1" does not contain a "File Definition" item.%2 | Error |
| 5480 | MP Control Manager detected DMP is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: DMP encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow Device Management Point access. If using integrated security, verify the account used by the DMP to connect to the SQL Server is a member of the SMS_SiteSystemToSQLConnection_ 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. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5481 | MP Control Manager detected DMP is not responding to HTTP requests. The http error is %1. Possible cause: DMP service is not started or not responding on all DMP physical machines. Solution: Manually restart the SMS Agent Host service on the DMP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5482 | MP Control Manager detected that this node of the NLB MP is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: MP encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow Management Point access. Verify the account used by the MP to connect to the SQL Server is a member of the SMS_SiteSystemToSQLConnection_ 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. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5483 | MP Control Manager detected that this node of the NLB MP is not responding to HTTP requests. The http error is %1. Possible cause: MP service is not started or not responding on all MP physical machines. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5484 | MP Control Manager detected that this node of the NLB MP is online. Node status code is %1 (%2). | Informational |
| 5485 | MP Control Manager detected that this node of the NLB MP is degraded. Node status code is %1 (%2). Possible cause: The node will be taken offline for maintenance or retired. Solution: Confirm with the system administrator responsible for the cluster. | Warning |
| 5486 | MP Control Manager detected that this node of the NLB MP is offline. Node status code is %1 (%2). Possible cause: The node has been suspended or stopped. Solution: Confirm with the system administrator responsible for the cluster. Possible cause: The node is in the process of converging. Solution: This should resolve itself when the node has completed converging. | Error |
| 5487 | MP Control Manager detected that the SQL Server hosting the database configured for the Management Point has its Common Language Runtime (CLR) disabled. This will cause multiple features of Configuration Manager requiring SQL CLR to fail. Possible cause: The database is a site database, not a replica, and Configuration Manager Setup failed to enable the CLR. Solution: Using SQL Server Management Studio, navigate to the database instance and select the Facets option. Choose the Surface Area Configuration facet. Ensure that ClrIntegrationEnabled is set to True. Possible cause: The Management Point is configured to communicate with a replica database on a SQL Server that does not have CLR enabled. Solution: Using SQL Server Management Studio, navigate to the database instance and select the Facets option. Choose the Surface Area Configuration facet. Ensure that ClrIntegrationEnabled is set to True. | Error |
| 5488 | MP Control Manager detected DMP Proxy is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: DMP Proxy encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow Device Management Point Proxy access. Verify the account used by the DMP Proxy to connect to the SQL Server is a member of the SMS_SiteSystemToSQLConnection_ 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. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use. Possible cause: The designated DM Proxy Web Site is disabled in IIS. Solution: Verify that the designated Proxy Web Site is enabled, and functioning properly. Possible cause: The ConfigMgr Web Service Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the DM Proxy Web Service is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 5489 | MP Control Manager detected DMP Proxy is not responding to HTTP requests. The http error is %1. Possible cause: DMP Proxy service is not started or not responding on all DMP Proxy physical machines. Solution: Manually restart the SMS Agent Host service on the DMP Proxy. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 549 | Could not write delta site control file "%1".%2 | Error |
| 550 | Parsed installation map "%1".%2 | Informational |
| 551 | Could not read installation map "%1".%2 | Error |
| 552 | Could not parse installation map "%1", the file contains a syntax error or it is improperly formatted or corrupt.%2 | Error |
| 553 | Read registry key "%1" on computer %2. | Informational |
| 554 | Wrote registry key "%1" on computer %2. | Informational |
| 555 | Deleted registry key "%1" on computer %2. | Informational |
| 556 | Read registry value "%1" on computer %2. | Informational |
| 557 | Wrote registry value "%1" on computer %2. | Informational |
| 558 | Deleted registry value "%1" on computer %2. | Informational |
| 559 | Opened a change notification handle for registry key "%1" on computer %2. | Informational |
| 560 | Closed the change notification handle for registry key "%1" on computer %2. | Informational |
| 5600 | Software Metering Processor failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: Software Metering Processor is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 5601 | Software Metering Processor failed to process the usage file "%1" for client "%2". Possible cause: The file is corrupt. Solution: If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 5602 | Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 5603 | Software Metering Processor failed to completely process local rule changes, the rule change log has not been cleared and the changes will be processed again. Possible cause: MSXML 3.0 has not been installed on the system. Solution: Download and install MSXML 3.0 from http://www.microsoft.com/xml. Possible cause: The site server drive is full. Solution: Make more space available on that drive. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. | Error |
| 5604 | Software Metering Processor failed to replicate the definition for rule %1 to child sites. Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.. | Error |
| 5605 | Software Metering Processor failed to process a rule replicated from the parent site. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 5606 | Software Metering Processor failed to replicate summary data to the parent site. Possible cause: The site server drive is full. Solution: Make more space available on that drive.. | Error |
| 5607 | Software Metering Processor could not process replicated summary data from a child site. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 5608 | Software Metering Processor failed to process usage data file %1 and moved it to the retry directory. The file will be reprocessed at a later time. Possible cause: The client that reported the metering data does not exist in the database. Solution: Verify that the client is active and attached to the network. Possible cause: MSXML 3.0 has not been installed on the system. Solution: Download and install MSXML 3.0 from http://www.microsoft.com/xml. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 5609 | Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is enabled. | Informational |
| 561 | Could not connect to registry hive %1 on computer %2. | Warning |
| 5610 | Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is disabled. | Informational |
| 5611 | Software Metering Processor maintenance cycle deleted %1 files from directory %2. | Informational |
| 5612 | Software Metering Processor experienced an error while processing and forwarding usage data to the parent site. Possible cause: The destination drive is full. Solution: Make more space available on that drive. | Error |
| 5613 | Software Metering Processor has retried the usage data file "%1" the maxumum number of times and has moved it to the discard directory. The file will be deleted when the minimum clean up age has been reached. Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 5614 | Software Metering Processor failed to process the usage file "%1" for client "%2" because a record contained a bad usage start or end time value. Usage times are rejected if the start time is greater than the end time, the end time is in the future, or the end time is more than 90 days old. Possible cause: The clock on the client computer is not accurate or has been recently changed. Solution: Reset the time on the client computer to the current time. Problem: The time on the Configuration Manager Site Server is incorrect. Solution: Reset the time on the Configuration Manager Site Server to the current time. | Error |
| 5615 | Software Metering Processor moved file "%1" to the corrupt directory. The file will be deleted when the minimum clean up age has been reached. See the previous and following error status messages for more details. | Error |
| 5616 | Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not found in the database. The file will be retried later. Possible cause: A child site was recently attached and some of the discovery records have not yet been processed by the Discovery Data Manager. Solution: No action is required; the problem will resolve itself once all of the discovery records have been processed. | Warning |
| 5617 | Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not found in the database. The file will not be retried again. Possible cause: A computer has been deleted from the database on the current site but not from the child site. Solution: The summary file has been deleted, no further action is required. | Error |
| 562 | Could not open registry key "%1" on computer %2 for reading. | Warning |
| 563 | Could not create or open registry key "%1" on computer %2 for reading and writing. | Warning |
| 564 | Could not read registry key "%1" on computer %2. | Informational |
| 565 | Could not write registry key "%1" on computer %2. | Informational |
| 566 | Could not delete the registry key "%1" on computer %2. | Warning |
| 567 | Could not enumerate the subkeys of the registry key "%1" on computer %2. | Warning |
| 568 | Could not open a change notification handle for registry key "%1" on computer %2. | Warning |
| 569 | The registry key "%1" on computer %2 is missing a required subkey or value, or contains one or more values that contain invalid data. | Warning |
| 570 | Could not read the registry value "%1" on computer %2. | Warning |
| 5700 | Device Management Point has encountered an unexpected error when processing %1. | Error |
| 5701 | Device Management Point has experienced out of memory condition when processing %1. | Warning |
| 5702 | Device Management Point encountered an error when connecting to its database. | Error |
| 5703 | Device Management Point failed to authenticate the client %1. | Error |
| 571 | Could not write the registry value "%1" on computer %2. | Warning |
| 572 | Could not delete the registry value "%1" on computer %2. | Warning |
| 5720 | Received an undefined message. Client ID is %1. | Warning |
| 5721 | Received message from unknown or unauthorized client %1. | Warning |
| 5722 | Received an invalid poll message. Client ID is %1. | Error |
| 5723 | Received an invalid download instructions request message. Client ID is %1. | Error |
| 5724 | Received an invalid package location request message. Client ID is %1. | Error |
| 5725 | Received an invalid status message. Client ID is %1. | Error |
| 5726 | Received an invalid hardware inventory message. Client ID is %1. | Error |
| 5727 | Received an invalid software inventory message. Client ID is %1. | Error |
| 5728 | Received an invalid file collection message. Client ID is %1. | Error |
| 5729 | Received an invalid registration message. Client ID is %1. | Error |
| 573 | Could not enumerate the values of the registry key "%1" on computer %2. | Warning |
| 574 | The registry value "%1" on computer %2 contains invalid data. | Warning |
| 5740 | Error generating or sending discovery message. Client ID is %1. | Error |
| 5741 | Error generating or sending hardware inventory message. Client ID is %1. | Error |
| 5742 | Error generating or sending software inventory message. Client ID is %1. | Error |
| 5743 | Error generating or sending file collection message. Client ID is %1. | Error |
| 5744 | Error generating or sending status message. Client ID is %1. | Error |
| 5745 | Error generating or sending package location request message. Client ID is %1. | Error |
| 5746 | Error processing download instructions request message. Client ID is %1. | Error |
| 5747 | Error processing registration request message. Client ID is %1. | Error |
| 5748 | Device Management Point encountered an error when processing App model policy. | Error |
| 5749 | Device Management Point encountered an error when sending Compliance Report. | Error |
| 575 | Could not connect to registry hive %1 on computer %2. | Error |
| 5750 | Device Management Point encountered an error when processing DCM CI. | Error |
| 5751 | Device Management Point encountered an error while reading policy xml. | Error |
| 5752 | Device Management Point encountered an error when processing Schedule policy. | Error |
| 5753 | Device Management Point encountered an error when processing Data policy. | Error |
| 5754 | Device Management Point encountered an error when processing prequisite applications policy. | Error |
| 5755 | Device Management Point encountered an error when registering a device. | Error |
| 5756 | Device Management Point encountered an error when processing client certificate. | Error |
| 576 | Could not open registry key "%1" on computer %2 for reading. | Error |
| 5760 | Error sending poll response. Client ID is %1. | Error |
| 5761 | Error sending download instructions. Client ID is %1. | Error |
| 5762 | Error sending package location response. Client ID is %1. | Error |
| 5763 | Error sending registration response. Client ID is %1. | Error |
| 577 | Could not create or open registry key "%1" on computer %2 for reading and writing. | Error |
| 578 | Could not read registry key "%1" on computer %2. | Error |
| 579 | Could not write registry key "%1" on computer %2. | Error |
| 580 | Could not delete the registry key "%1" on computer %2. | Error |
| 5800 | CI Assignment Manager successfully processed new CI Assignment %1. | Informational |
| 5801 | CI Assignment Manager successfully processed Update to CI Assignment %1. | Informational |
| 5802 | CI Assignment Manager successfully removed CI Assignment %1. | Informational |
| 5803 | SMS CI Assignment has been directly deleted from the site Database. Deletion of collection may cause the deletion of all the CI Assignments assigned to that collection. It is not recommended directly deleting CI Assignments from the site database, to verify this deletion was due to Collection delete review the CI Assignment Manager and Collection Evaluator Logs. | Informational |
| 5804 | CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 5805 | CI Assignment Manager failed to process CI Assignment %1. This CI Assignment will be retried %2 times on the next processing cycles. Solution: Review the previous status messages and logs for further clarification about this problem. | Warning |
| 5806 | CI Assignment Manager failed to process CI Assignment %1. This CI Assignment has been retried %2 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 5807 | CI Assignment Manager failed to process CI Assignment Replication File %1 as CI Assignment %2 referenced object of type %3 does not exists. This CI Assignment Replication file has been retried %4 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 5808 | CI Assignment Manager failed to process CI Assignment Replication File %1. This CI Assignment Replication file has been retried %2 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 581 | Could not enumerate the subkeys of the registry key "%1" on computer %2. | Error |
| 582 | Could not open a change notification handle for registry key "%1" on computer %2. | Error |
| 583 | The registry key "%1" on computer %2 is missing a required subkey or value, or contains one or more values that contain invalid data. | Error |
| 584 | Could not read the registry value "%1" on computer %2. | Error |
| 585 | Could not write the registry value "%1" on computer %2. | Error |
| 586 | Could not delete the registry value "%1" on computer %2. | Error |
| 587 | Could not enumerate the values of the registry key "%1" on computer %2. | Error |
| 588 | The registry value "%1" on computer %2 contains invalid data. | Error |
| 589 | Creating "%1" trigger for "%2". | Informational |
| 590 | Dropping trigger "%1".%2 | Informational |
| 591 | Creating table "%1".%2 | Informational |
| 592 | Dropping table "%1".%2 | Informational |
| 593 | Creating index "%1" on table "%2". | Informational |
| 594 | Dropping index "%1".%2 | Informational |
| 595 | Creating stored procedure "%1".%2 | Informational |
| 596 | Dropping stored procedure "%1".%2 | Informational |
| 597 | Creating view "%1".%2 | Informational |
| 598 | Dropping view "%1".%2 | Informational |
| 599 | SQL Login data is incomplete.%1%2 | Error |
| 600 | Failed to get a SQL Server connection. Either the SQL Server is not running, or all connections have been used.%1%2 | Error |
| 6000 | Object Replication Manager successfully processed Object %1 of Type %2. | Informational |
| 6001 | Object Replication Manager successfully processed modification to Object %1 of Type %2. | Informational |
| 6002 | Object Replication Manager successfully removed Object %1 of Type %2. | Informational |
| 6003 | Object Replication Manager failed to process Object %1 of Type %2. This Object has been retried %3 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 6004 | Object Replication Manager failed to process Object changes. These changes will be retried on next processing cycle. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 6005 | Object Replication Manager failed to process Object Replication File %1. This Object Replication file has been retried %2 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 6006 | Object Replication Manager failed to process Object %1 of Type %2. This Object will be retried %3 times on the next processing cycles. Solution: Review the previous status messages and logs for further clarification about this problem. | Warning |
| 6007 | Object Replication Manager failed to process Object Replication File %1 as Object %2 of Type %3 referenced object of type %4 does not exists. This Object Replication file has been retried %5 times and has reached the maximum retry limit. Solution: Review the previous status messages and logs for further clarification about this problem. | Error |
| 601 | Failed to execute SQL command: "%1". Check messages from SQL Server.%2 | Error |
| 602 | The following SQL operation has timed out: "%1".%2 | Error |
| 603 | Failed to get new table name.%1%2 | Error |
| 604 | Failed to create table "%1".%2 | Error |
| 605 | Failed to rename table "%1" to "%2". | Error |
| 606 | Failed to add columns to table "%1". | Error |
| 607 | Failed to drop table "%1".%2 | Error |
| 608 | Failed to create index "%1" on table "%2". | Error |
| 609 | Failed to create procedure "%1".%2 | Error |
| 610 | Failed to create view "%1".%2 | Error |
| 6100 | The State System failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 6101 | The State System message file processing experienced a severe error and suspended file processing. Review the statesys.log file for further details. | Error |
| 6103 | The State System summary task '%1' failed to execute. Review the statesys.log file for further details. | Error |
| 6104 | The State System message file processing could not process file '%1' and moved it to the corrupt directory. Review the statesys.log file for further details. | Error |
| 6105 | The State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details. | Error |
| 611 | Failed to create trigger "%1".%2 | Error |
| 612 | Failed to drop procedure "%1".%2 | Error |
| 613 | Failed to drop view "%1".%2 | Error |
| 614 | Failed to drop trigger "%1".%2 | Error |
| 615 | Microsoft SQL Server reported SQL error %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 616 | Microsoft SQL Server reported SQL error %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 616 | Microsoft SQL Server reported SQL error %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 617 | Microsoft SQL Server reported SQL error %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 617 | Microsoft SQL Server reported SQL error %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 618 | Microsoft SQL Server reported SQL message %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 619 | Microsoft SQL Server reported SQL message %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Warning |
| 619 | Microsoft SQL Server reported SQL message %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 620 | Microsoft SQL Server reported SQL message %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 620 | Microsoft SQL Server reported SQL message %1, severity %2: %3 Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information. | Informational |
| 6200 | The State Migration Point failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 6201 | The State Migration Point reached the minimum disk space threshold on all drives of computer %1. Possible cause: Restoring Clients haven't restored the state yet or store deletion wait time has not been reached. Solution: Wait for periodic store deletion time and retry or free up some disk space on SMP drives. | Error |
| 6202 | The State Migration Point has reached the maximum client threshold on all drives on computer %1. Possible cause: Restoring clients have not restored the state yet or state retention time has not expired. Solution: Wait for store retention time to expire. | Error |
| 6203 | Client with GUID %1 requested capture request while the store from previous request exists. | Warning |
| 6204 | The State Migration Point has reached the minimum disk space threshold of %1 %2 on drive %3 of computer %4. Current free space is %5 %2. | Warning |
| 6205 | The State Migration Point has removed the state store %2 on computer %1. | Informational |
| 6206 | The State Migration Point can not authenticate the client %1. Possible cause: Client machine is not part of the domain or access account presented by client is not found. | Error |
| 6207 | SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base. | Error |
| 6208 | SMP Control Manager detected SMP is not responding to HTTP requests. The http error is %1. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the SMP. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 6209 | State Migration Point cannot access the state store %1 on computer %2. | Error |
| 621 | Created the "%1" inbox definition. The inbox will exist on the Site Server with the relative path "%2". | Informational |
| 6210 | State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are SMP certificate is not yet signed by Site Server. | Error |
| 6211 | There is enough free disk on computer %1. | Informational |
| 622 | Created the "%1" inbox definition. The inbox will exist on the SQL Server with the relative path "%2". | Informational |
| 623 | Created the "%1" inbox definition. The inbox will exist on the Client Access Point with the relative path "%2". | Informational |
| 624 | Created the "%1" inbox definition. The inbox will exist on the named export "%2" with the relative path "%3".%4%5%6%7%8%9%10 | Informational |
| 625 | Read the existing "%1" inbox definition. The inbox should exist on the Site Server with the relative path "%2". | Informational |
| 626 | Read the existing "%1" inbox definition. The inbox should exist on the SQL Server with the relative path "%2". | Informational |
| 627 | Read the existing "%1" inbox definition. The inbox should exist on the Client Access Point with the relative path "%2". | Informational |
| 628 | Read the existing "%1" inbox definition. The inbox should exist on the named export "%2" with the relative path "%3".%4%5%6%7%8%9%10 | Informational |
| 629 | Deleted the "%1" inbox definition.%4%5%6%7%8%9%10 | Informational |
| 630 | Created an inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 6300 | The PXE Service Point failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: Restart the WDS Service. | Error |
| 6301 | The PXE Service Point failed to initialize the WDS PXE Provider. Check Previous Messages for more error information. | Error |
| 6302 | The PXE Service Point failed to perform a clean shutdown. | Error |
| 6303 | The PXE Service Point failed to initialize performance counters. | Error |
| 6304 | The PXE Service Point failed to initialize worker threads. | Error |
| 6305 | The PXE Service Point failed to process PXE request. | Error |
| 6306 | The PXE Service Point is not actively processing PXE messages. Ignoring request from device. Device MAC Address:%1 SMBIOS GUID:%2. | Warning |
| 6307 | The PXE Service Point failed to Lookup device in the database. Device MAC Address:%1 SMBIOS GUID:%2. | Error |
| 6308 | The PXE Service Point failed to get boot action from database for device. Device MAC Address:%1 SMBIOS GUID:%2. | Error |
| 6309 | The PXE Service Point failed to find boot image for package %3 while handling device. Device MAC Address:%1 SMBIOS GUID:%2. | Error |
| 631 | Created an inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 6310 | The PXE Service Point failed to find boot image for package %3 while handling device. Stalling device until package becomes available. If this situation persists the device might become unmanageable. Device MAC Address:%1 SMBIOS GUID:%2. | Warning |
| 6311 | The PXE Service Point instructed the device to boot to the bootimage %3 based on deployment %4. Device MAC Address:%1 SMBIOS GUID:%2. | Informational |
| 6312 | The PXE Service Point encountered an unknown device. Device MAC Address:%1 SMBIOS GUID:%2. | Informational |
| 6313 | The PXE Service Point intructed device to boot normally since it already had executed deployment %3. Device MAC Address:%1 SMBIOS GUID:%2. | Informational |
| 6314 | The PXE Service Point intructed device to boot normally since it has no PXE deployment assigned. Device MAC Address:%1 SMBIOS GUID:%2. | Informational |
| 6315 | The PXE Service Point failed to Initialize the Database Connection. | Error |
| 6316 | The PXE Certificate used for PXE clients is not valid. Please provide a valid certificate. | Error |
| 6317 | The PXE Certificate used for PXE clients will expire soon. Please renew the certificate. | Warning |
| 6318 | PXE control manager could not update its settings to the new values. Possible cause: PXE may be overloaded. Solution: Reapply the setting at a later time. | Error |
| 6319 | PXE Control Manager detected PXE service point is not responding to PXE requests. The error is %1. Possible cause: PXE service point is not started or not responding. Solution: Manually restart the PXE service point. Possible cause: WDS service is not responding. Solution: Manually restart the WDS service. | Error |
| 632 | Created an inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 6320 | PXE Control Manager detected PXE service point is not responding to PXE requests. The status code and text is %1, %2. Possible cause: PXE service point encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow PXE Service Point access. Verify the account used by the PXE service point to connect to the SQL Server is a member of the SMS_SiteSystemToSQLConnection_ Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL Server SPNs are correctly registered. | Error |
| 6321 | The PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device. Device MAC Address:%1 SMBIOS GUID:%2. Boot Image Architecture:%3. | Informational |
| 6322 | The PXE Service Point does not have a boot program matching the processor architetcure of the PXE booting device. Device MAC Address:%1 SMBIOS GUID:%2. Boot Program Architecture:%3. | Informational |
| 633 | Created an inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 634 | Created an inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%5%6%7%8%9%10 | Informational |
| 635 | Created an inbox rule to mirror "%1" directories that match the template "%1" from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%5%6%7%8%9%10 | Informational |
| 636 | Read the existing inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 637 | Read the existing inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 638 | Read the existing inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 639 | Read the existing inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%6%7%8%9%10 | Informational |
| 640 | Read the existing inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%5%6%7%8%9%10 | Informational |
| 6400 | Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds. Possible cause: Site server "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site server "%4" has a high backlog of files in its inboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further. | Warning |
| 641 | Read the existing inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%5%6%7%8%9%10 | Informational |
| 642 | Deleted the inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox.%4%5%6%7%8%9%10 | Informational |
| 643 | Deleted the inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox.%4%5%6%7%8%9%10 | Informational |
| 644 | Deleted the inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox.%4%5%6%7%8%9%10 | Informational |
| 645 | Deleted the inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox.%4%5%6%7%8%9%10 | Informational |
| 646 | Deleted the inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox.%4%5%6%7%8%9%10 | Informational |
| 647 | Deleted the inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox.%4%5%6%7%8%9%10 | Informational |
| 648 | Resolved the "%1" inbox to "%2". | Informational |
| 649 | Waiting for the "%1" inbox to be defined.%2 | Informational |
| 650 | Waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%2 | Informational |
| 6500 | The Wake On LAN component has failed to read the site control file settings. Possible cause: The information is not yet available. Solution: The component is waiting for the information to become available and will retry obtaining the information at its next interval. | Error |
| 6501 | The Wake On LAN component was enabled by the Configuration Manager Administrator. | Informational |
| 6502 | The Wake On LAN component was disabled by the Configuration Manager Administrator. | Informational |
| 6503 | The Wake On LAN component settings have been updated by the Configuration Manager Administrator. | Informational |
| 6504 | The Wake On LAN component is starting to send wakeup packets for the object id=%1 of type=%2. | Informational |
| 6505 | The Wake On LAN component component completed sending wakeup packets for the object id=%1 of type=%2. | Informational |
| 6506 | The Wake On LAN component component successfully sent wakeup packets to all clients targeted for the object id=%1 of type=%2. | Informational |
| 6507 | The Wake On LAN component component failed to send wakeup packets for some clients targeted by object id=%1 of type=%2. Possible cause:Client data was unavailable. Possible cause:Error occurred while reading client data. Possible cause:A network error occurred. | Warning |
| 6508 | The Wake On LAN component component failed to start sending wakeup packets for object id=%1 of type=%2. Possible cause:Client data was unavailable. Possible cause:Error occurred while reading client data. Possible cause:A network error occurred. Solution: Sending will be retried on the next retry time. | Error |
| 6509 | The Wake On LAN component failed access the database. Possible cause:Client data was unavailable. Possible cause: Solution: | Error |
| 651 | Still waiting for the "%1" inbox to be defined.%2 | Warning |
| 6510 | The Wake On LAN component successfully processed wakeup information for the object id=%1 of type=%2. | Informational |
| 6511 | The Wake On LAN component failed to process wakeup information for the object id=%1 of type=%2. Possible cause:An error occured accessing the information. Solution: | Error |
| 6512 | The Wake On LAN component has recovered from an unavailable state. The component is now online. | Informational |
| 6513 | The Wake On LAN component has entered an unavailable state due to a high number of failures. The component's services may not be available. | Error |
| 652 | Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%2 | Warning |
| 653 | Still waiting for the "%1" inbox to be defined.%2 | Error |
| 654 | Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%2 | Error |
| 655 | Could not connect to the "%1" inbox source on computer %2. | Error |
| 656 | Could not create the "%1" inbox definition. (Could not insert the inbox definition into the "%2" inbox source on computer %3.)%4%5%6%7%8%9%10 | Error |
| 657 | Could not create an inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%6%7%8%9%10 | Error |
| 658 | Could not create an inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%6%7%8%9%10 | Error |
| 659 | Could not create an inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%6%7%8%9%10 | Error |
| 660 | Could not create an inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%6%7%8%9%10 | Error |
| 6600 | WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "%1". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website. | Error |
| 6602 | WSUS Configuration Manager failed to get update categories, classifications and locales from WSUS Server "%1". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website. | Error |
| 6603 | WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "%1". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website. | Error |
| 6607 | WSUS Configuration Manager will not be able to configure WSUS Server "%1" as the WSUS Server remoting API's of version 3.0 SP2 or greater are not installed on this site server. Solution: WSUS Server configuration on the WSUS Site System requires WSUS Server remoting API of version 3.0 SP2 or greater to be installed on the site server. To install the remoting API for version 3.0 SP2 run "WSUSSetup.exe console_install=1" on the site server or refer to the documentation. | Error |
| 6609 | WSUS Configuration Manager has configured WSUS Server "%1" to sync from the parent WSUS Server instead of sync from Microsoft Update. | Informational |
| 661 | Could not create an inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%6%7%8%9%10 | Error |
| 6610 | WSUS Configuration Manager has detected that WSUS Server "%1" cannot sync from the parent WSUS Server as there is no parent WSUS Server. Choose the option from the Configuration Manager Console to sync from either Microsoft Update or Do not Sync. | Warning |
| 6611 | WSUS Configuration Manager has detected that Software Updates Point is not configured yet. client boot-strapper packag publishing will be tried later. | Warning |
| 6612 | WSUS Configuration Manager failed to get client package info. | Error |
| 6613 | WSUS Configuration Manager failed to publish client boot-strapper package "%1" with version "%2" to the Software Updates Point. | Error |
| 6614 | WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" with version "%2" from the Software Updates Point. | Error |
| 6615 | WSUS Configuration Manager successfully published client boot-strapper package "%1" with version "%2" to the Software Updates Point. | Informational |
| 6616 | WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" with version "%2" to the Software Updates Point. | Informational |
| 6617 | WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" from the Software Updates Point. | Error |
| 6618 | WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" to the Software Updates Point. | Informational |
| 662 | Could not create an inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%6%7%8%9%10 | Error |
| 663 | Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as low priority.%4%5%6%7%8%9%10 | Informational |
| 664 | Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as normal priority.%4%5%6%7%8%9%10 | Informational |
| 665 | Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as high priority.%4%5%6%7%8%9%10 | Informational |
| 666 | Could not instruct SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3.%4%5%6%7%8%9%10 | Warning |
| 667 | Could not instruct SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3.%4%5%6%7%8%9%10 | Error |
| 668 | The system is low on virtual memory and the component failed a memory allocation. The component will retry the allocation until it succeeds.%1%2 | Warning |
| 669 | The component raised an exception but failed to handle it and will be stopped immediately. Component name: %1 Executable: %2 Process ID: %3 Thread ID: %4 Instruction address: %5 Exception code: %6 Additional information: %7%8%9%10 | Error |
| 670 | Failed to update the site control file.%1%2 | Error |
| 6700 | SMS WSUS Sync Manager error. Message: %2. Source: %1. | Error |
| 6701 | WSUS Synchronization started. | Informational |
| 6702 | WSUS Synchronization done. | Informational |
| 6703 | WSUS Synchronization failed. Message: %2. Source: %1. | Error |
| 6704 | WSUS Synchronization in progress. Current phase: Synchronizing WSUS Server. | Informational |
| 6705 | WSUS Synchronization in progress. Current phase: Synchronizing site database. | Informational |
| 6706 | WSUS Synchronization in progress. Current phase: Synchronizing Internet facing WSUS Server. | Informational |
| 6707 | Content of WSUS Server %1 is out of sync with upstream server %2. Possible cause: Server %1 synchronization is disabled. Solution: Enable upstream synchronization for server %1 or manually import data from upstream server %2. | Warning |
| 6708 | WSUS synchronization complete, with pending license terms downloads. | Informational |
| 6709 | Failed to sync O365 update with title "%1". | Warning |
| 671 | Failed to read the site control file.%1%2 | Error |
| 672 | Failed to read registry.%1%2 | Error |
| 673 | Failed to copy file %1 to %2. | Error |
| 674 | Failed to open file %1.%2 | Error |
| 675 | Failed to connect to the inbox source..%1%2 | Error |
| 676 | Inbox %1 has not been created.%2 | Error |
| 677 | Required registry value %1 is empty.%2 | Error |
| 678 | Failed to update registry.%1%2 | Error |
| 679 | This component failed to retrieve the list of SMS sites from the site database. 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 SQL Server error logs. | Error |
| 680 | Failed to delete file %1.%2 | Error |
| 6800 | SMS Writer was unable to open control file "%1". Site backup will fail. Possible cause: Wrong name specified or permissions to "%1" are incorrect. Solution: Verify that a readable backup control file named "%1" exists. | Error |
| 6801 | SMS Writer stopped the "%1" executable on the local computer. | Informational |
| 6802 | SMS Writer could not stop the "%1" executable on the local computer. Possible cause: "%1" is an interactive Windows application and is waiting for user confirmation of the stop request. Solution: Manually stop this application. | Error |
| 6803 | SMS Writer started the "%1" executable on the local computer. | Informational |
| 6804 | SMS Writer could not start the "%1" executable on the local computer. Possible cause: "%1" does not exist in the specified location on the local computer. Solution: Verify that an executable "%1" exists on the local computer. Also specify its full path in the backup control file. | Error |
| 6805 | SMS Writer stopped the %1 service on site system %2. | Informational |
| 6806 | SMS Writer could not stop the %1 service on site system %2. Possible cause: SMS Writer does not have sufficient access rights to administer the site system. Solution: Verify that the accounts are properly configured to allow the site to administer the site system. If this problem persists, refer to the ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 6807 | SMS Writer started the %1 service on site system %2. | Informational |
| 6808 | SMS Writer could not start the %1 service on site system %2. Possible cause: SMS Writer does not have sufficient access rights to administer the site system. Solution: Verify that the accounts are properly configured to allow the site to administer the site system. If this problem persists, refer to the ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information. | Error |
| 6809 | SMS Writer stopped the %1 ConfigMgr client application on the local computer. | Informational |
| 681 | Failed to move file %1 to %2. | Error |
| 6810 | The %1 ConfigMgr client application on the local computer did not respond to SMS Writer's stop request. Possible cause: %1 is not a ConfigMgr client application and so cannot respond to a "close" event. Solution: Stop this application manually or as a standard executable. Possible cause: %1 was not running. Solution: Remove the "clientapp %1" definition from the backup control file. | Warning |
| 6811 | SMS Writer could not stop the %1 ConfigMgr client application on the local computer. Possible cause: %1 does not exist on the local computer. Solution: Verify that there are no errors in the "clientapp %1" definition, or remove the definition from the backup control file. | Error |
| 6812 | SMS Writer started the %1 ConfigMgr client application on the local computer. | Informational |
| 6813 | SMS Writer could not start the %1 ConfigMgr client application on the local computer. Possible causes: %1 is not in the system path or does not exist on the local computer. Solution: Verify that a ConfigMgr client application "%1" exists on the local system. Either add its directory to the system path, or specify its full path in the backup control file. | Error |
| 6814 | SMS Writer found syntax errors on the following lines:%1 in backup control file. Site backup will fail. Possible cause: There are syntax errors or unsupported commands that need to be removed. Solution: Edit backup control file and remove syntax errors on the given lines. | Error |
| 6815 | The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information. Possible cause: %1 is/are missing from their predefined location. Solution: Please copy the unavailable tools to their designated folder. | Warning |
| 6816 | Unable to verify the installation of the service : %1 This service will not be stopped or restarted. Possible cause: if %1 is a service then it is not installed or cannot be reached. Solution: Check the name and location of the Service and make sure that service is installed and the machine is reachable. | Warning |
| 6817 | Maximum sleep time is 15 minutes. Time given in Backup Control File exceeds this limit so it is being reset to this maximum limit. | Warning |
| 6818 | Token Symbol (%1) already defined. First value (%2) will be used. Possible cause: %1 is either a built-in symbol or already defined in Backup Control file. Solution: If it is a built-in symbol, it cannot be redefined, remove added definition from backup control file otherwise use only a single definition. | Warning |
| 6819 | SMS Writer was unable to locate the file system object %1. Possible cause: %1 is not readable. Solution: Adjust file attributes and/or permissions of %1. Possible cause: %1 are on remote computers that Site Backup does not have sufficient access rights to administer. Solution: Verify that the accounts are properly configured to allow the site to administer the remote computer. | Error |
| 682 | The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed but the authentication key did not match the recorded key for this client. | Error |
| 6820 | SMS Writer was unable to export the registry key %1 to %2. Possible cause: SMS Writer was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the accounts are properly configured to allow the site to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. | Error |
| 6821 | SMS Writer was unable to write the machine info to the temporary backup destination %1. Possible cause: %1 might be locked by another process. Solution: Delete %1 and restart SMS Writer; | Error |
| 6822 | SMS Writer tried to stop the %1 service on site system %2. This service is already stopped. | Informational |
| 6823 | SMS Writer tried to stop the %1 executable. This executable is already stopped. | Informational |
| 6824 | SMS Writer service was stopped manually. All the backup operations will be affected and cannot be completed. | Warning |
| 6825 | SMS Writer was unable to initialize the service. Possible cause: VSS services may not be running. | Error |
| 6826 | SMS Writer was unable to subscribe to the VSS services. | Error |
| 6827 | SMS Writer failed to build the metadata. Site Backup tasks will fail. | Error |
| 6828 | The backup application has not included all the required components in the backup list. | Warning |
| 6829 | SMS Writer is about to stop the ConfigMgr Services as part of the preparation for the Site backup. | Informational |
| 683 | The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was not signed and an authentication key was required. | Error |
| 6830 | The snapshots of the volumes required for the Site Backup have been successfully created. | Informational |
| 6831 | SMS Writer has started the ConfigMgr Services successfully. | Informational |
| 6832 | Site Backup task has been aborted. | Warning |
| 6833 | Site Backup task has completed successfully. | Informational |
| 684 | The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed and this client does not require authentication. | Error |
| 686 | Component %1 on %2 is %3. | Informational |
| 6900 | The Fallback Status Point failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 6901 | The Fallback Status Point can not authenticate the client %1. Possible cause: Client machine is not part of the domain or access account presented by client is not found. | Error |
| 6902 | The Fallback Status Point can not process any more messages. Possible cause: The disk is full. | Warning |
| 6903 | The Fallback Status Point could not load valid topics from registry. Possible causes: The registry can not be accessed or the registry is empty. | Error |
| 6904 | The Fallback Status Point could not write messages to the staging folder. Possible causes: The registry can not be accessed or the registry is empty or the staging folder can not be accessed. | Error |
| 6905 | The Fallback Status Point could not transfer messages from the staging folder to the outbox. Possible causes: The outbox is not accessible or is an invalid location. | Error |
| 7000 | WSUS Control Manager failed to configure proxy settings on WSUS Server "%1". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid. | Error |
| 7001 | Failures were reported on WSUS Server "%1" for WSUS components "%2". Solution: Verify that the failed WSUS components are installed and running. | Error |
| 7002 | Failures were reported on WSUS Server "%1" while trying to make WSUS database connection with SQL Server Exception error code %2. Possible cause: SQL Server service is not running or cannot be accessed. Solution: Verify that the SQL Server and SQL Server Agent services are running and can be contacted. | Error |
| 7003 | WSUS Control Manager failed to monitor WSUS Server "%1". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website. | Error |
| 7004 | WSUS Control Manager will not be able to configure WSUS Server "%1" as the WSUS Server of version 3.0 SP2 or greater is not installed on this site system. Solution: WSUS Site System requires WSUS Server of version 3.0 SP2 or greater to be installed on the site system. Verify that the correct version is installed | Error |
| 7100 | The Multicast Service Point failed to open multicast session. Possible cause: The WDS Multicast service is not running. Solution: Restart the WDS Service. | Error |
| 7101 | MCS Control Manager detected MCS is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base. | Error |
| 7102 | MCS Control Manager detected MCS is not responding to HTTP requests. The http error is %1. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MCS. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 7103 | Multicast Service was unable to create a WDS multicast namaspace for package with UNC "%2" and packageID "%3". The error is %1. | Error |
| 7104 | Multicast Service was unable to initialize multicast service. The error is %1. | Error |
| 7105 | Multicast Service was unable to initialize multicast provider. The error is %1. | Error |
| 7106 | Multicast Service was unable to initialize ISAPI. The error is %1. | Error |
| 7107 | Multicast Service did not grant access to directory %2 for client with account %3. The error is %1. | Error |
| 7108 | Multicast Service failed to read the SignedSerializedMCSKey from the registry on computer %1. Possible reasons are MCS certificate is not yet signed by Site Server. | Error |
| 7109 | Multicast Service has rejected a request from %2 for site %3 because it is not approved. | Warning |
| 7110 | Multicast Service has rejected request from %2 because this SMSID is marked as blocked. | Warning |
| 7111 | Multicast Service has rejected the request because %2 certificate has expired. | Warning |
| 7112 | Multicast Service rejected a request because %2 signature is invalid. | Warning |
| 7150 | The Multicast Service failed to initialize properly. The error encountered was %1. | Error |
| 7200 | The out of band service point failed to read notification registry. Possible cause: The out of band service point is not setup successfully. Possible cause: The registry is not accessible. Solution: Wait some time to verify out of band service point is setup successfully. Verify the registry can be accessible. | Error |
| 7201 | The out of band service point failed to initialize the inbox of %1. %Possible cause: The inboxes folder is not accessible. Possible cause: Inbox manager is not running. Solution: Verify the inboxer folder is accessible. Verify inbox manager is running. | Error |
| 7202 | The out of band service point is starting to send packets to completion port. | Informational |
| 7203 | The out of band service point completed sending %1 packet(s) to completion port. %2 packet(s) are in pending list. %3 packet(s) are failed to be sent to completion port. | Informational |
| 7204 | WinRM out of band service is not enabled. Solutions: Install WinRM out of band service manager and start it in out of band service point site role machine. | Error |
| 7205 | The port specified for incoming Hello packets is in use by another application. | Warning |
| 7206 | The out of band service point failed to provision %1 with error %2: %3. Possible cause: This condition can be caused by transient network connectivity errors. Possible cause: The account used to provision systems is not authorized to provision the management controller. Possible cause: the management controller is not in a state capable of being provisioned or updated. Solution: Verify network connectivity is functional between the out of band service point and the management controller. Verify that the account used to provision the management controller has sufficient permissions to update or provision the management controller. It may be necessary to reset the management controller to factory mode before it can be provisioned. | Error |
| 7207 | The out of band service point failed to %1 %2 with error %3. Possible cause: This condition can be caused by transient network connectivity errors. The credential used to connect management controller is invalid. The management controllers are in unavailable status. Solution: Verify network connectivity is functional between the out of band service point and the management controller. Verify that the credential used to connect the management controller is valid. It may be necessary to reset the management controller to factory mode and provision it again. | Error |
| 7208 | Provisioning failed because of an unsupported provisioning scenario. Possible causes: WinHTTP Proxy is being used between the out of band service point and the AMT-based computer; the AMT-based computer is not on a wired connection; the FQDN of the AMT-based computer exceeds the maximum allowed length of 44 bytes. Solution: Remedy the unsupported scenario by doing one of the following: Reconfigure the proxy configuration or remove the proxy requirement; connect the AMT-based computer to a wired network; reduce the length of the FQDN for the AMT-based computer. Then retry to provision the AMT-based computer. | Error |
| 7209 | Provisioning for %1 %2 failed due to an improper or missing provisioning certificate. Possible cause: This condition is caused when no provisioning certificate is selected or an incorrect certificate is selected. Solution: Create or apply provision certificates from trusted certificates authorities(for example: Verisign, etc). Select the certificates in the Component Configuration settings for the out of band component. | Error |
| 7210 | The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed. | Warning |
| 7211 | The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed. | Error |
| 7212 | The out of band service point failed to provision %1 with error %2: %3. Possible cause: This error can be caused by network configuration errors or because AMT has the wrong IP address for wired network access . Solution: Ensure that the DHCP scope for AMT is configured correctly with the options 006 (DNS Servers) and 015 (DNS Domain Name). Also check in AMT that the correct IP address is configured for wired network access. | Error |
| 7213 | Provisioning for %1 %2 failed due to all accounts failed to authentication with target device. Possible cause: The remote admin account password of this AMT device is out of sync with the site database. This condition might be caused by this device is provisioned by some other provision server, the MEBx password of this device has been changed locally or hasn't been configured as a provision account in the Component Configuration settings for the out of band component. Solution: If this device is provisioned by other provision server, please refer to migration scenario. If the MEBx password is changed, please change it into someone already known by Configuration Manager, or configure this MEBx password as a provision account. | Error |
| 7214 | The provisioning certificate with the thumbprint %1 failed to pass revocation check with error %2. Possible cause: This condition can be caused when the certificate is revoked by certificate authority. The computer does not have network connectivity to the certification authority. The proxy settings for the CRL checking are not set correctly. Solution: Verify that the certificate is unrevoked by certificate authority. Verify that the the system can connect to the certification authority (it could require internet connectivity for certain certification authorities). Verify the proxy configuration settings for the CRL checking are set correctly. | Error |
| 7215 | The provisioning certificate with the thumbprint %1 is invalid. Please ensure that CN name or OID is correct. | Error |
| 7216 | The out of band service point failed to run %1 on %2 with error %3. Possible cause: This error can occur when the AMT audit log is full and when %1 is set as critical event in the audit log settings. Solution: Verify the audit log settings on %2. Disable and then re-enable the AMT audit log settings on %2 in the Configuration Manager console. | Error |
| 7217 | The computer is configured to use IPv6 before IPv4. When out of band management uses IPv4 only, this configuration can negatively impact the performance of managing this computer out of band. Solution: You can change the precedence order by typing the following commands in a command prompt: "netsh interface ipv6 delete prefix ::ffff:0:0/96" and then "netsh interface ipv6 add prefix prefix=::ffff:0:0/96 precedence=45 label=4". | Warning |
| 7218 | The out of band service point failed to request a certificate by using the enrollment point. | Error |
| 7219 | The out of band service point cannot connect to the enrollment point. | Error |
| 7220 | The out of band service point can connect to the enrollment point. | Informational |
| 7300 | Asset Intelligence Update Service site role failed to install on "%1". Solution: Verify that the .Net Framework 2.0 or greater is installed. | Error |
| 7400 | Reporting Point site role failed to configure SQL Reporting Services on "%1". | Error |
| 7401 | SQL Reporting Services install is invalid on "%1". | Error |
| 7402 | Reporting Point failed to monitor SQL Reporting Services Server on "%1". | Error |
| 7403 | The report server service is not running on Reporting Service Point server "%1"; start the service to enable reporting. | Error |
| 7404 | SQL Reporting Services is not installed or properly configured on Reporting point server "%1". | Error |
| 7405 | SQL Reporting Services root folder "%1" is not present or not properly configured on the Reporting point server "%2". | Error |
| 7406 | The SQL Reporting Services datasource on Reporting point server "%1" is missing or has been changed outside of Configuration Manager. It will be rebuilt based on the RSP configuration. | Warning |
| 7502 | Asset Intelligence KB Manager encountered errors processing file %1 from online service. This file and subsequent data will be deleted, subsequent sync will bring the data again. | Warning |
| 7600 | Failure: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with error CR_DISP_DENIED: (CERTSRV_E_ENROLL_DENIED(0x80094011L) : The permissions on this certification authority do not allow the current user to enroll for certificates.) Possible cause: This condition may occur when the site server does not have permission to apply the requested certificate from the certification authority to the out of band management controller. Possible Cause: This condition may occur if the network connectivity is intermittent or failed during the attempt to update the out of band management controller with the requested certificate. Solution: Verify that the account used by SMS_EXECUTIVE service has permission to update the out of band management controller. For Intel AMT devices, the required permission (realm) is "PT Administer". Additionally, ensure that the network connection between the certification authority, the site server and the out of band management device is operational and required infrastructure components are accessilbe during the update. | Error |
| 7601 | Failure: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate trust error. Possible cause: This condition may occur when the root certificate of the CA is not in the store "Trusted Root Certification Authorities" or the root certificate is invalid. Solution: Verify that the root certificate of the CA is in the store "Trusted Root Certification Authorities" and it is valid. | Error |
| 7602 | Failure: The AMT Proxy Manager failed to add a object into AD. FQDN: %1, ADDN: %2, UUID: %3, AMT Version: %4. Possible cause: the site server does not have permission to publish the object in the Active Directory. | Error |
| 7603 | Failure: The AMT Proxy Manager failed to remove a object into AD. FQDN: %1, ADDN: %2. Possible cause: the site server does not have permission to remove the object in the Active Directory. | Error |
| 7604 | Failure: The AMT Proxy Manager failed to update a object in the AD. FQDN: %1, ADDN: %2. Possible cause: the site server does not have permission to remove the object in the Active Directory, or this object doesn't exist. | Error |
| 7605 | Warning: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate request pending. Please wait for a certification authority administrator to issue the certificate and the AMT Proxy Manager will retrieve it. | Warning |
| 7606 | The out of band service point failed to register the %1 in DNS. The machine's FQDN is %2. Possible cause: The site server does not have sufficient permission to update DNS. Solution: Check that the account used by SMS_EXECUTIVE has permission to publish records for the site server's DNS server. | Error |
| 7607 | The out of band service point failed to unregister the %1 in DNS. Possible cause: The site server does not have sufficient permission to update DNS. Solution: Check that the account used by SMS_EXECUTIVE has permission to publish records for the site server's DNS server. | Error |
| 7608 | The AMT Proxy Manager failed to replicate file %1 to out of band service point for the %2 time. The file will be re-send again later. | Warning |
| 7609 | The AMT Proxy Manager failed %2 times while replicating file %1 to out of band service point. The file has been moved to the BAD file inbox. | Error |
| 7700 | The Client Health Manager failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: The Client Health Manager is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 7800 | The RCM Control failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: The RCM Control is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 7801 | Site %1 is requesting initialization for replication group %2 from site %3. Refer to rcmctrl.log for further details. | Informational |
| 7802 | Received initialization request from Site %1 for replication group "%2". | Informational |
| 7803 | Snapshot for replication group "%1" for Site %2 created successfully. | Informational |
| 7804 | Failed to create snapshot for replication group "%1" for Site %2. Error: %3 Refer to rcmctrl.log for further details. | Error |
| 7805 | Snapshot for replication group "%1" from Site %2 applied successfully. | Informational |
| 7806 | Snapshot for replication group "%1" from Site %2 failed to be applied successfully. Error: %3 Refer to rcmctrl.log for further details. | Error |
| 7809 | The replication status for this site has changed from "%1" to "%2". | Informational |
| 7810 | Site %1 is ready for replication. | Informational |
| 7811 | A transmission error has been detected for messages going to site %1. Error: %2. Refer to rcmctrl.log for further details. | Error |
| 7812 | The queue %1 for site %2 is currently disabled. Refer to rcmctrl.log for further details. | Error |
| 7815 | Unable to determine link status for site %1 at this time. Setting link status to site %1 to unknown. Refer to rcmctrl.log for further details. | Warning |
| 7816 | The link status to site %1 is degraded at this time. Refer to rcmctrl.log for further details. | Error |
| 7817 | The replication system has experienced an error and is attempting to recover. All synchronizations are currently stopped. Refer to rcmctrl.log for further details. | Error |
| 7818 | The replication system has experienced an unrecoverable error and all synchronizations are currently stopped. Refer to rcmctrl.log for further details. | Error |
| 7819 | The replication system has recovered and is synchronizing with other sites again. | Informational |
| 7820 | This site is now in maintenance mode. Replication has been stopped until maintenance is complete. | Informational |
| 7821 | Maintenance is complete and replication has restarted. | Informational |
| 7822 | The link status to site %1 is failed at this time. Refer to rcmctrl.log for further details. | Error |
| 7825 | Site %1 is detaching. Refer to rcmctrl.log for further details. | Informational |
| 7826 | Site %1 has failed to detach. Refer to rcmctrl.log for further details. | Error |
| 7827 | Site %1 has successfully detached. Refer to rcmctrl.log for further details. | Informational |
| 7828 | The link status to site %1 has changed to active. Refer to rcmctrl.log for further details. | Informational |
| 7829 | The link status to site %1 is in an error state at this time. Refer to rcmctrl.log for further details. | Error |
| 7830 | Detected Service Broker is not enabled on site %1. To fix this, put the database in single user mode and execute 'ALTER DATABASE [%2] SET ENABLE_BROKER'. Refer to rcmctrl.log for further details. | Error |
| 7831 | On site %1, found service broker queue %2 disabled. It has been enabled now. Refer to the SQL view vLogs for more information. | Warning |
| 7832 | An unhandled exception has occurred - %1. Refer to rcmctrl.log for further details. | Error |
| 7833 | When RCM creates the linked server for %1, an exception has occurred - %2. Refer to rcmctrl.log for further details. | Error |
| 7834 | When RCM drops the linked server for %1, an exception has occurred - %2. Refer to rcmctrl.log for further details. | Error |
| 7835 | When RCM configures dview for table table %1, an exception has occurred - %2. Refer to rcmctrl.log for further details. | Error |
| 7836 | When RCM renames table %1 to %2_RCM for dview, an exception has occurred - %3. Refer to rcmctrl.log for further details. | Error |
| 7837 | When RCM tries to clean old replicated data on table %1 for dview, an exception has occurred - %2. Refer to rcmctrl.log for further details. | Error |
| 7838 | RCM has successfully configured dview on CAS for replicationgroup [%1]. Refer to rcmctrl.log for further details. | Informational |
| 7839 | RCM is currently configuring dview on CAS for replicationgroup [%1]. Refer to rcmctrl.log for further details. | Informational |
| 7840 | RCM received resync request for replicationgroup [%1] to version %2.Please refer to rcmctrl.log for further details. | Informational |
| 7841 | RCM has finished processing resync for replicationgroup [%1] to version %2.Please refer to rcmctrl.log for further details. | Informational |
| 7900 | Offline Image Servicing Manager started processing of schedule with ID %1 and name %2. | Informational |
| 7901 | Offline Image Servicing Manager completed processing of schedule with ID %1 and name %2. | Informational |
| 7902 | Offline Image Servicing Manager cancelled processing of schedule with ID %1 and Name %2. | Informational |
| 7903 | Offline Image Servicing Manager started copying image with ID %1 from image package source to local staging folder. | Informational |
| 7904 | Offline Image Servicing Manager started copying updated image with ID %1 from staging folder to the image package folder. | Informational |
| 7905 | Offline Image Servicing Manager completed copying image with ID %1. | Informational |
| 7906 | Offline Image Servicing Manager started applying updates on image with ID %1. | Informational |
| 7907 | Offline Image Servicing Manager completed installing updates on image with ID %1. | Informational |
| 7908 | Offline Image Servicing Manager successfully installed update with ID %1 on image with ID %2 (image index %3). | Informational |
| 7909 | Offline Image Servicing Manager determined that update with ID %1 is not required on image with ID %2 (image index %3). | Informational |
| 7910 | Offline Image Servicing Manager failed to process schedule with ID %1 and name %2. | Error |
| 7911 | Offline Image Servicing Manager failed to apply update with ID %1 on image with ID %2 (image index %3). | Error |
| 7912 | Offline Image Servicing Manager failed to mount image with ID %1 (image index %2) to mount directory %3. Error : %4. | Error |
| 7913 | Offline Image Servicing Manager failed to unmount image with ID %1 (image index %2) from mount directory %3. Error : %4. | Error |
| 7914 | Offline Image Servicing Manager failed because there is not enough free disk space left on the staging drive %1. Required disk Space = %2 MB, available free disk space = %3 MB. | Error |
| 7915 | Offline Image Servicing Manager cannot write to the image package source location for the image with ID %1. Please make sure that the image package source folder can be written to. | Error |
| 7916 | Offline Image Servicing Manager does not support image with ID %1 (image index %2) and therefore will not process this image. | Informational |
| 7917 | Offline Image Servicing Manager could not determine if binary %1 from an update with ID %2 is supported. | Informational |
| 7918 | Offline Image Servicing Manager: applicability check failed for binary %1 from an update with ID %2. | Informational |
| 7919 | Offline Image Servicing Manager failed to apply one or more updates on image with package ID %1 (image index %2), but continued offline servicing of the image on error per selected by user option. | Error |
| 8000 | Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which PORTALWEB is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which PORTALWEB is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. For more information, refer to Microsoft Knowledge Base. | Error |
| 8001 | Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http error is %1. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the PORTALWEB. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 8002 | Portal Web Site Control Manager detected PORTALWEB is responding to HTTP requests. | Informational |
| 8003 | Portal Web Site Control Manager detected PORTALWEB is not able to save the Web.config. Possible causes: Web.config is unavailable, deleted, or security properties have been set to prevent editing. Solution: Verify Web.config is present and that the account used for the SMS_EXECUTIVE service has rights to edit the web.config. If the web.config file is not present, you can reinstall the system role. | Error |
| 8004 | Portal Web Site Control Manager detected PORTALWEB can update the Web.config file. | Informational |
| 8005 | The application catalog website role did not find an SSL certificate required to communicate with the application catalog web service role. Possible causes: 1) The application catalog website role is configured to communicate using HTTP, but the application catalog web service role that this website communicates with is configured to use HTTPS. 2) The application catalog website is configured with an HTTPS binding in IIS but no certificate is configured for the binding. Solution: 1) Configure the application catalog website role with the required SSL certificate. | Error |
| 8100 | Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is %1, %2. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which AWEBSVC is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. For more information, refer to Microsoft Knowledge Base. | Error |
| 8101 | Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http error is %1. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the AWEBSVC. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 8102 | Application Web Service Control Manager detected AWEBSVC is responding to HTTP requests. | Informational |
| 8103 | Application Web Service Control Manager detected AWEBSVC is not able to save the Web.config. Possible cause: Web.config is unavailable, deleted, or security properties have been set to prevent editing. Solution: Verify Web.config is present and that the account used for the SMS_EXECUTIVE service has rights to edit the web.config. If the web.config file is not present, you can reinstall the system system role. | Error |
| 8104 | Application Web Service Control Manager detected AWEBSVC can update the Web.config file. | Informational |
| 8200 | Package Transfer Manager has successfully sent software distribution package "%1" version %2 to distibution point "%3". | Informational |
| 8201 | The address to distribution point server "%1" is invalid. Possible cause: The destination distribution point share name is missing. Solution: Define a valid address in the Configuration Manager Console for this distribution point. | Error |
| 8202 | The Package Transfer Manager cannot connect to distribution point server "%1" over the LAN. Possible cause: Distribution point server "%2" might not be connected to the LAN. Solution: Verify that distribution point server "%2" is connected to the LAN and functioning properly. Possible cause: Share "%3" might not be accessible. Solution: Verify that share "%3" is visible and that the site server machine account or site system connection account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network. | Error |
| 8203 | The Package Transfer Manager failed to send files to destination server "%1". Make sure the site server machine account or the site system connection account has full access to directory "%2" on the destination site server and the destination site server has sufficient free disk space. | Error |
| 8204 | Package Transfer Manager is currently sending software distribution package %1 to distribution point server %2, %3 percent of the sending has already completed. | Informational |
| 8205 | Package Transfer Manager encountered errors while sending software distribution package %1 to distribution point server %2, %3 percent of the sending has already completed. | Warning |
| 8206 | Package Transfer Manager is retrying to distribute package "%1" to distribution point %2. Wait to see if the package is successfully distributed on the retry. | Informational |
| 8207 | Package Transfer Manager has failed to distribute package "%1" to distribution point %2. Please try to distribute the package again to this distribution point server. | Error |
| 8208 | Package Transfer Manager has failed to verify hash for package "%1", Version %2 on distribution point %3. Please try to distribute the package again to this distribution point server. If this package has been marked for prestaging on the distribution points then make sure the package has been correctly copied to the appropriate package folder on the distribution point server. | Error |
| 8209 | Package Transfer Manager has successfully verified that the package "%1", Version %2 has been prestaged on distribution point %3. | Informational |
| 8210 | Package Transfer Manager has successfully updated the package "%1", Version %2 on distribution point %3. | Informational |
| 8211 | Package Transfer Manager failed to update the package "%1", Version %2 on distribution point %3. Review PkgXferMgr.log for more information about this failure. Possible cause: Site server does not have sufficient rights to the source directory. Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory. Possible cause: There is not enough disk space available on the distribution point. Solution: Verify that there is enough free disk space available on the distribution point. | Error |
| 8212 | Package Transfer Manager failed to update the package "%1", Version %2 on pull distribution point %3. This pull distribution point has no sources from which it can download content. We will try again later. Possible cause: The content was not distributed to source distribution points. Solution: Ensure that the content is distributed to at least one of the source distribution points. Possible cause: The content was distributed to source distribution points, but the source distribution points have not finished downloading the content. Solution: Check content status to see if this package is in-progress for the source distribution point. Possible cause: The source distribution point list is empty. Solution: Check the 'Pull Distribution Point' tab in distribution point properties in the admin console and ensure that the source distribution points are set correctly. | Informational |
| 8300 | Enrollment Point Control Manager detected that the Enrollment Point is not responding to HTTP/HTTPS requests. The http status code and text is %1, %2. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which Enroll Service is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which ENROLLSRV is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. For more information, refer to Microsoft Knowledge Base. | Error |
| 8301 | Enrollment Point Control Manager detected Enrollment Point is not responding to HTTP/HTTPS requests. The http status code is %1. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the ENROLLService. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 8302 | Enrollment Server is starting.... | Informational |
| 8303 | Enrollment Point fails to connect to SQL server. Possible cause: The SQL server service stopped working.The credentials used to connect to the SQL server are incorrect. Action to take: Manually restart the SQL server service. Check if the credentials used to communicate with the SQL server are correct. | Error |
| 8304 | Enrollment Point cannot accomplish tasks on the CA. Possible cause: The Certification Authority is down. Action to take: Check if the Certification Authority is running properly. Possible cause: The credentials used to connect to the Certification Authority are incorrect.The CA is not functioning correctly. Action to take: Check if the Certification Authority is running properly. Check if the credentials used to communicate with the CA server are correct. | Error |
| 8306 | ConfigMgr server cannot accomplish tasks in Active Directory. Possible cause: The credentials used to connect to the Domain Controller are incorrect.The Domain controller is not functioning correctly. Action to take: Check if the Domain controller is running properly. Check if the credentials used to communicate with the DC are correct. | Error |
| 8307 | The Enrollment Point failed to revoke the certificate (Cert Serial Number: %1) issued to the device/requester %2 on the Certification Authority %3. Possible cause: The site server does not have permission to revoke certificate on this Certification Authority. Action to take: Make sure that the site server has the permission to revoke certificates on the Certification Authority or ask the CA administrator to revoke the certificate manually. Possible cause: The certification authority is not reachable or not working properly. Action to take: Ensure that the certification authority is reachable and functional. | Error |
| 8314 | MDM Process For %1 Is Not Running. | Error |
| 8400 | Enrollment Point AD Service Control failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: The Enrollment AD Service Control is waiting for the information to become available and will retry obtaining the registry information at its next interval. | Error |
| 8500 | Enrollment Proxy Point Control Manager detected that the Enrollment Proxy Point Component is not responding to HTTP/HTTPS requests. The http status code and text is %1, %2. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which Enrollment Proxy Point is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which Enrollment Point is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. For more information, refer to Microsoft Knowledge Base. | Error |
| 8501 | Enrollment Proxy Point Control Manager detected that the Enrollment Proxy Point Component is not responding to HTTP/HTTPS requests. The http error is %1. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the ENROLLWEB. For more information, refer to Microsoft Knowledge Base article 838891. | Error |
| 8502 | Enrollment Proxy Point is starting.... | Informational |
| 8600 | The Migration Manager on Configuration Manager site server "%1" was able to connect and authenticate successfully to Configuration Manager 2007 site server "%2". | Informational |
| 8601 | The Migration Manager on Configuration Manager site server "%1" was unable to connect to Configuration Manager 2007 site server "%2" due to network connection time out. Check the network connection and the firewall configuration between the two servers. | Error |
| 8602 | The Migration Manager on Configuration Manager site server "%1" was unable to connect to Configuration Manager 2007 site server "%2" due to insufficient permissions. Ensure the account specified for the specified source Configuration Manager site is part of the local "SMS Admins" security group and has been granted full permissions to Configuration Manager 2007 site. | Error |
| 8603 | The Migration Manager on Configuration Manager site server "%1" detected the specified site "%2" is not a valid Configuration Manager 2007 top-level site or stand-alone primary site. Please specify the fully qualified domain name of a Configuration Manager 2007 top-level site or stand-alone primary site as the source hierarchy. | Error |
| 8604 | The Migration Manager on Configuration Manager site server "%1" has the same site code as the specified site "%2". Configuration Manager cannot migrate from sites with the same sitecode. Ensure the site codes are unique across both your Configuration Manager 2007 hierarchy and Configuration Manager 2012 hierarchy. | Error |
| 8605 | The Migration Manager on Configuration Manager site server "%1" finished the data gathering process with Configuration Manager 2007 site server "%2". | Informational |
| 8606 | The Migration Manager on Configuration Manager site server "%1" started the migration job "%2 (%3)" to migrate "%4" objects from the source hierarchy. | Informational |
| 8607 | The Migration Manager on Configuration Manager site server "%1" stopped the migration job "%2 (%3)" per manual request through SDK or Console. | Informational |
| 8608 | The Migration Manager on Configuration Manager site server "%1" finished the migration job "%2 (%3)". | Informational |
| 8609 | The source hierarchy "%1" specified is not a valid Configuration Manager 2007 top-level site or stand-alone primary site. | Error |
| 8610 | The Migration Manager on Configuration Manager site server "%1" was unable to complete the SQL operation on the SQL Server "%2" of Configuration Manager 2007 due to error "%3". | Error |
| 8611 | The value "%1" configured for the parameter "%2" of Migration Manager is invalid. | Warning |
| 8612 | The migration job "%1" failed to copy content for some packages due to error "%2". | Error |
| 8613 | Object %1 with path %2 have failed to migrate as part of migration job %3 (%4) which ran on site server %5 with error %6. | Error |
| 8614 | The Migration Manager on Configuration Manager site server "%1" encountered a SQL query timeout. Please consider increasing the timeout value for the Migraton Manager by configuring the registry. | Error |
| 8615 | The object "%1" being migrated is missing a dependency "%2". Confirm the configuration of the object "%1" in the Configuration Manager 2007 environment and initiate the "Gather Data Now" action in the console and recreate the migration job. | Error |
| 8616 | The Migration Manager on Configuration Manager site server "%1" gathered from Configuration Manager 2007 site server "%3" "%2" new source sites. | Informational |
| 8617 | An unexpected error occurred in the Migration Manager on Configuration Manager site server "%1". Please refer to the migmctrl.log file for details. | Error |
| 8618 | The Migration Manager on Configuration Manager site server "%1" encountered an error "%2" while performing SQL operations. Please refer to the migmctrl.log file for details. | Error |
| 8619 | Updates Assignment "%1" includes Update "%2" (BulletinID "%3", ArticleID "%4", CI_ID "%5") which is not available on the destination site. Please ensure updates have been synchronized at the destination, or remove this Update from the Updates Assignment. | Error |
| 8620 | The data gathering agent configuration type "%1" is not recognized. | Error |
| 8621 | When connecting to "%1", the migration data gathering process encountered a source site code ("%2") already being used for mapping "%3" to "%4" (%5). | Warning |
| 8622 | The CI "%1" was made applicable to all platforms during migration. | Warning |
| 8623 | The CI "%1" is not applicable to any platforms after migration. | Warning |
| 8700 | SMS Rule Engine error. Message: %2. Source: %1. | Error |
| 8701 | Rule Evaluation started. | Informational |
| 8702 | Rule Evaluation completed. | Informational |
| 8703 | Rule Evaluation failed. Message: %2. Source: %1. | Error |
| 8704 | Content download started. | Informational |
| 8705 | Content download completed. | Informational |
| 8706 | Content download failed. Message: %2. Source: %1. | Error |
| 8707 | Update group creation failed. Message: %2. Source: %1. | Error |
| 8708 | Deployment creation failed. Message: %2. Source: %1. | Error |
| 8800 | Connection to Exchange server %1 failed. Message: %2. | Error |
| 8801 | Connection to Exchange server %1 failed. Possible cause: incorrect server address or server address not reachable. | Error |
| 8802 | Connection to Exchange server %1 failed. Possible cause: unknown username or bad password. | Error |
| 8803 | Connection to Exchange server %1 failed. Possible cause: access is denied. | Error |
| 8810 | PowerShell 2.0 is not installed which is required by Exchange Connector component. Solution: please install PowerShell 2.0. For more information on PowerShell 2.0 installation see http://support.microsoft.com/kb/968930. | Error |
| 8811 | Configuration is corrupted for %1. Possible cause: incorrectly set configuration through SDK. Solution: delete and reset configuration through Admin Console. | Error |
| 8812 | Policy setting %1 is invalid. Possible cause: incorrectly set setting through SDK. | Warning |
| 8813 | Configured setting name %1 is invalid. Possible cause: incorrectly set setting through SDK. | Warning |
| 8814 | Ignore configured on-premise Exchange server %1. The Exchange organization %2 for this server has already been configured on site %3 as server %4. | Warning |
| 8815 | Ignore configured hosted Exchange server %1. The Exchange organization %2 for this server has already been configured on site %3 as server %4 with credential %5. | Warning |
| 8816 | No default policy for Exchange server %1.Possible cause: default policy has been deleted from Exchange side. | Warning |
| 8817 | Exchange cmdlet call failed. Cmdlet %1. ErrorId: %2 Message: %3 | Warning |
| 8818 | Exchange cmdlet %1 is not found. Possible cause: the credential used for this connector do not have proper permission. . Message: %2 | Warning |
| 8819 | Exchange ActiveSync device %1 is not found in Exchange server %2. Possible cause: the device has been removed from Exchange server. | Warning |
| 8831 | Connected to Exchange Server %1. Start full synchronization. | Informational |
| 8832 | Successfully ran the full synchronization on Exchange Server %1. %2 mobile devices has been discovered. | Informational |
| 8833 | Successfully ran the delta synchronization on Exchange Server %1. %2 mobile devices are updated. | Informational |
| 8834 | Global mobile device setting has been successfully synchronized to Exchange Server %1. | Informational |
| 8835 | Successfully send wipe request of the device %1 to Exchange Server %2. Waiting for the wipe confirmation. | Informational |
| 8836 | Received the wipe confirmation of the device %1. The device has been successfully wiped. | Informational |
| 8837 | Connected to Exchange Server %1. Start delta synchronization. | Informational |
| 8838 | Allow access request for Device %1 has been successfully sent to Exchange Server %2. | Informational |
| 8839 | Block access request for Device %1 has been successfully sent to Exchange Server %2. | Informational |
| 8840 | Organization DefaultAccessLevel and AdminEmailRecipients has been successfully synchronized to Exchange Server %1. | Informational |
| 8841 | Exchange ActiveSync access rule %1 has been successfully created on Exchange Server %2. | Informational |
| 8842 | Exchange ActiveSync access rule %1 has been successfully removed from Exchange Server %2. | Informational |
| 8900 | Active Directory Forest Discovery was run for forest %1 and discovered %5 IP subnets and %6 Active Directory sites. | Informational |
| 8901 | Active Directory Forest Discovery was run for forest %1 and it could not complete. The error code returned was %5. Possible cause: the FQDN for the forest cannot be resolved because the forest FQDN specified does not exist or cannot be reached. Solution: ensure that the FQDN for the forest is entered correctly, and that the forest can be contacted by the site server over the network. | Warning |
| 8902 | Active Directory Forest Discovery was not able to connect to Site Server database. Please see ADForestDisc.log for details. Active Directory Forest Discovery will be attempted on next cycle. | Error |
| 8903 | Active Directory Forest Discovery was not able to use credentials supplied for account %5 to discover forest %1. Please check if credentials supplied to discovery the forest are valid. | Error |
| 8904 | Active Directory Forest Discovery was not able to connect to forest %1. Error code returned is: %5. Forest discovery for this forest will be attempted again on next cycle. Possible causes include: Network connection problems (server unreachable, DNS problems, dis-joint namespaces), server busy or not operational, authentication issues preventing site server to connect to the forest. | Warning |
| 9100 | Alert notification sent notification email for Alert (ID:%1) successfully. | Informational |
| 9101 | Alert notification sent notification email failed for Alert (ID:%1), please check the email addresses of the sender(%2) and recipients(%3). | Error |
| 9102 | Alert notification sent notification email failed for Alert (ID:%1), the email could not be delivered to recipients(%2). | Error |
| 9103 | Alert notification sent notification email failed for Alert (ID:%1), an SMTP exception occured. | Error |
| 9104 | Alert notification failed to initialize the SMTP client, please check the credential of user "%1". | Error |
| 9200 | Endpoint Protection Control Manager failed to update malware definition. Verify that the Endpoint Protection client is installed and running on the Endpoint Protection role server. Verify that the Endpoint Protection client on the role server can receive updated definitions. Error code returned is:"%1". | Error |
| 9201 | Endpoint Protection Manager failed to generate malware detection alerts for type:"%1". Verify that the site database is configured correctly. Error code returned is:"%2". | Error |
| 9300 | Cloud Content Manager encountered an internal error [%1] Check logs for details. | Error |
| 9301 | Cloud Content Manager was unable to encrypt content for the package %1. | Error |
| 9302 | Cloud Content Manager was unable to connect to the service %1. | Error |
| 9303 | Cloud Content Manager was unable to determine the upload location for the package %1. | Error |
| 9304 | Cloud Content Manager was unable to find the content source [%1] for package %2. | Error |
| 9305 | Cloud Content Manager was unable to encrypt the file %1. | Error |
| 9306 | Cloud Content Manager was unable to access the storage account for %1. | Error |
| 9307 | Cloud Content Manager was unable to get content key for content %1. | Warning |
| 9308 | Cloud Content Manager encountered blank content XML for %1. | Warning |
| 9309 | Cloud Content Manager was unable to mark the upload status as completed for %1. | Warning |
| 9310 | Cloud Content Manager encountered an empty download address from content upload for package %1. | Warning |
| 9311 | Cloud Content Manager was unable to connect to the cloud distribution point service when trying to distribute package %1. | Error |
| 9400 | Cloud Services Manager encountered an internal error, %1. | Error |
| 9401 | Cloud Services Manager task [%1] has failed, exception %2. | Error |
| 9402 | Cloud Services Manager task [%1] has been canceled. | Warning |
| 9403 | Cloud Services Manager created service %1 in region %2. | Informational |
| 9404 | Cloud Services Manager created a deployment for service %1 in region %2. | Informational |
| 9405 | Cloud Services Manager has started provisioning service %1 in region %2. | Informational |
| 9406 | Cloud Services Manager has configured storage account %1 for service %2. | Informational |
| 9407 | Cloud Services Manager has uploaded the service package for service %1 to %2. | Informational |
| 9408 | Service %1 in region %2 is ready for use. | Informational |
| 9409 | Cloud Services Manager has successfully provisioned service %1 in region %2. | Informational |
| 9410 | Cloud Services Manager failed to provision service %1 in region %2. Please see cloudmgr.log for more details. | Error |
| 9411 | Cloud Services Manager is unable to connect to Windows Azure for subscription Id %1. Please check your proxy configuration. | Error |
| 9412 | Cloud Services Manager is starting to uninstall service %1. | Informational |
| 9413 | Cloud Services Manager has completed the uninstall for service %1. | Informational |
| 9414 | Cloud Services Manager has failed to uninstall service %1. Please delete the deployment using the Windows Azure portal. | Error |
| 9415 | Cloud Services Manager has failed to authenticate for subscription Id %1. Please check that the management certificate is property configured. | Error |
| 9416 | Cloud Services Manager has started maintenance for service %1. | Informational |
| 9417 | Cloud Services Manager has completed maintenance for service %1. | Informational |
| 9418 | Cloud Services Manager has failed to complete maintenance for service %1. | Error |
| 9419 | Cloud Services Manager has requested the deployment to start for service %1. | Informational |
| 9420 | Cloud Services Manager has started the deployment for service %1. | Informational |
| 9421 | Cloud Services Manager has failed to start the deployment for service %1. Exception %2. | Error |
| 9422 | Cloud Services Manager has requested the deployment to stop for service %1. | Informational |
| 9423 | Cloud Services Manager has stopped the deployment for service %1. | Informational |
| 9424 | Cloud Services Manager has failed to stop the deployment for service %1. Exception %2. | Error |
| 9425 | The %1 certificate was invalid for cloud service %2. Please check CloudMgr.log for further details. | Error |
| 9426 | Service Monitor could not find service %1. Please check the status of the service through the azure portal. | Error |
| 9427 | Service Monitor found that the Deployment %1 is in %2 state. Expected state is 'Running'. Please check the status of the deployment through the azure portal. | Error |
| 9428 | Service Monitor could not find the Deployment %1. Please check the status of the deployment through the azure portal. | Error |
| 9429 | Service Monitor received exception while monitoring service %1. Please check CloudMgr.log for further details. Exception: %2. | Error |
| 9430 | Service Monitor found the deployment in running state for service %1. | Informational |
| 9431 | Storage account was not found for service %1. | Error |
| 9500 | License Manager encountered an internal error [%1] Check logs for details. | Error |
| 9500 | PXE is enabled on distribution point %1 | Informational |
| 9501 | PXE is disabled on distribution point %1 | Informational |
| 9502 | Multicast is enabled on distribution point %1 | Informational |
| 9503 | Multicast is disabled on distribution point %1 | Informational |
| 9504 | Distribution Point un-installation successfully completed on server "%1". | Informational |
| 9505 | Distribution Point un-installation failed to complete on server "%1". | Error |
| 9506 | Package distribution cancelled by user for package "%1" on distribution point "%2". | Informational |
| 9507 | Pull Distribution Point "%1" started downloading package "%2". | Informational |
| 9508 | Pull Distribution Point "%1" is currently downloading package "%2". %3 percent download has completed. | Informational |
| 9509 | Pull Distribution Point "%1" completed downloading package "%2" and is now performing post download actions. | Informational |
| 9510 | Distribution Manager is sending package "%1" to connector on "%2". | Informational |
| 9511 | Distribution Manager failed to send package "%1" to connector on "%2". Solution: Verify that there is enough free disk space on Connector. | Error |
| 9512 | Distribution Manager sent package "%1" to connector on "%2". | Informational |
| 9513 | Connector is unable to upload version %1 of package "%2" to Windows Intune because a newer version of the package exists. Possible cause: A package update has recently been triggered, wait until the connector processes the newer version of the package. | Warning |
| 9514 | The hash of package "%1" is invalid on connector "%2". Please redistribute the package. | Error |
| 9515 | Successfully validated the content of package "%1" on connector "%2". | Informational |
| 9516 | Started uploading package "%1" to Windows Azure Intune from connector "%2". | Informational |
| 9517 | Failed to validate package "%1" on package share on distribution point "%2". | Warning |
| 9518 | The hash of package "%1" on package share on distribution point "%2", is invalid. Please redistribute it. | Error |
| 9519 | The package "%1" was processed successfully, but was not copied to the Windows Intune distribution point. To be copied to the Windows Intune distribution point, the package must contain a deployment type that is supported by devices that are enrolled by Windows Intune which include Windows RT, Windows Phone, Android, or iOS. | Informational |
| 9600 | Failed to initialize. Please refer to dmpuploader.log for further details. | Error |
| 9601 | Site has finished processing resync request for replicationgroup [%1]. Please refer to dmpuploader.log for further details. | Informational |
| 9602 | Received drs_syncstart message for replicationgroup [%1], however it is pending resync. Please refer to dmpuploader.log for further details. | Warning |
| 9603 | Received resync request for replicationgroup [%1] to version %2. Please refer to dmpuploader.log for further details. | Informational |
| 9604 | StartUpload replicationgroup [%1] last sync version %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details. | Error |
| 9605 | Upload transmission [%1] blockID %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details. | Error |
| 9606 | EndUpload transmission [%1] blockID %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details. | Error |
| 9607 | Failed to upload. Please refer to dmpuploader.log for further details. | Error |
| 9608 | Site has finished uploading. Please refer to dmpuploader.log for further details. | Informational |
| 9700 | Failed to initialize. Please refer to dmpdownloader.log for further details. | Error |
| 9701 | Failed to download. Please refer to dmpdownloader.log for further details. | Error |
| 9702 | Site has finished uploading. Please refer to dmpdownloader.log for further details. | Informational |
| 9800 | Notification Server on %1 failed to initialize. Possible cause: Failed to initialize with error code %2. To help identify the problem, see the bgbserver.log on the management point %3. | Error |
| 9801 | Notification Server on %1 initialized successfully. | Informational |
| 9802 | Windows Firewall on %1 does not allow clients to connect to the Notification Server via TCP port %2. Possible cause: Windows Firewall configuration for port %3 is blocked. Review Windows Firewall configuration for port %4. You might require an exception rule for this port or for dllhost.exe. To help identify the problem, see the bgbserver.log on the management point %5. | Warning |
| 9803 | Windows Firewall on %1 allows clients to connect to Notification Server via TCP port %2. | Informational |
| 9804 | Notification Server on %1 failed to connect to the site database %2. Possible cause: Notification Server failed to connect to the site database. Possible causes: 1. The network is temporally unavailable. 2. Firewall misconfiguration. 3. Authentication issues. Verify that the site database is up and running. To help identify the problem, see the bgbserver.log on the management point %3. | Error |
| 9805 | Notification Server on %1 successfully connected to the site database %2. | Informational |
| 9806 | Notification Server on %1 failed to initialize the TCP listener on port %2. Possible cause: TCP port %3 might be in use by another application. Verify that no other application is listening on TCP port %4. To help identify the problem, see the bgbserver.log on the management point %5. | Error |
| 9807 | Notification Server on %1 successfully initialized the TCP listener on port %2. | Informational |
| 9900 | Notification Manager failed to initialize. Possible cause: Failed to initialize with error code %1. To help identify the problem, see the bgbmgr.log on the site %2. | Error |
| 9901 | Notification Manager initialized successfully. | Informational |
| 9902 | The SQL Server Service Broker %1 used by Notification Manager is disabled. Possible cause: Enable the SQL Server Service Broker %2 in the site database %3. To help identify the problem, see the bgbmgr.log on the site %4. | Error |
| 9903 | The SQL Server Service Broker %1 used by Notification Manager is enabled. | Informational |
Responses