Quantcast
Channel: TechNet Blogs
Viewing all articles
Browse latest Browse all 34890

Support Tip: ConfigMgr clients fail to register and generate 0x80040231 errors in CCMExec.log

$
0
0

imageHi everyone, Arvind Kr. Rana here with another Configuration Manager support tip for you. I’ve run across this a couple times and thought it would be worth mentioning here in case you happen to run into the same issue.

What happens is that we try to install the Configuration Manager client using following command line where “SIGNCERT.cer” is the document signing certificate:

ccmsetup.exe /native:Fallback SMSSIGNCERT="c:\SIGNCERT.cer" SMSSLP=serverName.domain.com SMSSITECODE=<siteCode>

The client was getting installed, however there were failures with the registration process with the Management Point. Looking in CCMExec.log we found the following:

CCMHTTP] HTTP ERROR: URL=http://<Site Server Name>/ccm_system/request, Port=80, Protocol=http, SSLOptions=0, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE CCMEXEC
Raising event:
instance of CCM_CcmHttp_Status
{
DateTime = "20121212220939.655000+000";
HostName = "<Site Server Name>";
HRESULT = "0x8004027e";
ProcessID = 4000;
StatusCode = 403;
ThreadID = 3024;
};
Successfully sent security settings refresh message.
HandleRemoteSyncSend failed (0x80040231).
CForwarder_Sync::Send failed (0x80040231).
CForwarder_Base::Send failed (0x80040231).

We checked the client certificate and found that it was exported from a client machine on the domain without the private key and was imported here on the workgroup machine.

What we did to resolve the issue was create a new client certificate on the Certificate Authority (CA) and exported it along with the private key, then imported it on the client machine and placed it in the personal store. Once we did this the client could install and register as designed.

The takeaway here is that while there can be multiple causes that may prevent the client install registration process, we need to make sure that we have the client authentication certificate and the document signing certificate present on the target machine in order to successfully install the client.

Arvind Kumar Rana | Senior Engineer | System Center Team

Get the latest System Center news onFacebookandTwitter:

clip_image001clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/


Viewing all articles
Browse latest Browse all 34890

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>