Crypto error on first time installation

Question

I am trying to install Complete FTP on a 2012 R2 server

Nothing fancy, just double click the icon, next next next etc.

when it is generating the certficates it errors with the following. (note I've run the install on another of our 2012 R2 servers and it's just fine, both are supposedly the same template and certainly "look" the same. However, the server that isn't working is in our DMZ, but why would that affect the install?)

System.Security.Cryptography.CryptographicException: Couldn't acquire crypto service provider context.

   at EnterpriseDT.Mentalis.Security.Tools.X509CertificateGenerator.Create(Int32 keysize, String issuerName, CertificateSettings settings)

   at cyNedeGtiUs8wIiCcFI.nRvlu5G6tmu5OR5AAiX.ADns38UudNw(String , String , String , String , String , String , String , DateTime , DateTime , Int32 )

   at EFi8DY5MAmyhnAVku4d.vu9oK45U35iVFZm9bJt.c4qSvenQaV(IDbConnection )

   at EFi8DY5MAmyhnAVku4d.vu9oK45U35iVFZm9bJt.xZNSQ93npL()

   at EFi8DY5MAmyhnAVku4d.vu9oK45U35iVFZm9bJt.pkHS2ScapL()

   at mKYJxZADID8gIM7Crai.fkKZNuAXhZtF5ug8hL2.WPen0ayJrN(Object , DoWorkEventArgs )

   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Many thanks

Rich

Comments

This is usually a file permissions problem. The Local System user (that the service runs as) needs permissions to write to C:\ProgramData\Microsoft\Crypto\RSA and subdirectories. This is where Microsoft stores certificate keys.

As this is happening on install, it could be that your user account lacks these permissions. I assume you are installing as an admin, but perhaps it has different permissions on this machine?

---

Hi, Thanks for the quick reply.
I should have mentioned, after searching for a fix i'd found this issue and i gave "users" of the server full control to that folder and subdirectories but that didn't solve the issue. I also specifically gave my user full control rather than just accepting I was an administrator. The tail of the install log is

File: overwriteflag=0, allowskipfilesflag=2, name="cbrightclickprivate.png"
File: wrote 34328 to "C:\ProgramData\Enterprise Distributed Technologies\Complete FTP\Share\Help\en\images\cbrightclickprivate.png"
File: overwriteflag=0, allowskipfilesflag=2, name="cbsettings.png"
File: wrote 20442 to "C:\ProgramData\Enterprise Distributed Technologies\Complete FTP\Share\Help\en\images\cbsettings.png"
File: overwriteflag=0, allowskipfilesflag=2, name="cbshareprops.png"
File: wrote 14392 to "C:\ProgramData\Enterprise Distributed Technologies\Complete FTP\Share\Help\en\images\cbshareprops.png"
Exec: command="C:\Program Files (x86)\Complete FTP\Server\CompleteFTPBootstrapper.exe /m "C:\Program Files (x86)\Complete FTP\Manager\CompleteFTPManager.exe""
Exec: success ("C:\Program Files (x86)\Complete FTP\Server\CompleteFTPBootstrapper.exe /m "C:\Program Files (x86)\Complete FTP\Manager\CompleteFTPManager.exe"")
Aborting: "An error occurred while generating the configuration file.  Please contact support@enterprisedt.com for assistance."

I am fairly certain it isn't the applications fault, as it installed just fine when I tested it elsewhere, but hoped there may be a quick fix rather than ordering a new server build from the supplier.

Thanks again
Rich

---

I just saw it was 2012, it could be that this is the wrong folder, check  C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto

---

I'm also assuming you are installing 11.0.x

---

Hi,

I have 10.2, but it installed just fine on another 2012 server, also with no permission changes on any folder. We have just submitted the PO as our support had expired so when that goes through I will use the latest version. But as mentioned, it installed just fine on another 2012 R2 server so I have asked the server suppliers to confirm what is different about the the two servers.

I don't have C:\Documents and Settings\ on 2012 R2

Thanks

---

I have just installed the latest version as a test, and that went on fine. Very confusing as it works ok on other servers, just not this particular one.
Still, resolved now whatever the glitch was.

---

We did make a minor change after 10.2 with regard to this issue, so that may have resolved it.