"Evaluation period has expired..." Error Will Require Uninstalling SQL Server 2008 R2 Due To Evaluation Edition
My SQL server was working fine since yesterday and suddenly i got this error , which is "Evaluation period has expired...".I just tried to find some solutions online and i found some blogs on that but i keep on getting different errors while following those steps,Some of this steps that i have written are those that i have followed from someones blog,so i have taken it as it is from that,but whatever situation i have faced that i have added to them :-
Today I spun up a rather aging VM so that I could take some screen shots from the 2008 R2 version of Management Studio.
When I clicked on my shortcut, I received this error:
For searchability, here is the text (with an actual clickable link, imagine that):
---------------------------
Microsoft SQL Server Management Studio
---------------------------
Evaluation period has expired. For information on how to upgrade your evaluation software please go to http://www.microsoft.com/sql/howtobuy
---------------------------
OK
---------------------------
Of course what this meant was that, for this particular VM, I had installed an Enterprise Evaluation instance before the RTM bits for Developer Edition were available. And clearly this happened more than 180 days ago, and I forgot about it.Microsoft SQL Server Management Studio
---------------------------
Evaluation period has expired. For information on how to upgrade your evaluation software please go to http://www.microsoft.com/sql/howtobuy
---------------------------
OK
---------------------------
If you go the link (which ends up at http://www.microsoft.com/sqlserver/en/us/default.aspx), there isn't really any information about converting evaluation software to licensed software (even if I already have licensed bits in hand). In fact there is not really any information about Evaluation Edition at all, except for an offer to install a second trial instance on my machine. I'm trying to remove one, but thanks anyway.
So the first thing I do is to install a real, licensed version of SQL Server 2008 R2 Developer Edition. I figure, if anything, it will at least give me a functional Management Studio again, even if I have an outdated Evaluation Edition engine lying around. Nope, I run through install, and when I try to launch Management Studio, my evaluation period has still expired. I plead to #sqlhelp on twitter, and I'm told I need to remove all of the 2008 R2 bits. This was the first time I'd had any reason to uninstall 2008 R2; at my previous job, we had only just migrated to 2008 in production late last year. I guess I should test cleanup more often.
Now, removing SQL Server 2008 R2 turns out to be a much bigger challenge than you might expect. Sure, you can go through the Control Panel and uninstall all of the components individually, but this is a hassle, and it still might not work very smoothly. To clear a path, I've been uninstalling applications that might be related (e.g. Visual Studio), and even applications with no hope in hell of being related: Office 2010, Flash, Windows Live "Essentials"... I even uninstalled an instance of SQL Server 2008 (not an eval), and when I tried to remove the setup support files, I received this warning:
Why on earth are the R2 Common Files dependent on SQL Server 2008 Setup Support Files? And further to that, I'd like to know why, when I clicked No on this dialog, it seemed to remove the SQL Server 2008 Setup Support Files anyway. It turns out there is some flag that removes the entry from the Programs and Features list, even if you don't go through with the uninstall. All was returned to normal when I closed the window and opened it again. Anyway, let's see what happens when I try to remove R2 via the Control Panel. I right-click the item in the list (and as you can see, "the list" is pretty short - and never mind the blurred out entries, I'll talk more about those soon, and they aren't related to R2):
When I choose Uninstall/Change, I get this box, and I click Remove of course:
When I click Remove, I get the Setup Support Rules dialog (just like I do for a new installation), and then when I click OK, I get this lovely dialog (I trimmed it so I wouldn't have to shrink it, but you get the gist):
Why does this not seem like it will end well?
Because according to the dialog, nothing is going to be removed (usually you see actual features with checkboxes). I should not even be able to see a Next > button. But for fun, I'll click it anyway, since my only other option at this point is to Cancel. I click Next > a couple of times, then a big shiny Remove button, and then after several seconds I get another even more lovely dialog, indicating that the uninstall has crashed:
And again for searchability (typo and all):
TITLE: SQL Server Setup failure.
------------------------------
SQL Server Setup has encountered the following error:
No feature were uninstalled during the setup execution. The requested features may not be installed. Please review the summary.txt logs for further details.
Error code 0x84B30002.
------------------------------
OK
------------------------------
SQL Server Setup has encountered the following error:
No feature were uninstalled during the setup execution. The requested features may not be installed. Please review the summary.txt logs for further details.
Error code 0x84B30002.
------------------------------
OK
------------------------------
At this point I've spent more time on this than I would have if I had just built a brand new VM and. But I was determined to see it through. So I finally gave in and decided to go the msiexec.exe /x route. I located all of the R2-related GUIDs in the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ Here is one example:
So I went through the entire list in uninstall folder, and saved the following commands to a batch file: (make one file with .bat extension that we can run by double click on it and we can add content in that by right click on it and edit)
rem DisplayName
msiexec /x "{guid}"
msiexec /x "{guid}"
The above formula means that , i have go through all folders under uninstall folder and take DisplayName and UninstallString from folders whose UninstallString start from “MsiExec.exe /I”. And I also added one that wasn't in the GUID list; there was a key under Uninstall called "Microsoft SQL Server 2008 R2" with the following properties:
Here is what my final .bat file looked like. You'll note that I put the Setup Support Files last. Also please note that your set of GUIDs may be different than mine... I'm just listing what I did as an example: rem SQL Server 2008 R2 Common Files
msiexec /x "{234F6B0D-10AE-4BB7-B2F3-E48D4861952D}"
rem SQL Server 2008 R2 Common Files
msiexec /x "{36F70DEE-1EBF-4707-AFA2-E035EEAEBAA1}"
rem SQL Server 2008 R2 Database Engine Shared
msiexec /x "{A2122A9C-A699-4365-ADF8-68FEAC125D61}"
rem Microsoft SQL Server 2008 Setup Support Files
msiexec /x "{C0C690C8-F335-4BA4-A2AD-675EAD1DFA90}"
rem SQL Server 2008 R2 Database Engine Shared
msiexec /x "{C942A025-A840-4BF2-8987-849C0DD44574}"
rem Microsoft SQL Server 2008 R2 (64-bit)
msiexec /x "{20E42995-BBE9-4697-8394-FCDC4338706B}"
rem Microsoft SQL Server 2008 R2 Setup (English)
msiexec /x "{C3E48238-5FA0-4C82-9509-36D47E371A29}"
rem SQL Server 2008 R2 Common Files
msiexec /x "{36F70DEE-1EBF-4707-AFA2-E035EEAEBAA1}"
rem SQL Server 2008 R2 Database Engine Shared
msiexec /x "{A2122A9C-A699-4365-ADF8-68FEAC125D61}"
rem Microsoft SQL Server 2008 Setup Support Files
msiexec /x "{C0C690C8-F335-4BA4-A2AD-675EAD1DFA90}"
rem SQL Server 2008 R2 Database Engine Shared
msiexec /x "{C942A025-A840-4BF2-8987-849C0DD44574}"
rem Microsoft SQL Server 2008 R2 (64-bit)
msiexec /x "{20E42995-BBE9-4697-8394-FCDC4338706B}"
rem Microsoft SQL Server 2008 R2 Setup (English)
msiexec /x "{C3E48238-5FA0-4C82-9509-36D47E371A29}"
In above list they have listed “SQL Server 2008 R2 Common Files” with msiexec /x but i find all with msiexec /I so i have removed them but in this command i have written msiexec /x and “{guide from msiexec /I}”
Running through these, I had several that returned a dialog about an unexpected error, but I ignored those and plowed through. When I was finished, I ran the batch file again, and every line item raised this dialog:
This is a good thing; it smells like I'm almost home. So - finally - I try to run SQL Server 2008 R2 setup again. To avoid some wasted time, I install only the Management Tools on my first run. Though, if I'm being honest, even installing just the client tools takes several minutes. Precious, Monday Night Football minutes.
After doing all above things I was able to uninstall sql server but when i rerun the setup again to install sql server i got an error once again : -
---------------------------
Rule Check Result
---------------------------
Rule "Performance counter registry hive consistency" failed.
The performance counter registry hive is corrupted. To continue, you must repair the performance counter registry hive. For more information, see http://support.microsoft.com/kb/300956.
---------------------------
OK
Rule Check Result
---------------------------
Rule "Performance counter registry hive consistency" failed.
The performance counter registry hive is corrupted. To continue, you must repair the performance counter registry hive. For more information, see http://support.microsoft.com/kb/300956.
---------------------------
OK
For that follow the steps given below :-
This may mean that the value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib under Last Counter and the last number value in Counter under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 are not the same. The same also for Last Help and Help.
In this example, 4720 is the number in both Last Counter and the last counter value. However, in my case my HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 looks like this:
How Do You Solve this Problem?
This fix only applies if HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 has no values and you can not add any.
009 is the English Locale ID. You may have this problem with another locale where you have no values and cannot add any either. The same fix will apply. I am trying to install on a virtual differencing disk that I have run NewSID against.
I found myself in the Microsoft Forums (see reference #5), but no one had figured out how to fix my particular problem. One person came close but wasn't quite there. So I started searching for how to fix my performance counter problem. Isn't it awesome that things that you don't really care about sometimes become issues with things you do?! I found the solution and I wanted to share. I found that I had disabled performance counters and to have the Counter and Help registry values, I only needed to fix that and reload all of my counters.
Steps to Resolve Performance Counter Issues
1. Back up your registry.
2. Enable Performance Counters: Check the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib to see if you have the key Disable Performance Counters and it is set to 1. If so set it to 0. This should now allow you to build your Counter and Help registry items following the rest of the instructions. (NOTE: You will not find this in any link I have referenced. This is the piece every set of instructions was missing.)
3. Then you may or may not need to rebuild your performance counters (see reference #1). Try to see your performance counters (step #4 below). If you can't see any or you just see numbers, you will need to rebuild your performance counters. If you have Windows 2003, you can run the command line and put in these two commands:
cd %systemroot%\system32
lodctr /R
lodctr /R
4. You know this has worked when you open your performance counters (Control Panel -> Administrative Tools -> Performance) and try to add and actually see items for your computer:
5. Try your install again.
6. If that doesn't work, you need to perform an in-place upgrade of Windows (see reference #4). Then follow the instructions above to rebuild the performance counters. You will also need to re-install all service packs for Windows after you do this. The good news is that you don't lose your applications at all.
7. Once you have completed this, try to install the application you were originally trying to install. In my case this is the monolithic SQL Server 2008.
But here i face another problem that when i click on 009 folder i got one another error
[Window Title]
Error Opening Key
[Content]
009 cannot be opened.
An error is preventing this key from being opened.
Details: Access is denied.
[OK]
Error Opening Key
[Content]
009 cannot be opened.
An error is preventing this key from being opened.
Details: Access is denied.
[OK]
- You have to run RegEdit as Administrator
- Right Click on the inner most folder for that you want to open
- select permissions from the context menu
- In the permissions dialog, click the advanced button.
- In the advanced security settings dialog switch to the Owner tab
- I assume your usercode is a member of the local Administrators group
- Click the Replace owner on subcontainers and objects box.
- If Administrators is NOT the owner, select it in the change owner to box...press Apply...OK.
- You are now back at the Permissions dialog box.
- Select Administrators and give them Full control by selecting the Full Control checkbox in the Allow column...press Apply ... Ok
And Here I got one more error list :-
First one is
And still if m trying to change permission i just keep on getting above error on every step and finally when i m trying to change owner by clicking on apply, i get error given below :-
And to resolve this follow steps given below :-
- to be able taking the ownership, you should logged in with administrator privileges. the easiest way is to enable the built-in and hidden super administrator account.
- goto start menu, find the icon to open cmd -don't open/run it-, right click on it->run as administrator.
- then on the cmd console, type : net user administrator /active:y
- press enter. if everything ok, there should be prompted: ... successfully.
- logoff windows. you should see the Administrator account. it usually has no password.
- login using administrator, then you can take the ownership on most files including the registry key















No comments:
Post a Comment