Troubleshooting MS SQL login failure
Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication.
Follow the steps given below the resolve this error.
1. Verify Credentials
Ensure that the username and password of the SQL account (domain\username) are correct.
Check if the user account is locked or disabled.
Try connecting to the SQL Server using a query tool like SQL Server Management Studio (SSMS) or DB Visualizer (with MS JDBC driver) using the same account.
If the connection is successful, the credentials are valid.
2. Check Local Security Policy
Ensure the user account is added to the "Access this computer from the network" policy.
Refer to this page for more details.
3. Update SQL Service Account (if required)
If the SQL account is also used as the SQL Server service account, and you've recently changed its password, make sure the updated password is reflected in the service configuration:
- Open SQL Server Configuration Manager.
- Click on SQL Server Services.
- In the right pane, right-click on SQL Server (<instance name>) and select Properties.
- Under the Log On tab, enter the new password in both the Password and Confirm Password fields.
- Select OK to apply the changes.
Note: Click here for more details.4. Check for NTLM Restrictions
On the database server, check if NTLM authentication is restricted:
- Navigate to Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options
- Look for the NTLM-related settings.
- If NTLM is restricted, remove the restriction or configure it to allow Windows authentication.
Still facing issues?If you've followed the above steps and are still unable to log in to MSSQL, please send the following details to the Applications Manager Support Team:
- MsSQLDebug result – Click here for instructions.
- Screenshot of successful login using a query tool (SSMS/DBVisualizer).
- Screenshot showing user access from Step 2.
- SIF (Support Information File).
New to ADSelfService Plus?
Related Articles
Troubleshooting MS SQL Monitor Addition Problems
1. Ensure that the SQL Server is running and accessible. Try connecting to the SQL Server instance via SQL Server Management Studio or DBVisualizer using the same credentials. This step helps diagnose connection issues, ensuring that both the server ...SQL Server Kerberos Configuration Troubleshooting Guide
Step 1: Verify Kerberos Configuration in AppManager Step 2: Check Hostname and Domain Step 3: Verify Service Principal Name (SPN) Configuration Step 4: Check krb5.ini Configuration Step 5: Ensure System Clock Synchronization Step 6: Check Ticket ...gMSA troubleshooting steps
Troubleshooting Guide for GMSA account issues in Applications Manager This guide provides step-by-step instructions to resolve authentication issues when using a Group Managed Service Account (gMSA) with ManageEngine Applications Manager for SQL ...How to generate MS SQL Self-Help Tool report
Steps to generate MS SQL Self-Help tool report: Report by selecting existing host Navigate to Settings → Tools → Self Help Tools → DB Debug. Select "MS SQL" on the "Select Monitor" Drop-down. Select the issue reported MS SQL on the "Choose the Host" ...Azure SQL Database - Troubleshooting - Add client IP to Azure firewall
"Connection to the database failed with error : Cannot open server <ServerName> requested by the login. Client with IP address <SomeIP> is not allowed to access the server. To enable access, use the Windows Azure Management Portal or run ...