May 1, 2009 at 12:54 pm
I have windows 2008 Enterprise Edition Installed on 2 servers and windows clustering is configured on that 2 servers as well. Now I want to install SQL server 2005 on that Windows 2008 cluster environment.
The installation failed a couple of time after i reboot anything, the error is the same saying “The installation was canceled by the user". ? The Installation options for SQL Cluster are all accepted and everything looks good till I get to the actual Installation. And the setup begins, I don’t know suddenly the status for all products went to red X state and it showing “The installation was canceled by the user".
I was stuck with this problem. i don’t think so their is some thing wrong on my installation.
Any help will be Highly Appreciated.
ddfg
May 19, 2009 at 10:56 am
I am having the exact same problem, is there anyone out there who can shed some light on this? i have tried everything to sort this out and I'm on to day 3. I have completely rebuilt my cluster and same problem occurs.
July 10, 2009 at 7:16 am
Hi AWU / Bruce
This may help ....... There is a new policy in windows 2008:
Network access: Do not allow storage of credentials or .NET Passports for network authentication = Enabled
Apparently SQL 2005 cluster installs needs the ability to cache credentials to run the remote task scheduler on the other side of the cluster. When this policy is enabled the install will fail.
To get around the problem do either of the following:
1. Make the following change in the registry on both nodes of the cluster and reboot.
KEY: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
VALUE: disabledomaincreds
set it to 1.
2. Or use gpedit.msc on both nodes to make the change with the gui and then again .... reboot both nodes.
- start/run/gpedit
- computer configuration/windows settings/security settings/localpolicies/security options
- right-click Network access: Do not allow storage of credentials or .NET Passports for network authentication, Properties / disabled
Cheers
Tim
July 10, 2009 at 7:38 am
yes you are right but the problem I had which i was able to fix was 2 things actually;
1. we got hit with the conficker virus and followed MS intructions on how to apply a GPO to stop the spread of the virus. Part of this GPO is to disable task scheduler creating new tasks so i had to reverse this GPO for 2 sql servers that were infected
2. Uninstall kb958644 which is the conficker patch.
Once I made these 2 changes everything worked perfectly.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply