Shulou(Shulou.com)06/03 Report--

Recently installed Exchange2013 on 2012, has been wrong, always can not install complete, toss for a few days. Exchange2013 cu10 was installed at the beginning, but after installation, the admin center could not log in, and no solution was found online. Later, the latest 2013 cu16 was downloaded and installed. The first installation on 2012 was unsuccessful. Tip: The network service cannot be granted access to the certificate containing fingerprint 4DD3D65FDCE6420D420FF1790E73541DF3DF 827A due to an encryption exception. ---> System.Security.Cryptography.CryptographicException: Access denied.

Tormented for a long time did not solve, and then went to 2008 to install, update a bunch of patches installed in, is finally seen the true face. Later, I went back to install it in 2012, and I encountered the same problem again. There is a similar article on the Internet, but it is the 2016 system. His workaround was to move Microsoft Exchange Server Auth Certificate zhengshu certificates from individuals to trusted root certification authorities, which I tried several times and didn't work for my error. However, he provided me with a direction to solve my error, that is, the error was caused by the certificate. The error message "Unable to grant network services access to certificate with fingerprint 4DD3D65FDCE6420D420FF1790E73541DF3DF827A" appears to be a problem with this certificate. So on the 2008 comparison, the difference between the two certificates is that there is a duplicate certificate under the personal certificate of 2012.

A comparison of the above two figures shows that a certificate is repeated in 2012. Open it separately and find that one of the certificate fingerprints is: 4DD3D65FDCE6420D420FF1790E73541DF3DF 827A, which may be caused by this certificate.

So try to move this certificate to the trusted root certificate, prompt found that the trusted root certificate already has this certificate. Fig.

After thinking for a few seconds, could it be that the untrusted certificate in the personal certificate conflicts with this trusted certificate? The first reaction is to delete it, and considering that the situation is unclear, or to keep the transfer test first is more secure, move the untrusted certificate under this personal certificate to the blank certificate behind it for convenience.

After moving the certificate, click setup again and continue with the unfinished steps. If you can skip over, it means that the problem is solved. After waiting, I finally skipped over and proceeded to the next step until the final installation was completed, thus solving the problem.

As shown in the figure, the error is called remote XXX in the previous step, skip this step.

Finally, the installation was completed and successfully entered the management center.

This error seems to be very easy to appear in 2012, and it took a few days to fix it. There are similar errors encountered, you can refer to the next.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.