Server 2008 R2 Add AD CA role Crashing MMC

Home Forums Server Operating Systems Windows Server 2008 / 2008 R2 Server 2008 R2 Add AD CA role Crashing MMC

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    emge
    Member
    #167240

    I have a Domain Controller running on Server 2008 R2. I have been attempting to add the Active Directory Certificate Services role and it keeps crashing MMC as soon as I click the check box for the AD CA role in the add roles dialog. I’ve been searching around online all day and trying a variety of solutions but so far nothing has worked. The only thing that I haven’t tried that I’ve seen suggested is copying MMC registry keys over from another working server. I haven’t done this because I don’t have access to a similarly configured domain controller to copy from right now.

    *Full disclosure – I am not an IT professional. I am an automation engineer that has been tasked with setting up and maintaining our lab network – so don’t assume I know anything. :) *

    I would much appreciate any thoughts or suggestions anyone may have.

    The server manager log shows this:
    5628: 2017-10-04 14:59:55.604 [CBS] IsCacheStillGood: True.
    5628: 2017-10-04 15:00:01.205 [Provider] System changed since last refresh: False
    5628: 2017-10-04 15:00:07.335 [CAManager] Test Initialization: CCertSrvSetup
    5628: 2017-10-04 15:00:07.413 [CAManager] Test initialization: True
    5628: 2017-10-04 15:00:08.459 [CAManager] Initialization: Creating CCertSrvSetup
    5628: 2017-10-04 15:00:08.459 [CAManager] Initialization: Initializing defaults
    5628: 2017-10-04 15:00:08.474 [CAManager] Initialization: Getting default key information
    5628: 2017-10-04 15:00:08.474 [CAManager] Initialization: Getting existing certificates
    5628: 2017-10-04 15:00:08.490 [CAManager] Error (Id=0) An exception occurred at at Microsoft.CertificateServices.Setup.Interop.CCertSrvSetupClass.GetExistingCACertificates()
    at Microsoft.Windows.ServerManager.CertificateServer.CAManager.UpdateModel(Boolean certificateAuthorityAdded). Exception: ‘Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'[/CODE]

    And when MMC crashes, the problem details dialog shows this:
    [CODE]Description:
    Stopped working

    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: mmc.exe
    Problem Signature 02: 6.1.7601.23892
    Problem Signature 03: 5990c6ab
    Problem Signature 04: mscorlib
    Problem Signature 05: 2.0.0.0
    Problem Signature 06: 58e46330
    Problem Signature 07: 4227
    Problem Signature 08: a9
    Problem Signature 09: System.AccessViolationException
    OS Version: 6.1.7601.2.1.0.272.7
    Locale ID: 1033

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:Windowssystem32en-USerofflps.txt
    [/CODE][CODE]5628: 2017-10-04 14:59:55.604 [CBS] IsCacheStillGood: True.
    5628: 2017-10-04 15:00:01.205 [Provider] System changed since last refresh: False
    5628: 2017-10-04 15:00:07.335 [CAManager] Test Initialization: CCertSrvSetup
    5628: 2017-10-04 15:00:07.413 [CAManager] Test initialization: True
    5628: 2017-10-04 15:00:08.459 [CAManager] Initialization: Creating CCertSrvSetup
    5628: 2017-10-04 15:00:08.459 [CAManager] Initialization: Initializing defaults
    5628: 2017-10-04 15:00:08.474 [CAManager] Initialization: Getting default key information
    5628: 2017-10-04 15:00:08.474 [CAManager] Initialization: Getting existing certificates
    5628: 2017-10-04 15:00:08.490 [CAManager] Error (Id=0) An exception occurred at at Microsoft.CertificateServices.Setup.Interop.CCertSrvSetupClass.GetExistingCACertificates()
    at Microsoft.Windows.ServerManager.CertificateServer.CAManager.UpdateModel(Boolean certificateAuthorityAdded). Exception: ‘Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'[/CODE]

    And when MMC crashes, the problem details dialog shows this:
    Description:
    Stopped working

    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: mmc.exe
    Problem Signature 02: 6.1.7601.23892
    Problem Signature 03: 5990c6ab
    Problem Signature 04: mscorlib
    Problem Signature 05: 2.0.0.0
    Problem Signature 06: 58e46330
    Problem Signature 07: 4227
    Problem Signature 08: a9
    Problem Signature 09: System.AccessViolationException
    OS Version: 6.1.7601.2.1.0.272.7
    Locale ID: 1033

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:Windowssystem32en-USerofflps.txt
    [/CODE][CODE]Description:
    Stopped working

    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: mmc.exe
    Problem Signature 02: 6.1.7601.23892
    Problem Signature 03: 5990c6ab
    Problem Signature 04: mscorlib
    Problem Signature 05: 2.0.0.0
    Problem Signature 06: 58e46330
    Problem Signature 07: 4227
    Problem Signature 08: a9
    Problem Signature 09: System.AccessViolationException
    OS Version: 6.1.7601.2.1.0.272.7
    Locale ID: 1033

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:Windowssystem32en-USerofflps.txt
    [/CODE]

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.