PXE - 0x80004005

[squmph]

Hi all,

 

We have an installation of CM2012 SP1 in our forest root, with secondary sites in a couple of child domains at different sites. This is all working fine (including PXE).

 

We are trying to get a new secondary site working, again at a different site, but on the same domain as an existing secondary site (so we know that it works). Installation goes fine & installation of PXE goes fine too, but when the PXE provider starts and/or a client requests PXE, the smspxe log displays the following:

 

reply has no message header marker SMSPXE 17/10/2013 09:29:32 5272 (0x1498)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 17/10/2013 09:29:32 5272 (0x1498)
reply has no message header marker SMSPXE 17/10/2013 09:29:32 5272 (0x1498)
Failed to send status message (80004005) SMSPXE 17/10/2013 09:29:32 5272 (0x1498)
Failed to send the status message SMSPXE 17/10/2013 09:29:32 5272 (0x1498)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 17/10/2013 09:29:32 5272 (0x1498)
PXE Provider failed to process message.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 17/10/2013 09:29:32 5272 (0x1498)
00:15:5D:91:42:27, F44C341E-17F1-43D9-B774-F9122D697F00: Not serviced. SMSPXE 17/10/2013 09:29:32 5272 (0x1498)

It repeats the above every time a client sends a request. The client eventually times out with PXE-E53.

 

So what have we done to try and fix this:

1) confirmed that the MP is OK (MPControl says fine, and checked MPcert/MPlist)

2) removed the PXE service point and re-added, including reboots, deletion of remoteinstall folder & temp folder

3) rebuilt the server twice - once from template and once from CD

 

At this point I am completely stuck for ideas. Google finds a few errors like this, but most are down to certificate issues and have lines mentioning this - we are using basic HTTP on the MP and DP.

 

Help!

Rob

[squmph]

Solved myself.

Just incase anyone else hits this:

 

Looked at the MP_Framework log on the sec site (other MP logs seemed OK), and every time PXE failed it reported this:

 

CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E09 MpFramework 17/10/2013 10:04:59 2984 (0x0BA8)
======================================= MpFramework 17/10/2013 10:04:59 2984 (0x0BA8)
MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name : (MySiteServer)\CONFIGMGRSEC
SQL Database Name : CM_(Site)
Integrated Auth : True
MPDB ERROR - EXTENDED INFORMATION
MPDB Method : ExecuteSP()
MPDB Method HRESULT : 0x80040E09
Error Description : The EXECUTE permission was denied on the object 'sp_GetPublicKeyForSMSID', database 'CM_(primarysite)', schema 'dbo'.
OLEDB IID : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
ProgID : Microsoft SQL Server Native Client 11.0
MPDB ERROR - INFORMATION FROM DRIVER
SQL Server Name : (primarySQL)\SCCM
Stored Procedure : sp_GetPublicKeyForSMSID
Native Error no. : 229
Error State : 5
Class (Severity) : 14
Line number in SP : 1
MpFramework 17/10/2013 10:04:59 2984 (0x0BA8)
=======================================
MpFramework 17/10/2013 10:04:59 2984 (0x0BA8)
CMpDatabase::GetClientPublicKeyEx(ClientID='23d0e153-9c60-417a-8184-b1fcb1a79caf') failed (0x87d00242). MpFramework 17/10/2013 10:04:59 2984 (0x0BA8)

 

After much faffing about, I found the referenced SP on the primary site SQL server. The SQL login for the computer account looked present and correct, and the execute permissions made sense.

As I had rebuild the server, there was a possibility that the SQL login was referencing an old SID... So I:

 

1) Deleted the SQL login for the secondary site server (on the primary site SQL server)

2) Deleted the login from the primary DB for good measure

3) recreated the login, must be done by script:

"Create login [domain\secsiteserver$] from windows;"

4) re-mapped the login to the primary site DB, granting role "smsdbrole_MP"

5) rebooted the secondary site server.

 

This worked immediately...

 

Hope that helps someone

 

Rob

[danny206]

Rob - Thank you SO much. I have been on the phone with MS for 2 days dealing with this issues. I rebuilt the secondary site, they insisted on rebuilding the secondary site and after my frustration level hit it's top, i stumbled here. Your fix, 5 minutes later, BOOM! Cheer's and thanks for contributing to the community!