Skip to main content

SCCM 2012 - SMSPXE Error

I write this to help all you technical warriors out there who get shitty advice from the Microsoft Forums and other profound idiots about the 0x80092002 error in SCCM - usually to do with PXE booting but can manifest in other ways around DP -> MP communications.

The tricky one about this error is that it happens even if you are only using HTTP communication and not HTTPS/TLS. So to get an error about certificates is somewhat confusing.

What the uneducated masses of the internet will tell you is to re-install the PXE role over an over. This will do nothing.

Then they will tell you to re-install your management point and effectively re-build your entire infrastructure. This will work, but only because it is the nuclear option and will run the step that actually makes a difference as a matter of course.

So, here it is folks. If you have these kinds of errors in your logs:

PXE::MP_InitializeTransport failed; 0x80092002 SMSPXE 22/03/2017 2:45:58 PM 4144 (0x1030)
PXE::MP_ReportStatus failed; 0x80092002 SMSPXE 22/03/2017 2:45:58 PM 4144 (0x1030)
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80092002 SMSPXE 22/03/2017 2:45:58 PM 4144 (0x1030)
All you need to do is re-generate your distribution point certificates in the ConfigMgr console.


To do this, go to your Distribution Point properties, and on the general tab, just change the date by a day.

This will fire off a job and in a few minutes a new cert will be created and you will be right to go.

Remember, the error is generated by the Windows crypto libraries - it's not an SCCM specific error. In this case, error 0x80092002 means CRYPT_E_BAD_ENCODE (https://msdn.microsoft.com/en-us/library/windows/desktop/dd542646(v=vs.85).aspx) which makes for an easy and obvious place to start searching.

Remember kids, if you don't understand how Windows actually works, wildly clicking around won't help - nor will posting dumb and incorrect solutions on the Internet.

Comments

  1. THANK YOU - YOU HAVE SAVED ACCELERATED AGING AND ME GETTING RADIATION POISONING from too much googling!
    Alternatively - a huge thanks from here.

    R

    ReplyDelete
  2. p.s that didnt come out right, lack of sleep im afraid.

    Awesome of you to put this on the internet for battle hardened tech warriors (with the associated scars!)

    Thanks again

    ReplyDelete
  3. Thanks Man. This worked for me. You're correct in saying that there is a lot of wrong information out there about this. It's easier to regenerate a cert than rebuild site system roles.

    The main difference for me was that the error code was more generic and not indicative of a certificate issue like yours. 0x80070490

    **** Manifestation in SMSPXE.log

    **** One off chunk of errors after upgrading to ConfigMgr 1806 from 1802 in SMSPXE.log on the remote Distribution Point:

    Could not load logging configuration for component ccmperf. Using default values. SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    Unable to open Registry Value Software\Microsoft\CCM\HttpsState. Return Code [80070002]. Client HTTPS state is Unknown. SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    RequestMPKeyInformation: Send() failed. SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    Unsuccessful in getting MP key information. 80004005. SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    PXE Provider failed to initialize MP connection.
    Element not found. (Error: 80070490; Source: Windows) SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    RequestMPKeyInformation: Send() failed. SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    Unsuccessful in getting MP key information. 80004005. SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)
    PXE::CPolicyProvider::InitializeMPConnection failed; 0x80070490 SMSPXE 21/08/2018 1:17:32 PM 7720 (0x1E28)


    **** Subsequently, several of these same sets of errors were presenting whenever a client attempted to PXE boot at the remote site:

    PXE::MP_GetList failed; 0x80070490 SMSPXE 22/08/2018 11:29:33 AM 2684 (0x0A7C)
    PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 22/08/2018 11:29:33 AM 2684 (0x0A7C)
    PXE::MP_GetList failed; 0x80070490 SMSPXE 22/08/2018 11:29:33 AM 2684 (0x0A7C)
    PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 22/08/2018 11:29:33 AM 2684 (0x0A7C)
    PXE Provider failed to process message.
    Element not found. (Error: 80070490; Source: Windows) SMSPXE 22/08/2018 11:29:33 AM 2684 (0x0A7C)

    ReplyDelete
  4. Thank you, you made my day after searching for hours removing and adding roles and components over and over... and all the former SCCM gurus on the web had no clue or pointed in the wrong direction.
    Thanks again!!!

    ReplyDelete
  5. We porvide you quality item which you buy on a single click in Auckland New Zealand. Treasurebox nz is one of the most rising store which provide their customers all the items at low rates.

    ReplyDelete

Post a Comment

Popular posts from this blog

Writing to the event log in .NET - the right way

As a DevOper, I spend a lot of time instrumenting code. This involves adding stuff like performance counters, tracing and logging.

One thing that constantly irks me when I go looking for ways or means to improve how I do my logging, is the complete and utter misinformation and misuse of the Windows Event Log. The problem relates to the canonical implementation of logging in .NET, log4net. Look at this method signature:

void Info(object message);
Note the lack of structure, the lack of context. Note the ability for a developer to put absolutely anything into the message object (which will be outputted as a string). When these types of messages are hooked up to an Event Log sink, the result is a generic message, usually in the Application log with a bit of free form text. Fairly useless for anyone to be able to filter and report on. The above style of logging is really more suited towards tracing and debug logging than actual operational logging,

Why you should write operational logs…

Log Reader Error On Adding Subscription

Ever tried to add a new subscription to an existing publication, using the "replication support only" or "initialize from backup" methods and go the following error?
The process could not execute 'sp_MSadd_replcmds' on <'Distribution Server>'. (Source: MSSQLServer, Error number: 1007) Conversion failed when converting the nvarchar value '.' to data type int. (Source: MSSQLServer, Error number: 1007) Batches were not committed to the Distributor. (Source: MSSQL_REPL, Error number: MSSQL_REPL22020) The last step did not log any message! (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
If so, you will know the internet is absolutely useless, filled with worthless workarounds or advice to just "rebuild replication"

Well, if you want an actual solution, just read on. Between SQL 2012 RTM and SQL 2012 SP4 there was a change made to the Distributor proc sp_MSadd_replcmds. This change was to facilitate a change in the format of l…