We've set up a new SQL v18.5 server running on Windows 2016. We're seeing these errors in the log every two minutes:
Login failed for user 'Domain\ServerName$'. Reason: Could not find a login matching the name provided. [CLIENT: ]
It's for user NT Service\NT SERVICE\SSISScaleOutMaster140
I did a little digging, and the answer seemed to be to add a login in SQL for NT SERVICE\SSISScaleOutMaster140, which I did. After that I started getting this error:
Login failed for user 'Domain\SERVERNAME$'. Reason: Failed to open the explicitly specified database 'SSISDB'. [CLIENT: ]
This SQL server is for a couple of specific applications we have, we do no development. Could it be that SSIS was installed and simply shouldn't have been?
Related
Im installing the MDM of Informatica.
MDM 10.2 - Jboss 6.4 EAP - SQL Server 11 - Windows Server 2008 R2.
During the creation of the schema 'sip_ant.bat create_bpm' i got this error
Microsoft ODBC Driver 13 for SQL Server : Login failed for user 'sa'.
(Same eeror with another user)
I already tried to use the Auth Mixed Mode and restarted the instance of the DB.
Error received is
D:\informatica\database\bin\common.xml:248: The following error occurred while executing this line:
D:\informatica\database\bin\mssql\database.xml:1214: Launched command return error code 1.
And that's the line of database.xml:1214 that refers:
collation_name="${activevos.collation}" param2=""${dbpath_short}"" param1="${activevos.password}">
Im able to login via SQLCMD on CMD with user 'sa' and other users.
MDM and SQL Server are on different Machine.
Any suggestion?
By default SQL Server will track failed logins and register it in the server log along with the reason. So check out your errorlog and look for errors 18456.
You can read the log by using SQL Server Management Studio by going to server, Management, SQL Server Logs, Current. Or any other way you prefer.
You'll find something like this:
2018-02-27 13:51:26.120 Logon Error: 18456, Severity: 14, State: 5.
2018-02-27 13:51:26.120 Logon Login failed for user 'fasd'. Reason: Could not find a login matching the name provided. [CLIENT: 10.80.62.89]
server=Yourservername,portnumber
You can put the above in your connection string
Problem was due to Customer configured another Default SQL port to use on SQL Management.
I'm trying to connect to my database using the following connection string:
Data Source=LORDKANELSNEGLE\SQLEXPRESS;AttachDbFilename="C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\Database.mdf";Integrated Security=True;MultipleActiveResultSets=True
However, this gives me the error Login failed for user "LORDKANELSNEGLE\Lord Kanelsnegle", despite me being able to login with those exact credentials in SSMS as shown here.
I've even tried adding the login from the Security tab within SSMS and received this error,
confirming that this login does in fact already exist (as if me logging in with them wasn't evidence enough).
I've read every other post, stackoverflow or other, that I could find regarding failed Windows Authentication logins for SQL Server but none of the solutions worked for me. Ideas?
You should remove AttachDbFilename="C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\Database.mdf from your connection string.
You don't use localdb but fully functional Express Edition.
I imagine that your database is permanently attached to the instance and there is no need to re-attach it. So I think if you look in your SQL Server error log you'll see the error saying that it was impossible to attach that database because it's already attached and it was the reason of login failure.
Another reason can be that your login is not mapped to that database. In this case unless it's sysadmin it cannot enter the database. And this reason is also reported in error log. Server does not write the reason to the user in login failed error for security reasons but any sysadmin can find it in error log next to 18456 error
I made a VM clone of a SQL Server 2012 install. Now on the original install, the SQL Server log is showing login attempts by the clone server.
OLDSERVER was cloned to NEWSERVER, along with SQL 2012 database.
In OLDSERVER logs there are error messages (two per minute) that read:
"Login failed for user 'DOMAIN\NEWSERVER$'. Reason: Could not find a login matching the name provided. [CLIENT: 10.x.x.xxx]. Error: 18456. Severity 14. State: 5."
I am glad the login is failing because I do not want NEWSERVER connecting to the old database. My question is, what process on NEWSERVER is trying to connect to the OLDSERVER SQL database? How do I find it, and shut it off?
I believe I uncovered the problem. The Report Services was trying to connect through the OLDSERVER Report Services database. After changing it to NEWSERVER Report Services, the logs stopped reporting the login error.
I am trying to connect a SQL Server 2014 database into Servoy 8 but I am receiving the following error:
The password for the user 'sa' is correct such as the links. I searched everywhere but I couldn't find a solution.
You should check SQL Server error log for this error. There will be two rows, one containing 18456 error with the state and the second decoding what the state means. It can be not only a bad password, the login can be disabled or the server can be configured to use windows authentication only
I have been tasked with deploying an application that has been successfully running in a development environment to a staging environment. After deploying the published files and configuring IIS, I can see the inital login screen, as expected. However, when I try and log in, I get:
Cannot open database "db1" requested by the login. The login failed.
Login failed for user 'user1'.
The setup contains these pieces:
Windows Web Server 2008 R2,
SQL Server Express 2008 R2,
IIS 7,
ASP.NET MVC4, and
Entity Framework 4.4
Googling turned up no sucessful leads - answers posted here and elsewhere were all concerned with either the credentials ultimately being incorrect or dual-mode authentication not being enabled in server properties.
I see dual-mode authentication enabled in server properties, and I can confirm this by logging in with either SQL Server or Windows authentication in SSMS. This also confirms to me that the credentials are good and accepted by the server. (Please correct me if I'm wrong in thinking this)
SQL Server, IIS, and the browser I'm testing with are all running on the same machine.
Here is my connection string: (with internal info substituted out)
<add name="app1Entities" connectionString="metadata=res://*/app1.csdl|res://*/app1.ssdl|res://*/app1.msl;provider=System.Data.SqlClient;provider connection string="data source=localhost\SQLEXPRESS;initial catalog=db1;user id=user1;password=pass1;multipleactiveresultsets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
I found the resolution. It was ultimately a permissions issue.
This question got me on the right track:
SQL Server: Cannot open database requested by the login
Examining the server logs showed:
"Failed to open the explicitly specified database", then
"Error 18456, Severity: 14, State: 38"
Google revealed that state 38 means a permissions problem. This particular user had the 'public' server permission and the 'db_datareader' and 'db_datawriter' permissions on the database already so I deleted and remade the user on the database, which fixed the issue.
EDIT:
This was happening to me every time I restored the database. Apparently SQL server gets confused about users on restore. The fix is to execute this:
EXEC sp_change_users_login UPDATE_ONE, 'username_of_user', 'username_of_user';
After a restore, which fixes the issue entirely.