"error -1101" when you use the Ntdsutil.exe utility to check an AD DS database's integrity in Windows Server 2008 R2 or in Windows Server 2008

Article translations Article translations
Article ID: 2644042 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2 or Windows Server 2008 and has more than 16 logical processors.
  • You install the Active Directory Domain Services (AD DS) role on the computer.
  • You try to use the Ntdsutil.exe utility to check an AD DS database's integrity when the computer starts in Normal mode.
In this scenario, the integrity check fails and you receive the following error message:
Operation terminated with error -1101( JET_errOutOfSessions, Out of sessions ).

Cause

This issue occurs because the Ntdsutil.exe utility does not set a value for the maximum session number if the computer starts in Normal mode. Instead, it uses the operating system's default value of 16.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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=support
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 Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply the hotfix in this package, you do not have to make any changes to 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ntdsutil.exe6.0.6002.22758366,08019-Dec-201114:05x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ntdsutil.exe6.0.6002.22758460,28819-Dec-201114:25x64
Ntdsutil.exe6.0.6002.22758366,08019-Dec-201114:05x86
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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 1 . 21xxxWindows Server 2008 R2SP1LDR
  • 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 R2" section. MUM 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 x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ntdsutil.exe6.1.7601.21863470,01619-Nov-201111:59x64

Workaround

To work around this issue, use one of the following methods:
  • Limit the maximum processor number to 16 or fewer by using the following command at the command prompt:
    BCDEDIT /set NUMPROC processor count
  • Limit the physical processor number to 16 or fewer in the basic input/output system (BIOS).
  • Start the computer in directory services repair mode and then use the Ntdsutil.exe utility to perform the integrity check.

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
For more information about how to restart the domain controller in Directory Services Restore Mode (DSRM) locally, visit the following Microsoft website:

General information about how to restart the domain controller in DSRM locally

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot Applicable
File size3,358
Date (UTC)20-Dec-2011
Time (UTC)09:02
PlatformNot Applicable
File nameX86_98b441346d82fe7abddb7df188fa32bc_31bf3856ad364e35_6.0.6002.22758_none_22a4679b213b0d88.manifest
File versionNot Applicable
File size739
Date (UTC)20-Dec-2011
Time (UTC)09:02
PlatformNot Applicable
File nameX86_microsoft-windows-d..ommandline-ntdsutil_31bf3856ad364e35_6.0.6002.22758_none_dd932af745f88dd8.manifest
File versionNot Applicable
File size8,606
Date (UTC)19-Dec-2011
Time (UTC)16:25
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_98b441346d82fe7abddb7df188fa32bc_31bf3856ad364e35_6.0.6002.22758_none_7ec3031ed9987ebe.manifest
File versionNot Applicable
File size741
Date (UTC)20-Dec-2011
Time (UTC)09:02
PlatformNot Applicable
File nameAmd64_c408836ceebbe081ef6bf7feb6df257c_31bf3856ad364e35_6.0.6002.22758_none_dd25096555484ab2.manifest
File versionNot Applicable
File size743
Date (UTC)20-Dec-2011
Time (UTC)09:02
PlatformNot Applicable
File nameAmd64_microsoft-windows-d..ommandline-ntdsutil_31bf3856ad364e35_6.0.6002.22758_none_39b1c67afe55ff0e.manifest
File versionNot Applicable
File size8,644
Date (UTC)19-Dec-2011
Time (UTC)16:39
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size3,548
Date (UTC)20-Dec-2011
Time (UTC)09:02
PlatformNot Applicable
File nameX86_microsoft-windows-d..ommandline-ntdsutil_31bf3856ad364e35_6.0.6002.22758_none_dd932af745f88dd8.manifest
File versionNot Applicable
File size8,606
Date (UTC)19-Dec-2011
Time (UTC)16:25
PlatformNot Applicable

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_168b9d60fd91ceb48b09d58f648d1ccd_31bf3856ad364e35_6.1.7601.21863_none_bb0cf6f1b1a7021b.manifest
File versionNot applicable
File size743
Date (UTC)22-Nov-2011
Time (UTC)05:01
PlatformNot applicable
File nameAmd64_2eea109e17d0fa1b6a18462c300cc963_31bf3856ad364e35_6.1.7601.21863_none_221df5f90fbdc16c.manifest
File versionNot applicable
File size741
Date (UTC)22-Nov-2011
Time (UTC)05:01
PlatformNot applicable
File nameAmd64_microsoft-windows-d..ommandline-ntdsutil_31bf3856ad364e35_6.1.7601.21863_none_39c9ae9a5f79f2d5.manifest
File versionNot applicable
File size2,760
Date (UTC)19-Nov-2011
Time (UTC)12:28
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,355
Date (UTC)22-Nov-2011
Time (UTC)05:01
PlatformNot applicable
File nameX86_microsoft-windows-d..ommandline-ntdsutil_31bf3856ad364e35_6.1.7601.21863_none_ddab1316a71c819f.manifest
File versionNot applicable
File size2,756
Date (UTC)19-Nov-2011
Time (UTC)11:36
PlatformNot applicable

Properties

Article ID: 2644042 - Last Review: January 4, 2013 - Revision: 6.0
Applies to
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Standard
  • Windows Server 2008 Standard without Hyper-V
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2644042

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com