Cumulative Update 3 and Clusters

#21

The issue is that there were no changes to our doamin or AD when this cluster
was put into place.

This problem only occurs iun our clustered environment. When running the
application in a non-clustered environment this behavior doesn't manifest
itself.

"Linchi Shea" wrote:

Quote:

I have not run into similar issues. I'd check if this coinsides with some
changes on your domain controllers/AD side. To a large extent, Windows
authentication is unware of the fact that the SQL instance is clustered.

Linchi

"A. Robinson" wrote:

We moved our environment from a stand aloone SQL Server scenario to a
clustered environment. Our cluster consists of two nodes, set up as
Active/Passive. Ever sine moving to this setup, we've been seeing some odd
behavior with regards to authentication.

In the past, everything worked just fine. But since moving to the cluster,
we are CONTINUALLY seeing the "Login not associated with trusted..." error
and the "SSPI handshake failed..." error. Before the cluster, we never saw
these.

I've heard from several people that there appears to be an issue with CU3
and clustered SQL Servers, and the only way to get these to stop is to appply
CU5.

Has anyone else experienced anything similar? If so, how did you address the
problem?

thanks!!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Cumulative Update 3 and Clusters

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

RE: Cumulative Update 3 and Clusters - 08-11-2008 , 10:08 AM