Roxanne25
asked on
SQL Server Error: 18452 Login Failed for user ''
Hi, we are having a strange intermittant problem with some of our SQL logins. At first, we thought it was an isolated problem with a developer on my team. He was getting the following error intermittantly when connecting to the database:
SQLState: '28000'
SQL Server Error: 18452
Login Failed for User ''. The user is not associated with a trusted SQL Server connection.
We are operating in mixed mode and he is accessing the database via a domain account. It just happens sporatically and the error message just has '' as the username. He can try again a few minutes or few hours later and it works fine.
At first we thought it was something with his machine and our Networking people could not identify any problems.
Today, I got a help desk ticket from a user who is using MS Access to connect to the SQL Server via ODBC. He has been using this method without problem for over a year and just started having the exact same error message popping up intermittantly.
I also access the database the same way that the developer does and I have never had this problem. We are all using domain accounts. We have very few local SQL logins and those are only used by automated processes and internal db stuff.
Does anybody have any clue why this is happening? I tried googling it and the only solutions I found actually had something showing up in the error message for a username and said to enable mixed mode...but we're already running in mixed mode.
Thanks!
SQLState: '28000'
SQL Server Error: 18452
Login Failed for User ''. The user is not associated with a trusted SQL Server connection.
We are operating in mixed mode and he is accessing the database via a domain account. It just happens sporatically and the error message just has '' as the username. He can try again a few minutes or few hours later and it works fine.
At first we thought it was something with his machine and our Networking people could not identify any problems.
Today, I got a help desk ticket from a user who is using MS Access to connect to the SQL Server via ODBC. He has been using this method without problem for over a year and just started having the exact same error message popping up intermittantly.
I also access the database the same way that the developer does and I have never had this problem. We are all using domain accounts. We have very few local SQL logins and those are only used by automated processes and internal db stuff.
Does anybody have any clue why this is happening? I tried googling it and the only solutions I found actually had something showing up in the error message for a username and said to enable mixed mode...but we're already running in mixed mode.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The default port for SQL IS 1433 and is not dynamic according to my knowledge. Also I can't see anyone running a enterprise SQL Server on dynamic IP....maybe if you are looking for trouble.
ASKER
Well the developer is connecting to the db directly with SQL Enterprise Manager and getting that error... as far as I know I don't know any other way to tell it to connect when you use that. The other user can only access the db through ODBC and I'm not aware of how I would modify an ODBC connection to use TCP/IP?
I don't have any knowledge of our domain environment so I'm not sure about that question. The user does not experience any other network problems when this error message happens.
I don't have any knowledge of our domain environment so I'm not sure about that question. The user does not experience any other network problems when this error message happens.
Hi Roxanne25
What version is the server running?
Run @@version from query analyser/Sql Server Management Studio is one way to find out.
Can the developer connect to other servers? The local instance on his workstation?
Regards
David
What version is the server running?
Run @@version from query analyser/Sql Server Management Studio is one way to find out.
Can the developer connect to other servers? The local instance on his workstation?
Regards
David
ASKER
Hi, we do not have local instances on our workstations. Just to our development and production servers.
We are running this version on our development server:
Microsoft SQL Server 2005 - 9.00.5000.00 (X64) Dec 10 2010 10:38:40 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
Product Version Product Level Product Edition
9.00.5000.00 SP4 Enterprise Edition (64-bit)
Production is running the exact same things but its on service pack 2.
I just experienced the error message not 2 minutes ago myself. I could connect perfectly fine to the development server but I got the error connecting to production. I hit connect about four or five times and still same error then about a minute later it connected and let me in just fine. I have never received this error before today.
We are running this version on our development server:
Microsoft SQL Server 2005 - 9.00.5000.00 (X64) Dec 10 2010 10:38:40 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
Product Version Product Level Product Edition
9.00.5000.00 SP4 Enterprise Edition (64-bit)
Production is running the exact same things but its on service pack 2.
I just experienced the error message not 2 minutes ago myself. I could connect perfectly fine to the development server but I got the error connecting to production. I hit connect about four or five times and still same error then about a minute later it connected and let me in just fine. I have never received this error before today.
The alisa to port# only works if you've fixed the port on a named instance. The default is dynamic port.
Regards
David