Tough One - 28000 (18452) Not Associated With A Trusted Connection
Sep 6, 2007
Here's a real puzzler. I have a remote SQL Server running on a different domain than the one I am logged in to. From my own PC, logged in as myself, I can create an ODBC connection to this remote server (using integrated authentication) with no problem. When I log in to any other PC as myself, I get the "28000 (18452) Not associated with a trusted connection" error. This would therefore seem to be a PC-specific problem, but I can't see any difference between the PCs. All PC's are running the same version of MDAC.
Firewall is down, no proxy is involved, and I have given myself Administrative privelege on the PCs.
Can anyone give a quick description of the meaning of this message andwhat needs to be done to get a connection.I'm running DBArtisan with SQLServer 2000 client SP4 installed.I also get the same message with MS Enterprise Manager so this iscoming out of the actual ODBC connection attempt.Thanks in advance!
When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .
I added my domainuserName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domainuserName but rather ComputerNameUserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?
I have a problem that I hope anyone here can help me with. We have a new server with Windows Server 2003 installed as well as MS SQL Server 2005. Both of these are freshly installed with default options set. The server is configured to accept both windows certification and SQL server certification (mixed), and our company has a domain setup. This server will be used for internal development, so all of the necessary people have an administrator account on the domain, which is uploaded currently into SQL Server's Security > Users folder. When I am on the server itself, I can log in using my domain name with no problem, as well as sa. However, when I try to connect to the server remotely (by my machine down the hall) using Windows Authentication I cannot. The server has BUILTINAdministrators set up for users, as well as 'sa' and whatever other defaults were there.
I CAN connect using sa remotely on my machine, though, after I enabled the account. The error message I get when I try to log in through Windows Authentication is:
*********************************************
TITLE: Connect to Server
------------------------------
Cannot connect to LAF-SQL1.
------------------------------
ADDITIONAL INFORMATION:
Login failed for user '(null)'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)
*********************************************
No other options other than what I've mentioned are installed. The (null) is not present, but the error message shows up as two single quotes ''. I strongly suspect there is a security option set by default somewhere in WinServer or SQLServer that does not permit remote connections, but I do not know where.
There are two servers €˜A€™ and €˜B€™. At server €˜A€™, there is installed Window server at server €˜B€?, there is installed Window Server2000. And both servers have SQL SERVER 2000. I have created link server from A to B. I have to insert data into table of server €˜B€™ from server €˜A€™. When I used directly insert command like
Insert into [server name (B)]. [Database]. [Owner].[table name] Select * from [server name (A)]. [Database]. [Owner].[table name]
The data is inserted successfully.
But when I created Jobscheduling , it is failed and show message :-
"Executed as user: HOerpserver. Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. [SQLSTATE 28000] (Error 18452). The step failed."
I received the above error yesterday and haven't been able to trace it to any job or process running. We haven't implemented any changes to the server in the past few months, and it doesn't look to be a user-established connection, since the Client IP Address of the SSPI handshake error is from the server itself.
I logged this set of messages in SQL AgentServer error log:
Date 10.03.2008 6:15:19 PM Log SQL Server (Current - 11.03.2008 2:32:00 PM) Source Logon Message SSPI handshake failed with error code 0x80090304 while establishing a connection with integrated security; the connection has been closed. [CLIENT: <IP Address>]
When our administrators login on the workstation the application works well. But when ordinary users login they get the following error. (We only have 1 domain)
SQLState: 28000
SQL Server Error: 18452
Login failed for user ". The user is not associated with a trusted SQL Server connection.
Then the standard SQL Server Login window pops up asking for the Login ID and Password. On the window the 'Use Trusted Connection' is checked and the name of the user on the workstation appears on the LoginID. What we do is uncheck the 'Use Trusted Connection' then login using the credentials above.
Login Failed for user , the user is not associated with a trusted sql server connection. (microsoft SQL Server,Error:18452)
hi , i am getting the above error message once in a while maybe two or 3 times a week , and then it goes away in 10 to 15 minutes or 5 minutes ,
our mode is set to mixed and we are able to connect and use both sql and windows , but once in a while , it will give us the above message when we try connecting throught sql server management studio client (using sql 05) using windows login , although it lets us connect using sql login while the windows login is denied, and after a while it lets us connect with both.
occurs randomly on some days , we run our servers on VM ware virtual machines using windows 2003 r2 enterprise 64 bit with sp2 with esx 301 virtual machine.
Last week I was receiving an error when trying to connect to two of our seven sql servers from my laptop via my domain admin account. The only fix was to have my laptop rebuilt and everything re-installed.
Today however another administrator is starting to have the same problem but to only one of the seven servers! When that administrator uses my laptop with her domain admin account it works!?
What could possibly be going wrong with our laptops? We have not installed or changed anything.
The full error message we see:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsoft Sql Server, Error: 18452)
The error being logged on the server: (two errors are logged each time)
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 53.35.165.148]
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 53.35.165.148]
When I use sa to log into one of my database , it give me the following error: The user is not associated with a trusted conncections. error code: 18452, please tell me how to solve this problem.
I have SQL 2000 installed in my windows 2003 server with mixed mode authentication. When I login to the server and open the SQL server manager under my windows name everything works. And if I try to create an odbc connection from one of the client pc's or from the server itself using windows authentication still everything works. Now I opened the SQL enterprise manager and in the Security section, there is a user group called BUILTINAdministrators, I was asked to deny access to this group in SQL. So I did that and added my windows login name in the security -> Login section. Now still if I try to open the enterprise manager and and login to sql under my windows login name it works. But if I try to create an odbc connection to the sql server either from the server itself or from the client work station I get the following error: connection failed:SQLstate: '28000'SQL Server Error: 18456[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'PRODpchelin' If I go to the security -> Login and enable BUILTAministrators group, everything works. But I would like to know how to disable that group and add my own windows group or login id in SQL server and connect using ODBC. Your valuable feedback is greatly appriciated.
I'm having major problems with SqlClient Data provider connections in my application. I'm using Win 2003 Server with SQL Server 2000 (both on the same machine), and my application is developed in VB.NET.
I'm using the following db connection string: Data Source=(local);Initial Catalog=database;Uid=user;Pwd=password;max pool size=100;
As you can see max pool size is set to 100. The SQL Database has it's MAX_CONNECTIONS property set to >32000.
The symptoms are that at seemingly random times, not nessecarily during peak hours, the application becomes extremely slow and stops responding. The error message that is beeing generated is "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
After monitoring and debugging, I've found two things.
1) At random times, zero-three times a day, the number of database connections (according to performance monitor) rises from normally 2-8 up to 20-25. After a while, usually 10-60 minutes, it drops back to normal. This is directly related to when the timeout errors occur. It doesn't seem to happen more often during peak load, for some reason. I suspect there is connection leakage in the application, but I've done extensive debugging, and I just can't find any. Also, since the peaks occur randomly and I can't reproduce the error in my development environment, I have no solution to this problem. A few weeks ago, the application ran during heavy load without this problem for 7 days. Before and after that, there have been errors at least every second day. That confuses me even more.
2) The number of connections (monitored in perf mon) never reach above 25. Why? I'm using SQL Server enterprise edition, it's connection limit is over 32000. ADO pool size is 100, and I can't find anything else that would limit the amount of concurrent connections. I'm totally confused. Why does number of connections never rise above 25? Is there a setting hidden somewhere that I just can't find? Also, according to Performance Monitor, I don't get any failed connects, I just get failed commands. Maybe that's a clue? Could the problem some kind of deadlocks in the database that causes timeout?
I realize this entire post is rather confusing. It reflects the state of my mind, I guess, after working around the clock on this issue for a month :)
All -- Please help. I have some questions about connection strings.
BACKGROUND...
Note that I am using the "SQL Native Client OLE DB Provider", SQL Sever 2005 Express, ASP.NET, C#.NET, and VS.NET 2005. Note that I do not want to use the "Attach a database file" type of connection string. Note that I am using the site http://www.ConnectionStrings.com as a reference. Note that this "Standard security" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Uid=MyDatabaseUser;Pwd=MyDatabasePassword;" />...does not work and causes the following run-time error...A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) Note that this "Trusted connection" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Trusted_Connection=yes;" />...works but is less-than ideal because it uses a Trusted Connection rather than a Username/Password combination.
QUESTIONS... (A) What exactly does the error in Item 4 mean? (B) Do 4 and 5 imply that one must use a Trusted_Connection for all SQL Server 2005 Express connection strings when the database does not reside in the web application's App_Data folder or use a "Attach a database file" type of connection string? (C) Are there any alternatives? (D) What do you suggest?
We are using the Windows Task Scheduler as a substitute for the SQL Server Agent, which isn't available in the Express edition. The scheduled task just calls a batch file, which in turn, runs a stored procedure using osql with the -E option for a Trusted Connection.
SQL Server Express has been installed using the defaults, which means the service is running in the "NT AUTHORITYNETWORK SERVICE" account. The scheduled task we create is set to run using the "NT AUTHORITYSYSTEM" account.
Now we find that on Windows Vista (tested using Ultimate Edition) that the scheduled task fails to run the stored procedure until the machine is rebooted the first time after installing SQL Server Express. When I say "fail", I mean that the stored procedure isn't executed. The scheduled task however completes and reports no errors. On Windows XP, we do not run into this problem so I suspect it has something to do with the UAC in Vista?
We further found that after installing SQL Server Express and creating the scheduled task in the "NT AUTHORITYNETWORK SERVICE" account, the scheduled task (and stored procedure) runs fine WITHOUT requiring a reboot.
Can anyone explain why a reboot is needed to get SQL Server Express to run the scheduled task correctly under Windows Vista and the SYSTEM account?
When using jdbc with IntegratedSecurity, I run into this problem when the machine is not part of a domain & gets its IP address via dhcp. Is this expected behavior or a bug in the jdbc driver.
The SQLServer and client application are installed on the same machine and a local admin is logged in, running the client app.
If I change one of the two parameters mentioned above, the connection can be established leading me to believe this may be intentional for security issues. Am I correct?
I have a Web application in asp.net 1.1Iam using windows authentication. The application is on IIS on MachineA. When i try to access this from MachineB as http://MachineA/test/test.aspx, it gives me the error "login failed for user 'null' : not associated with a trusted sql connection"Both MachineA and MachineB are on the same domain & iam not using any sql authentication. Could someone suggest me where i might have gone wrong. Web.config has authentication as 'windows', allow users = "*" and Identity impersonation = trueOn IIS, the vitual directory of 'test' application has Directory secuirty set to 'Integrated Security'Please let me know if someone had dealt with similar scenario. Thanks.
I have just installed MSSQL 2000 on Windows 2000. what I am finding is that I cannot open an isql (or query analyzer) session using the sql login (i am successful when i use NT authentication). The error message I get is as follows
Msg 18452, Level 14, State 1: Login failed for user 'xxx'. Reason: Not associated with a trusted SQL Server connection. DB-Library: Login incorrect.
MSDN talks about setting the registry entries differently, but that seems to be only for SQL 7.
Can anyone please tell me how to create a trusted connection?. I am from Unix world and NT is still kind of new to me. Let say my SQL server is located in this machine residing in domain X and I want a NT user, ABC, who is in domain Y to have acess to my server. What do I need to do?. Many thanks.
What does it mean when a users is connected but it is a "non-trusted connection". This is showing up in the log file after my users connect. How does this effect the system/user? We have been experiencing speed issues and I was wondering if this might be a possible source of the problem.
Hi-Is it possible to do a trusted connection for a web server not onthe same physical machine. By this I mean can I make a remoteconnection from a web server to a sql server using a trusted connection.If so, how?Thanks,Dave
I'm trying to get a utility to run, and it's insisting on a user or trusted connection. I'm using SQL Server 2000 running locally. I've tried every login name, default, user I can think of but it rejects all of them.
I have an application we use here at work that I wanted to bring home to work from my house. At work I can get the application to connect to the SQL Server without problems. At home I get:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
I am connected to the office using a VPN connection. I have permissions to access the database (I am the server admin). It only happens when I connect thru VPN. I have tried it on 2 other systems here in the house to insure its not just my computer.
At the moment the application will only work with a trusted connection or Windows Authentication. It will not work with SQL authentication.
Hello, I appologize if this is in the wrong spot, but it seemed like the appropriate place. We have IIS installed on one box and SQL on another. We use a trusted connection to connect. When we try an connect to our DB, we don't get an error, the page just refreshes. From what i have gathered, it looks like we are not being authenticated. We have the ASPNET domain user on both boxes and its configured with the correct permissions, but we still can't connect. Do i need to set up or give permissions to another account i dont know about, or is there some file that needs access?
Hi folks, when i try to connect to my sql express sever through Sql sever authentication I keep getting an error that says "Login failed for user 'username'. The user is not associated with a trusted SQL Server connection. " I know the password is right.. how do i overcome this??
Hello All, I know this issue has been dealt with every where in the universe. but none seem to solve my problem. I need help desperatelyThe Web Application is a Classic ASP/Sql Server 2000 using two computers in the same physical network:Computer-A is the Sql Server2000 running Windows XP Professional.Inside Sql Server2000 i created a login, AA, as a dbowner of a database called XXX. Inside XXX, AA is right there as a user. i configured the SqlServer to accept mixed (Windows and Sql) logins.I restarted the computer and i logged into sqlserver successfully as AA. Everything is fine here.
Computer-B is the Web Server running IIS in Windows XP Professional.Here, I successfully created a System ODBC i named EEEE to connect to XXX using the AA login. Everything is fine up to this point.But, to my greatest surprise when i use - conn.Open("DSN=EEEE;UID=AA;PWD=AApassword;") in a classic ASP page, it returns this very famous error.
Hi All, My Webserver and SQL Server are of different machines.I have connected my website with sql server database. I published that website in IIS. I can able to browse that in local machine. But, if I try to browse from some other machine its giving me error saying "NOT ASSOCIATED WITH TRUSTED SQL SERVER CONNECTION". MY Connection string is this: connectionString="Data Source=BOOKSQL;Initial Catalog=CustomerDb;Trusted_Connection=True;" I also tried with connectionString="Data Source=BOOKSQL;Initial Catalog=HeCustomerDb;Integrated Security=SSPI;" How can I overcome this problem. Please help me! I need ur immediate response.
I am trying to use a trusted connect to connect to a DB. Currently I use this code:
WindowsPrincipal wp = (WindowsPrincipal)HttpContext.Current.User; WindowsIdentity id = (WindowsIdentity)wp.Identity;
// impersonate user to connect to DB WindowsImpersonationContext impersonatedUser = id.Impersonate(); try { connection = new SqlConnection("Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=DBname;Data Source=server;Packet Size=4096;"); dataAdapter = new SqlDataAdapter("select query"); data = new DataSet(); connection.Open(); dataAdapter.Fill(data); connection.Close(); } finally { // restore our old security context impersonatedUser.Undo(); }
I am testing the app with my user which has full access to the server and database I am trying to connect to. But I always get this error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Now I'm new to this and not sure if I am going about it correctly, so any help would be appreciated. I just want it to use the ID of the person viewing the page to login to the server.
Login failed for user 'ASPNET'. Reason: Not associated with a trusted SQL Server connection. -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
