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

    Question

  • I have System Center Essentials 2010 installed on a Windows Server 2008 R2 Standard. I then enabled WDS and configured it without adding any images or drivers. Installed MDT 2010 Update 1 and WAIK and configured Deployment workbench. Forest and domain functional level is Windows 2003.

    I'm getting the following event log entries when trying to start WDS server. I followed the suggestions on http://technet.microsoft.com/en-us/library/dd353488(WS.10).aspx but I still get the errors.

    Log Name:      Application
    Source:        BINLSVC
    Date:          8/24/2010 4:56:02 PM
    Event ID:      783
    Task Category: BINLSVC
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    An error occurred while initializing the Auto Add database.
     
     Error Information: 0xFFFFFBB3

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="BINLSVC" />
        <EventID Qualifiers="49413">783</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4281</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        BINLSVC
    Date:          8/24/2010 4:56:02 PM
    Event ID:      768
    Task Category: BINLSVC
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    An error occurred while trying to initialize the Auto Add Policy.
     
     Error Information: 0xFFFFFBB3

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="BINLSVC" />
        <EventID Qualifiers="49413">768</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4283</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        WDSPXE
    Date:          8/24/2010 4:56:02 PM
    Event ID:      261
    Task Category: WDSPXE
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    An error occurred while trying to initialize provider BINLSVC loaded from C:\Windows\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be  shutdown.
     
     Error Information: 0xFFFFFBB3

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="WDSPXE" />
        <EventID Qualifiers="49415">261</EventID>
        <Level>2</Level>
        <Task>7</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4284</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>BINLSVC</Data>
        <Data>C:\Windows\system32\binlsvc.dll</Data>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        WDSPXE
    Date:          8/24/2010 4:56:02 PM
    Event ID:      261
    Task Category: WDSPXE
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    An error occurred while trying to initialize provider BINLSVC loaded from C:\Windows\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be  shutdown.
     
     Error Information: 0xFFFFFBB3

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="WDSPXE" />
        <EventID Qualifiers="49415">261</EventID>
        <Level>2</Level>
        <Task>7</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4284</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>BINLSVC</Data>
        <Data>C:\Windows\system32\binlsvc.dll</Data>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        WDSPXE
    Date:          8/24/2010 4:56:02 PM
    Event ID:      265
    Task Category: WDSPXE
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    An error occurred while trying to initialize provider BINLSVC. Since the provider  is marked as critical, the Windows Deployment Services server will be shutdown.
     
     Error Information: 0xFFFFFBB3

    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="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4285</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>BINLSVC</Data>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        WDSServer
    Date:          8/24/2010 4:56:02 PM
    Event ID:      513
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    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: 0xFFFFFBB3

    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="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4286</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WDSPXE</Data>
        <Data>C:\Windows\system32\wdspxe.dll</Data>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        WDSServer
    Date:          8/24/2010 4:56:02 PM
    Event ID:      257
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    An error occurred while trying to start the Windows Deployment Services server.
     
     Error Information: 0xFFFFFBB3

    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="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4295</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        WDSServer
    Date:          8/24/2010 4:56:02 PM
    Event ID:      257
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    An error occurred while trying to start the Windows Deployment Services server.
     
     Error Information: 0xFFFFFBB3

    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="2010-08-24T20:56:02.000000000Z" />
        <EventRecordID>4295</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Log Name:      System
    Source:        Service Control Manager
    Date:          8/24/2010 4:56:02 PM
    Event ID:      7024
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.school.edu
    Description:
    The Windows Deployment Services Server service terminated with service-specific error %%-1101.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7024</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2010-08-24T20:56:02.955773600Z" />
        <EventRecordID>10131</EventRecordID>
        <Correlation />
        <Execution ProcessID="916" ThreadID="4448" />
        <Channel>System</Channel>
        <Computer>STORM.school.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Windows Deployment Services Server</Data>
        <Data Name="param2">%%-1101</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        WDSServer
    Date:          8/24/2010 4:32:35 PM
    Event ID:      513
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      STORM.hopkins-school.hopkins.edu
    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: 0xFFFFFBB3

    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="2010-08-24T20:32:35.000000000Z" />
        <EventRecordID>4217</EventRecordID>
        <Channel>Application</Channel>
        <Computer>STORM.hopkins-school.hopkins.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WDSPXE</Data>
        <Data>C:\Windows\system32\wdspxe.dll</Data>
        <Data>0xFFFFFBB3</Data>
      </EventData>
    </Event>

    Thanks.


    F.Palacio

    F.Palacio
    Wednesday, August 25, 2010 10:58 AM

Answers

  • Hi Ankit,

    In AD I went to the WDS server properties / security and checked that the permissions are as what you outlined.

    WDS server still would not start up.

    Thanks for the follow-up.

     ----------------------------

    Ankit,

    As we were discussing over the phone, what fixed it was to set the number of logical processors to 20 or less.

    As you instructed, I ran msconfig / boot / advanced options and selected 20 processors from the drop-down list. After the reboot, WDS service started up with no problems. I tried 22 processors but WDS failed to start.

    Thank you very much for your help.

     

     

    • Marked as answer by F.Palacio Wednesday, September 15, 2010 7:57 PM
    Wednesday, September 15, 2010 10:56 AM

All replies

  • Hi,

    The Auto-Add database (named Binlsvcdb.mdb) can be found in the RemoteInstall\MGMT folder. Please check it and try re-register binlsvc.dll

     

    Please check below link for WDSPXE

    http://kb.prismmicrosys.com/evtpass/evtPages/EventId_265_WDSPXE_63007.asp

     

    Thanks and Regards,

    Vikas

     

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.


    Thanks and Regards, Vikas This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Wednesday, August 25, 2010 1:37 PM
  • Hi,

     

    Please try Vikas’s suggeston first. If it does not work, please try below:

     

    1.    Click Start, click Run, type cmd, and then click OK.

    2.    At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.

    3.    Move the WDS account to Active Directory in the new organizational unit.

    4.    To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.

     

    Also please logon as a domain or Enterprise administrator and check the permissions for the computer account by doing the following: 

     

    ·         Log into a Domain Controller and launch Active Directory Users and Computers

    ·         Enable Advanced Features from the View menu

    ·         Find the server object for the WDS server and in Properties select the Security tab

    ·         Verify the following permissions:

    ·         Domain Admins:  Full Control

    ·         Enteprise Admins:  Full Control

    ·         Account Operators:  Full Control

    ·         System:  Full Control

    ·         SELF:  Create All Child Objects, Delete All Child Objects, Validated write to DNS host name, Validated write to service principal name, Read Personal Information, Write Personal Information

     

    Related information:

     

    http://technet.microsoft.com/en-us/library/dd353488(WS.10).aspx

    http://technet.microsoft.com/en-us/library/cc726739(WS.10).aspx

    http://technet.microsoft.com/en-us/library/cc726735(WS.10).aspx

     

    Hope it helps.

     

    Tim Quan

    • Proposed as answer by Mike.Brown Monday, January 30, 2012 11:56 PM
    Thursday, August 26, 2010 2:19 AM
    Moderator
  • I tried Vikas' procedure (all permissions appear good) and the procedure you emailed.

    !======================== START ===================================
    Re: wdsutil /uniniatlize-server ...

    The service ran under Local System so I changed it to a domain account that is a member of the Domain Admins group. When I ran wdsutil /initialize-server /reminst:e:\RemoteInstall I got the following error:
    C:\Windows\system32>wdsutil /uninitialize-server

    Windows Deployment Services Management Utility [Version 6.1.7600.16385]
    Copyright (C) Microsoft Corporation. All rights reserved.

    The command completed successfully.

    C:\Windows\system32>wdsutil /initialize-server /reminst:e:\RemoteInstall

    Windows Deployment Services Management Utility [Version 6.1.7600.16385]
    Copyright (C) Microsoft Corporation. All rights reserved.


    An error occurred while trying to execute the command.
    Error Code: 0x511
    Error Description: A privilege that the service requires to function properly does not exist in the service account configuration.
    You may use the Services Microsoft Management Console (MMC) snap-in (services.ms
    c) and the Local Security Settings MMC snap-in (secpol.msc) to view the service
    configuration and the account configuration.
    !================================ END ============================================

    However, the domain account shows up as having Log on as a service right.

    One thing that seems not right is when I try to run "regsvr32.exe binlsvc.dll" I get an error message -
    The module "binlsvc.dll" was loaded but the entry-point DllRegisterServer was not found.
    Make sure that "binlsvc.dll" is a valid DLL or OCX file and then try again.

    I get the same error when I tried "regsvr32.exe sqldmo.dll" on a totally different issue with SCE 2010. However, SCE 2010 is running and working.

    Is it maybe something related with regsvr32.exe?

    Thanks.


    F.Palacio
    Thursday, August 26, 2010 8:25 PM
  • Question:

    1. Which client images are you planning to deploy from WDS SERVER?

    2. Does WDS service ever start and stay started?

    3. Has it ever worked before and stop working?

    4. Can you please check if your default shares  are shared on WDS server

    C$           C:\                             Default share
    IPC$                                         Remote IPC
    ADMIN$       C:\Windows                      Remote Admin

    command to test > Start > run > CMD > net share > Enter

    5. Are you running WDS in mixed or native mode?

    Thanks,

    Ankit Oberoi


    ankit
    Monday, August 30, 2010 7:24 PM
  • Hi Ankit,

    1. I'm planning to use WDS to simply boot with the Lite Touch Windows PE(86) or Lite Touch Windows PE(x64) imported from the MDT 2010 Update1 installed on the same server. All the deployment processing is to be handled by MDT 2010. Interestingly, I created a hyper-v VM server running under the same physical server, installed WDS on it using the same credentials I used ti install WDS on the physical server. WDS on the hyper-v server starts with no problem. It actually talks to the MDT 2010/WAIK installed on the physical server and is able to deploy Windows 7 OS and capture Windows 7 images and deploy them.

    2. The WDS service on the physical server seems to start properly for the first part of its initialization process then starts to fail with Event 783.
    Event 1025 - WDSServer   -The RPC server started on TCP port 5040.
    Event 517   - WDSServer   - Provider BINLSVC loaded from C:\Windows\system32\binlsvc.dll and initialized successfully.
    Event 102   - ESENT          -svchost (4208) DDP: The database engine (6.01.7600.0000) started a new instance (0).
    Event 517   - WDSServer   - Provider WDSDDPS loaded from C:\Windows\system32\wdsddps.dll and initialized successfully.
    Event 256   - WDSIMGSRV -The Windows Deployment Services image server initialized successfully.
    Event 517   - WDSServer   - Provider WdsImgSrv loaded from C:\Windows\system32\WdsImgSrv.dll and initialized successfully.
    Event 517   - WDSServer   - Provider WDSMC loaded from C:\Windows\system32\wdsmc.dll and initialized successfully.
    Event 102   - ESENT          - svchost (4208) ESE: The database engine (6.01.7600.0000) started a new instance (1).
    Event 783   - BINLSVC      - An error occurred while initializing the Auto Add database. Error Information: 0xFFFFFBB3
    Event 103   - ESENT          - 
    svchost (4208) ESE: The database engine stopped the instance (1).
    Event 768   - BINLSVC      - An error occurred while trying to initialize the Auto Add Policy. Error Information: 0xFFFFFBB3.
    Event 261   - WDSPXE       - An error occurred while trying to initialize provider BINLSVC loaded from C:\Windows\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0xFFFFFBB3
    Event 265   - WDSPXE       -
    An error occurred while trying to initialize provider BINLSVC. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0xFFFFFBB3
    Event 513   - WDSServer   - An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown.Error Information: 0xFFFFFBB3
    Event 521   - WDSServer   - Provider WDSPXE was shutdown successfully.
    Event 1026 - WDSServer   - The RPC server shutdown successfully.
    Event 521   - WDSServer   - Provider BINLSVC was shutdown successfully.
    Event 102   - ESENT          - svchost (4208) DDP: The database engine stopped the instance (0).
    Event 521   - WDSServer   - Provider WDSDDPS was shutdown successfully.
    Event 257   - WDSIMGSRV - The Windows Deployment Services image server shutdown successfully.
    Event 521   - WDSServer   - Provider WdsImgSrv was shutdown successfully.
    Event 521   - WDSServer   -
    Provider WDSMC was shutdown successfully.

    3. It has never started successfully on the physical server which has SCE 2010, MDT 2010 Update 1, and WAIK installed. As I mentioned, WDS starts successfully on the hyper-v server and communicates with MDT 2010 on the physical server.

    4. The default shares that you listed exist.

    5. WDS is on native mode on the physical server and the hyper-v server.

    I followed http://technet.microsoft.com/en-us/library/dd353488(WS.10).aspx to try to resolve the Event 783 issue. WDS still would not start on the physical server.

    Ensure that the registry data and permissions are correct
    The Pre-Boot Execution Environment (PXE) provider provides client boot services over the network. This provider must be able to create and modify the Auto-Add Devices database and the tables and indexes contained in the database so that it can create and manage pending devices.

    To resolve this issue, first ensure that there is enough memory on the server. If there is enough memory, then do the following in the specified order until the issue is resolved:

    To resolve this issue, do the following:

    Ensure that the WDSServer service has permissions to the RemoteInstall folder
    Ensure that the WDServer service has access to the registry.
    Ensure that the configuration data in the registry is correct.
    Recreate the database.
    Ensure that the WDSServer service has permissions to the RemoteInstall folder
    To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

    To ensure that the WDSServer service has the necessary permissions:

    1.Right-click the RemoteInstall folder (by default, this folder is located on drive C).
    2.On the Security tab, make sure that WDSServer is set to Full control.
    If the Full Control check box is already selected, use the procedure in the following section to ensure that the WDServer service has access to the registry.

    Ensure that the WDServer service has access to the registry
    Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

    To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

    To ensure that WDSServer has the necessary permissions:

    1.Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER).)
    2.Locate the following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\
    3.Right-click the WDSServer node, click Permissions, click SYSTEM, and then make sure that Full Control is selected.
    If WDSServer has access to the registry and the problem persists, perform the procedure in the following section to make sure that the configuration data in the registry is correct.

    Ensure that the configuration data in the registry is correct
    To perform this procedure, you must either be a member of the local Domain Admins group or have been delegated the appropriate authority.

    To ensure that the configuration data is correct, use the following steps to restart the WDSServer service:

    1.Open the Command Prompt window.
    2.At the command prompt, run net stop wdsserver.
    3.At the command prompt, run net start wdsserver.
    If you continue to encounter this error, use the procedure in the following section to recreate the Auto-Add Devices database.

    Recreate the database
    To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

    To recreate the database:

     

     


    F.Palacio

     

    1.Delete the contents of the RemoteInstall\Mgmt folder. By default, the RemoteInstall folder is located on drive C.
    2.Open the Command Prompt window.
    3.At the command prompt, run net stop wdsserver.
    4.At the command prompt, run net start wdsserver.
    ===== END ======

    Monday, September 06, 2010 3:04 PM
  •  

    Please try following

    -Backup content of Remote Install folder if needed

    - Uninstall the WDS Role from Server Manager and reboot the box
    -  Delete the 'RemoteInstall' folder. If it gives 'Permission needed' message, 
       delete the Subfolders before deleting the 'RemoteInstall' folder
    -  Install WDS Role from Server Manager
    -  Open WDS Console and right click on the WDS Server and choose 'Configure'
    -  Configure the 'RemoteInstall' folder to any available Volume on the disk
    -  Check to ssee if WDS Service should start successfully.

    Thanks,

    Ankit Oberoi


    ankit
    Tuesday, September 07, 2010 4:14 AM
  • Hi Ankit,

    I had gone thru the procedure you outlined at least three times before. WDS still would not start.

    Is there a known conflict with the following sequence of installations?

    1. Installed SCE 2010.
    2. Installed MDT 2010 Update 1
    3. Installed WAIK
    4. Installed WDS

    Thanks.


    F.Palacio
    Thursday, September 09, 2010 8:39 AM
  •  

    Let me try to repro this issue and get back to you.

    Thanks,

    Ankit Oberoi


    ankit
    Monday, September 13, 2010 4:03 PM
  • Hello,

    I am able to repro the issue and here is what I did to fix the problem

    It looks like the problem is the SELF (i.e. "machine account") does not have permission to Create Child Objects, Delete child Objects because the SCP is a child object. WDS machine account does not have permission to modify the SCP object for WDS.

    [3632] 14:09:40: <- CWdsConfigurationManager::CreateScpObject(0x000000000029B2F0) =80070005
    [3632] 14:09:40: [2168][WDSPXE] [BINLSVC] [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\pxeprov\binlsvc\binlserverpolicy.cpp:145] Expression: , hr=0x80070005
    [3632] 14:09:40: [2168][WDSPXE] [BINLSVC] [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\pxeprov\binlprovider.cpp:127] Expression: , Win32 Error=0x5
    [3632] 14:09:40: -> CWdsServer::FinalRelease(0x000000000029B200)
    [3632] 14:09:40: -> CWdsConfigurationManager::FinalRelease(0x000000000029B2F0)
    [3632] 14:09:40: -> CWdsDeviceAnswerPolicy::FinalRelease(0x000000000029DC00)

     
    We need to locate the SCP object in AD and add permission to the server's machine account
     
    Locate the WDS computer account in Active Directory > Properties > Security
    Make sure following permissions are check
    Create All Child Objects, Delete All Child Objects, Validated write to DNS host name, , Validated write to service principal name, Read Personal Information, Write Personal Information
     
     
    After adding above permissions, I am able to start the WDS SERVER service.
     
    Another followup Question: Can you please tell me how many logical processor do we have on WDS SERVER?
    Thanks,
    Ankit
     

     


    ankit
    Monday, September 13, 2010 8:25 PM
  • Hi Ankit,

    In AD I went to the WDS server properties / security and checked that the permissions are as what you outlined.

    WDS server still would not start up.

    Thanks for the follow-up.

     ----------------------------

    Ankit,

    As we were discussing over the phone, what fixed it was to set the number of logical processors to 20 or less.

    As you instructed, I ran msconfig / boot / advanced options and selected 20 processors from the drop-down list. After the reboot, WDS service started up with no problems. I tried 22 processors but WDS failed to start.

    Thank you very much for your help.

     

     

    • Marked as answer by F.Palacio Wednesday, September 15, 2010 7:57 PM
    Wednesday, September 15, 2010 10:56 AM
  • Ankit,

    facing same issue with same error messages. It gets fixed if i reduce the number of cores to 20 or less...

    I deleted the Binlsvc.mdb and other ESE files under RemoteInstall\Mgmt and recycled the WDS service to recreate the database files. It did recreate the files but failed with below error...while starting service

    "An error occured while initializing Auto-Add database"

    Error code # 0xFFFFFBB3

    Post this we have other events about failures in Auto Add policy & WDS failure

    Based upon the database initializing failure, I wanted to check if we have any known limitations with ESE database not able to initialze with more than 20 cores here ? or is this has got something to do with WDS..

    Thanks,

    K

     

    Tuesday, September 28, 2010 8:55 AM
  • KailashC - the issue with WDS on a server with more then 20 cores can be fixed with this hotfix: http://support.microsoft.com/kb/2121690
    • Proposed as answer by Charles Wood Tuesday, September 25, 2012 5:17 PM
    Wednesday, May 18, 2011 5:13 PM
  • KailashC - the issue with WDS on a server with more then 20 cores can be fixed with this hotfix: http://support.microsoft.com/kb/2121690

    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Thats was for my the solution !!!

    thanks a lot


    Tuesday, September 25, 2012 6:35 PM