none
Multiple Services failing. WDS, SCCM PXE

    Question

  • We have installed SCCM SP1 on Windows Server 2008 SP1. Detabase for site is located on SQL 2008. Both Windows server and SQL server are virtual Server. 

    On the Windows Server that hosts SCCM we have also installed WDS, WAIK, IIS with ASP.NET. This Server has ConfigMgr Component server, destribution point, management point, PXE service point, server locater point, site server and site system roles assigned.

    I am going thru my event log and we are getting following errors:
    --------------------------
    Log Name:      Application
    Source:        SMS Server
    Date:          4/2/2009 9:09:25 AM
    Event ID:      6319
    Task Category: SMS_PXE_SERVICE_POINT
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVERNAME.DOMAIN.ORG
    Description:
    On 4/2/2009 9:09:25 AM, component SMS_PXE_SERVICE_POINT on computer SERVERNAME reported:  PXE 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.


    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SMS Server" />
        <EventID Qualifiers="49152">6319</EventID>
        <Level>2</Level>
        <Task>68</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-04-02T15:09:25.000Z" />
        <EventRecordID>1973</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVERNAME.DOMAIN.ORG</Computer>
        <Security />
      </System>
      <EventData>
        <Data>16389</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>On 4/2/2009 9:09:25 AM, component SMS_PXE_SERVICE_POINT on computer SERVERNAME reported:  </Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    --------------------------
    Log Name:      Application
    Source:        WDSServer
    Date:          4/2/2009 9:08:20 AM
    Event ID:      257
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVERNAME.DOMAIN.ORG
    Description:
    An error occurred while trying to start the Windows Deployment Services server. 
     
     Error Information: 0x36B1 

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="WDSServer" />
        <EventID Qualifiers="49409">257</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-04-02T15:08:20.000Z" />
        <EventRecordID>1970</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVERNAME.DOMAIN.ORG</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0x36B1</Data>
      </EventData>
    </Event>
    --------------------------
    Log Name:      Application
    Source:        WDSServer
    Date:          4/2/2009 9:08:19 AM
    Event ID:      513
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVERNAME.DOMAIN.ORG
    Description:
    An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown.
     
     Error Information: 0x36B1 

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="WDSServer" />
        <EventID Qualifiers="49409">513</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-04-02T15:08:19.000Z" />
        <EventRecordID>1963</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVERNAME.DOMAIN.ORG</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WDSPXE</Data>
        <Data>C:\Windows\system32\wdspxe.dll</Data>
        <Data>0x36B1</Data>
      </EventData>
    </Event>
    --------------------------
    Log Name:      Application
    Source:        WDSPXE
    Date:          4/2/2009 9:08:19 AM
    Event ID:      265
    Task Category: WDSPXE
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVERNAME.DOMAIN.ORG
    Description:
    An error occurred while trying to initialize provider Microsoft.BDD.PXEFilter. Since the provider  is marked as critical, the Windows Deployment Services server will be shutdown. 
     
     Error Information: 0x36B1 

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="WDSPXE" />
        <EventID Qualifiers="49415">265</EventID>
        <Level>2</Level>
        <Task>7</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-04-02T15:08:19.000Z" />
        <EventRecordID>1962</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVERNAME.DOMAIN.ORG</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft.BDD.PXEFilter</Data>
        <Data>0x36B1</Data>
      </EventData>
    </Event>
    --------------------------
    Log Name:      Application
    Source:        WDSPXE
    Date:          4/2/2009 9:08:19 AM
    Event ID:      259
    Task Category: WDSPXE
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVERNAME.DOMAIN.ORG
    Description:
    An error occurred while trying to load the module from C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.PXEFilter.dll for provider Microsoft.BDD.PXEFilter. If  the provider is marked as critical, the Windows Deployment Services server will  be shutdown. 
     
     Error Information: 0x36B1 

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="WDSPXE" />
        <EventID Qualifiers="49415">259</EventID>
        <Level>2</Level>
        <Task>7</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-04-02T15:08:19.000Z" />
        <EventRecordID>1961</EventRecordID>
        <Channel>Application</Channel>
        <Computer></Computer>
        <Security />
      </System>
      <EventData>
        <Data>C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.PXEFilter.dll</Data>
        <Data>Microsoft.BDD.PXEFilter</Data>
        <Data>0x36B1</Data>
      </EventData>
    </Event>
    ------------------------------
    Log Name:      Application
    Source:        SideBySide
    Date:          4/2/2009 9:08:19 AM
    Event ID:      33
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVERNAME.DOMAIN.ORG
    Description:
    Activation context generation failed for "C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.PXEFilter.dll". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SideBySide" />
        <EventID Qualifiers="49409">33</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-04-02T15:08:19.000Z" />
        <EventRecordID>1960</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVERNAME.DOMAIN.ORG</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.PXEFilter.dll</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Pathik Shah
    Thursday, April 02, 2009 4:01 PM

Answers

  • I dont think this has anything to do with the PXE Service point. The only reason why the service point is not starting is due to Microsoft.BDD.PXEFilter Provider no loading properly. On the WDS server, try setting HKLM\SYSTEM\CCS\Services\WDSServer\Providers\Microsoft.BDD.PXEFilter\IsCritical Dword Value to 0, then restart WDSServer. If WDS starts successfully then there is a problem with your version of MDT. Try upgrading to latest version of MDT. I am experiencing this problem on Server 2008 R2, seems the Microsoft.BDD.PXEFilter is not working properly on 2008r2 yet :-(. If you are on the latest version of MDT make sure you have edited the VBScript correctly.
    Tuesday, May 05, 2009 8:25 AM

All replies

  • 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.

    Have you already checked what ConfigMgr suggested? Is WDS installed? What's in pxecontrol.log?
    Thursday, April 02, 2009 5:34 PM
  • Hi, I'm having the same problem. The PXEControl.log has this in it:

    adding address to server list 192.168.121.185 SMS_PXE_SERVICE_POINT 23/04/2009 11:13:46 3484 (0x0D9C)
    adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 23/04/2009 11:13:46 3484 (0x0D9C)
    Sending availiability packet to: 192.168.121.185 SMS_PXE_SERVICE_POINT 23/04/2009 11:13:46 3484 (0x0D9C)
    Sent 274 bytes to 192.168.121.185:4011 SMS_PXE_SERVICE_POINT 23/04/2009 11:13:46 3484 (0x0D9C)
    Recieved Packet 02DD4238 does not have associated request. SMS_PXE_SERVICE_POINT 23/04/2009 11:13:46 3484 (0x0D9C)
    Error validating replies SMS_PXE_SERVICE_POINT 23/04/2009 11:13:46 3484 (0x0D9C)
    Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 23/04/2009 11:13:47 3484 (0x0D9C)
    Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 23/04/2009 11:13:47 3484 (0x0D9C)
    Error receiving replies SMS_PXE_SERVICE_POINT 23/04/2009 11:14:02 3484 (0x0D9C)
    Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 23/04/2009 11:14:02 3484 (0x0D9C)
    PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 23/04/2009 11:14:02 3484 (0x0D9C)
    Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 23/04/2009 11:14:02 3484 (0x0D9C)
    Initialization still in progress. SMS_PXE_SERVICE_POINT 23/04/2009 11:14:02 3484 (0x0D9C)

    It just seems to cycle through this.

    WDS is installed and OS deployment was working until yesterday. I was troubleshooting the 12030 IIS errors with the Management Point and I re-installed IIS, MP and SP2 as the w3core.dll file had a version mis-match. Could this be causing a problem with the PXE?

    I'm working at a charity at the moment who won't spend money on PSS and I didn't build the original SCCM. AND - the build wasn't documented at all :-(

    I was considering a total re-build but please tell me it won't come to that :-)

    Any help would be massively appreciated!

    Cheers,
    Matt
    Thursday, April 23, 2009 10:18 AM
  • Is the WDS service up and running?
    You can try to remove the PXE service point role, remove WDS, reboot, install (but don't configure) WDS, add PXE service point, re-add the boot images again.
    Thursday, April 23, 2009 10:22 AM
  • Thanks for the quick response Torsten!

    The WDS service isn't running, it fails with the following errors:

    An error occurred while trying to initialize provider BINLSVC from C:\WINDOWS\system32\binlsvc.dll. Windows Deployment Services server will be shutdown.

     

    Error Information: 0xC1050702

     An error occurred while trying to start the Windows Deployment Services server.

     

    Error Information: 0xC1050702


    IF I'm going to remove the role and WDS do I need to backup any files or are they not removed on un-install? Namely the stuff in RemoteInstall directory.

    Cheers,
    Matt

    Thursday, April 23, 2009 10:27 AM
  • Ok - so when I try and remove the PXE Service Point I get an error stating that there are still packages in the service point that need to be removed before the role can be removed. I have removed both the x64 and x86 boot images but I'm still getting the error.

    Cheers,
    Matt
    Thursday, April 23, 2009 12:29 PM
  • Are the packages really removed? What does distmgr.log tell you? Any errors removing the boot images?

    Thursday, April 23, 2009 1:49 PM
  • The boot images were removed ok according to the logs file.

    After that error message came up I went in and manually removed the SMSPXEIMAGES$ share. Then, I realised the packages under Software Distribution were configured to have copies in the SMSPXEIMAGES$ DP so I went in through the console and removed the replica from the SMSPXEIMAGES$ share. Now when I try to remove the PXE Service Point I still get the error about existing packages.

    I have since re-created the SMSPXEIMAGES$ share and placed the original files back in it.

    I know, it sounds pretty dirty :-(

    Here is an entry from the distmgr.log file:



    Retrying package LON00040 SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    No action specified for the package LON00040. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    ["Display=\\VENUS\"]MSWNET:["SMS_SITE=SPE"]\\VENUS\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The next start time for pkg LON0003E is 24/04/2009 10:24:00 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 4084 (0x0FF4)
    ["Display=\\SATURN\"]MSWNET:["SMS_SITE=SGL"]\\SATURN\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The last source update time for pkg LON0003F is 23/04/2009 13:37:22 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 4084 (0x0FF4)
    The next start time for pkg LON0003F is 24/04/2009 13:37:00 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 4084 (0x0FF4)
    ["Display=\\PROTEUS\"]MSWNET:["SMS_SITE=SBA"]\\PROTEUS\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Sleep 381 seconds... SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 4084 (0x0FF4)
    ["Display=\\PEGASUS\"]MSWNET:["SMS_SITE=SPO"]\\PEGASUS\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    ["Display=\\MERCURY\"]MSWNET:["SMS_SITE=SCA"]\\MERCURY\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    ["Display=\\MARS\"]MSWNET:["SMS_SITE=SMA"]\\MARS\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    ["Display=\\EUROPA\"]MSWNET:["SMS_SITE=SBE"]\\EUROPA\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    No action specified for the package on server ["Display=\\BURGUNDY\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Start deleting the package from server ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\... SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to remove package LON00040 from MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\SMSPKG\LON00040\. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    for ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\, machine account is to be used SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to get access to the package server ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to make an accessible connection to ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\, get its NOS path, and get its number of free bytes. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Established connection to ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Getting the NAL path's NOS equivalent. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The NOS path is \\BURGUNDY\SMSPXEIMAGES$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The number of free bytes at the specified location has not been requested. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Successfully made an accessible connection, got a NOS path, and, if requested, got the number of free bytes at this location. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to get access to the package share. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to make an accessible connection to MSWNET:\\BURGUNDY\SMSPXEIMAGES$\, get its NOS path, and get its number of free bytes. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Established connection to MSWNET:\\BURGUNDY\SMSPXEIMAGES$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Getting the NAL path's NOS equivalent. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The NOS path is \\BURGUNDY\SMSPXEIMAGES$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The number of free bytes at the specified location has not been requested. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Successfully made an accessible connection, got a NOS path, and, if requested, got the number of free bytes at this location. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Package LON00040 has already been removed from MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\SMSPKG\LON00040\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to remove share MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\SMSPKG\LON00040\ from server ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Will not remove share MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\SMSPKG\LON00040\ from server ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\ because it is a Windows Share type site system created by the Admin SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to get access to the package share directory MSWNET:\\BURGUNDY\E$\SMSSIG$\SMSPXEIMAGES$\. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to make an accessible connection to MSWNET:\\BURGUNDY\E$\SMSSIG$\SMSPXEIMAGES$\, get its NOS path, and get its number of free bytes. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Established connection to MSWNET:\\BURGUNDY\E$\SMSSIG$\SMSPXEIMAGES$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Getting the NAL path's NOS equivalent. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The NOS path is \\BURGUNDY\E$\SMSSIG$\SMSPXEIMAGES$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The number of free bytes at the specified location has not been requested. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Successfully made an accessible connection, got a NOS path, and, if requested, got the number of free bytes at this location. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Won't remove the common SMS package share SMSPXEIMAGES$ on server BURGUNDY because there are other files in it SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to remove share MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSSIG$\SMSPXEIMAGES$\LON00040.46.tar from server ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Will not remove share MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSSIG$\SMSPXEIMAGES$\LON00040.46.tar from server ["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\ because it is a Windows Share type site system created by the Admin SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to get access to the package share directory MSWNET:\\BURGUNDY\E$\SMSSIG$\. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Attempting to make an accessible connection to MSWNET:\\BURGUNDY\E$\SMSSIG$\, get its NOS path, and get its number of free bytes. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Established connection to MSWNET:\\BURGUNDY\E$\SMSSIG$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Getting the NAL path's NOS equivalent. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The NOS path is \\BURGUNDY\E$\SMSSIG$\ SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The number of free bytes at the specified location has not been requested. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Successfully made an accessible connection, got a NOS path, and, if requested, got the number of free bytes at this location. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Won't remove the common SMS package share SMSSIG$ on server BURGUNDY because there are other files in it SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Successfully removed the package server from the data source SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    STATMSG: ID=2331 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BURGUNDY SITE=LON PID=2116 TID=424 GMTDATE=Thu Apr 23 14:03:08.891 2009 ISTR0="LON00040" ISTR1="["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="LON00040" AID1=404 AVAL1="["Display=\\BURGUNDY\SMSPXEIMAGES$\"]MSWNET:["SMS_SITE=LON"]\\BURGUNDY\SMSPXEIMAGES$\" SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Updating package info for package LON00040 SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Package LON00040 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    The package and/or program properties for package LON00040 have not changed,  need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    StoredPkgVersion (45) of package LON00040. StoredPkgVersion in database is 45. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    SourceVersion (46) of package LON00040. SourceVersion in database is 46. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BURGUNDY SITE=LON PID=2116 TID=424 GMTDATE=Thu Apr 23 14:03:08.969 2009 ISTR0="TalkbyText" ISTR1="LON00040" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LON00040" SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Removing retry key for package LON00040 SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:08 424 (0x01A8)
    Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:13 4084 (0x0FF4)
    The last source update time for pkg LON0003E is 23/04/2009 10:24:18 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:13 4084 (0x0FF4)
    The next start time for pkg LON0003E is 24/04/2009 10:24:00 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:13 4084 (0x0FF4)
    The last source update time for pkg LON0003F is 23/04/2009 13:37:22 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:13 4084 (0x0FF4)
    The next start time for pkg LON0003F is 24/04/2009 13:37:00 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:13 4084 (0x0FF4)
    The last source update time for pkg LON00040 is 23/04/2009 11:08:28 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:13 4084 (0x0FF4)
    The next start time for pkg LON00040 is 24/04/2009 11:08:00 GMT Daylight Time SMS_DISTRIBUTION_MANAGER 23/04/2009 15:03:13 4084 (0x0FF4)


    Thanks,
    Matt
    • Proposed as answer by Roger Ling Tuesday, May 05, 2009 8:14 AM
    Thursday, April 23, 2009 2:12 PM
  • I dont think this has anything to do with the PXE Service point. The only reason why the service point is not starting is due to Microsoft.BDD.PXEFilter Provider no loading properly. On the WDS server, try setting HKLM\SYSTEM\CCS\Services\WDSServer\Providers\Microsoft.BDD.PXEFilter\IsCritical Dword Value to 0, then restart WDSServer. If WDS starts successfully then there is a problem with your version of MDT. Try upgrading to latest version of MDT. I am experiencing this problem on Server 2008 R2, seems the Microsoft.BDD.PXEFilter is not working properly on 2008r2 yet :-(. If you are on the latest version of MDT make sure you have edited the VBScript correctly.
    Tuesday, May 05, 2009 8:25 AM