Are your results of `puppet module install simondaen/iis --debug --trace` similar to what the others were getting?
On Wed, Sep 18, 2013 at 1:52 PM, Samuel Huang <[email protected]> wrote: > Yeah I rebooted, and it still didn't work. > > > On Monday, September 16, 2013 1:40:34 PM UTC-7, Rob Reynolds wrote: > >> Yes, that is the one that I meant. I know you hate hearing this question, >> but did you reboot after you removed it (prior to module install) for full >> effect? >> >> >> On Mon, Sep 16, 2013 at 1:24 PM, Samuel Huang <[email protected]> wrote: >> >>> If what you mean by Machine store is the Local Computer, I just deleted >>> it from both Machine and Current User stores and still puppet module >>> install does not work. Here's a screenshot of it appearing in the Machine >>> store. >>> >>> >>> On Sunday, September 15, 2013 8:42:24 PM UTC-7, Rob Reynolds wrote: >>> >>>> Can you determine if the cert is also under Machine certificate store >>>> and not just the Current User certificate store? >>>> >>>> >>>> On Fri, Sep 13, 2013 at 1:27 AM, Samuel Huang <[email protected]>wrote: >>>> >>>>> I deleted the cert you mentioned *(thatwte-timestamping.png)*, but I >>>>> still have the same error everyone's been mentioning * >>>>> (module-install-fails.png)*. Any help please? >>>>> >>>>> Sam >>>>> >>>>> >>>>> On Sunday, August 18, 2013 7:59:04 PM UTC-7, Robert Redgwell wrote: >>>>>> >>>>>> For what it's worth, I had the same problem and figured out the >>>>>> particular cert on Windows 7 (64bit) that was causing the issue: >>>>>> >>>>>> ------------------------------******------------------------------*** >>>>>> ***------------------------------ >>>>>> [Subject] >>>>>> CN=Thawte Timestamping CA, OU=Thawte Certification, O=Thawte, >>>>>> L=Durbanville, S=Western Cape, C=ZA >>>>>> >>>>>> [Issuer] >>>>>> CN=Thawte Timestamping CA, OU=Thawte Certification, O=Thawte, >>>>>> L=Durbanville, S=Western Cape, C=ZA >>>>>> >>>>>> [Serial Number] >>>>>> 00 >>>>>> >>>>>> [Not Before] >>>>>> 1/01/1997 1:00:00 p.m. >>>>>> >>>>>> [Not After] >>>>>> 1/01/2021 12:59:59 p.m. >>>>>> >>>>>> [Thumbprint] >>>>>> BE36A4562FB2EE05DBB3D32323ADF4******45084ED656 >>>>>> ------------------------------******------------------------------*** >>>>>> ***------------------------------ >>>>>> >>>>>> I found it under Trusted Root Certification Authorities. >>>>>> After deleting that, I no longer had the module/cert issue. >>>>>> >>>>>> On Wednesday, 17 July 2013 07:54:02 UTC+12, Josh Cooper wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Jul 16, 2013 at 11:19 AM, Arno den Uijl >>>>>>> <[email protected]>wrote: >>>>>>> >>>>>>>> I thought i tried the debug and trace options but i this trace was >>>>>>>> new for me. I looked through the code and I think that it was caused >>>>>>>> by the >>>>>>>> fact that there were some certificates installed with the same name. I >>>>>>>> deleted some from my certificate store and now it runs correct. >>>>>>>> >>>>>>>> Thanks for the help. I do think that this can be an issue for more >>>>>>>> people. >>>>>>>> >>>>>>> >>>>>>> I didn't realize MS cert store could contain duplicates. We should >>>>>>> be more defensive of this, in general, to ensure the failure to add one >>>>>>> cert doesn't stop puppet from running: >>>>>>> >>>>>>> begin >>>>>>> add_cert(x509) >>>>>>> rescue OpenSSL::X509::StoreError => detail >>>>>>> Puppet.warning "Failed to add certificate >>>>>>> '#{x509.subject}'" >>>>>>> end >>>>>>> >>>>>>> Josh >>>>>>> >>>>>>> -- >>>>>>> Josh Cooper >>>>>>> Developer, Puppet Labs >>>>>>> >>>>>>> *Join us at PuppetConf 2013, August 22-23 in San Francisco - * >>>>>>> http://bit.ly/pupconf13* >>>>>>> **Register now and take advantage of the Early Bird discount - save >>>>>>> 25%!* >>>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Puppet Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to puppet-users...@**googlegroups.**com. >>>>> To post to this group, send email to [email protected]. >>>>> >>>>> Visit this group at >>>>> http://groups.google.com/**group**/puppet-users<http://groups.google.com/group/puppet-users> >>>>> . >>>>> For more options, visit >>>>> https://groups.google.com/**grou**ps/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>> >>>> >>>> >>>> -- >>>> Rob Reynolds >>>> Developer, Puppet Labs >>>> >>>> Join us at PuppetConf 2014, September 23-24 in San Francisco >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users...@**googlegroups.com. >>> To post to this group, send email to [email protected]. >>> Visit this group at >>> http://groups.google.com/**group/puppet-users<http://groups.google.com/group/puppet-users> >>> . >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >> >> >> -- >> Rob Reynolds >> Developer, Puppet Labs >> >> Join us at PuppetConf 2014, September 23-24 in San Francisco >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- Rob Reynolds Developer, Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
