December 8, 2003 at 9:23 am
Here is the situation...
I have numerous SQL Servers. All SQL2K w/SP2 and security patches. All report the same version number. All are set to use mixed mode security, although all our applications/users connect using NT authentication. All our servers reside in the same domain as do the users.
Our client machines are a mix of WIN2K and NT4. Our apps connect using either ADO, OLEDB, or ODBC. The servers are setup to listen on TCP, Shared Memory, and Named Pipes. Workstations are setup to communicate on TCP and NP.
Our primary production database server is NT4. We are looking to upgrade it to WIN2K. In order to do this, I must "failover" to the backup system during the upgrade (our business is 24/7). The backup system, being a mirror, is also NT4. When trying to failover this weekend, we got the:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
...error message from the apps while trying to connect to the backup system. The exact same apps work fine against production or any of our other systems. Meanwhile, I am able to connect to the backup server from Query Analyzer and EM with no problems.
Other things to note...
* The error seems to only occur when connecting from Win2K workstations. And some Win2K workstations also get the error under EM and QA.
* We are in the middle of a transition from NT4 to Win2K domain controllers. Could this be impacting our authentication?
* The backup server was recently a Win2K machine that was later downgraded to NT4. Could that be causing an issue somewhere?
I believe this problem to actually be outside of SQL Server itself, but it doesn't make it any less my problem nonetheless.
Thoughts?
Brian Glass
Sr. Database Adminstrator
Bombardier Aerospace
December 11, 2003 at 8:00 am
This was removed by the editor as SPAM
December 11, 2003 at 10:07 am
This is an issue with the token and credentials being sent by the client to the server. It appears (from what I've seen and dug into) to be related to Active Directory. I had one server that kept giving me this and after trying numerous things, I gave up. Sometime later it started to work with native connections again.
I'd call PSS on this one, especially in a mixed mode domain.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply