Message ID | Severity | Message |
---|---|---|
3000 |
Error |
SMS Client Configuration Manager (CCM) 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 SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file’s permissions or attributes so that this SMS service can access the file. 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 SMS and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
3001 |
Error |
SMS Client Configuration Manager failed to read the site identification values from the registry in the \HKLM\Software\Microsoft\SMS\Identification key. Solution: Reboot. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
3002 |
Warning |
SMS Client Configuration Manager failed to connect to the registry of site server %1. Solution: Reboot. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
3003 |
Error |
SMS Client Configuration Manager (CCM) failed to read the SMS Service 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 SMS and reset the current installation. If you ignore this problem, CCM will continue using any SMS Client Remote Installation account that is available (if specified), but client installations might not be successful. |
3004 |
Error |
SMS Client Configuration Manager (CCM) 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 SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file’s permissions or attributes so that this SMS service can access the file. 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 SMS and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. If you ignore this problem, CCM will continue using previously read information, but client installations might not be successful. |
3005 |
Error |
SMS Client Configuration Manager (CCM) failed to create a thread. Possible cause: The computer is low on memory or other resources. Solution: Reboot. |
3006 |
Warning |
SMS Client Configuration Manager failed to establish inbox %1 on the site server. Solution: Do nothing. SMS 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. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the SMS Service account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
3007 |
Warning |
SMS Client Configuration Manager failed to establish inbox %1 on CAPs. Solution: Do nothing. SMS 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. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the SMS Service account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
3008 |
Warning |
SMS Client Configuration Manager failed to create an inbox rule to copy files %1 from inbox %2 to inbox “%3.” Solution: Do nothing. SMS 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 SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
3009 |
Warning |
SMS 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 SMS Client Configuration Manager is not processing CCRs properly. Solution: Stop and restart SMS Client Configuration Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator 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 SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. |
3010 |
Warning |
In the past %3 hours, SMS Client Configuration Manager (CCM) has made %1 unsuccessful attempts to install SMS on 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 SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. |
3011 |
Error |
SMS Client Configuration Manager (CCM) failed to complete the SMS 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 SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. |
3012 |
Error |
SMS Client Configuration Manager failed to complete its periodic account maintenance cycle. Possible cause: Network problems. Solution: Do nothing. SMS Client Configuration Manager will retry in the next interval (the default is 30 days). This error will not cause problems with the operation of SMS. The account maintenance cycle merely deletes obsolete domain accounts. |