• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 392
  • Last Modified:

sql server 2008 installation on windows 2008 cluster

I am facing  a issue where sql server instalaltion abruptly  terminates at the end.
Its 2 node cluster.
Any help is appreciated.
Below attached the setup logs.
t.txt
0
venk_r
Asked:
venk_r
  • 6
  • 4
1 Solution
 
cyberkiwiCommented:
Hi there,

To have it working in a cluster, have you specified the SQL Server startup account to be NETWORK?  The normal LOCALSYSTEM or LOCALSERVICE cannot access the network.  If you have properly designed security, you can also use a domain account to run the SQL Server service.
0
 
venk_rAuthor Commented:
I have specified the  start up services to domain admin account.
0
 
venk_rAuthor Commented:
One more thing  I forgot to mention you is I am using mount points in the cluster
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
Beth KludtIndependent Business OwnerCommented:
I just went through this.  The abrupt termination with no meaningful explaination sounds like you are installing RTM on Win2008R2.  If that is the case you need to slipstream SQL 2008 SP1.  
http://support.microsoft.com/default.aspx?scid=kb;EN-US;955392
0
 
venk_rAuthor Commented:
The patch that you recommended seems to running only after the sql server installation.I cant do the sql installation.How would I run this without sql server in it.?
0
 
Beth KludtIndependent Business OwnerCommented:
I had to completely uninstall my failed installation.  Do this from setup.exe by going to Maintenence then choosing remove a node.  Once you have successfully uninstalled, make sure your disks haven't failed over to the other node, mine did.  if they did, let me know. There's a trick to moving those too.
Then download SQL Server 2008 SP1 and place the .exe on your C drive.  I put it in c:\install\sql2008.  I'll use that for the rest of my instructions.  
1.  Go ahead and run the SP1 .exe.  It will open the usual wizard and you follow the prompts.  it may reach a point where it tells you that there is nothing to upgrade or it may complete.  close or cancel as appropriate.  
2.  Create a folder for SP1 files: I used c:\install\sql2008\SP1
3.  Open a command window, cd c:\install\sql2008, then run this command which extracts the files into that new folder:  
sqlserver2008sp1-kb968369-x64-enu /x:C:\install\SQL2008\SP1
4.  then install SQL2008 using the command line and the following command which tells it to do a slipstream install using the files you just extracted:
setup /PCUSOURCE=C:\install\SQL2008\SP1
This will bring up the usual installation wizard.  When you get to the Summary screen make sure you see Action Install FailoverCluster(slipstream)
 
0
 
Beth KludtIndependent Business OwnerCommented:
Oh yes, you have to do the slipstream setup on every node of your cluster.
0
 
venk_rAuthor Commented:
I followed your instruction but at the end of the installation I am getting error "object reference not set to instance of an object" and finally terminates.
0
 
Beth KludtIndependent Business OwnerCommented:
that sounds familiar.  Here's a couple of additional issues I encountered:
1.  I had to Pre-stage the SQL Server clustered service account in AD.  Add new computer (SQLServerName) to the preferred OU container for computer accounts in the domain.  This is the name you associated with the IP for the instance and also the name you used in Instance Configuration\SQL Server Network Name during installation.  Then Open Properties for the new account and select Security tab.  Add.  In Object Types make sure Computers is selected. Type cluster name account (your cluster name with $ at the end) (this account was created when you installed your cluster) and grant it Full Control.   Click OK.
Right click new account again and disable account.  The problem here is that its actually the cluster name account that is trying to create the SQL Server Network Name account.  Of course, being a new account it doesn't have the privelege to do that.  Microsoft recommeded just pre-staging them.
2.  Mount points were an issue for me.  The service id can't write files directly to the mount point.  There must be a subfolder.  The disk one you designate as "root" is fine because the install creates a subfolder itself, but if you are putting the tempdb on a different mount point be sure to create a folder for it and use that.  The symptom for this is that it looks like your folder permissions keep getting reset so they don't inherit anymore.  
0
 
venk_rAuthor Commented:
Iam still getting the below error in the set up log and the installation fails.
2010-04-20 08:45:50.69 Logon       Error: 18456, Severity: 14, State: 11.
2010-04-20 08:45:50.69 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 192.168.2.86]
0
 
venk_rAuthor Commented:
Actually , The solution worked .Great!!
Thanks again
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now