A delicious bug in the September update of SQL Server 2012 Data Tools
-
This post is about dates and certificates. On the 7th of October, 2013 I needed to install the September update of SQL Server 2012 Data Tools (I'll be using the acronym SSDT further). Imagine how surprized I was when after attempting to download something the installer failed claiming that the reason for the failure is a wrong certificate which is already out of a valid date range. I tried to google some solution, but the only thing that I found is a post from some guy which had the same problem. After some thinking I have come to the solution (just taste it): in order to install the stuff you have to correct a date on your PC to something close to the release date of that update! I used September, 20th. Wonderful, isn't it? Was it way too hard for the Microsoft guys to just ensure their certificate doesn't expire before they release another update?:confused:
lifecycle of a lifecycle of a lifecycle