Comments for kvantum.ca

Comment on SQL 2008 on Win2k8 Cluster doesn’t start on failover by Kerberos, SQL Server 2008, Windows Server 2008 | DataRealized – The Blog

Tue, 04 Jan 2011 17:15:26 +0000

[...] it’s for a handful of well-know reasons such as these : Resource #1 | Resource #2 | Resource #3 | Resource #4 … each of these provided a great deal of insight, but none of them resolved [...]

Comment on SQL 2008 on Win2k8 Cluster doesn’t start on failover by The Geekery » SQL cluster failure, and name changes…

The Geekery » SQL cluster failure, and name changes… — Sun, 19 Sep 2010 02:31:03 +0000

[...] some searching I stumbled across this post who seemed to be having a very similar issue. This hinted to an issue with the services rejecting [...]

Comment on SQL 2008 on Win2k8 Cluster doesn’t start on failover by Kerberos, SQL Server 2008, Windows Server 2008 « Data Realized – The Blog

Wed, 14 Jul 2010 22:40:34 +0000

Comment on How to read a dictionary by Tim Burrows

Tim Burrows — Thu, 03 Jun 2010 16:23:28 +0000

ROTFLOL
Really? Are you serious?
Come on you’re pulling my leg. You can’t believe all that…can you?
Whoose putting you up to this.

Comment on SQL 2008 on Win2k8 Cluster doesn’t start on failover by Yo Voy En Bici

Yo Voy En Bici — Fri, 30 Apr 2010 08:38:35 +0000

Another fix:

For the second generic command line for establishing the SPN:
setspn –a MSSQLSvc/FullNetworkName:InstanceName dom:port dom\SQLServiceAccount
It must be:
setspn -a MSSQLSvc/FullNetworkName:port dom\SQLServiceAccount

Comment on SQL 2008 on Win2k8 Cluster doesn’t start on failover by Yo Voy En Bici

Yo Voy En Bici — Thu, 29 Apr 2010 08:48:34 +0000

Looking for the same problem on the Internet, I was directed to this site. SQL 2008 sometimes failed, but not if started manually, the cluster was not able to see if it was up.

The problem is that when SQL is clustered you must set the SPN (Service Principal Name) statically and not allow the SQL service to set them, especially if there is more than one domain controller.

You can find more information about this at http://blogs.msdn.com/dataaccesstechnologies/archive/2010/01/06/how-to-grant-readserviceprincipalname-and-writeserviceprincipalname-rights-to-sql-server-service-start-up-account-without-using-adsdiedit-tool.aspx

I took some time to fix it. Here my solution:

Stop the affected instances. Then deny the permission to write SPN to the service account you use for starting SQL. You can do it by using Adsiedit.msc tool and navigating to Write servicePrincipalName Properties in the advanced security tab and selecting SELF for the SQL Service Account you use or by using similar command:

dsacls CN=ServiceAccount,OU=”The OU chid”,OU=”The first OU”,DC=dom,DC=com /D SELF:WP;”servicePrincipalName”

Be sure SQL service account is not member of domains administrators or member of another group that can write SPN or overwrite the changes you do.

Now setup the SPN for your clustered instance of SQL 2008 by executing these two commands:

setspn –a MSSQLSvc/FullNetworkName:InstanceName dom\SQLServiceAccount
setspn –a MSSQLSvc/FullNetworkName:InstanceName dom:port dom\SQLServiceAccount

For example:
setspn –a MSSQLSvc/myvirtualmachine.mydom.com:SQLInstanceOne mydomain\SQLAccount
setspn –a MSSQLSvc/myvirtualmachine.mydom.com:25431 mydomain\SQLAccount

Once the SPN’s are replicated on all domain controllers you should bring up online correctly your SQL Instances from the Cluster Administrator tool. Be sure the SQL service account has access to the databases by adding it to the security tab, if not SQL Agent will not start.

Hope this help to all those with the same problem but don’t find the correct solution on Internet.

Por un mundo mejor, usa la bici para moverte.

Pour un monde meilleur, utilise le vélo pour se déplacer.
Per un mondo migliore, usa la bici per muoversi.
Für eine bessere Welt, nutzt das Fahrrad zu bewegen.

For a better world, use the bike to move yourself.

Edit: Fixed the link. -admin

Comment on SQL 2008 on Win2k8 Cluster doesn’t start on failover by Tweets that mention SQL 2008 on Win2k8 Cluster doesn’t start on failover | kvantum.ca -- Topsy.com

Sat, 10 Apr 2010 21:22:45 +0000

[...] This post was mentioned on Twitter by dsfnet. dsfnet said: Does anyone know what DisableLoopbackCheck does? This article http://bit.ly/dw9WGY states it can fix a problem with SQL failover. #sqlhelp [...]

Comment on XBMC killed by kernel update on Acer Revo by admin

admin — Mon, 29 Mar 2010 16:12:41 +0000

Wait… I missed the last part of your post first time around. Are you actually getting the error?
Do startx, then run xbmc from the shell.

Comment on XBMC killed by kernel update on Acer Revo by admin

admin — Mon, 29 Mar 2010 04:49:35 +0000

XBMC was depending on glxcreatecontext. Driver reinstall fixed it. Symlink finished the step that driver install forgot to do.
So in short, yes, xbmc was up and running after just those steps

Comment on XBMC killed by kernel update on Acer Revo by rothgar

rothgar — Sat, 27 Mar 2010 20:40:50 +0000

This fixed X starting but did it also fix XBMC loading? I am having the same problem but thought I would ask if that was the solution for XBMC as well. I just did a kernel update too and I am assuming the GLX module isn’t getting loaded properly with the new kernel.