Base de connaissances

Windows Server: Windows Deployment Service Fails to Start on a Windows Server 2008 or 2008 R2 Server with More than 20 Processor Cores



Article Summary: This article provides information on a condition that prevents Windows Deployment Services from starting on a server running Windows Server 2008 or 2008 R2.


After the installation of Windows Deployment Services (WDS) on Windows Server 2008 or 2008 R2, the Windows Deployment Services Configuration Wizard fails when attempting to start the WDS service with the error The service did not respond to the start or control request in a timely manner, as shown below:


If you attempt to manually start the WDS service in the Services console, it fails to start with the error Windows could not start the Windows Deployment Services Server on Local computer… as seen below:



When the WDS service fails to start, all of the following events can be found in the Windows Deployment Services event log:



EventID 768, Source BINLSVC: An error occurred while trying to initialize the Auto Add Policy.
Error Information 0xFFFFFBB3.

EventID 783, Source BINLSVC: An error occurred while initializing the Auto Add database.
Error Information 0xFFFFFBB3.

EventID 265, Source WDSPXE: An error occurred while trying to initialize provider BINLSVC. Since the provider is critical, the Windows Deployment Services server will be shutdown.
Error information 0xFFFFFBB3.

EventID 261, Source WDSPXE: An error occurred while trying to initialize provider BINLSVC from c:\Windows\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown.
Error information 0xFFFFFBB3.

EventID 257, Source WDSSERVER: An error occurred while trying to start the Windows Deployment Services Server.
Error information 0xFFFFFBB3.

EventID 513, Source 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.

The error code included in the above events, 0xFFFFFBB3, indicates that the database is out of sessions. The total number of processor cores installed in the system causes the database engine to create too many sessions. By default, for the WDS service to start successfully, the operating system must use 20 or fewer processors.
Since the initial publication of this article, Microsoft has created a hotfix for Windows Server 2008 and 2008 R2 which addresses this issue: Hotfix for Windows Deployment Services in Windows Server 2008 and 2008 R2.
Prior to the release of the hotfix, several possible workarounds could be used to get the WDS service to start, but they all involved disabling physical or logical processors in the server. These workarounds are presented here as alternatives in case the hotfix cannot be installed.
Workaround 1. Disable Logical Processor in the System BIOS under Processor Settings.
Hyperthreading makes logical processor cores available to the operating system, effectively doubling the total number of processor cores. If the number of physical processor cores installed on the server is less than 20, disable logical processors in the System BIOS to limit the total number of cores seen by the operating system to physical cores only.

Note: Logical processors are enabled on Dell servers by default.

Workaround 2. Use BCDEDIT with the NUMPROC setting to limit the number of processor cores.
If hyperthreading is desired or the number of physical processor cores is greater than 20, use BCDEDIT with the NUMPROC setting to limit the number of processors the operating system will use. From an elevated command prompt, run:
BCDEDIT /set NUMPROC 20
The number of processors can also be limited by using the MSCONFIG utility. Click the Advanced Options button under the Boot tab.
Workaround 3. Remove a processor or disable a physical processor in the System BIOS.




ID de l'article : SLN266201

Date de la dernière modification : 07/17/2015 04:34 PM


Noter cet article

Précis
Utile
Facile à comprendre
Avez-vous trouvé cet article utile ?
Oui Non
Envoyez-nous vos commentaires
Les commentaires ne doivent pas contenir les caractères spéciaux : <>()\
Désolé, notre système de collecte des commentaires est actuellement indisponible. Veuillez réessayer ultérieurement.

Merci pour vos commentaires.