%11Client Configuration Manager failed to read the account information for site %1.%12 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.%0
Client Configuration Manager failed to connect to the registry of site server %1.%12 Solution: Reboot. If you suspect a software ...
Client Configuration Manager failed to create a thread.%12 Possible cause: The computer is low on memory or other resources. ...
Client Configuration Manager failed to create an inbox rule to copy files "%1" from inbox "%2" to inbox "%3."%12 Solution: ...
Client Configuration Manager failed to establish inbox "%1" on the site server.%12 Solution: Do nothing. Client Configuration ...
Client Configuration Manager failed to read the account information for site %1.%12 Possible cause: The site control file ...
Client Configuration Manager failed to read the component item "%1" from the site control file on the server "%2".%12 Possible ...
Client Configuration Manager failed to read the site control file for site "%1."%12 Solution: Do nothing. If CCM has just ...
Client Configuration Manager failed to read the site identification values from the registry in \HKLM\Software\Microsoft\SMS\Identification ...
Client Configuration Manager reports that queue "%1" contains %2 Client Configuration Requests (CCRs), which exceeds the ...