none
WDS stops when PXE service point is installed

    Question

  • on my child site i've set up the WDS role and it's running, but when i install the pxe service point it stops the WDS.

    I've already tried all different combinations:

    leaving the WDS unconfigured reboot pxe SP install reboot, thrown some bootimages on it
    configuring the WDS reboot pxe SP install reboot, thrown some bootimages on it

    the sccm serviceaccount and the primary computer account are admin on the child server and SQL db

    this is the PXESetup.log

    <03-30-2012 10:13:53>         ======== Completed Installion of Pre Reqs for Role SMSPXE ========
    <03-30-2012 10:13:53> Installing the SMSPXE
    <03-30-2012 10:13:53> Machine is running Windows 2003 SP1 or later. (NTVersion=0X601, ServicePack=1)
    <03-30-2012 10:13:53> WDS Service is installed.
    <03-30-2012 10:13:53> No versions of SMSPXE are installed.  Installing new SMSPXE.
    <03-30-2012 10:13:53> Enabling MSI logging.  pxe.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\pxeMSI.log
    <03-30-2012 10:13:53> Installing D:\Program Files\Microsoft Configuration Manager\bin\i386\pxe.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
    <03-30-2012 10:14:00> pxe.msi exited with return code: 0
    <03-30-2012 10:14:00> Installation was successful.

    this is the pxecontrol.log

    SMS_EXECUTIVE started SMS_PXE_SERVICE_POINT as thread ID 5168 (0x1430). SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 2592 (0x0A20)
    ******************************************************************************** SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    SMS_PXE_SERVICE_POINT received START notification. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    ReadPXEDwordSettings(): RegQueryValueExW() failed for PXEHealthCheckIntervalInSeconds; error = 2. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    ReadPXEDwordSettings(): RegQueryValueExW() failed for PXEHealthCheckTimeoutInSeconds; error = 2. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    ReadPXEDwordSettings(): RegQueryValueExW() failed for PXEHealthCheckStatusMessageIntervalInSeconds; error = 2. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    PXEStart(): CreateThread() succeeded with id 0xa2c. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    ------ RegisterForNotification(): Registering again! ------- SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    PXEStart(): Registered for Notifications. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    Successfully Registered for IP Address Change notifications. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    PXEStart(): RegisterForIPAddressChangeNotification() returned 0x0 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    SMS_PXE_SERVICE_POINT successfully STARTED. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    ******************************************************************************** SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 5168 (0x1430)
    Configuration and Availability Monitor thread started. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 2604 (0x0A2C)
    Initialized 'SMS Server Availability' performance instance => SMS PXE Service Point. SMS_PXE_SERVICE_POINT 30/03/2012 10:14:02 AM 2604 (0x0A2C)
    adding address to server list 169.254.254.86 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:32 AM 2604 (0x0A2C)
    adding address to server list 10.22.01.05 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:32 AM 2604 (0x0A2C)
    adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:32 AM 2604 (0x0A2C)
    Sending availiability packet to: 169.254.254.86 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:32 AM 2604 (0x0A2C)
    Sent 274 bytes to 169.254.254.086:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:32 AM 2604 (0x0A2C)
    Error receiving replies SMS_PXE_SERVICE_POINT 30/03/2012 10:14:47 AM 2604 (0x0A2C)
    Sending availiability packet to: 10.22.1.5 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:47 AM 2604 (0x0A2C)
    Sent 274 bytes to 010.022.001.005:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:14:47 AM 2604 (0x0A2C)
    Error receiving replies SMS_PXE_SERVICE_POINT 30/03/2012 10:15:02 AM 2604 (0x0A2C)
    Availability check in progress. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:02 AM 2604 (0x0A2C)
    Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:02 AM 2604 (0x0A2C)
    Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:02 AM 2604 (0x0A2C)
    Error receiving replies SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    STATMSG: ID=6319 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PXE_SERVICE_POINT" SYS=S-0161 SITE=LUX PID=2204 TID=2604 GMTDATE=Fri Mar 30 08:15:17.540 2012 ISTR0="16389" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    Initialization still in progress. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    Received a registry change notification. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    ------ RegisterForNotification(): Registering again! ------- SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    Successfully handled registry changes. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    Received a registry change notification. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    ------ RegisterForNotification(): Registering again! ------- SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    Successfully handled registry changes. SMS_PXE_SERVICE_POINT 30/03/2012 10:15:17 AM 2604 (0x0A2C)
    adding address to server list 169.254.254.86 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:32 AM 2604 (0x0A2C)
    adding address to server list 10.22.01.05 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:32 AM 2604 (0x0A2C)
    adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:32 AM 2604 (0x0A2C)
    Sending availiability packet to: 169.254.254.86 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:32 AM 2604 (0x0A2C)
    Sent 274 bytes to 169.254.254.086:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:32 AM 2604 (0x0A2C)
    Error receiving replies SMS_PXE_SERVICE_POINT 30/03/2012 10:15:47 AM 2604 (0x0A2C)
    Sending availiability packet to: 10.22.1.5 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:47 AM 2604 (0x0A2C)
    Sent 274 bytes to 010.022.001.005:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:47 AM 2604 (0x0A2C)
    Error receiving replies SMS_PXE_SERVICE_POINT 30/03/2012 10:16:02 AM 2604 (0x0A2C)
    Availability check in progress. SMS_PXE_SERVICE_POINT 30/03/2012 10:16:02 AM 2604 (0x0A2C)
    Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 30/03/2012 10:16:02 AM 2604 (0x0A2C)
    Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:16:02 AM 2604 (0x0A2C)
    Error receiving replies SMS_PXE_SERVICE_POINT 30/03/2012 10:16:17 AM 2604 (0x0A2C)
    Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 30/03/2012 10:16:17 AM 2604 (0x0A2C)
    PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 30/03/2012 10:16:17 AM 2604 (0x0A2C)
    Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 30/03/2012 10:16:17 AM 2604 (0x0A2C)
    Initialization still in progress. SMS_PXE_SERVICE_POINT 30/03/2012 10:16:17 AM 2604 (0x0A2C)

    I've been searching for a solution for over 2 weeks now, reading every single thread about this, but nothing worked.
    the child server is running 2008r2


    when i remove the PXE SP the WDS starts again
    • Edited by royjacobs Friday, March 30, 2012 8:36 AM
    Friday, March 30, 2012 8:35 AM

Answers

  • found it: SPN's were not registered (correctly?)

    setspn -A MSSQLSvc /hostname.domain:1433 accountname

    setspn -A MSSQLSvc /hostname:1433 accountname

    

    • Edited by royjacobs Friday, April 06, 2012 10:05 AM
    • Marked as answer by royjacobs Friday, April 06, 2012 10:05 AM
    Friday, April 06, 2012 10:05 AM

All replies

  • maybe it's your DNS, seems it's sending messages to localhost and that won't go to far..

    Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 30/03/2012 10:16:02 AM 2604 (0x0A2C)
    Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:16:02 AM 2604 (0x0A2C)



    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    Friday, March 30, 2012 8:57 AM
  • it tries to send to all it's IP's, including the correct 10.22.01.05 and that is giving the same error:

    Sending availiability packet to: 10.22.1.5 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:47 AM 2604 (0x0A2C)
    Sent 274 bytes to 010.022.001.005:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:47 AM 2604 (0x0A2C)
    Error receiving replies SMS_PXE_SERVICE_POINT 30/03/2012 10:16:02 AM 2604 (0x0A2C)

    Friday, March 30, 2012 8:59 AM
  • firewall issue perhaps ?

    Sent 274 bytes to 010.022.001.005:4011 SMS_PXE_SERVICE_POINT 30/03/2012 10:15:47 AM 2604 (0x0A2C)



    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    Friday, March 30, 2012 11:44 AM
  • all traffic has been allowed on the firewall in both directions and the local firewalls have been disabled.

    This traffic doesn't even leave the machine itself as it tries to connect to it's own IP.

    Friday, March 30, 2012 2:41 PM
  • smspxe.log gives:

    CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 SmsPXE 30/03/2012 10:13:59 4288 (0x10C0)
    ======================================= SmsPXE 30/03/2012 10:13:59 4288 (0x10C0)

    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : PRIMARYSERVER
    SQL Database Name   : SMS_XXX
    Integrated Auth     : True

    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : Init()
    MPDB Method HRESULT : 0x80004005
    Error Description   : Cannot generate SSPI context
    OLEDB IID           : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server

    MPDB ERROR - INFORMATION FROM DRIVER
    null SmsPXE 30/03/2012 10:13:59 4288 (0x10C0)
    =======================================
     SmsPXE 30/03/2012 10:13:59 4288 (0x10C0)
    MP: RaiseDBFailureStatusMessage failed to open registry 2 SmsPXE 30/03/2012 10:13:59 4288 (0x10C0)
    Failed to read PXE DB settings.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 30/03/2012 10:13:59 4288 (0x10C0)
    PXE Provider failed to read configuration parameters.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 30/03/2012 10:13:59 4288 (0x10C0)

    PRIMARYSERVER = my primary site server where the SQL also resides
    SMS_XXX = XXX = primary site code

    the child site server's computer account and the sccm-service account are members of smsdbrole_PSP

    Monday, April 02, 2012 3:22 PM
  • i spent few days troubleshooting PXE service point. I think it is not perfect part of SCCM but i end up with this step-by-step which start work for me. May be this will helps to you too.

    1, install RDC
    2, turn off Firewall
    3, disbale UAC => restart
    4, put group sccm servers in local administrators group
    5, remove secure key exchange from upper site
    6, install secondary site
    7, put sccm server group to local groups: site to site,site systems to site.
    8, remove secury key exchange on New site
    9, install DHCP,WDS > restart
    10, Apply SP2 htfx and SCCM 2007 R3 patch
    11, install PXE Service point


    Jaromir

    Tuesday, April 03, 2012 12:17 PM
  • the secure key exchange has always been enabled, also on my other child site.

    it seems to be something with the DB connection

    Wednesday, April 04, 2012 6:25 AM
  • found it: SPN's were not registered (correctly?)

    setspn -A MSSQLSvc /hostname.domain:1433 accountname

    setspn -A MSSQLSvc /hostname:1433 accountname

    

    • Edited by royjacobs Friday, April 06, 2012 10:05 AM
    • Marked as answer by royjacobs Friday, April 06, 2012 10:05 AM
    Friday, April 06, 2012 10:05 AM