none
PXE roll Errors - WDS will not start

    שאלה

  • Hi All,

      Ive added the pxe roll to my secondary site but get the following status message warnings. Any ideas on a solution?  I cannot start the WDS service at all it just hangs & errors. Ive read it could be a permissions isue with connecting to the primary site DB but if it was wouldnt my seconday site have loads of errors as more the PXe will require the connection.? The secondar site was working without errors till I added PXE roll.

    The SMS PXE Service Point failed to read and configure the registry keys necessary for this component.Possible cause: The registry information is not available yet.
    Solution: Restart the WDS Service.

    The SMS PXE Service Point failed to Initialize the Database Connection.

    The SMS PXE Service Point failed to initialize the WDS PXE Provider.

    Check Previous Messages for more error information.

    XE Control Manager detected PXE service point is not responding to PXE requests.  The error is 16389.

    Possible cause: PXE service point is not started or not responding.
    Solution: Manually restart the PXE service point.

    Possible cause: WDS service is not responding.
    Solution: Manually restart the WDS service.

    יום ראשון 29 אוגוסט 2010 10:03

כל התגובות

  • What happens if you set the WDS service to startup type "manual", reboot the server, wait until every service is up and running? Would WDS start then manually?
    יום ראשון 29 אוגוסט 2010 11:52
    מנחה דיון
  • Hi Torsten,

      Ive set to manual & tried starting the serivces 5 mins after the server has been rebooted but get 'Service-Specific error 16389'.

    יום ראשון 29 אוגוסט 2010 18:03
  • Anything in the eventlog? Or the WDS logs (there's a kb article that talks about enabling verbose logging).
    יום ראשון 29 אוגוסט 2010 19:23
    מנחה דיון
  • Hi Torsten,

      Yes, there is errors in event viewer on the server. See below.

    Were I have installed PXe roll several times. ive got 6 PXE certificates with 5 blocked & 1 unblocked. The working cert is avalible till 2011.

     

    Event ID 265

    An error occurred while trying to initialize provider SMSPXE. Since the provider  is marked as critical, the Windows Deployment Services server will be shutdown.
     
     Error Information: 0x4005

     

    Event ID 513

    An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown.
     
     Error Information: 0x4005

     

    Event ID 257

    An error occurred while trying to start the Windows Deployment Services server.
     
     Error Information: 0x4005

     

    Event ID 258

    An error occurred while trying to initialize the Windows Deployment Services image server.
     
     Error Information: 0xC1030104

     

    Event ID 261

    An error occurred while trying to initialize provider SMSPXE loaded from D:\SMS_CCM\x64\smspxe.dll. If the provider is marked as critical the Windows Deployment Services server will be  shutdown.
     
     Error Information: 0x4005

    PXE MSI.log Not sure if these bits where on a previous install

    MSI (s) (C0:DC) [15:34:00:800]: Windows Installer installed the product. Product Name: SMS PXE Service Point. Product Version: 4.00.6487.2000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

    Property(S): InstallErrorDialog_Title = Setup Aborted

    Property(S): InstallErrorDialog_SubTitle = Setup failed

    Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue.

    Property(S): ErrorDialog = ErrorDialog

    [15:32:42] WARNING: Failed to remove configuration for performance application SMSPXE (80070057)
    [15:32:42] WARNING: Failed to remove PerfLib entries for performance application SMSPXE (2)

    [15:32:40] WARNING: Upgrade Code [{C4EC0F63-B88C-43BA-A35D-2E9B4B31CAAD}] is not a recognized upgrade code

    PXEcontrol.log

    Pxe test request failed, error code is 16389.

    PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'.

     

     

    יום שני 30 אוגוסט 2010 22:20
  • Ive got this SCCm Secondary server on a 2008 R2 VM which is on the same physical box as the DC which has DNS/DHCP but this is on its own VM.

    do I need to configure the port 67 thing even though they are two different servers but on the same box?

     

    WDS logging wont work till WDS is configured. PXE roll is meant to configure it.

     

    Server State:
         OS version: 6.1
         WDS operational mode: Not Configured


    An error occurred while trying to execute the command.
    Error Code: 0xC1030136
    Error Description: Windows Deployment Services or Remote Installation Services i
    s not configured on the server. If the server is running an operating system lat
    er than Windows Server 2003, this feature is only available after configuring Wi
    ndows Deployment Services.

    יום שני 30 אוגוסט 2010 22:30
  • Hi,

    As the WDS service is not starting, please take the following steps:

    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. If prompted for media or source file location, make sure the source files that are being pointed to are at the same service pack level that Windows Server 2003 is at. If they are not at the same service pack level, the installation will succeed but WDS will not be able to be properly setup or configured.

    5) Once the server has restarted, in the SCCM Admin Console, add the PXE Service Point role.

    6) Monitor the PXESetup.log and make sure that installation was successfully.


    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.
    יום שלישי 31 אוגוסט 2010 07:39
  • Uninstall PXE roll reports ok but hangs on removing PXE registry.

    <08-31-2010 10:20:09> ====================================================================
    <08-31-2010 10:20:09> SMSPXE Setup Started....
    <08-31-2010 10:20:09> Parameters: D:\SCCM\bin\i386\ROLESE~1.EXE /deinstall /siteserver:WEL-IMG-01 SMSPXE
    <08-31-2010 10:20:09> Deinstalling the SMSPXE
    <08-31-2010 10:20:09> Enabling MSI logging.  pxe.msi will log to D:\SCCM\logs\pxeMSI.log
    <08-31-2010 10:20:09> Deinstalling SMSPXE, with product code {C63C1FBD-C9C8-469D-8ADE-12387FB5EA75}
    <08-31-2010 10:20:17> SMSPXE deinstall exited with return code: 0
    <08-31-2010 10:20:17> Deinstallation was successful.
    <08-31-2010 10:20:17> Removing PXE Registry.

     

    ive also got 6 PXE certificates remaining for this site. One adds each time I reinstall this PXE roll but none remove when I uninstall it. Can I remove these manually?.
    יום שלישי 31 אוגוסט 2010 09:24
  • Ive uninstalled PXE roll, rebooted uninstalled WDS & Rebooted.

    Installed WDS, reboot, Install PXE roll.

    PXesetup.log reports below but I still get the same errors as above in PXEMSI.log

     

    <08-31-2010 15:27:35> ====================================================================
    <08-31-2010 15:27:35> SMSPXE Setup Started....
    <08-31-2010 15:27:35> Parameters: D:\SCCM\bin\i386\ROLESE~1.EXE /install /siteserver:WEL-IMG-01 SMSPXE
    <08-31-2010 15:27:35> Installing Pre Reqs for SMSPXE
    <08-31-2010 15:27:35>         ======== Installing Pre Reqs for Role SMSPXE ========
    <08-31-2010 15:27:35> Found 1 Pre Reqs for Role SMSPXE
    <08-31-2010 15:27:35> Pre Req MSXML60 found.
    <08-31-2010 15:27:35> No versions of MSXML60 are installed.  Would install new MSXML60.
    <08-31-2010 15:27:35> Enabling MSI logging.  msxml6_x64.msi will log to D:\SCCM\logs\msxml6_x64MSI.log
    <08-31-2010 15:27:35> Installing D:\SCCM\bin\x64\00000409\msxml6_x64.msi
    <08-31-2010 15:27:37> msxml6_x64.msi exited with return code: 0
    <08-31-2010 15:27:37> msxml6_x64.msi Installation was successful.
    <08-31-2010 15:27:37>         ======== Completed Installion of Pre Reqs for Role SMSPXE ========
    <08-31-2010 15:27:37> Installing the SMSPXE
    <08-31-2010 15:27:37> Machine is running Windows 2003 SP1 or later. (NTVersion=0X601, ServicePack=0)
    <08-31-2010 15:27:37> WDS Service is installed.
    <08-31-2010 15:27:37> No versions of SMSPXE are installed.  Installing new SMSPXE.
    <08-31-2010 15:27:37> Enabling MSI logging.  pxe.msi will log to D:\SCCM\logs\pxeMSI.log
    <08-31-2010 15:27:37> Installing D:\SCCM\bin\i386\pxe.msi CCMINSTALLDIR="D:\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
    <08-31-2010 15:29:01> pxe.msi exited with return code: 0
    <08-31-2010 15:29:01> Installation was successful.

    יום שלישי 31 אוגוסט 2010 14:40
  • Hi,

    Take a look at this thread which had the similar error messages:

    http://social.technet.microsoft.com/forums/en-US/configmgrosd/thread/a5cb1bfc-4416-41ef-88af-27ee2225bf01/


    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.
    יום רביעי 01 ספטמבר 2010 07:19
  • Ive reinstalled the server, Setup Webdav & AD permissions, reinstalled SCCM, installed WDS, installed PXe roll & same errors.

    Im presuming the secondary site should be able to connect to the primary site SQL Database without me having to set any permissions on it. I have heard though later SQL versions you have to add accounts to SQL. Could this possibly be my problem?

    Secondary sites work fine its only when I add PXE rol it complains about not being able to set SQL reg keys Cannot connect to DB.

    יום חמישי 02 ספטמבר 2010 21:27
  • Yes, I know this is an old post, trying to clean them up. Did you figure this out yet? What was the solution?

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    יום חמישי 24 אוגוסט 2017 12:45
    מנחה דיון
  • I did resolve it but cant recall how.
    יום רביעי 09 מאי 2018 22:43