April 30, 2009 at 8:48 am
I have a 2 node active/active SQL Server 2008 cluster running on Windows Server 2008. I want to upgrade my instances from Standard Edition to Enterprise Edition; do I start the upgrade on the passive node of each instance or the active node?
May 7, 2009 at 12:28 pm
Thank you for the response. When I try to do the edition upgrade, I get this message:
The following error occurred:
Access to the path 'C:\Program Files\Microsoft SQL Server\100\License Terms\SQLServer2008_License_ENT_1033.rtf' is denied.
Error result: -2068119551
Result facility code: 1211
Result error code: 1
Please review the summary.txt log for further details
The summary.txt log just has the same message that access to the license file is denied. I'm running this as a Windows Administrator, my SQL service logins have full access to C:\Program Files\Microsoft SQL Server and subdirectories, and I've tried giving the Windows Group 'everyone' read & execute access to this license file but no luck. It occurs on both nodes of my SQL cluster. I'm using a legal Standard Edition instance that is working fine otherwise. Any ideas why the edition upgrade would fail with this error?
May 7, 2009 at 2:09 pm
where are you running the setup from CD, HDD, etc?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 7, 2009 at 10:12 pm
The DVD has been copied to the C: drive so setup is running from HDD.
May 8, 2009 at 2:55 am
have you tried running it from the DVD?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 8, 2009 at 11:25 am
Tried it - no change although it fills in the PID automatically so there's no chance of my typing in the wrong key. I did find the fix, however. My cluster is running 2 SQL 2008 instances and I had upgraded the less important one first to see what the upgrade did (no problems). This upgrade put the enterprise license file out there on the node and when the upgrade was attempted on the other instance, it couldn't overwrite it. Renaming the enterprise license file allowed the upgrade to proceed. Problem solved!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply