January 30, 2012 at 9:45 am
One of my users was having issues connecting over the internal network. This just started, and he has already rebooted. I had no issues connecting, but thought to go ahead and restart the services just to be on the safe side.
I tried to restart SQL Server(MSSQLSERVER) via the configuration tool, but I received errors. It was stopped when I tried this the first time, but I was still able to connect. I thought then to simply restart everything related to SQL, and I was able to bring the SQL Server(MSSQLSERVER) service back up.
Now I try to login with across the network or on the server directly, and I am getting Login Failed for user 'Domain\Jarid'. (Miscrosoft SQL Server, Error: 18456)
My next thought is to bring down the server over all, but this is the only server my company has (yes, I heard the collective and excited, "WHAT! That is SOO not the way to do that! Split those out!"...needless to say, I am trying to talk my bosses into that, but until then this is what I have to work with). In short, restarting the server impacts everyone, and I am trying to find an alternative means of doing that. Thoughts?
[font="Arial"]“Any fool can know. The point is to understand.”
- Albert Einstein
"DOH!"
- Homer Simpson[/font]
January 30, 2012 at 10:18 am
Issue update:
I was able to isolate the login fails issue. There are 2 SQL Server(MSSQLSERVER) kind of instances on this server (one by the standard name, and one with our company's name). I stopped the standard name instance, and restarted the company name instance. Now I am able to login.
The original issue starting this still exists, and I now have the specific error message:
Cannot generate SSPI context. (Microsoft SQL Server)
This user was able to login until Friday. I have confirmed that no updates were made to the server or the user's system (they say, so take that as you will). The services refresh did not make an impact.
Both I and my sys admin are researching the Double Hop issue I've read about to see if that plays into this. Any other direction you can provide would be helpful.
[font="Arial"]“Any fool can know. The point is to understand.”
- Albert Einstein
"DOH!"
- Homer Simpson[/font]
January 30, 2012 at 10:22 am
Have you seen this article, http://support.microsoft.com/kb/811889?
Based on what you have described it doesn't sound like a double-hop problem because the user is connecting directly from their PC to the SQL Server, not to a web server that connects to the SQL Server.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply