.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Issues with Kerberos and SQL Server failover-cluster

Posted By:      Posted Date: September 15, 2010    Points: 0   Category :Sql Server
I have a dual-instance SQL 2008 SP1 2-node Failover-cluster running on Server 2008 x64 SP2. SPNs have been manually created in AD for the service account running SQL Server (on both nodes).When the cluster nodes first boot up and the virtual groups come online, everything works flawlessly. I have linked server connections set up between the two instances of SQL server, with one instance running on each node. I can successfully make linked server connections from one instance to another from a third client PC, indicating Kerberos is working successfully, which is great!Problem is, this all stops working as soon as one of the SQL cluster groups fails over (or is taken offline, and moved to the other node). As soon as this happens, all authentications seems to fall back to NTLM. Of course, running both instances on the same physical node will work since Kerberos is not required for this. But as soon as an instance moves to another node - kerberos seems to be permenantly broken for that instance, even if moved back to its original node, until both nodes are rebooted again.One thing to note - the service account running SQL server is not a domain admin. This of course prevents SQL server from auto-registering the SPN upon startup and generates the following in the SQL log: "The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL

View Complete Post

More Related Resource Links

Any issues removing backup mount point cluster resources from SQL Server dependencies?

Win 2003, SQL 2005/SQL2008 64 bit enterprise failover cluster with 3 nodes and 6 instances. The mount points configured as cluster resources for the data/backup/logs. The entire cluster mount points are SAN replicated to a DR Site. But backup drives/LUNs are excluded from the replication. All the disk resources including backup LUNs are set to dependencies on the SQL Server server. The SQL Server is not coming on-line in the DR Site due to unavailability of the backup LUNs (failed resources). As per the documentation all the disk resources must be set to dependencies (http://support.microsoft.com/kb/835185). Thought it did not specifically mentions only Data/Log mount points and/or the backup LUNs as well. "The SQL Server 2005 resource depends on the SQL network name resource and the physical disk resources that hold its data. When mount points are being used together with the physical disks, each mount point must appear as a cluster resource. Additionally, each mount point must also be added as a SQL Server dependency. If only the root physical disks dependency is added and the mount points are not added, database corruption will occur on failover. Database corruption may also occur when SQL Server is restarted without failing over. "     What if I remove the backup LUNs from dependencies list. This will allow me to recover the SQL Server

SQL server 2008 failover cluster install

Hello all, Looking for the definitive answer with supporting documentation (link). Does a SQL server 2008 cluster have to be installed as or run as a domain service account or can local accounts be used?  I looked for a document that stated yes or no and could not find one. If anyone can provide info it would be much appreciated. Have all ready looked at these 2 links of interest. http://msdn.microsoft.com/en-us/library/ms143504.aspx#Service_SID http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx Thanks in advance,  

The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. S

Hello, I have a node of 2 servers of Win 2008 R2 Enterprise and trying to install a 2nd instance in a SQL 2008 R2 Cluster. I had SQL_INSTANCE2 previously installed that I removed from the two nodes. Now when I attempt to install it again from scratch, in setup GUI where I specify the SQL Server Network Name and enter the previously entered name "Server02", I get a failure in the setup with the following error message: "The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. Specify a different failover cluster instance name." How do I fix this problem, I don't want to enter a new name like "Server03" in order to proceed with the setup, because when I do enter "Server03" the setup does continue without an error message. So what am I missing? Do I have to ask the DNS administrator to see if there's an A record for "Server03" and have him delete it so that the setup works? Or the fix is by doing something else? I would appreciate any help. Thank you  

SQL server 2008R2 install on a server 2008 R2 failover cluster. Other resources won't failover to o

As the subject says, I've built a fresh install w2k8r2 and sql2k8r2 failover cluster. Sql works fine on the primary node, but when I test a failover it breaks. Specifically, if I were to stop the node1 cluster service (causing the cluster to switch to node2), windows changes the cluster DNS appropriatly and moves the shared storage just fine, but sql server doesn't failover.  Server Name, Disk Drives and Other Resources all go offline. I've verified that the advanced policies of the server name, IP, cluster drives all have both nodes checked as possible owners However, Other resources only lists node1 as a possible owner and there appears to be no way to add node2.  Under the Other resources, SQL Server and SQL Server Agent are listed. I'm sorta stumped, I've been combing the forums and have found similar issues, but nothing seems to explain why the two resources won't failover.

SQL Server 2005 Cluster failover issue

Hi All, I'm fequently experience Cluster failover issue. The cluster tries to failover and it fails back. Because of this the SQL server is getting restarted and this is a bugging issue during business hours. The following are the System event logs, Cluster resource 'SQL Server' in Resource Group 'Production' failed. The SQL Server Agent (MSSQLSERVER) service was successfully sent a stop control. The SQL Server Agent (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a stop control. The SQL Server (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a start control. The SQL Server (MSSQLSERVER) service entered the running state. The Cluster Service brought the Resource Group "Production" online.    The following are the application event logs, The client was unable to reuse a session with SPID 131, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired [sqsrvres] OnlineThread: QP is not online. The client was unable

SQL Server 2008 A/P Cluster Does not Failover



I have a SQL Server 2008 Enterprise Edition A/P cluster Server on Windows 2008. Recently One of the Clustered Disks Went OFFLINE. The SQL Resource which has Dependency on the clustered Disk also went offline. Shouldnt a Failover of the resources be happening to the second node, if there is a failure in the first node? Are there any settings which need to altered?




Hi, I have successfully installed the slip stream SQL SERVER 2008 Enterprise  sp1  on the two node fail over cluster.Now i need to implement the 2 node failover cluster installation again with the standard  edition of SQL SERVER 2008 sp1.

My question is do i  need to go for a slipstream installation with  standard edition also?

Failover Cluster Install on Server 2008 R2 (RC)

Has anyone successfully installed a SQL Server 2008 Failover Cluster on Server 2008 R2 (RC)? I'm getting stuck at the Instance Configuration screen, i get an error when trying to detect the SQL Server Network Name, here is the error:

The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'

I've setup a 2008 SQL Failover Cluster in Server 2008 SP1 without a problem.

single node SQL server 2008 R2 failover cluster is down

I install a single node SQL server 2008 R2 failover cluster (server 1) and add a node (server 2) on other server . Now , the first sql server (server 1) is down , server 2 still up so i have 1 server running When i install a new single node sql server cluster on a new server two error occur (failed) : - Microsoft Cluster service (MSCS) cluster verification errors. -Cluster shared disk available check Or can i change the server 2 to the single node sql server clutser to add new node ?

SQL Server Service does not start on SQL Failover Cluster Node B even though i turn off Node A (acti


We ahev setup a SQL Server (64-bit) Failover Environment which consist of a Node A (active) and Node B (passif).

The setup was completed successfully and was working fine since june 2008.

Our system administrators have reported that, after they made some changes during a maintenance week-end, the SQL Server Services don't start anymore on the node B (even though they turn off the active node A and make Node B as active). Our attempts to manually start those services arealways failing.

Can someone help?

Built For Speed: Develop Turbocharged Apps For Windows Compute Cluster Server


This article explores the services provided by Compute Cluster Server 2003 and the tools provided by Visual Studio 2005 that will help you develop High-Perfomance Computing applications.

Rich Ciapala

MSDN Magazine April 2006

Security Briefs: Exploring S4U Kerberos Extensions in Windows Server 2003


Building Web sites that provide services external to the corporate firewall is tricky. Usually it's not desirable to grant corporate domain accounts to external clients, and from a purely practical standpoint Kerberos does not work well over the Internet due to the typical configuration of client-side firewalls.

Keith Brown

MSDN Magazine April 2003

Migrating aspnet tables to dev server - having issues



We're trying to migrate a one of our apps to our dev server for testing and development, but we're having problems with the membership functionality. We can add users, but there seems to be a disconnect with roles. We can query the aspnet_users table and find the new user in there, but when we query the aspnet_usersinroles table, that user id is not present.

We're also unable to run the Roles.GetUsersInRole("somerole") method. It returns 0 records. When I run Roles.ApplicationName, it returns the correct name, so .NET should be passing the correct app name.

We're just a little baffled. If anyone could shed some light on what could be the issue, we would appreciate it.

Thanks! :)

Facing MSDTC related issues while archiving data from one database server machine to another databas

I have a question with respect to distributed transactions when carried out between two database server machines on the same network.   Consider there are two database server machines \SOURCE_DATABASE_SERVER\ and \DESTINATION_DATABASE_SERVER\. Now we have to archive the data from one database server to other database server.   Let us suppose the database server \SOURCE_DATABASE_SERVER\ is the live production database server and \DESTINATION_DATABASE_SERVER\ is Long term storage database server. Now data from \SOURCE_DATABASE_SERVER\ needs to be archived into the database server \DESTINATION_DATABASE_SERVER\.   So I have written a dynamic stored procedure which includes distributed transaction (begin Tran, commit Tran, rollback            Tran) coding in it.   Now initially when I executed the procedure, it gave some of the following errors   1) OLE DB provider "SQLNCLI" for linked server "\DESTINATION_DATABASE_SERVER\" returned message "The partner transaction manager has disabled its support for remote/network transactions.". Msg 7391, Level 16, State 2, Line 1 The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "\DESTINATION_DATABASE_SERVER\" was unable to begin a distributed transaction.    

SQL Server 2005 - Installation in Cluster Environment - "Service SQL Server Browser (SQLBrowser) fai

Windows Server 2003 R2 Enterprise Edition SP2 32-bit All updates and patches installed Two-node cluster environment configured. Cluster functions perfectly. Trying to install SQL Server 2005 Enterprise Edition (32-bit) as a clustered application. Installation proceeds fine until it begins to install the SQL Server Database Services product. Status window says "Starting Services. Service: SQL Server Browser". Error message is presented: "Service 'SQL Server Browser' (SQLBrowser) failed to start. Verify that you have sufficient privileges to start system services". SQL Server Service Account is in the Administrators group on both local systems, and is a domain account. Account used for the installation is in the Administrators group on both local systems, and is a domain account. Have cancelled out of the install and rebooted both servers numerous times. Exact same error continues to occur. Cluster is active and all resources are owned by node #1 - the node where SQL Server Installation is being run. In the event viewer, I see: Event ID: 10 Description: The SQLBrowser service was unable to establish SQL instance and connectivity discovery". I am also seeing errors like: Source: SQLBrowser. The SQL configuration for SQL is inaccessible or invalid. Source: SQLBrowser. The Configuration of the AdminConnection\TCP protocol in the SQL instance xxxxxx i

Stand alone server into Cluster Server...recomandations and Suggestion

Hi all I have Stand alone server(SQL Server 2000) on Win2k3(SP2). Now I want make as Cluster server. way I am thinking 1.I have create fresh Cluster Environment and move the Databases 2.Arrange SAN drive and move all Databases(Data files/Log files) to SAN drive and Add one more Node and Create Cluster. I am realy new cluster some body help me the Direction to move Standalone to Clusteer.   Thanks in AdvanceSNIVAS

Sql Server 2005 Cluster on EXS 4.0 VMWARE

Hi, I have this problem, i have sql server on Cluster with two nodes, the nodes are machine vmware, i was exs 3.5 and in december the esx was upgrade to version 4.  Of January the nodes present this problem:The node lost communication with cluster node 'SVRSQLN02' on network 'Servidores'.The node lost communication with cluster node 'SVRSQLN02' on network 'HeartBeat'.What can i do?
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend