8

I've been looking around on this problem and whilst I've found a few "solutions" it seems that a lot of these "solutions" are stumbled upon or cannot adequtely explain what really worked.

I've tried a number of the solutions but I'm still having issues.

I've created a .PFX within Visual Studio. TeamCity and the Build Agent are all on my local development machine so there isn't any other PC involved in my situation.

When TeamCity tries to build this project I get an error:

error MSB3325: Cannot import the following key file: name.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_6E76201C7E991E97

Everything is running under Local System Account both Team City Server and the TeamCity Build Agent.

So where do I install the certificate? I've opened MMC.exe and imported it into a number of "obvious places" such as the Local Computer Certificate Snap-In. I tried importing it into the Personal and Trusted CA roots but neither of those worked.

So where on earth do you put it?

Jammer
  • 9,969
  • 11
  • 68
  • 115

2 Answers2

3

My solution to this was to create a new user account and import the pfx file under that user account. Then configure the TeamCity build agent on the machine to use that user as it's logon. For more steps on changing the credentials the build agent uses, see this post

Community
  • 1
  • 1
Oxymoron
  • 1,380
  • 2
  • 19
  • 47
0

Certificate is installed as a MSCP container (so it's not installed as a normal certificate). Standard way is to use sn.exe but you can also use SnInstallPfx.exe

For more information, see the following blog article.

Dan
  • 778
  • 7
  • 18