![]() The user’s Windows account will (through an AD group) give access to both the file server and the database server. The connection string was in both cases specified in an UDL file that the application refers to, and I used trusted login. I have had an application run smoothly on 20+ sites for years, only to have this reported from two sites last week. Perhaps it was not a coincidence that these emails all came together. If you are not able to login with your SQL Server username after following above steps, it is quite possible your username is incorrect, please check again. ![]() You should be able to login with your SQL Server username. Select SQL Server and Windows Authentication Mode. ![]() Now go to Security Tab and go to Server Authentical Area. Open SQL Server Management Studio and right click on Server Node and select Properties ![]() You can quickly fix this error by following steps listed below. This can also happen if you are attempting to login to SQL Server with SQL Username but it is only configured to connect to Windows Login. This is quite a common error and can happen when incorrect username is communicated to SQL Server. The user is not associated with a trusted SQL Server connection. When they attempted to login using their application to SQL Server they faced following error: Login failed for user 'username'. Earlier this week, I was on vacation and did not check my emails for three days and when I returned, I found six different emails from 4 different people asking for the same problem.
0 Comments
Leave a Reply. |