Issuing CA fail to start

KHH 26 Reputation points
2022-01-26T18:50:00.38+00:00

Hi Everyone,

Trying to migrate 2 tier offline CA from 2012R2 to 2020 and encountered issues.

The root CA is okay but the enterprise issuing CA is not. After importing the database, the issuing CA fail to start with the following error:

The system cannot find the file specified. 0x2 (WIN32: 2 ERROR_FILE_NOT_FOUND)

Can anyone help? Thanks.

KHH

Windows Server Security
Windows Server Security
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Security: The precautions taken to guard against crime, attack, sabotage, espionage, or another threat.
1,732 questions
0 comments
Accepted answer
  1. sudip 76 Reputation points
    2022-01-26T19:11:28.067+00:00

    This might be helpful LINK

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,396 Reputation points
    2022-01-27T09:46:48.34+00:00

    Hello KHH

    I would invite you to check the next link to ensure that all the permissions are configured correctly:

    https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee126140(v=ws.10)?redirectedfrom=MSDN#granting-permissions-on-aia-and-cdp-containers

    Most likely the issue is that it doesn't find the file due to a lack of access permission.

    Furthermore, for the same issue, there is a previous thread with different instructions for troubleshooting. Check it here: https://social.technet.microsoft.com/Forums/en-US/107d431f-3003-4ab2-94f7-bed355d7d43d/active-directory-certificate-services-wont-start-error-100?forum=winserversecurity

    ------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments
  2. KHH 26 Reputation points
    2022-01-28T14:36:50.753+00:00

    Thanks, everyone,

    Issue resolved. It was a permission issue.

    0 comments