Having an SSL certificate that does not match the server name or expired or is invalid for any other reason can cause this error.

You will receive the above error message when connecting to your SQL server.

Very annoying and hard to find especially if the server hasn't been started for a few weeks since the certificate was installed  ( it seems like the certificate usage is refreshed only when the SQL server service is restarted).

After a little searching, I found an article about this SQL error and how to solve it.

In our case we used a SelfSSL generated certificate.

Note that to fix the problem we had to delete certificates from:

Certificates (local computer)
  Personal
     Certificates

After deleting the certificate you need to stop and start the SQL server service.

There have been a lot of talk lately about Microsoft losing the battle for new technology and its place as a market leader.

But as it turns out in a bold secret move Microsoft decided to incorporate cutting edge and even futuristic technology into some of its more popular products.

The technology is of course very processor intensive and is not recommend for use on single core machines with less then 1GB of RAM.

One of the best examples of the level of innovation can be seen in Microsoft Outlook.

Apparently it is now possible for Microsoft Outlook to predict what emails you will receive in the next foreseeable future.

Using a 2GHz dual core machine with 2GB of RAM I was actually able to see what emails I would receive in the next 24hr:

With a triple quad core machine I could actually see until next week and with a small Beowulf cluster running Wine I could actually see beyond next month:

BTW, if you really want to reproduce this phenomena simply take your Outlook client machine clock back in time until your server is at least 1 day ahead in time.

No pun intended and 2 much beer...:)