Home » SQL ServerRSS

Error 18452 Microsoft SQL Server Login

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 !!!

 

 

4 Answers Found

 

Answer 1

Setting the owner for the database solved the problem for me :)
 

Answer 2

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..

 


 

Answer 3

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.
 

Answer 4

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.

 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter