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.
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.
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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
Version
Product
SR_Level
Service branch
6.0.600
2.
22xxxWindows Server 2008
SP2
LDR
-
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 name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Binlsvc.dll |
6.0.6002.22570 |
182,784 |
13-Jan-2011 |
16:05 |
x86 |
For all supported x64-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Binlsvc.dll |
6.0.6002.22570 |
234,496 |
13-Jan-2011 |
16:25 |
x64 |
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:
Version
Product
Milestone
Service branch
6.1.760
0.20xxxWindows Server 2008 R2
RTM
LDR
6.1.760
1.21xxxWindows Server 2008 R2
SP1
LDR
-
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 name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Binlsvc.dll |
6.1.7600.20872 |
259,584 |
04-Jan-2011 |
11:51 |
|
Binlsvc.dll |
6.1.7601.21633 |
259,584 |
04-Jan-2011 |
12:00 |
|
Wdsddps.dll |
6.1.7600.20872 |
177,664 |
04-Jan-2011 |
11:58 |
|
Wdsddps.dll |
6.1.7601.21633 |
177,664 |
04-Jan-2011 |
12:04 |
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.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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 name |
Update.mum |
|
File version |
Not applicable |
|
File size |
1,577 |
|
Date (UTC) |
27-Jan-2011 |
|
Time (UTC) |
08:29 |
|
Platform |
Not applicable |
|
File name |
X86_89957c3d58156be8bb25a0c5e4783a26_31bf3856ad364e35_6.0.6002.22570_none_245ba306b870b6d1.manifest |
|
File version |
Not applicable |
|
File size |
719 |
|
Date (UTC) |
27-Jan-2011 |
|
Time (UTC) |
08:29 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.0.6002.22570_none_9f91932e521e8c18.manifest |
|
File version |
Not applicable |
|
File size |
41,573 |
|
Date (UTC) |
13-Jan-2011 |
|
Time (UTC) |
16:20 |
|
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows Server 2008
|
File name |
Amd64_d4009a78780b62851c08d4fd0c68591b_31bf3856ad364e35_6.0.6002.22570_none_03a478b3ce5025da.manifest |
|
File version |
Not applicable |
|
File size |
723 |
|
Date (UTC) |
27-Jan-2011 |
|
Time (UTC) |
08:29 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.0.6002.22570_none_fbb02eb20a7bfd4e.manifest |
|
File version |
Not applicable |
|
File size |
41,611 |
|
Date (UTC) |
13-Jan-2011 |
|
Time (UTC) |
16:42 |
|
Platform |
Not applicable |
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
1,587 |
|
Date (UTC) |
27-Jan-2011 |
|
Time (UTC) |
08:29 |
|
Platform |
Not applicable |
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
|
File name |
Amd64_1a8a170ac2bc46748bf0488bffbd7074_31bf3856ad364e35_6.1.7600.20872_none_8a95296074729f5d.manifest |
|
File version |
Not applicable |
|
File size |
723 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
22:41 |
|
File name |
Amd64_7d9b2e71106ef1eda0b33a202df9977d_31bf3856ad364e35_6.1.7600.20872_none_47218af8fedd842f.manifest |
|
File version |
Not applicable |
|
File size |
748 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
22:41 |
|
File name |
Amd64_b26c569ab66e101147e2c46cc71830c0_31bf3856ad364e35_6.1.7601.21633_none_186082fb6411c156.manifest |
|
File version |
Not applicable |
|
File size |
748 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
22:42 |
|
File name |
Amd64_c387519dd9c0cffd25421c5fcf0dd303_31bf3856ad364e35_6.1.7601.21633_none_5e3a2dbbd5e495a5.manifest |
|
File version |
Not applicable |
|
File size |
723 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
22:42 |
|
File name |
Amd64_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.1.7600.20872_none_f9f38bbd6e6b1a99.manifest |
|
File version |
Not applicable |
|
File size |
36,016 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
12:37 |
|
File name |
Amd64_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.1.7601.21633_none_fc0628bd6b703018.manifest |
|
File version |
Not applicable |
|
File size |
36,016 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
12:35 |
|
File name |
Amd64_microsoft-windows-d..ovisioning-provider_31bf3856ad364e35_6.1.7600.20872_none_a955ab4e93e6148c.manifest |
|
File version |
Not applicable |
|
File size |
5,878 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
12:44 |
|
File name |
Amd64_microsoft-windows-d..ovisioning-provider_31bf3856ad364e35_6.1.7601.21633_none_ab68484e90eb2a0b.manifest |
|
File version |
Not applicable |
|
File size |
5,878 |
|
Date (UTC) |
04-Jan-2011 |
|
Time (UTC) |
12:40 |
