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

Login failed

Hello all. I am running two instances (SQL Server-2000 and SQL Server-2005) on my workstation and I have domain admin rights in active directory. Yesterday I had to change my password in active directory. I have a cluster in which I can no longer connect to the virtual server with my credentials. I've deleted and readded myself in the primary servers logins, gave myself system admin rights and made myself owner of all of the databases. With the EM in 2000 I can connect as "sa" (Thank GOD) but not with my user name in active directory. The error that I get when I try and connect the database engine with my user name in 2005 is:

Cannot connect to DOCVS1
Login failed for user 'null'. Reason: Not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452).

With 2005 I can't even connect using the "sa" account with SQL authentication. Can someone help me resolve this? Thanks, Jordan.
0
JordanKingsley
Asked:
JordanKingsley
  • 8
  • 3
  • 2
  • +1
3 Solutions
 
Kevin3NFCommented:
Check the SPN in AD for that SQL Server....for a cluster there ought to be one for the virtual server name without TCP port number, and one with.

Have you tried a named pipes connection as a workaround?

Login failed for user 'null' means the credentials are getting stripped before you get to the SQL Server
0
 
JordanKingsleyAuthor Commented:
How do I check the SPN? (not an AD expert). In in AD, there isn't one for the virtual server. There should be two for DOCVS1? Can you help me with this a bit further kevin?
0
 
Kevin3NFCommented:
is it a cluster?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Kevin3NFCommented:
BTW....I don't know squat about 2005 :)
0
 
JordanKingsleyAuthor Commented:
LOL, yeah, it's a cluster. I tried the named pipes fix. That let me register the server but not connect.
0
 
JordanKingsleyAuthor Commented:
The server it's running on in the cluster is 2000. I was able to connect fine with 2005 up until I changed my password yesterday.
0
 
Eugene ZCommented:
Server Principal Name (SPN)

setspn -A MSSQLSvc/<FQDN> <SQL_Service_Account>
more:
SQL Server 2005 Books Online  
How to: Enable Kerberos Authentication Including SQL Server Virtual Servers on Server Clusters  
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
0
 
Eugene ZCommented:
BTW:
your NT account is not locked; and not Win services are running with your old password?
0
 
JordanKingsleyAuthor Commented:
Hello Eugene, I'm not sure which services you mean with my old password?
0
 
JordanKingsleyAuthor Commented:
(I'd just change my password back but the network is novell and you can't use the same one twice)
0
 
JordanKingsleyAuthor Commented:
I can connect to eight other SQL Servers with windows authentication and two are not letting me. They're all in the same domain.
0
 
imran_fastCommented:
>Yesterday I had to change my password in active directory

Try refreshing your active directory. Because usually it takes time to refresh to other servers.
0
 
JordanKingsleyAuthor Commented:
It's been refreshed and I'm still getting that error.
0
 
JordanKingsleyAuthor Commented:
Now out of the blue today it let me authenticate with my Windows account. Had to be something in AD. Thanks for all of your help and I'll split the points up.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 8
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now