Build Error When Importing to Visual Studio 2012

I'm getting the following keyfile errors when I download the source through the svn link and try to build in VS2012 Pro on a Windows 7 64-bit Enterprise edition box:

Cannot import the following key file: StrongNameFile.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_72E5E1171EEDE02D

Cannot import the following key file: StrongNameKey.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_C099FEAA7C00A73E

I tried to import these pfx's manually into my key store, but they're password protected. Is there anyway around this? I'd like to be able to build the project myself so I can add better checkbox functionality.

Thanks Ian. I was able to build by creating my own pfx files and including them in the project. Unfortunately now when I run any unit test at all it completely crashes visual studio. The message in the event log is below from running Test_Pattern_Replacement().
Is this something you have seen before when you add your own key, or do you think I should log this in the issue tracker?

/**************************************************************/
The description for Event ID 0 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

I turned assembly signing off in both the DocX and the UnitTests projects. VS still crashes and the same error is written to the event log. DocX is running in 3.5, UnitTests is running in 4.0. I have a Windows 7, 64-bit Enterprise edition box. When I opened
in VS2012 the only thing changed was the Documentation\Documentation.shfbproj file, according to my migration report. All other files were untouched.

I'm wondering if you have access to the MSBuild file on the build server...? Maybe there's something a bit funny in there which needs to be done so the project will build itself non-crashing unit tests, since it looks like signing makes no difference.