September 18, 2010 at 6:22 am in Uncategorized by mikeresseler
On the forums, we got a notification from a user that he got the following error when trying to open the SQL Management Studio from DPM.
I had asked him to check if it was a licensed version and so it was. This intrigued me and I decided to check a few things. On my test environment, I received the exact same notification although DPM and SQL were still running. Because my test environment was an upgrade from beta to RC to eval, I figured that it had to do something with the upgrade, and the fact that the first instances of SQL were installed with evaluation versions.
Apparently, there are two versions of this problem.
1. Only the SQL Management Studio has expired. This is the problem when you did the upgrade path from the Beta 1 because that was still with SQL 2008 evaluation without SP1, and this was fixed in SP1. To fix it now, you can follow KB 971268 (http://support.microsoft.com/kb/971268/en-us)
2. The second issue is that SQL itself has also expired, which strangely leads that DPM continue to work, until the first time that you need to restart the SQL server or restart the server itself (everybody needs to patch right :-)) This is discussed in KB 2020443 (http://support.microsoft.com/kb/2020443)
So in the end, if you are facing or the Management Studio expiration, or after a restart the the SQL instance doesn’t start, then work with the solutions and it will be fixed
Thanks for the assistance guys