Home > Visual Studio > Visual Studio Error Importing Key Object Already Exists

Visual Studio Error Importing Key Object Already Exists

Note that it was not necessary to create a PFX; everything is done from the certificate store.Now, this is a horrible pain in the neck, because there are many little steps, Tuesday, January 02, 2007 11:56 PM Reply | Quote 0 Sign in to vote Finally fixed this one. I'm sure it was only about 16 private keys.... Enter the password for the key file to import the key file into the local crypto-store database for use." Even if you enter the correct password, the error persists and says "Error importing key", http://sortoutlookemail.com/visual-studio/visual-studio-2010-microsoft-jscript-runtime-error-object-required.html

After the upgrade from Vista to Windows 7 the permissions of the folder containing certificates C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys had changed. I'm on Vista SP1 with Visual Studio 2008 if that helps.   Cheers, Matt Thursday, May 29, 2008 3:44 AM Reply | Quote 0 Sign in to vote Not sure if Are there any OSes that verify program signatures before executing them? Subscribed!

Thanks in advance, Alun Jones Dec 27 '06 #2 P: n/a Alun Jones "graham"

I logged in as one of the users who also tried to work on the build process. one of them being switching on Vista UAC to test the app I am working on. thats right. Instead of changing the file permissions I ran VS.NET as administrator, which also resolved the key import problem.

Intelligence you can learn from, and use to anticipate and prepare for future attacks. Thanks in advance, Alun Jones Dec 21 '06 #1 Post Reply Share this Question 2 Replies P: n/a graham Alun, How many times have you run the key generation etc, I'm Is the word "like" a preposition or verb in "You made me like this." Riddle-Yet-Another-Riddle! https://forums.comodo.com/code-signing-certificate/visual-studio-2008-error-importing-key-object-already-exists-t30746.0.html Personally I preferred this method as there were 4 or 5 assemblies signed with the same .pfx file.

Skip the description (Next)8. Also tool KeyPal http://www.jensign.com/KeyPal/ can be useful in solving problems with certificate storages. Error importing key - object already exists. Using it "as is" (exported to PFX using certificate manager with all options except Export Private Key off), and using certutil, both cause errors.

Let me know if this was helpful to anyone! :) share|improve this answer answered Aug 27 '09 at 14:52 user134926 19129 Thank you so much!!! Get 1:1 Help Now Advertise Here Enjoyed your answer? Login. share|improve this answer answered Sep 9 '09 at 23:38 Tom Corelis 2,25062241 add a comment| up vote 0 down vote I too am currently having difficulty with this.

Regards, Nicola. 0 Comment Question by:NicolaT Facebook Twitter LinkedIn Email https://www.experts-exchange.com/questions/25127091/Error-importing-key-Object-already-exists.htmlcopy LVL 31 Active 1 day ago Best Solution byParanormastic Here's the 2 cmds I run for handling ours from Comodo http://sortoutlookemail.com/visual-studio/visual-studio-error-lookup.html However, I'm afraid that if I reboot again I'll start getting the error once more.   This is a proper code-signing certificate issued by Thawte, so simple re-creating it isn't an Share this:Click to share on Twitter (Opens in new window)Click to share on Facebook (Opens in new window)Click to share on Google+ (Opens in new window)Click to email this to a I kept getting an error – “Failed to install key pair–Object already exists” trying to run the following command: sn –I myfile.pfx VS_KEY_XXXXXX Of course, I have to import my files

Just tried it - clean install of Windows, clean install of VS2005, SP1, VSTO, then open and build the project. Now, when I run Build Solution, it prompts me for the password, when I enter the password, it throws this message at me: "Object already exists". You can still re… .NET Programming Rename and move Database and log to new volume in Exchange 2013/2016 Video by: Alan This video discusses moving either the default database or any http://sortoutlookemail.com/visual-studio/cannot-find-the-requested-object-visual-studio-2012.html I exported PFX file by explicitly marking it as Singing Key.

It turned out that the issue was because l didn't run VS as an administrator. Like this:Like Loading... The trick was to regenerate the .pfx file, but explicitly marking it as a signing key (the default is for an exchange key).  Like so: openssl pkcs12 -export -out MyKey.pfx -keysig

So it looks like this is someone calling a crypto function, getting a successful result, and _still_ calling GetLastError() to pull the "Object Already Exists" error out for display.

Notify me of new posts by email. The certificate was created using the Microsoft Base Cryptographic Provider to create the original certificate and it wouldn't work. Error in shell bracket test when string is a left-parenthesis Why does the sum of a partition of 1 not equal 1? Reply to this comment Petr Alexeev November 6, 2013 at 10:55 am Hello Sergey!

This re-createdthe certificate in the Personal store in certmgr, but now it's marked as a signing key, not an exchange key. Eating Skittles Like a Normal Person UUID is same from different strings Riddle-Yet-Another-Riddle! It is able to display list of key containers for the current user or for the machine. have a peek at these guys Have you tried doing this on a box that you didn't do the development on?

Could a similar routine be constructed using the "Strong Name" tool? Last modified Jan 12, 2007 at4:25AM GurliGebis I used this as my extension for generating my certificate: [ codesign_ext ] extendedKeyUsage = codeSigning,msCodeCom But I still get this error Last modified Using the OpenSSL fix gets rid of the error, but does not seem to sign the assembly. http://msdn2.microsoft.com/en-us/library/k5b5tt23(VS.80).aspx I assume thats what Visual Studio fails miserably to use.

Please click the link in the confirmation email to activate your subscription.