"Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)"
The Issues
1. Accessing a shared folder in the client always locks the account I used to login.
2. Connecting to the clients database in the server, gives the "Login failed for user ''" error. The actual message is
"Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)"
3. Replication is not working.
4. Event viewer indicates exceptions from System.Data.SqlClient.
The Solution
1. Check if the account you are using to access the client is a valid account.
2. Check if the password used is correct.
3. If all looks ok, follow the following test :
a. Verify that name resolution is working correctly.
- From a command prompt at the client, ping the server by name and verify that it returns the correct IP address: PING {ServerName}
- From a command prompt at the client, ping the server by IP address, and verify that it returns the correct server name: PING -a {ServerIP}
- From a command prompt at the server, ping the client by name and verify that it returns the correct IP address: PING {ClientName}
- From a command prompt at the server, ping the client by IP address and verify that it returns the correct client name: PING -a {ServerIP}
b. If the above steps does not reveal any problem, verify that we can access the logon server:
- Open a command prompt on the client machine
- Type "SET logonserver" (without the quotes) and press Enter.
- On the server, open the command prompt and type "dir \\[ValueReturned]\etlogon" and press Enter. ValueReturned = the value from the SET statement above. The directory listing should not return an error. If it does, troubleshoot that error.
Source : Microsoft Help Page
Comments