January 20, 2011 at 1:45 pm
Hello all,
I hope you can help me, I've been 4 days trying this over and over. Have a fully working Server 2008-R2 two node cluster.
Has the roles for NET, File Server, and IIS, so the SQL 2005 Setup initial check passes. Then I proceed to install it as a failover cluster, and it all goes well, and just when it's about to end the setup process, I get this:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
Failed to set registry settings for server network libraries. The action is SetDefaults. The error is 11004 (The requested name is valid, but no data of the requested type was found.
)
------------------------------
I've googled this, have gone through so many KB, have reinstalled OS from scratch several times now, checked DNS, have setup host file entries, tried manual DNS entries, have the sqlservice account become a domain admin, and locally set to be able to log in as a service.
Any idea as to what could be causing this error? Thanks in advance for your help!
Also, the other error I've gotten while trying to install SQL 2005 cluster is this:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
The setup has encountered an unexpected error while Completing Commit. The error is: The parameter is incorrect.
------------------------------
If I install SQL2005 in each node as independant, it works just fine, so it only fails when trying to set a cluster.
Any idea as to what could be causing this error? Thanks in advance for your help!
Northenio.
May 16, 2011 at 12:51 pm
I am getting the same error. Is there any work around or solution for this problem?
May 17, 2011 at 1:39 am
In Windows Server 2008 R2 clusters, the SQL Server network name will need to be a computer object within Active Directory or the Windows cluster computer account will need to have rights to create objects within AD.
Win Cluster Network Name = AD computer name
SQL Server Cluster Network Name = AD computer name either manually created or created by the AD object associated with the Win Cluster Network Name for SQL Server Network Name
MSDTC Cluster Network Name = AD computer name either manually created or created by the AD object associated with the Win Cluster Network Name for MSDTC
Check out this article for more information on active directory account setup for win 2008 r2.
I personally haven't seen that error, however. Do you mind posting a copy of your Details file from the C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log\ folder?
Once the installer is successful, you'll want to install SP4 so that you can see it in the failover cluster manager (SP2 and above will work, but SP4 is what you should be installing from here on out if it is SQL 2005).
Regards,
Steve
May 17, 2011 at 1:48 am
I came across something same problem and able to resolve it by using SLipStream method.
See this link: http://support.microsoft.com/kb/955392
May 17, 2011 at 2:02 am
SG_Explorer (5/17/2011)
See this link: http://support.microsoft.com/kb/955392%5B/quote%5D
I believe the poster is trying to install SQL Server 2005 which does not have the Slipstream option.
May 17, 2011 at 5:29 am
Let me clarify what I am doing. This is a SQL cluster upgrade from 2005 to 2008 R2. I was able to install SQL 2008 R2 on the cluster successfully after uninstalling SQL 2005. After testing and everything checked out...they now want to uninstall it and re-install SQL 2005, just to show that we have a rollback/fall back stratergy. The cluster is Windows Server 2008 R2 and they dont want to reinstall windows at all. I tried over 20 times yesterday to install SQL 2005, each time fixing the problems that show up in the log. But as i fix one problem andother one craps up and right now the error i am getting is during final commit " the error is parameters don not match".
I dont know if stopping short of destroying the windows cluster and rebuilding it if there is a work around?
May 17, 2011 at 10:47 am
reido70 (5/17/2011)
I dont know if stopping short of destroying the windows cluster and rebuilding it if there is a work around?
So far as I know, you can't go back without destroying the cluster with a rebuild. Too many OS upgrades for SQL 2k5 (not to mention what it does to your DBs).
This is why I prefer parallel upgrades as opposed to in place upgrades.
May 17, 2011 at 1:53 pm
If you had a 2008 or above failover instance installed and then uninstalled everything, I would guess that there are portions of that install leftover that is causing issues installing 2005.
My honest recommendation would be to rebuild the cluster to ensure you have a stable system. Even if you were able to eventually get SQL Server 2005 back up and running, I wouldn't personally feel comfortable that the build will be free of problems going forward.
May 18, 2011 at 6:23 am
I also think that uninstall of an old SQL cluster and install of a new SQL cluster on the same Windows OS is not a safe option for a production machine. Running SQL Server on a cluster introduces new and interesting ways to totally trash your server compared to not using a cluster, and risk reduction has to take a high priority.
I have done a lot of testing with clusters as part of developing FineBuild. My normal approach is to set up two guest servers under Hyper-V, then take snapshots of each of them. I then cluster the servers and take another set of snapshots. I then install SQL Server.
To quickly retest an install, I typically apply a saved snapshot and manually delete the AD and DNS entries and re-format the quorum disk. Maybe 4 out of 5 times this works fine and I can do another install of SQL Server. The other time the cluster is broken and I cannot get a working SQL install. There no pattern I have found to predict what causes the cluster to break. When this happens I normally rebuild the guest machines as this is the only way to reliably get things working again.
If you are looking at a fallback process for a cluster install, my suggestion is that you always start with a clean install of Windows and then build the new cluster. There are just too many things that can go wrong if you try to reuse an existing cluster after doing an uninstall.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
May 20, 2011 at 2:27 pm
Thanks for all your advice, I was able to convince them to destroy the machine and install windows fresh.
We installed and it works like a charm now.
again, Thanks for the great advice.
Chris
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply