CryptoAPI cryptographic service provider (CSP) Error

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear

Post Reply
dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

CryptoAPI cryptographic service provider (CSP) Error

Post by dan » Tue Feb 17, 2004 5:26 pm

If after installing, you get the following error:

Error System.Security.Cryptography.CryptographicException: CryptoAPI cryptographic
- service provider (CSP) for this implementation could not be acquired.

On the machine where the Vault server is installed, go to the following directory, and grant everyone full control.

--Windows 2003
\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys

--Windows 2008 and later
C:\ProgramData\Microsoft\Crypto\RSA

If the problem persists after adding these permissions, stop IIS, and find a file that starts with "edb3...." in the directory mentioned earlier. Delete it, and then restart IIS. Then try to log into Vault.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: CryptoAPI cryptographic service provider (CSP) Error

Post by Beth » Fri Mar 13, 2015 4:40 pm

I'm adding an additional post to add that if you get the error "Could not get public key from server" that similar instructions will apply.

1. Determine which account is being used by the Vault Service. The system started message in the Vault Server Log file will contain a line stating "Identity = USER", where user is ASPNET, SYSTEM, NETWORK SERVICE, IIS APPPool or the user that is being impersonated.

2. On the Vault server, go to the %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys folder. Make sure that the user specified above has read / write / modify permissions to the MachineKeys folder.

On new operating systems look for this directory:
C:\ProgramData\Microsoft\Crypto\RSA

3. If the problem persists after adding these permissions, stop IIS, and find a file that starts with "edb3...." in the directory mentioned earlier. Delete it, and then restart IIS. Then try to log into Vault.
Beth Kieler
SourceGear Technical Support

Post Reply