ODBC Error: SQLState 28000 & Server Error 18452 RRS feed

  • Question


    We have an application that connects to SQL 2005 thru ODBC with the following string:

    driver=SQL Server;server=server1;database=db2005;uid=serveruser;pwd=pwd1;

    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.

    Need help on this one please. Thanks.

    Monday, October 9, 2006 10:17 PM


All replies

  • Check whether server is configured to allow mixed authentication modes (SQL Server and Windows) (or) only Windows Authentication mode. You can do this by opening SQL Server Management Studio - Right Click on Server - Choose Properties - Security
    • Proposed as answer by ca-bluebird Saturday, January 9, 2010 6:38 AM
    Tuesday, October 10, 2006 3:01 AM

    Checked the setting, it is on SQL Server ad Windows auth mode.

    Tuesday, October 10, 2006 3:39 AM
  • Try sp_adduser to make sure that the login is identified as trusted by SQL Server.

    Link for sp_adduser : http://msdn2.microsoft.com/en-us/library/ms181422.aspx

    Wednesday, October 11, 2006 2:19 AM
  • Have you tried to stop and restart the database service after the changes took effect?
    Monday, October 23, 2006 3:31 AM
  • Hi ,

     I am facing Same problem and it is as follows:-


    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 trigger (for insertion) on table of server (A) (because I want as there is insertion in the table of server(A), rest

    Records that are not in the table of server (B) , are automatically inserted into the table of server(B)).


    The Insertion is not complete and there is shown system message which is as follows:-


    Server: Msg 7391, Level 16, State 1, Procedure rms_trn_con_details_insertion, Line 6

    The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.

    [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]


    I have searched in Google , I found that there are problems in heterogeneous system.


    But till today, I have no solution for it. Temporary, I find solution through Job Scheduling.


    Try to find out solution for this problem.






    Nikhil Chaturvedi

    Friday, June 1, 2007 7:21 AM
  • How is this the same problem?
    Tuesday, November 2, 2010 6:10 PM
  • hi there, I found that the user 'sa' pwd 'sa' does not work in mixed authorization mode if windows requires complex passwords. I changed the password of user 'sa' in complex type (eg:'Pippo@2010') and now it works!


    Thursday, November 4, 2010 8:39 AM
  • I had the same issue today. It turned out that my user had put off resetting her password and today was the day it expires. I found this out after asking her to reboot :-) . She mentioned the prompt and I told her to go ahead and change her password. 

    Once she logged in with the new PW, the Excel file fired right up and refreshed with the current data.

    This may not match your issue, but it is another thing to add to the troubleshooting list. Hope this helps someone.

    • Proposed as answer by Spacapan Tuesday, June 4, 2019 12:05 PM
    Tuesday, February 3, 2015 2:46 PM