“ASN1 bad tag value met” error when processing a certificate request in IIS 7

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Peter — Sun, 18 Jan 2009 23:06:46 GMT

Thanks a lot. Solution 2 solved my problem!

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Phil — Tue, 03 Feb 2009 03:17:57 GMT

When I attempt to run the certutil command on SBS2008 I get a permission error stating this command requires elevated priviledges to run. Administrator privs are required to run this command. Since the Administrator account is disabled/dissappears in SBS2008, I tried using the netword admin account and it gets the permissions error. Am I missing something

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Drew — Wed, 01 Apr 2009 18:13:48 GMT

Thank you. Solution 2 worked for me with a GoDaddy SSL cert.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Mads Nissen — Sun, 07 Jun 2009 18:15:48 GMT

The second approach using certutil (under elevated privs on win2008 web edition) is getting an access denied :

No key provider information

Cannot find the certificate and private key for decryption.

CertUtil: -repairstore command FAILED: 0x80090010 (-2146893808)

CertUtil: Access denied.

Guess I'll need to try option 1 then :(

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Harry Lee — Tue, 30 Jun 2009 00:56:28 GMT

solution 2 did not work with Godaddy without the following modifications on server 2008 on the last step

certutil -repairstore "My" "insert all of the thumbprint characters here"

Basically put quotes "My" and don't put the {} marks where the thumbprint goes. Thanks.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Matthew Kaney — Sun, 12 Jul 2009 18:20:47 GMT

I believe I have found the cause of the problem. If you are renewing an existing certificate (when I say renew I am not referring to the renew certificate function which most instructions warn against, but rather creating a certificate request from an existing certificate), when you complete the certificate request, you MUST right click on the existing certificate and select complete from the context menu. If you attempt to right-click in an open area of the window and select complete request from that context menu, or if you delete the original certificate first and therefore can only right click in the open area of the window, you will receive this message.

If you have in fact deleted the original certificate, then you must follow the first procedure outlined above to rekey the certificate. Then you will be able to right click in the open area and select complete from that context menu.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Steve Bishop — Tue, 14 Jul 2009 03:34:43 GMT

Option 2 worked for me as well except it didn't give it a name... just blank. Still worked.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Eric — Mon, 17 Aug 2009 18:37:49 GMT

When I try this I get prompted to enter a smartcard. When I cancel out of that (we don't use smartcards) the certutil command fails with an ACCESS DENIED message.

We don't use smartcards so I'm not sure why I'm being prompted for this.

Anybody know anything about this?

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Camelopardium — Mon, 21 Sep 2009 16:39:25 GMT

Thanks a ton. Solution 2 rocks.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Joel Carlson — Sun, 27 Sep 2009 08:57:46 GMT

Same here, thanks so much for Solution #2 - you saved a lot of headache and downtime!

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Nick Seibert — Tue, 29 Sep 2009 21:18:32 GMT

Many thanks for this solution. #2 worked perfectly for me.

Also, even though the Name for the cert is blank in IIS, this can be remedied through the MMC.

start -> run -> mmc -> File -> Add/Remove Snap-in -> select Certificates etc.

Then go to Certificates -> Personal -> Certificates -> select the desired cert, right click, properties -> set a friendly name. Easy.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Paul — Fri, 23 Oct 2009 12:52:47 GMT

I tried option 1 first, that did not work. Then tried option 2 which did work. Thank you.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Vlad — Tue, 24 Nov 2009 14:35:44 GMT

Thanks a lot! # 2 worked great!!!!

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

james knight — Wed, 25 Nov 2009 02:38:19 GMT

awesome my friend.. thank u so much... really option 2 was the one that worked for me. also on another forum they had said that copy from current to local account but that didnt work for me as the certutil command would complain that it could not find the certificate and private key for decryption. By doing the add-in and guiding to the .cer file, cert util worked fine...

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Richard S — Sat, 28 Nov 2009 10:33:33 GMT

Amazing!! Option 2 worked for me as well!

Thanks again!

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Madrooki — Wed, 02 Dec 2009 15:33:21 GMT

Thank you! Solution 2 worked a treat!

Wasted so much time with this rubbish until I saw your blog.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Charlie Messerly — Fri, 11 Dec 2009 19:31:27 GMT

Thanks Option 2 did the trick!!! This solved my problem of installation of GoDaddy SSL Certificate on I1S 7.0 with response ANS1 bad tag in cert enroll.

re: “ASN1 bad tag value met” error when processing a certificate request in IIS 7

Scott — Tue, 15 Dec 2009 00:50:12 GMT

I couldn't get either option to work but I managed to export the certificate to a .PFX (with the private key) and import it to IIS7 on the same box.

GoDaddy were no help whatsoever with their automated responses.