Microsoft Knowledge Base Email Alertz

Error message when you try to create a RODC IFM in Windows Server 2008 if an earlier IFM procedure was canceled or has closed unexpectedly: “Could not initialize the Jet engine: Jet Error -1216”

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 954403 - Last Review: July 25, 2008 - Revision: 1.0

Error message when you try to create a RODC IFM in Windows Server 2008 if an earlier IFM procedure was canceled or has closed unexpectedly: “Could not initialize the Jet engine: Jet Error -1216”

On This Page

SYMPTOMS

When you try to create a Read-Only Domain Controller (RODC) Install from Media (IFM) or a RODC SYSVOL IFM by using the Ntdsutil.exe tool in Windows Server 2008, you may receive the following error message:
Could not initialize the Jet engine: Jet Error -1216
You receive this error message if an earlier IFM procedure was canceled or has closed unexpectedly. Additionally, the following events are logged in the Application log:
  • Source: ESENT
    Event ID: 454
    Level: Error
    Computer: Domain Controller Name
    Description: NTDS (4676) Database recovery/restore failed with unexpected error -1216.

  • Source: ESENT
    Event ID: 494
    Level: Error
    Computer: Domain Controller Name
    Description: NTDS (4676) Database recovery failed with error -1216 because it encountered references to a database, ‘C :\< Folder ws2k3preLocation>\Active Directory\ntds.dit', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message

CAUSE

This problem occurs if an earlier IFM procedure was canceled or has closed unexpectedly. Dirty log files may be left behind in the %Temp% folder if an earlier IFM procedure was canceled or if the IFM procedure closed unexpectedly.

RESOLUTION

To resolve this problem, remove any dirty log files that are left behind. To do this, use one of the following methods.

Method 1

Restart the Windows Server 2008-based domain controller.

Method 2

Locate the %Temp% folder, and manually delete the log files. To do this, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type Set temp, and then press ENTER. Or, at the command prompt, type Echo %temp%, and then press ENTER.

    The location of the %Temp% folder appears.
  3. Manually delete the log files from the %Temp% folder.

MORE INFORMATION

For more information about RODC, visit the following Microsoft Web site: http://technet2.microsoft.com/windowsserver2008/en/library/ea8d253e-0646-490c-93d3-b78c5e1d9db71033.mspx?mfr=true (http://technet2.microsoft.com/windowsserver2008/en/library/ea8d253e-0646-490c-93d3-b78c5e1d9db71033.mspx?mfr=true)

APPLIES TO
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
Keywords: 
kbfix kbexpertiseadvanced kbtshoot kbprb KB954403
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate