• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 421
  • Last Modified:

SCCM PXE not working Event IDs 12002, 12012, 12022, 12042, 12052

I installed the Admin Studio 10 (AS) that comes complementary with SCCM onto our SCCM 2012 server (2008 Ent. R2), (NOT a brilliant idea) and now I am unable to PXE boot our workstations to the SCCM server.  The PXE boot was working fine prior to my installing the AS so I'm pretty confident the AS install is the cause of the problem.

I'm receiving Event IDs 12002 (The Reporting Web Service is not working.), 12012 (The API Remoting Web Service is not working.), 12022 (The Client Web Service is not working., 12042 (The SimpleAuth Web Service is not working.), and 12052 (The DSS Authentication Web Service is not working.) when I reboot the SCCM server.

When I attempt to PXE boot a workstation and get to the part that states "Press F12 for the Network service boot, I get the following:
Architecture x64
Contacting Server: [server ip address here]
TFTP Download: boot\x64\pxeboot.n12

After that a second screen appears Titled Windows Boot Manager (Server IP: [server address]) with the following text:
Windows failed to start.  A recent hardware or software change might be the cause.  To fix the problem:
1.Insert your Windows installation disc and restart your computer
2. Choose your language settings and then click "Next".
3. Click "Repair you computer"

If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

File: \Boot\BCD
Status: 0xc0000098
Info: The Windows boot configuration data file does not contain a valid OS entry.

I'm not sure what other information may be helpful in trouble shooting this problem.
0
RichfieldTech
Asked:
RichfieldTech
  • 4
  • 3
  • 2
  • +3
1 Solution
 
Nagendra Pratap SinghCommented:
It seems that there is corruption of some key files.

Please remove the OS and re add it.

This may help

http://www.windows-noob.com/forums/index.php?/topic/667-deploy-windows-7/
0
 
vivigattCommented:
You get the error because after your client has successfully downloaded and executed pxboot.n12, it can't actually connect to the image server, can't mount a disk image etc.
At this stage, I would not suspect any issue with your images. I think it's more with your infrastructure.

What to do? well :
Uninstall AS, see if this is any better.
If it is, then investigate interactions between AS and SCCM, in particular why it seems to prevent key services to run OK
0
 
RichfieldTechAuthor Commented:
Uninstalling AS had zero impact.  I should have mentioned this in my original post.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
vivigattCommented:
Actually, I may have been wrong. Your client might get some image, but that are not the correct ones. This error, for instance, would happen if the client is x86 only and tries to boot off an x64 image.

Can you confirm that the x64 clients will get an x64 image but, more important, that the x86 clients will NOT get an x64 image? Double check within SCCM/WDS administration and configmgr

Useful link:
http://social.technet.microsoft.com/Forums/eu/configmgrgeneral/thread/1b009231-ab0d-40d6-811f-a7228591b1a0
0
 
RichfieldTechAuthor Commented:
Imaging is not working at all.  We've only been testing this on x64 machines and it was working as intended until I added the AS.  Now the PXE boot simply will not complete the boot process.  Therefore, the client cannot receive any image (right or wrong).
0
 
vivigattCommented:
Technically, the PXE boot completes as soon as the PXE client (PXE rom) loaded the PXE NBP (network boot program) and executed it.
Now, I get your point: your PXE boot program (pxeboot.n12) was executed, began its work and could not complete it.
If it wasn't able to connect to the server or to get an image, the error should be different...
Can you check what image(s) has been assigned to a specific client?

Since you have some Events, you may want to fix the cause for them. Could it be that AS changed some access rights or authorizations?

Check this:
I was getting a bunch of errors: 12002, 12032, 12022, 12042, 12052 for WSUS 3.0 SP1. I fixed this by enabling the iusr_serverx account in AD that was being used for anonymous authentication by this is IIS. (For added security, change the password then you have to change in IIS, Directory Security, Authentication & access control, as well).

Also, another possible resolution - remove the GUESTS account from the USER RIGHTS
ASSIGNMENT:DENY ACCESS TO THIS COMPUTER FROM THE NETWORK.

I found it here:
http://eventid.net/display-eventid-12002-source-Windows%20Server%20Update%20Services-eventno-9383-phase-1.htm
0
 
RichfieldTechAuthor Commented:
I did read this post and it did not specifically apply to our situation.  As far as images assigned, I had three different tasks available to this machine.  As mentioned, they were working as intended when tested in previous days.

Thanks
0
 
Mike TLeading EngineerCommented:
Hi,

It sounds like the PXE files themselves are corrupt to me. It's the PXE boot config file that's crashing out, not the OS. If you never even see the white PXE bar along the bottom of the screen, go straight to RemoteInstall, do not pass Go....

Check Henk's blog on the files:

PXE files explained

Unless you have good copy of these files somewhere, the easiest way to make fresh ones is remove the PXE role and add it again. I've managed to copy the contents of RemoteInstall \boot\x86 from another server and it worked fine, recently.

Mike
0
 
technicalexpertsCommented:
Admin Studio installation changes IIS Default Application Pool settings to 32 bit and that will cause serious problems with all SCCM services on that server. Change that settings back to default (64 bit), reboot server and everything works fine!
Link to change settings for Applications Pools defaults:
http://www.iis.net/configreference/system.applicationhost/applicationpools/applicationpooldefaults
0
 
RichfieldTechAuthor Commented:
Since we had very little in the way of apps, images, driver packages, collections, etc., we decided to wipe the server and start over.  An extreme measure, but in the absence of a timely solution, this was our most logical path.

Thanks for your replies.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for RichfieldTech's comment #a38885450

for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
 
Nagendra Pratap SinghCommented:
I had suggested this

Please remove the OS and re add it.

Op did this

we decided to wipe the server and start over.

I should get the points.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 3
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now