SMSPXE.dll Provider Wont Start
I've had a PXE Service Point and WDS installation running for about 2 months now with no issues. From the looks of things last Friday something happened that I haven't been able to identify. Currently the PSP and WDS installation are both running on the same server. Status logs in the CM admin console report the PSP as running and fine. The Application logs on the server itself report that WDS isn't able to start. RPC Server starts without issue. BINLSVC loads and intializes without issue. WDSIMGSRV initializes without issue. WDSMC loads and initializes without issue. WDSPXE fails its load of smspxe.dll with an event ID of 259 and error code of 0x7E. Everything then unloads without issue. I've tried manually starting the WDS but this just reproduces the situation. I've tried pointing WDS to a particular known working DC and GC as suggested in another thread. No help. I'm not against removing the PSP role and WDS and reinstalling but what happens to my existing boot images at this point in time? Will I need to customize new ones?
November 22nd, 2010 2:01pm

have you configured WDS ? if not try it. does it start then ? My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 3:06pm

Configure what in particular? CM has been handling the WDS configuration up to this point.
November 22nd, 2010 3:24pm

start up the wds console, if it's not configured it'll have a yellow exclamation mark, right click and choose configure..go through the wizard once done you should be able to start wds, it's the first thing i'd try My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 3:48pm

My apologies, I wasn't sure if you meant something more than that wizard. Yes, I've gone through that and the Provider is still failing to load. Thanks for responding by the way. Been going over this in my head while looking through any post or blog I can find about the topic. Last week I started the process of removing application packages from a distribution point on this same server that was residing on a smaller volume. I created a new DP share on the same server to the volume that the original DP should have been using to begin with. Once that was installed and functional I copied all of our existing packages for this site to the new share and removing them from the original DP using the Admin console. In the process I noticed that one of our other admins has been placing applications packages into the PXE share. Just like the others, I copied them to the correct location and removed the other. When everything had its new home, application packages, OS images, OS install packages, and finally driver packages I removed the original DP. Just to clarify, this particular site has a total of 5 DP's. There was no issue with the removal of the DP either. I mention this because this was the only system change between last week and now for this site. I don't believe anything that I changed in the above process would have caused this but I realize I could be completely wrong in that opinion.
November 22nd, 2010 4:12pm

Try removing the PSP, WDS, rebooting then installing WDS and then the PSP. All you'll need to do is then redeploy your existing customised boot images to your PXE distribution point Good luck!
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2010 12:33am

Hi, Could you please check SMSPXE.log for any error? Also, you can take the following steps to reinstall WDS and PXE point: 1) Uninstall the PXE Service Point. Monitor the PXESetup.log and make sure it uninstalls correctly. 2) Once the PXE Service Point has successfully uninstalled, uninstall WDS. Once the WDS uninstall is complete, reboot the server. 3) Once the server is rebooted, rename the RemoteInstall folder on the root level of all drives. Make sure to check all drives and to rename all of the RemoteInstall folders. Not all drives may contain a RemoteInstall folder and usually only one of the drives has a RemoteInstall folder. When renaming the folder, it may break an existing share. It is OK to go ahead and break this share. 4) Reinstall WDS. Once WDS is finished reinstalling, reboot the server. . 5) Once the server has restarted, in the ConfigMgr 2007 Admin Console, add the PXE Service Point role. 6) Monitor the PXESetup.log and make sure that installation was successfully. 7) Once the PXE Service Point has been successfully installed (and if necessary, the server restarted), check to make sure that the WDS service has started.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
November 24th, 2010 2:50am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics