Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The Windows Deployment Service cannot be started on a computer that has more than 20 logical processors and that is running Windows Server 2008 R2 or Windows Server 2008


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have the Windows Deployment Services server role installed on a computer that is running Windows Server 2008 R2 or Windows Server 2008.
  • The computer has more than 20 logical processors.
In this scenario, the Windows Deployment Service cannot be started, and you receive the following error message:
Error: the service did not respond to the start or control request in a timely fashion.
Additionally, the following event is added to the application event log:


If you try to perform an integrity check on a domain controller that is running Windows Server 2008 or Windows Server 2008 R2 and that has multiple processors installed, you might receive the following error when you run NTDSUTIL Files / integrity:
JET_errOutOfSessions
-1101
For example, you have a computer that has dual 6-core Xeon processors. These processors support hyper-threading technology. Therefore, the logical processor number is 24. If you install the Windows Deployment Service server role on the computer, the Windows Deployment Service cannot be started because of this issue.

↑ Back to the top


Cause

This issue occurs because the Windows Deployment Service does not scale the value of the JET_paramMaxSessions value correctly. The service cannot be started on a computer that has more than 20 logical processors because the computer reaches the limitation of maximum sessions for a database engine.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
Additionally, you must have the Windows Deployment Services server role installed.

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx
    Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Binlsvc.dll6.0.6002.22570182,78413-Jan-201116:05x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Binlsvc.dll6.0.6002.22570234,49613-Jan-201116:25x64
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.20xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.21xxx
    Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTime
Binlsvc.dll6.1.7600.20872259,58404-Jan-201111:51
Binlsvc.dll6.1.7601.21633259,58404-Jan-201112:00
Wdsddps.dll6.1.7600.20872177,66404-Jan-201111:58
Wdsddps.dll6.1.7601.21633177,66404-Jan-201112:04

↑ Back to the top


Workaround

To work around the issue, you must limit the number of logical processors by using one of the following methods:
  • Use the BCDEDIT command-line tool together with the NUMPROC setting. For example, run the following command:
    BCDEDIT /set NUMPROC 20
  • Disable physical processors in the BIOS.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size1,577
Date (UTC)27-Jan-2011
Time (UTC)08:29
PlatformNot applicable
File nameX86_89957c3d58156be8bb25a0c5e4783a26_31bf3856ad364e35_6.0.6002.22570_none_245ba306b870b6d1.manifest
File versionNot applicable
File size719
Date (UTC)27-Jan-2011
Time (UTC)08:29
PlatformNot applicable
File nameX86_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.0.6002.22570_none_9f91932e521e8c18.manifest
File versionNot applicable
File size41,573
Date (UTC)13-Jan-2011
Time (UTC)16:20
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_d4009a78780b62851c08d4fd0c68591b_31bf3856ad364e35_6.0.6002.22570_none_03a478b3ce5025da.manifest
File versionNot applicable
File size723
Date (UTC)27-Jan-2011
Time (UTC)08:29
PlatformNot applicable
File nameAmd64_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.0.6002.22570_none_fbb02eb20a7bfd4e.manifest
File versionNot applicable
File size41,611
Date (UTC)13-Jan-2011
Time (UTC)16:42
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,587
Date (UTC)27-Jan-2011
Time (UTC)08:29
PlatformNot applicable

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_1a8a170ac2bc46748bf0488bffbd7074_31bf3856ad364e35_6.1.7600.20872_none_8a95296074729f5d.manifest
File versionNot applicable
File size723
Date (UTC)04-Jan-2011
Time (UTC)22:41
File nameAmd64_7d9b2e71106ef1eda0b33a202df9977d_31bf3856ad364e35_6.1.7600.20872_none_47218af8fedd842f.manifest
File versionNot applicable
File size748
Date (UTC)04-Jan-2011
Time (UTC)22:41
File nameAmd64_b26c569ab66e101147e2c46cc71830c0_31bf3856ad364e35_6.1.7601.21633_none_186082fb6411c156.manifest
File versionNot applicable
File size748
Date (UTC)04-Jan-2011
Time (UTC)22:42
File nameAmd64_c387519dd9c0cffd25421c5fcf0dd303_31bf3856ad364e35_6.1.7601.21633_none_5e3a2dbbd5e495a5.manifest
File versionNot applicable
File size723
Date (UTC)04-Jan-2011
Time (UTC)22:42
File nameAmd64_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.1.7600.20872_none_f9f38bbd6e6b1a99.manifest
File versionNot applicable
File size36,016
Date (UTC)04-Jan-2011
Time (UTC)12:37
File nameAmd64_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.1.7601.21633_none_fc0628bd6b703018.manifest
File versionNot applicable
File size36,016
Date (UTC)04-Jan-2011
Time (UTC)12:35
File nameAmd64_microsoft-windows-d..ovisioning-provider_31bf3856ad364e35_6.1.7600.20872_none_a955ab4e93e6148c.manifest
File versionNot applicable
File size5,878
Date (UTC)04-Jan-2011
Time (UTC)12:44
File nameAmd64_microsoft-windows-d..ovisioning-provider_31bf3856ad364e35_6.1.7601.21633_none_ab68484e90eb2a0b.manifest
File versionNot applicable
File size5,878
Date (UTC)04-Jan-2011
Time (UTC)12:40

↑ Back to the top


Keywords: kb, kbqfe, kbfix, kbautohotfix, kbhotfixserver, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2121690
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2011
Exists online : False
Views : 325