Jump to content


edie209

PXE-T04: Access Violation after SP1

Recommended Posts

I have just upgraded my sccm 2012R2 to SP1 and now I am having the following error

 

PXE-T04: Access Violation

 

PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom
Before the upgrade everything was working properly
I have done this as RocketMan has explained in another post

I have never had to reinstall PXE/WDS so correct me if I am wrong when doing this procedure.

  • If you uncheck all from the PXE tab on the DP properties and apply.
  • Wait for some time.....open up the wds console(If it still exists after the last step) and make sure that there is a yellow exclamation mark on the server node of the console. If this is correct then manually remove the wds role via server management.
  • Restart your server.......check the drive and if Remote Install folder exists then manually delete it.

Now this is the way I always set up PXE and have never had any problems.

I manually add the WDS role from server manager first on the site system DP. Do not configure it or do anything in relation to manually configuring it in any way. Restart the server. Now enable the PXE options again on the DP. This will configure WDS for you and should pre-populate the extra directories and extra files automatically as you already have the boot images configured to deploy from PXE server.

 

 

Does anyone have any suggestions?

Share this post


Link to post
Share on other sites

After much reading of many similar problems I have got to this screen

 

win8-repair-efi-bootloader.jpg

 

I have also managed to get smspxe.log working and this is the errors I am getting

 

Prioritizing local MP SCCM Server SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
RequestMPKeyInformation: Send() failed. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
Failed to get information for MP: SCCM Server 80004005. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
reply has no message header marker SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
Prioritizing local MP SCCM Server SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
RequestMPKeyInformation: Send() failed. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
Failed to get information for MP: SCCM Server 80004005. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
reply has no message header marker SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
Failed to send status message (80004005) SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
Failed to send the status message SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
PXE Provider failed to process message.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
00:1A:4B:8C:08:24, 9006B0DA-15AA-11E0-7884-6D990E5F6D29: Not serviced. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
Can anyone help?

 

 

Share this post


Link to post
Share on other sites

Well after trying every possible answer I have found on the web I have given up and taken my server back to an earlier checkpointed dated and now everything is working as it was.

 

I have come to the conclusion that my Management Point was the issue but I was not able to find out for sure.

 

I will upgrade again but not immediately as I have a bit od a backlog SCCM wise.

Share this post


Link to post
Share on other sites

After many problems upgrading my SCCM2012 to R2 SP1. I am finally there.

 

I have deployments working up to the point of installing software or driver packages, this just won't work any more but it did before I started the upgrade process.

 

Could someone give me a pointer as to what I should now be looking for in the logs

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.