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

Visual Studio Error Importing Key Object Already Exists

Reply to this comment traviswhidden November 7, 2014 at 8:10 pm Thanks! Alun. ~~~~ Dec 28 '06 #3 This discussion thread is closed Start new discussion Replies have been disabled for this discussion. Starting Visual Studio with 'Run as Administrator' solved the issue. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are navigate here

Microsoft reserves all rights associated with the materials on this site. Why the key already exists, I don't know, nor have I found a way to remove it but I will update this question when I do share|improve this answer answered Jun What errors you got?2. I've posted an entry on my blog detailing the entire process.Garick Newtziehttp://www.nootz.net Thursday, January 25, 2007 7:37 PM Reply | Quote 0 Sign in to vote Check the comments on your

It's a third-party download? The assembly is a DLL which will be installed as an Outlook add-in, is written in C#, and was created by using the Outlook Add-in template from VSTO 2005. I'm not sure how the folder permissions could have been changed. If I try to build the project, the following error is listed immediately after the first appearance of the "Object already exists" dialog: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Micr osoft.Common.targets(1718,7): error MSB3321: Importing key file "codesign.pfx"

My AccountSearchMapsYouTubePlayNewsGmailDriveCalendarGoogle+TranslatePhotosMoreShoppingWalletFinanceDocsBooksBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages 419,004 Members | 2,237 Online Join Now login Ask Question Home Questions Articles Browse Topics Latest Top Members I had no problems using the Comodo cert last year just with this new one. Have you tried doing this on a box that you didn't do the development on? Wednesday, June 02, 2010 9:16 PM Reply | Quote 0 Sign in to vote Guys ..

I tried both the changes mentioned above (OpenSSL & certutil). Tuesday, January 02, 2007 10:06 PM Reply | Quote 0 Sign in to vote I tried that - the only errors that relate to private keys are "NAME COLLISION" on the thats right. https://forums.comodo.com/code-signing-certificate/visual-studio-2008-error-importing-key-object-already-exists-t30746.0.html Entries (RSS) and Comments (RSS) %d bloggers like this: Sergey Barskiy's Blog Software Development Thoughts Menu Skip to content AboutAboutContact Me Failed to install key pair–Object already exists Posted by Sergey

CONTINUE READING Join & Write a Comment Already a member? I was using a pfx file from our domain's certificate authority. That was valid at that time and it is still valid if you are still using these versions. Using the >OpenSSL fix gets rid of the error, but does not seem to sign the assembly.1.

Any ideas of what is wrong? click Enjoy. 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", This re-createdthe certificate in the Personal store in certmgr, but now it's marked as a signing key, not an exchange key.

Select Typical6. http://ndsman.net/visual-studio/visual-studio-next-error.php Open cmd, run signtool with the signwizard option: signtool.exe signwizard4. Why did the humans never use EMP bombs to kill the machines in The Matrix? Finally, I exported this certificate to a new .pfx file and used this one to sign my assembly (in Visual Studio 2008).

It asked me four times - once while opening, and three times while building - for the pfx file's password, and while it accepted the password without error on the first How many times have you run the key generation etc, I'm sure there are only so many spaces for private keys that can be generated. Get 1:1 Help Now Advertise Here Enjoyed your answer? his comment is here thanks a lot! –manulorenzo Jan 24 '12 at 9:33 add a comment| Did you find this question interesting?

I tried to delete the container, issuing the following command: sn –d VS_KEY_XXXXXX I got an error – “Container does not exist”. Browse to the obj\Release directory and select the EXE (NOT the exe in the bin directory) 5. Open the solution that contains both the application project and the installer project.2.

Thanks @andynormancx. –Derrick Oct 14 '13 at 13:41 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook

Also tool KeyPal http://www.jensign.com/KeyPal/ can be useful in solving problems with certificate storages. I've made a PFX file using pvkimprt.exe, the PFX works fine for signing my ClickOnce manifest; however, I want to use the same file for my "Sign the Assembly" part. Fundamental Isomorphism Theorem How could I have modern computers without GUIs? You still cannot see the keys installed under another administrator account.

Views Block Question Which planet does Leia represent in the New Republic? Copy from the obj\Release directory to the bin directory. 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 weblink This way I was able to get past the "object Already Exists" error.

I tried both the changes mentioned above (OpenSSL & certutil). Privacy statement Dev Centers Windows Office More... I faced this issue in VS 2008 on my Windows 7 machine and had to get rid of this error somehow. Am I missing an important step here?

Save your wife Why does MIT have a /8 IPv4 block? Cheers, Graham "sometimes no help is better than some help" Alun Jones wrote: Entering the password, and clicking OK, I get the dialog "Error importing key", "Object already exists". Skip the description (Next)8. 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".

one of them being switching on Vista UAC to test the app I am working on. Join them; it only takes a minute: Sign up Certificate problem - Error Importing Key “object already exists” after Windows 7 upgrade up vote 10 down vote favorite 2 I have Friday, December 08, 2006 10:43 AM Reply | Quote Answers 0 Sign in to vote Finally fixed this one. I created a new certificate to use the Microsoft Enhanced Cryptographic Provider and created the pfx off of that and it works great.

It's quick & easy. The manifest has this:Development machine: Vista Enterprise x64, MS Visual Studio 2008 Team / Database, UAC offTarget machine: Vista Ultimate x64, UAC onObviously, I have a Comodo code I'm sure I've hosed something. On building you get the following message error MSB3321: Importing key file ".pfx" was canceled.

openssl.org? Required fields are marked *Comment Name * Email * Website Notify me of follow-up comments by email. However, the EXE that is created is not signed -- right clicking the EXE, and selecting properties shows no Digital Signatures tab.