http://blogs.technet.com/b/mscom/archive/2007/05/30/how-to-get-sql-to-accept-the-cert-or-a-day-or-two-in-the-life-of-an-mscom-debug-engineer-part-2.aspx(Mr. Cert’s side of the story) Some days, it just doesn't pay to get out of bed. Nevertheless the day described by Mr. Debug in A day (or two) in the life of an MSCOM Debug Engineer was not one of them for me. If you already had the chance to readen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/mscom/archive/2007/05/30/how-to-get-sql-to-accept-the-cert-or-a-day-or-two-in-the-life-of-an-mscom-debug-engineer-part-2.aspx#2843195Thu, 07 Feb 2008 13:21:33 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:2843195Craig<p>Excellent post.</p> <p>That tip on WinHttpCertCfg was exactly what I needed. &nbsp;All the MS documentation is based on the sql service running under a system account instead of a named one like it should be. &nbsp;Once I granted my service account rights to the cert, all was fine.</p> <p>Now to figure out why aspnet doesn't trust the certificate chain! &nbsp;(self-signed cert).</p><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=2843195" width="1" height="1">