THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | Join | Help
in Search

Aaron Bertrand

Aaron is a senior consultant for SQL Sentry, Inc., makers of performance monitoring and event management software for SQL Server, Analysis Services, and Windows. He has been blogging here at sqlblog.com since 2006, focusing on manageability, performance, and new features; has been a Microsoft MVP since 1997; tweets as @AaronBertrand; and speaks frequently at user group meetings and SQL Saturday events.

Your Denali installation will self-destruct in 5... 4... 3...

I woke up this morning fully intending to test a scenario on Denali CTP1. I was surprised to see that, after installing Windows Updates overnight and rebooting, my Denali instance was not running. I tried to start it from the Services applet, and received the following error message:

 

For search yumminess:

Windows could not start the SQL Server (Denali) service on Local Computer.
Error 1067: The process terminated unexpectedly.

So, this was another error message from Vague County, Washington. Off to the event log, where I immediately see Event ID 17051:

SQL Server evaluation period has expired.

<facepalm>

Of course. This was the first time I'd rebooted this particular server since installing Denali more than 180 days ago (as an MVP, I had access to the Denali bits some time before they were publicly released at the PASS Summit).

I haven't started yet, so I don't know what kind of hassle it will be, but I wanted to post another reminder that the evaluation editions of SQL Server software can be quite a pain to remove. Back in October, I posted about my horrible experience, and I am still receiving thank you messages today from people finding themselves in the same nightmare (scroll down to the most recent comments).

Unfortunately, Evaluation Edition does not give an easy way to directly determine when the instance was installed (or when it will expire). Now, I've complained about this umpteen times in the past, but my Connect item was closed as "Won't Fix" (please vote to change their minds). In the meantime, you can quickly tell if you're at or near the 180 day limit by checking the "Date created" property of the instance folder. As you can see, my Denali instance was installed about 185 days ago:

 

So, if you have an instance of Denali installed, and you're coming up on 180 days, be prepared to uninstall and either start over with CTP1 or sit on your hands for a while.  Because it doesn't seem like there is a new CTP publicly available yet (and you typically can't upgrade a CTP anyway, particularly to avoid a timebomb).

 

Published Thursday, April 21, 2011 1:04 AM by AaronBertrand

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

ALZDBA said:

180 days yet, and no CTP-2 ?! No warnings, just the timebomb.  Very narrow minded by MS indeed. :-((

April 21, 2011 1:01 PM
 

AaronBertrand said:

Johan, I agree. Sadly the prevailing wisdom is that CTP2 will not be released to the public in any form; the next bits you'll see will be CTP3. Why do I think that? Well, users have been reporting bugs against CTP2 on Connect for over a month:

http://connect.microsoft.com/SQLServer/feedback/details/651870/unable-to-create-open-upgrade-ssis-projects-in-a-sxs-denali-ctp2-installation-with-r2

They're supposed to be filing these bugs privately, but that's another story.

April 21, 2011 1:12 PM
 

Shawn Melton said:

That sounds like a PowerShell script with some type of countdown message :)

April 21, 2011 4:38 PM
 

AaronBertrand said:

Quick update: removal of the Denali CTP1 eval was quick and painless. Nothing like the craziness I encountered trying to remove the 2008 R2 eval.

April 21, 2011 5:18 PM
 

Robert said:

Why not plan ahead, and use a virtual?  

April 25, 2011 12:50 PM
 

AaronBertrand said:

Robert,

I am using all virtual. I don't have a single Windows installation that is on bare metal. But how does that help? Unless the virtual machine was used exclusively for testing Denali (which, in my case it is not), the software still expires.

Anyway, this post was intended for a wide audience, those who plan, those who don't, and those who forget. My previous experience with the 2008 R2 eval was enough to warrant this, because I had a heck of a time removing it once I discovered that it had expired AFTER the fact. Hopefully a little heads up will help others deal with this in advance as well...

April 25, 2011 1:56 PM
 

Aaron Bertrand said:

In case you missed my previous post, the CTP3 of SQL Server Code-Named "Denali" is now available. You

July 12, 2011 7:47 AM
 

Aaron Bertrand said:

Where is my graphical ShowPlan? Many of you on SQL Server 2008 R2 are experiencing a major annoyance

December 1, 2011 9:37 AM
 

Jeff Rush said:

Rolling back the system clock will work so you can start the services and upgrade to RC0

March 6, 2012 4:07 PM
 

Aaron Bertrand said:

Jeff, sure, but not everyone *can* roll their clock back (think group policy, etc). Also why would you upgrade to RC0 now? RTM was released today (at least the Eval and Express editions):

http://www.microsoft.com/download/en/details.aspx?id=29066

http://www.microsoft.com/download/en/details.aspx?id=29062

March 6, 2012 4:15 PM

Leave a Comment

(required) 
(optional)
(required) 
Submit

About AaronBertrand

...about me...

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement