Saturday, 9 June 2012

MP Reg: Failed to get client(GUID:) public key: 0x80040238

Recently I thought I had an issue with SCCM clients being unable to register normally when initially installed. I had noticed the following error in the MP_RegistrationManager.log on the site server with the management point role installed and could not find any information on the web discussing this particular error. As a result I opened a case with Microsoft PSS and was informed that 0x80040238 can be safely ignored because it just represents a temporary status when a new client is trying to register. When a MP receives a new client registration request it will try to match the client public certificate hash (mixed or native mode environments)  to any already known in the database as a means of matching to an existing resource record. If there is no existing resource record with the same hash to match with then the following error will be recorded temporarily until the registration process is completed and a new resource record is created. Unfortunatily without verbose agent logging enabled you do not see the entire process including success entries in the mp_registrationmanager.log, only the error messages.

MP_RegistrationManager.log Error:
MP Reg: Failed to get client(GUID:) public key: 0x80040238

0x80040238 simply means the public key is not found. This error will almost always be reported when a new client is trying to register itself. Because the client is new, it is normal that no public key exists in the ClientKeyData table for that client. It is after that error is reported that the registration happens.

For example, here is a MP_RegistrationManager.log displaying successful registration where verbose agent logging has been enabled on the SCCM site server:

We can see the 0x80040238 error is just informational, as long as a second “Confirmation” of “ClientRegistrationResponse” can be received by the client. Here’s what the client’s ClientIDManagerStartup.log says at the same time:

Reference:How to enable verbose logging for the SCCM Agent.

No comments:

Post a Comment