locked
Error 18452 Microsoft SQL Server Login RRS feed

  • Question

  • I have Client - Server system where client is MS access 2007 and server database is SQL server 2008. Conversion happened recently from MS Access 2003 and SQL Server 2005. User suddenly experiences these kind of error which they never encountered. Please help.

     

    Microsoft SQL Server Login

    ---------------------------

    Connection failed:

    SQLState: '28000'

    SQL Server Error: 18452

    [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

     

    MS Access uses ADO connectivity to connect to SQL server 2008.

    Connectionstring the application uses is,

    "ODBC;DRIVER=SQL Server;SERVER=CT2WP010.svr.us.companyname.net;DATABASE=AMLMetrics;Trusted_Connection=Yes"

     

    Please help !!!

     

    Thursday, October 7, 2010 6:51 PM

Answers

  • Did the Operating System or VDI situation change? It sounds like you are using Windows Authentication (Trusted_Connection=Yes) but the user is not logged in with a domain account. Perhaps they are using a special account that is local to the OS, but is not a domain account.
    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty
    • Marked as answer by Ai-hua Qiu Friday, October 15, 2010 9:11 AM
    Thursday, October 7, 2010 10:20 PM

All replies

  • I have Client - Server system where client is MS access 2007 and server database is SQL server 2008. Conversion happened recently from MS Access 2003 and SQL Server 2005. User suddenly experiences these kind of error which they never encountered. Please help.

     

     

    Microsoft SQL Server Login

    ---------------------------

    Connection failed:

    SQLState: '28000'

    SQL Server Error: 18452

    [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

     

    MS Access uses ADO connectivity to connect to SQL server 2008.

    Connectionstring the application uses is,

    "ODBC;DRIVER=SQL Server;SERVER=CT2WP010.svr.us.companyname.net;DATABASE=AMLMetrics;Trusted_Connection=Yes"

     

    Please help !!!

     

    Note: Users are on VDI and uses this application..

     


    Thursday, October 7, 2010 8:49 PM
  • Did the Operating System or VDI situation change? It sounds like you are using Windows Authentication (Trusted_Connection=Yes) but the user is not logged in with a domain account. Perhaps they are using a special account that is local to the OS, but is not a domain account.
    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty
    • Marked as answer by Ai-hua Qiu Friday, October 15, 2010 9:11 AM
    Thursday, October 7, 2010 10:20 PM
  • I have some points here which you can check:

    Does your application check the roles before login? In SQL Server 2008 they have changed a sp which returns role for the user.

    Second probability can be user is not configured in DB with proper access.

    check it and let us know the outcome.


    Cheers!!! Vatsa
    Friday, October 8, 2010 4:31 AM
  • Setting the owner for the database solved the problem for me :)
    Tuesday, January 11, 2011 9:16 AM
  • For us, this was fixed when the user logged off their workstation and then changed their password before logging in again. After that, they were able to continue as normal.  It seems that the SQL server and the client were somehow using the wrong authentication.

    Monday, January 31, 2011 6:36 PM
  • Can you tell me the details? I'm stuck with the same problem

    Thanks

    Tuesday, July 10, 2012 9:35 AM