Jump to content


labesk

Error PXE-E53 - RequestMPKeyInformation: Send() failed

Recommended Posts

Hello,

 

after much searching I can not find a solution, I'd have a little help from you if possible.

 

I can not boot from PXE I get the error message PXE-E53: No bootfilame receive

 

On logs smspxe.log he appears:

 

PXE::CBootImageManager::PurgeOldImages SMSPXE 24/08/2012 10:52:23 4176 (0x1050)

PXE::CNotifyTimer::Init SMSPXE 24/08/2012 10:52:23 4176 (0x1050)

PXE::CNotifyTimer::CancelTimer SMSPXE 24/08/2012 10:52:23 4176 (0x1050)

PXE::CNotifyTimer::RegisterTimeout SMSPXE 24/08/2012 10:52:23 4176 (0x1050)

Set media certificate in transport SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

Set authenticator in transport SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

RequestMPKeyInformation: Send() failed. SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

Failed to get information for MP: http://server.domain.com. 80004005. SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

Set media certificate in transport SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

Set authenticator in transport SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

RequestMPKeyInformation: Send() failed. SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

Failed to get information for MP: http://server.domain.com. 80004005. SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 24/08/2012 10:58:08 4000 (0x0FA0)

PXE Provider failed to process message.

Unknown error (Error: 80004005; Source: Unknown) SMSPXE 24/08/2012 10:58:09 4000 (0x0FA0)

 

SCCM is install on a standalone server

The component status and site, all is green.

the boot images, task sequences, applications, OS and packages are updated on the distribution point

computer is known

the task sequence is deployed for this computer

the management point and the point of distribution are in http mode (no SSL used).

 

If you have ideas, i'm ok for testing.

Thanks.

Share this post


Link to post
Share on other sites

I have a solution !

Maybe it's possible to make that with GUI but i have change 2 register keys for DP :

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP

- HttpPort

- MPPort

In registry, port 80 was save but i have create a custom website (SMSWEB) with another port.

Now it's working.

Share this post


Link to post
Share on other sites

Same problem, but my site is not a custom site and it is running on port 80.

 

This is driving me crazy, I don't care what everyone else is saying but this is not enterprise ready. It is not ready for production environment, it it the most bug-ridden software I have ever seen!

 

 

 

================= PXE Provider loaded. ===================== SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
Machine is running Windows Longhorn. (NTVersion=0X602, ServicePack=0) SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
MAC Ignore List Filename in registry is empty SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
Begin validation of Certificate [Thumbprint 752F483638472B40EDB63F389771B9F390BD45CA] issued to '9d0d15e3-2e15-4f84-8d54-29117f28e0a3' SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
Completed validation of Certificate [Thumbprint 752F483638472B40EDB63F389771B9F390BD45CA] issued to '9d0d15e3-2e15-4f84-8d54-29117f28e0a3' SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
Initializing PXEPerfObject. SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
Client is set to use HTTPS when available. The current state is 480. SMSPXE 3/4/2013 6:43:28 PM 2904 (0x0B58)
RequestMPKeyInformation: Send() failed. SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
Failed to get information for MP: http://DCM-SRV-SCCM-01.ulbsibiu.local. 80004005. SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE Provider failed to initialize MP connection.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
RequestMPKeyInformation: Send() failed. SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
Failed to get information for MP: http://DCM-SRV-SCCM-01.ulbsibiu.local. 80004005. SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005 SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
Adding ULB00002.7 SMSPXE 3/4/2013 6:43:29 PM 2904 (0x0B58)
Adding ULB00005.5 SMSPXE 3/4/2013 6:43:33 PM 2904 (0x0B58)
Found new image ULB00002 SMSPXE 3/4/2013 6:43:39 PM 2904 (0x0B58)
Opening image file D:\RemoteInstall\SMSImages\ULB00002\boot.ULB00002.wim SMSPXE 3/4/2013 6:43:40 PM 2904 (0x0B58)
Found Image file: D:\RemoteInstall\SMSImages\ULB00002\boot.ULB00002.wim
PackageID: ULB00002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 3/4/2013 6:43:40 PM 2904 (0x0B58)
Closing image file D:\RemoteInstall\SMSImages\ULB00002\boot.ULB00002.wim SMSPXE 3/4/2013 6:43:40 PM 2904 (0x0B58)
Found new image ULB00005 SMSPXE 3/4/2013 6:43:46 PM 2904 (0x0B58)
Opening image file D:\RemoteInstall\SMSImages\ULB00005\boot.ULB00005.wim SMSPXE 3/4/2013 6:43:46 PM 2904 (0x0B58)
Found Image file: D:\RemoteInstall\SMSImages\ULB00005\boot.ULB00005.wim
PackageID: ULB00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 3/4/2013 6:43:46 PM 2904 (0x0B58)
Closing image file D:\RemoteInstall\SMSImages\ULB00005\boot.ULB00005.wim SMSPXE 3/4/2013 6:43:46 PM 2904 (0x0B58)
Begin validation of Certificate [Thumbprint 752F483638472B40EDB63F389771B9F390BD45CA] issued to '9d0d15e3-2e15-4f84-8d54-29117f28e0a3' SMSPXE 3/4/2013 6:43:54 PM 2904 (0x0B58)
Completed validation of Certificate [Thumbprint 752F483638472B40EDB63F389771B9F390BD45CA] issued to '9d0d15e3-2e15-4f84-8d54-29117f28e0a3' SMSPXE 3/4/2013 6:43:54 PM 2904 (0x0B58)
PXE Provider finished loading. SMSPXE 3/4/2013 6:43:54 PM 2904 (0x0B58)
and then there are these errors:
failed to copy D:\RemoteInstall\SMSTempBootFiles\ULB00005\WINDOWS\Boot\Fonts\segmono_boot.ttf to D:\RemoteInstall\Boot\Fonts\segmono_boot.ttf SMSPXE 3/1/2013 2:05:45 PM 4140 (0x102C)
InstallBootFilesForImage failed. 0x80070003 SMSPXE 3/1/2013 2:05:45 PM 4140 (0x102C)
Warning: Failed to copy the needed boot binaries from the boot image D:\RemoteInstall\SMSImages\ULB00005\boot.ULB00005.wim.
The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 3/1/2013 2:05:45 PM 4140 (0x102C)
Failed adding image D:\RemoteInstall\SMSImages\ULB00005\boot.ULB00005.wim. Will Retry..
The system cannot find the path specified. (Error: 80070003; Source: Windows) SMSPXE 3/1/2013 2:05:45 PM 4140 (0x102C)
It creates SMSTempBootFiles with Installer service having full access and everyone else with limited access including SYSTEM and Bultin\Administrator accounts. Then It screams that it cannot update these files using the SYSTEM account. Doooh!
If you take ownership of these files and give the system account access to them, IT does the same thing over again locking itself out.
Removing the PXE and WDS, and deleting the remote install folder does not help because it cannot reinstall WDS on its own once removed no matter how many restarts and workarounds your try. Error after error after error.
Thank god i am running a vm and can take snapshots.
It took me two days configuring everything and now I'm stuck on the deployment component for almost a week now.
Ive tried just about everything except a clean install.
If someone has any idea how to solve this please share.
Thank you

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.