Cannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'
Cannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'
Cannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'
Re: Cannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'
I was running into this problem as well.
I was able to resolve the issue by running
`sn -i ` (*installs key pair into a named container*).
`sn` is usually installed as part of a Windows SDK. For example `C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\sn.exe`. Most likely this location is not on the search path for your standard environment. However, the "Developer Command Prompt" installed by Visual Studio adds additional information that usually includes the correct location.
Based on your post that would look like
**`sn -i companyname.pfx VS_KEY_3E185446540E7F7A`**
This must be run from the location of your PFX file, if you have the solution loaded in VS 2010 you can simply right click on the pfx file from the solution explorer and choose Open Command Prompt which will launch the .net 2010 cmd prompt tool in the correct directory.
Before running this sn command I did re-install the pfx by right clicking on it and choosing install however that did not work. Just something to note as it might be the combination of both that provided the solution.
I was able to resolve the issue by running
`sn -i
`sn` is usually installed as part of a Windows SDK. For example `C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\sn.exe`. Most likely this location is not on the search path for your standard environment. However, the "Developer Command Prompt" installed by Visual Studio adds additional information that usually includes the correct location.
Based on your post that would look like
**`sn -i companyname.pfx VS_KEY_3E185446540E7F7A`**
This must be run from the location of your PFX file, if you have the solution loaded in VS 2010 you can simply right click on the pfx file from the solution explorer and choose Open Command Prompt which will launch the .net 2010 cmd prompt tool in the correct directory.
Before running this sn command I did re-install the pfx by right clicking on it and choosing install however that did not work. Just something to note as it might be the combination of both that provided the solution.