October 12, 2009 at 12:50 pm
Got a call this afternoon about a production server that appears to be down and out.
server has been running fine for the last 2 years and has a home grown application on it. The app failed as it couldn't authenticate to the server via Windows Auth.
SQL auth works fine.
No changes have been made to the server config. I reviewed the Network protocols, and the authentication mode is set to mixed.
Only thing that was apparently done to the server was it had 'SCOM' installed on it awhile ago and that was apparently uninstalled today.
The issue in regards to Windows auth appears to have happened within the last 48 hours as it wasn't being monitored over the weekend.
I can authenticate to the server via remote tools, but cannot authenticate to the SQL server via Windows Auth and I am local admin on the server and the Builtin\Administrators is still valid on the server.
I can also add windows logins to the server via enterprise manager so that would tell me it can connect to the domain controller (at least I think)...
Writing this in a hurry so I appoligize in advance for sentence fragments and ramblings...
Any recommendations would be appreciated.
Thanks,
Lee
October 14, 2009 at 1:22 am
what is the error Text while connecting thru windows auth.?
Sanket Ahir
Don't run behind the success, Try to be eligible & success will run behind u......
October 14, 2009 at 1:32 am
I would check the windows logs to see if anything is apparent, it might be an concidence about the scom uninstall, but i would check if the uninstall was successful.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
October 14, 2009 at 9:49 am
The error message is as I stated in the title...the description is
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
The issue timeline starts around 8 a.m. where things don't connect via windows auth.
The SCOM install was undone around 11 a.m. so after the problem started from what I am told.
SCOM existed previously and was only removed apparently at the request of someone due to resources being hogged by the agent.
I went through the event log on the server initially and cannot find anything of substance that points to any one issue.
You can see a security entry for the authentication failure but it doesn't give any indication as to why.
I am a little troubled by the fact that I can log into E.M. with the sa account or a SQL account, add a new user, search A.D. and find valid users, add them as an account but the account cannot authenticate to the domain via windows authentication.
To top it off the application is over 10 years old ( developed for the windows NT 4.0 platform), has NO error handling whats so ever and no documentation that is valid.
We got it working by 'hacking' it to run against a valid SQL account for the time being and I have requested they build a new server out in parallel to move it over to since none of us can figure out the issue...we will see what happens.
Thanks for the replies.
Lee
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply