Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Windows Deployment Server not starting

Posted on 2013-01-16
7
4,066 Views
Last Modified: 2013-01-22
I am getting the following errors while trying to start WDS on Server 2008 R2.
error 783 768 261 265 513 257 (see bottom for details)

I have tried the steps here and permissions are set correctly.  
http://technet.microsoft.com/en-us/library/dd353488.aspx

C:\Users\DomainAdmin>net start wdsserver
System error 5 has occurred.
Access is denied.

Also, I cannot seem to find the WDSServer user/group.
I also have and unknown user (S-1-5-80-2388302770-174706144-1409087682-264643484-2321118268) that is getting setup. I deleted the old RemoteInstall folder so the server is setting the permission.

As per steps
http://kb.prismmicrosys.com/evtpass/evtpages/EventId_257_WDSServer_62896.asp
Running this wdsutil /initialize-server /reminst:{RemoteInstallFolder}

I get this:
An error occurred while trying to execute the command.
Error Code: 0x41D
Error Description: The service did not respond to the start or control request i
n a timely fashion.






++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Log Name:      Application
Source:        BINLSVC
Date:          1/16/2013 9:58:35 AM
Event ID:      783
Task Category: BINLSVC
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.local
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="2013-01-16T15:58:35.000000000Z" />
    <EventRecordID>2799626</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0xFFFFFBB3</Data>
  </EventData>
</Event>

++++++++++++++++++++++++++++++++++++++++++++++++++++

Log Name:      Application
Source:        BINLSVC
Date:          1/16/2013 9:58:36 AM
Event ID:      768
Task Category: BINLSVC
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.local
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="2013-01-16T15:58:36.000000000Z" />
    <EventRecordID>2799628</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0xFFFFFBB3</Data>
  </EventData>
</Event>

++++++++++++++++++++++++++++++++++++++++++++++++++++

Log Name:      Application
Source:        WDSPXE
Date:          1/16/2013 9:58:36 AM
Event ID:      261
Task Category: WDSPXE
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.local
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="2013-01-16T15:58:36.000000000Z" />
    <EventRecordID>2799629</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.local</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:          1/16/2013 9:58:36 AM
Event ID:      265
Task Category: WDSPXE
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.local
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="2013-01-16T15:58:36.000000000Z" />
    <EventRecordID>2799630</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>BINLSVC</Data>
    <Data>0xFFFFFBB3</Data>
  </EventData>
</Event>

++++++++++++++++++++++++++++++++++++++++++++++++++++

Log Name:      Application
Source:        WDSServer
Date:          1/16/2013 9:58:36 AM
Event ID:      513
Task Category: WDSServer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.local
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="2013-01-16T15:58:36.000000000Z" />
    <EventRecordID>2799631</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.local</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:          1/16/2013 9:58:36 AM
Event ID:      257
Task Category: WDSServer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.local
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="2013-01-16T15:58:36.000000000Z" />
    <EventRecordID>2799640</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0xFFFFFBB3</Data>
  </EventData>
</Event>
0
Comment
Question by:BHeshka
  • 4
  • 2
7 Comments
 
LVL 80

Expert Comment

by:David Johnson, CD, MVP
ID: 38785916
have you tried removing and reinstalling the WDS role?
0
 
LVL 21

Expert Comment

by:dan_blagut
ID: 38785955
Hi
The user in SID is strange. Can you reach the domain from the server?
If you save the WDS installation folder you can reinstall the service (or the server) without data loss, so make a copy of that folder.

Dan
0
 

Author Comment

by:BHeshka
ID: 38787312
I tried removing and reinstalling the role.  I removed (copied) the folder and deleted the hklm\current control\services\wdsserver folder (not at computer may be slightly wrong).  Same errors.

I should state that this is our only server in this location and is running ad ds, dns, dhcp, file,  and hyperv. I know this is not ideal but I have had this same configuration working before so i know it works. I can connect to the domain/everything else is working just fine.

Option 60 has been configured and the only dns server configured is itself. I have read that these 2 things may cause problems.

I really think that the unknown SID is the root of my problems.
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 
LVL 21

Expert Comment

by:dan_blagut
ID: 38787530
Is the AD ok? it look's like this error is close to AD configuration problems. So please check the AD with dcdiag
You can maybe find some infos here:
http://social.technet.microsoft.com/Forums/en/winserversetup/thread/9217d987-bc7b-407a-a9b7-6424a3611dea

Dan
0
 

Author Comment

by:BHeshka
ID: 38788512
After much searching and trial and error I ran into this

http://support.microsoft.com/kb/2121690

Also I was having error in dcdiag but are now fixed, still not working. I will try above link tonight and report back.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   Home Server = Server

   * Identified AD Forest.
   Done gathering initial info.


Doing initial required tests

   
   Testing server: Canora\Server

      Starting test: Connectivity

         ......................... Server passed test Connectivity



Doing primary tests

   
   Testing server: Canora\Server

      Starting test: Advertising

         ......................... Server passed test Advertising

      Starting test: FrsEvent

         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         ......................... Server passed test FrsEvent

      Starting test: DFSREvent

         ......................... Server passed test DFSREvent

      Starting test: SysVolCheck

         ......................... Server passed test SysVolCheck

      Starting test: KccEvent

         ......................... Server passed test KccEvent

      Starting test: KnowsOfRoleHolders

         ......................... Server passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         ......................... Server passed test MachineAccount

      Starting test: NCSecDesc

         ......................... Server passed test NCSecDesc

      Starting test: NetLogons

         ......................... Server passed test NetLogons

      Starting test: ObjectsReplicated

         ......................... Server passed test ObjectsReplicated

      Starting test: Replications

         ......................... Server passed test Replications

      Starting test: RidManager

         ......................... Server passed test RidManager

      Starting test: Services

         ......................... Server passed test Services

      Starting test: SystemLog

         ......................... Server passed test SystemLog

      Starting test: VerifyReferences

         ......................... Server passed test VerifyReferences

   
   
   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : Schema

      Starting test: CheckSDRefDom

         ......................... Schema passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Schema passed test CrossRefValidation

   
   Running partition tests on : Configuration

      Starting test: CheckSDRefDom

         ......................... Configuration passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Configuration passed test CrossRefValidation

   
   Running partition tests on : Domain

      Starting test: CheckSDRefDom

         ......................... Domain passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Domain passed test CrossRefValidation

   
   Running enterprise tests on : Domain.local

      Starting test: LocatorCheck

         ......................... Domain.local passed test LocatorCheck

      Starting test: Intersite

         ......................... Domain.local passed test Intersite
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
0
 

Accepted Solution

by:
BHeshka earned 0 total points
ID: 38790331
http://support.microsoft.com/kb/2121690

This fixed my problem.  There is a known issue with WDS and more than 20 cores.
0
 

Author Closing Comment

by:BHeshka
ID: 38804844
http://support.microsoft.com/kb/2121690

This fixed my problem.  There is a known issue with WDS and more than 20 cores.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…

838 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question