locked
Stop c00002e2 after DCPromo in Server 2008 x64 on Gigabyte MB RRS feed

  • Question

  • I have the same problem that was discussed in http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/42c999b5-0a45-4501-9d69-cd30a6193c21/

    After running dcpromo and the required reboot, i get:
    STOP: c00002e2 Directory Services could not start because of the following error:
    A device attached to the system is not functioning.

    Error Status: 0xc0000001.
    Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.

    I did as the error message says but could not really find anything indicative in the event logs.  I looked up the error messages using err.exe mentioned in a response in the above post.  C00002e2 means just what the error message says, "Directory Services could not...".  C0000001 means:  "The function is not yet implemented".

    I have the same GA-MA78GM-S2H motherboard and a SATA Raid1 mirror (on two 160G Seagate drives).
    I have all the latest 64 bit drivers installed.  I installed using a modified WinPE boot cd that had the drivers added to it and also made sure to load the drivers during the instllation.

    I did not see any resolution in the above post.  If anyone has any ideas, please let me know.

    In the mean time, I'll continue to examine the event log, and possibly try other drivers.

    Saturday, September 20, 2008 3:11 PM

Answers

  • I had the same error codes as this.

    Restored using a system image backup on to new hardware.  After rebooting the system was just rebooting over and over again with no blue screen or any information.  After hitting F8 and choosing 'Dont reboot at failure'  I was able to see the blue screen.

    I had the following blue screens:

    STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. - Error Status: 0xc0000001

    After about 7 hours of messing around with the system using 'Directory Services Restore Mode', trawling through countless web sites and pages, I couldnt find any further useful information.  I noticed that if I renamed the NTDS folder to something else and rebooted, I got the following error:

    STOP: c00002e2 Directory Services could not stsrt because of the following error: Could not find the file specified  - Error Status: 0xc000000f

    My initial thought was that the system couldnt see the NTDS folder, for some reason related to it being on a different drive.  This second error code was a step forward for me, because it proved that the system could actually see the NTDS folder afterall, and it was unlikely to be something to do with the drive letter etc...

    The windows event log was not particularly helpful at all and none of the AD tools would work, to name a few:

    DSA.MSC
    DCDIAG
    NETDIAG
    REPADMIN
    So looking further into the issue, I noticed that the backup I was using to restore from was very old!  this was not my initial intention.  I thought it was new.... it turns out that the domain controller I was restoring had not been backed up using this method for months.  We did have a backup, but only using HP Data Protector, which I wanted to avoid restoring from.

    Anyway, to cut a long story short.  This problem was fixed by setting the date back in time several months, to just after the backup was taken.  Once booted successfully, I was able to set the date back to present and everything worked spot on!  This domain was a root domain so the accounts didnt really change much.  If it was our main domain, someone might have got some serious flack!

    Hopefully this helps someone!

    Cheers,

     

    • Marked as answer by Brian Borg Thursday, April 14, 2011 8:51 PM
    Wednesday, January 19, 2011 5:42 PM
  • I had the same error codes as this.

    Restored using a system image backup on to new hardware.  After rebooting the system was just rebooting over and over again with no blue screen or any information.  After hitting F8 and choosing 'Dont reboot at failure'  I was able to see the blue screen.

    I had the following blue screens:

    STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. - Error Status: 0xc0000001

    After about 7 hours of messing around with the system using 'Directory Services Restore Mode', trawling through countless web sites and pages, I couldnt find any further useful information.  I noticed that if I renamed the NTDS folder to something else and rebooted, I got the following error:

    STOP: c00002e2 Directory Services could not stsrt because of the following error: Could not find the file specified  - Error Status: 0xc000000f

    My initial thought was that the system couldnt see the NTDS folder, for some reason related to it being on a different drive.  This second error code was a step forward for me, because it proved that the system could actually see the NTDS folder afterall, and it was unlikely to be something to do with the drive letter etc...

    The windows event log was not particularly helpful at all and none of the AD tools would work, to name a few:

    DSA.MSC
    DCDIAG
    NETDIAG
    REPADMIN
    So looking further into the issue, I noticed that the backup I was using to restore from was very old!  this was not my initial intention.  I thought it was new.... it turns out that the domain controller I was restoring had not been backed up using this method for months.  We did have a backup, but only using HP Data Protector, which I wanted to avoid restoring from.

    Anyway, to cut a long story short.  This problem was fixed by setting the date back in time several months, to just after the backup was taken.  Once booted successfully, I was able to set the date back to present and everything worked spot on!  This domain was a root domain so the accounts didnt really change much.  If it was our main domain, someone might have got some serious flack!

    Hopefully this helps someone!

    Cheers,

     


    Snake Moore You are my Savior, I was begining to think it was a 2008 R2 issue. Sure enough the tapes were 2 months old, My co-worker had dropped this on my plate, so I had now idea.  I feel your pain with HP DataProtector. 

     

    Stop Errors:  c00002e2 Directory services could not start because of the following error: A device attached to the system is not functioning

     

    Error Status: 0xc0000001

     

    Check the date of the backups. If it is more than a few days from the current date, boot the target machine into bios and change the system date to a day after the backup was made. Then windows should boot.

    • Marked as answer by Brian Borg Friday, February 3, 2012 2:33 AM
    Thursday, April 14, 2011 7:22 PM
  • No, the domain controller was the Hyper-V host machine.  I had not configured any virtual machines yet.

    In any case, it is now moot since I decided to delete the new domain controller and re-install Windows Server 2008.  I just did DCPromo and have not rebooted yet.  I have yet to install Hyper-V.  I'll report back how it goes.

    No good.  After going to Windows Update and rebooting, I get the same BSOD error:
    STOP: c00002e2 Directory Services could not start because of the following error:
    A device attached to the system is not functioning.

    It must be one of the updates, but I can only boot to Directory Services Restore Mode.  I need to somehow back out of updates while in DSR mode.
    • Edited by Brian Borg Monday, September 29, 2008 7:03 PM
    • Marked as answer by David Shen Thursday, October 2, 2008 8:53 AM
    Monday, September 29, 2008 2:45 AM

All replies

  • Anyone?

    Is it possible that installing Hyper-V before DCPromo is the problem?  Or is it the AMD Raid1 mirror?
    Tuesday, September 23, 2008 3:01 AM
  • Hi customer,

     

    If I don't misunderstand, you encounter the blue screen error message on the domain controller which is installed as a Virtual machine based on the Hyper-V physical machine.

     

    If so, please check the disk that contains the VHD file of the virtual machine on the host machine to see if there is enough disk space on it. If the disk space is insufficient, this could cause this blue screen issue when we promote the domain controller in the virtual machine. To prevent it, you need to free up some disk space on the physical machine. Afterwards, you may try performing a clean installation of Windows Server 2008, and then rebuild the domain to check if the blue screen issue will re-occur.

     

    If the Blue Screen issue still exists, we need to analyze the performance log and system crash dump file to solid locate the root cause. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Hope it helps.


    David Shen - MSFT
    • Marked as answer by David Shen Monday, September 29, 2008 2:01 AM
    • Edited by David Shen Monday, March 16, 2009 2:58 AM
    • Unmarked as answer by Brian Borg Wednesday, October 21, 2009 8:24 PM
    Wednesday, September 24, 2008 8:27 AM
  • No, the domain controller was the Hyper-V host machine.  I had not configured any virtual machines yet.

    In any case, it is now moot since I decided to delete the new domain controller and re-install Windows Server 2008.  I just did DCPromo and have not rebooted yet.  I have yet to install Hyper-V.  I'll report back how it goes.

    No good.  After going to Windows Update and rebooting, I get the same BSOD error:
    STOP: c00002e2 Directory Services could not start because of the following error:
    A device attached to the system is not functioning.

    It must be one of the updates, but I can only boot to Directory Services Restore Mode.  I need to somehow back out of updates while in DSR mode.
    • Edited by Brian Borg Monday, September 29, 2008 7:03 PM
    • Marked as answer by David Shen Thursday, October 2, 2008 8:53 AM
    Monday, September 29, 2008 2:45 AM
  • Just an update.  The problem seems to be the Sata-Raid driver from AMD.  Although certified, it does not correctly support the Sata drives when configured as Sata in the bios.  When the drives are set to be ACHI compatible, the system works fine.  I just can't use the bios supported Sata Raid.

    I have Windows Server 2008 x64 Enterprise installed, with Active Directory as secondary DC.  I haven't enabled much else yet.
    Wednesday, October 15, 2008 10:59 PM
  •  http://www.asrock.com/mb/download.asp?Model=A780GXE/128M&s=AM2%2b

     This is a chipset issue. I don't have the board you guys have; I have AsRock a780gxe/128mb, it has the sb700, and it to REFUSES TO LOAD RAID, i even tried a silicon image and it puked it out, trasffered at like 2mb a second lmao. I tried installing every damn way possible 0,1, 10, ready, jbod; backwards, forwards, sides ways; I even tried linux, and unix; i have yet to find an operating system that this damn raid will work on!!!!! And mine would install the x64 or x86 drivers just fine, and install any damn role i wanted too....except the domain controller. Once promo.exe is ran, there is no getting back into windows; unless you rip the freakin DC out by its throat. I am not lieing when i said i did this like 30 times at least, just with windows. As mentioned above, the only way for it to work is in achi mode sometimes, ide all the time, Raid w/DC zero times. Ubuntu 8.10 recognizes the raid and just like windows, this is reproduceable issue, thinking it will restart. Someone fix this :)!! corrosione@gmail
    Monday, March 9, 2009 7:12 PM
  •  
    corrosione - Posted a few seconds ago
    for got sakes, i just realiezed that this post is 6 months old, and still no fix, and i just bought my mb!!!!!! SIGH!
    Monday, March 9, 2009 7:14 PM
  • Yeah, I think I'll buy NVidia next time.
    Saturday, March 14, 2009 5:12 AM
  • I had the same error codes as this.

    Restored using a system image backup on to new hardware.  After rebooting the system was just rebooting over and over again with no blue screen or any information.  After hitting F8 and choosing 'Dont reboot at failure'  I was able to see the blue screen.

    I had the following blue screens:

    STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. - Error Status: 0xc0000001

    After about 7 hours of messing around with the system using 'Directory Services Restore Mode', trawling through countless web sites and pages, I couldnt find any further useful information.  I noticed that if I renamed the NTDS folder to something else and rebooted, I got the following error:

    STOP: c00002e2 Directory Services could not stsrt because of the following error: Could not find the file specified  - Error Status: 0xc000000f

    My initial thought was that the system couldnt see the NTDS folder, for some reason related to it being on a different drive.  This second error code was a step forward for me, because it proved that the system could actually see the NTDS folder afterall, and it was unlikely to be something to do with the drive letter etc...

    The windows event log was not particularly helpful at all and none of the AD tools would work, to name a few:

    DSA.MSC
    DCDIAG
    NETDIAG
    REPADMIN
    So looking further into the issue, I noticed that the backup I was using to restore from was very old!  this was not my initial intention.  I thought it was new.... it turns out that the domain controller I was restoring had not been backed up using this method for months.  We did have a backup, but only using HP Data Protector, which I wanted to avoid restoring from.

    Anyway, to cut a long story short.  This problem was fixed by setting the date back in time several months, to just after the backup was taken.  Once booted successfully, I was able to set the date back to present and everything worked spot on!  This domain was a root domain so the accounts didnt really change much.  If it was our main domain, someone might have got some serious flack!

    Hopefully this helps someone!

    Cheers,

     

    • Marked as answer by Brian Borg Thursday, April 14, 2011 8:51 PM
    Wednesday, January 19, 2011 5:42 PM
  • I had the same error codes as this.

    Restored using a system image backup on to new hardware.  After rebooting the system was just rebooting over and over again with no blue screen or any information.  After hitting F8 and choosing 'Dont reboot at failure'  I was able to see the blue screen.

    I had the following blue screens:

    STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. - Error Status: 0xc0000001

    After about 7 hours of messing around with the system using 'Directory Services Restore Mode', trawling through countless web sites and pages, I couldnt find any further useful information.  I noticed that if I renamed the NTDS folder to something else and rebooted, I got the following error:

    STOP: c00002e2 Directory Services could not stsrt because of the following error: Could not find the file specified  - Error Status: 0xc000000f

    My initial thought was that the system couldnt see the NTDS folder, for some reason related to it being on a different drive.  This second error code was a step forward for me, because it proved that the system could actually see the NTDS folder afterall, and it was unlikely to be something to do with the drive letter etc...

    The windows event log was not particularly helpful at all and none of the AD tools would work, to name a few:

    DSA.MSC
    DCDIAG
    NETDIAG
    REPADMIN
    So looking further into the issue, I noticed that the backup I was using to restore from was very old!  this was not my initial intention.  I thought it was new.... it turns out that the domain controller I was restoring had not been backed up using this method for months.  We did have a backup, but only using HP Data Protector, which I wanted to avoid restoring from.

    Anyway, to cut a long story short.  This problem was fixed by setting the date back in time several months, to just after the backup was taken.  Once booted successfully, I was able to set the date back to present and everything worked spot on!  This domain was a root domain so the accounts didnt really change much.  If it was our main domain, someone might have got some serious flack!

    Hopefully this helps someone!

    Cheers,

     


    Snake Moore You are my Savior, I was begining to think it was a 2008 R2 issue. Sure enough the tapes were 2 months old, My co-worker had dropped this on my plate, so I had now idea.  I feel your pain with HP DataProtector. 

     

    Stop Errors:  c00002e2 Directory services could not start because of the following error: A device attached to the system is not functioning

     

    Error Status: 0xc0000001

     

    Check the date of the backups. If it is more than a few days from the current date, boot the target machine into bios and change the system date to a day after the backup was made. Then windows should boot.

    • Marked as answer by Brian Borg Friday, February 3, 2012 2:33 AM
    Thursday, April 14, 2011 7:22 PM
  • Thank you very much, I set the CMOS date to a day after the image was taken which was last year and it finally booted with no problem.
    Tuesday, May 17, 2011 3:16 AM
  • I have the same problem after restore from Symantec Image.
    I set the CMOS date to one day after the image was taken and its booted without problems.

    excellent idea !!!

    Thank you very much


    Friday, January 27, 2012 8:14 AM
  • I got the same error as the original poster when trying to update Windows Server 2008 R2 DC to Service pack 1

    I was stuck on bluescreens when trying to restart windows, and Directory Services Restore Mode did not help.

    Since this was a VM, i mounted the W2008R2 installation image, and ran the command prompt, and diskpart.

    when writing list volumes, i noticed that the system drive had the letter D:(it was C: before the attempted update)

    I used diskpart to change the drive letter back to C: (assign letter=c) then, after reboot,it was able to start up in safe mode


    • Edited by Jan Magne Tuesday, October 2, 2012 4:17 PM
    Tuesday, October 2, 2012 4:08 PM
  • Hi, 

    I have the same issue / error, restoring an image from a week or so ago, so hopeing this date set back solution will resolve it for me.

    mine is a Hyper-V 2012 guest, how can I set the date back? it is not possible to set the date back on the guest (bios etc), and if I set the date back on the host I can't open / connect too Hyper-V manager any more because I can't Authenticate to it (I assume this is because the dates are out)

    any idea on how to get around this issue?

    Sunday, February 10, 2013 11:54 PM
  • Well, I located the cause on My rig; - I had connected ONLY the boot drive but NOT the drive with all my fashion accessories such as my VM library, my (AD) SYSVOL + NTDS folders........ - the whole pooh started with my main server crashing and Then I did THIS; https://www.youtube.com/watch?v=B7aArn83KeE - the result was DISASTER and I felt like Puking - in the end, a visit to SafeModeVille put stuff on the road to recovery........

    Woops! - I forgot to mention the probable cause; - a (surprise surprise) dodgy cable...

    • Edited by AVBooth Tuesday, December 2, 2014 10:11 AM
    Tuesday, December 2, 2014 10:05 AM