I am trying to install Microsoft velocity on a machine that will use a sql database for it's configuration store.
I have entered the connection string correctly but when I test the connection it fails, here are the logs:
2009-01-23 11:54:30.03 Logon Error: 18456, Severity: 14, State: 11.
2009-01-23 11:54:30.03 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: xxx.xx.xx.xxx]
Which implies that the login is valid but the connection failed along the way, can anybody help?
Thank you in advance
'NT AUTHORITY\ANONYMOUS LOGON' would indicate that the account you used to login was not identified in SQL Server. You need to make sure that the account is listed in the security and has rights to the database you want to connect.
Related
Error message
[jcc][t4][2013][11249][4.26.14] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000
I have tried everything suggested by the IBM chatbot but I did not get a solution. Please help.
This means it failed due to disabled or expired user id or wrong password or not a valid password.
Please contact your DB administrator
I'm facing a situation which every 10 seconds an error log is recorded with the following msg:
2018-07-25 09:07:09.59 Logon Error: 18456, Severity: 14, State: 38.
2018-07-25 09:07:09.59 Logon Login failed for user 'svc_sql'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: <local machine>]
In my instance I don't have a 'ReportServer' database. I know that in the past the server was migrated to a new machine and I reckon the 'ReportServer' database was created with a new name in the new server. I really don't know how the migration was done.
I've activated the SQL_Profiler with all audit options and I could see that this user also executes a procedure sometimes.
I've checked the default database for this user and it's Master.
Any ideas how can I fix this issue? My error log is flooding with this message.
Thanks a lot.
Rod
I've checked the default database for this user and it's Master.
The error doesn't tell you about default database but about explicitly specified database, that is different, it's the database that is mentioned in connection string under Initial Catalog or Database.
Do you see what application tries to open this database? The problem is in that application, it uses old connection string. If it's SSMS, it's simple, it's in the Options of connection dialog, but if it's another application, the connection string can be written in the ini file or hardcoded.
I don't know if I try to run DBCC CHECKDB master will solve this.
Of course it cannot solve this. This has nothing to do with database integrity. It's your client that uses wrong connection string.
Any ideas how can I fix this issue? My error log is flooding with this
message.
If you just want to save your errorlog from these messages just turn off failed logins audit:
Or you should find this application by its name or host or client address.
Or you can temporarily disable this login and see who will call you saying he cannot login anymore, or, if it's your local machine, some of your applications will fail, this way you'll find it.
I had the same error and doing the following resolved the error for me:
From within the SQL Server Management Studio
Security
Logins
Right Click the user ID that was failing login
Server Roles
Make sure all the checkboxes are checked. Right clicked Security and refresh.
Trying to learn SQL Server, so bear with my noobness, please.
I see the same errors repeatedly in the SQL Server log:
Error: 18456, Severity: 14, State: 38.
Login failed for user 'domain\username'. Reason: Failed to open the explicitly specified database. [CLIENT: ]
There were also many failed login attempts for the same client prior to this error starting.
I checked the connection string on the problem client and it's identical to the string used on other clients that successfully connect. Can SQL Server limit access to a specific IP/client, but continue to allow access to all other users?
This has been discussed here by Aaron Bertrand:Troubleshooting Error 18456
Error: 18456, Severity: 14, State: 38.
Login failed for user ''.
Reason: Failed to open the database specified in the login properties.
Reason:
The database specified in the connection string, or selected in the Options > Connection Properties tab of the SSMS connection dialog, is no longer valid or online (it might be set to AutoClose or the user may simply not have permission).
Note that this could also be a symptom of an orphaned login. In this situation, you will need to synchronize the login and user information
Can SQL limit access to a specific IP/client, but continue to allow access to all other users?
SQL will not and won't deny access to a specific client,it must fall into one of the above cases
I am scratching my head here and I need a hand with this. Please save my sanity!
1
I can log into SSMS with the username and it works.
I can open the ODBC/System DSN and test the connection using the same username and it works.
3
I have the vtimecard.ini configured with the username and password IDENTICAL to the login for SQL and that used for the 2 logins that work...
[ODBC]
DSN=
Driver=SQL Server
Server=MLAERP01\VTIMECARD
Database=vTimeCard
UID=vtc2
PWD=
BUT once I try to access the website, it fails.
Details: Global database error Open (global): 'Login failed for user 'vtc2'.' (D=, D=SQL Server, S=MLAERP01\VTIMECARD, D=vTimeCard, U=vtc2)
and when I check the SQL server log it gives:
Login failed for user 'vtc2'. Reason: Password did not match that for the login provided. [CLIENT: ] Error: 18456, Severity: 14, State: 8
Please direct me what I need to look at with this. I am not that versed in SQL and webApps. Any help is good help!
I have a powershell script for DB backup/restore. For some reason I am executing the script remotely using new-pssession and invoke-command. I am
1.connecting to remote server
2.the local server is in a domain
3.the remote server is in same domain
4.Using the domain account which exist in both the machine and have admin rights.
5.My SQL Service (I mean the instance/engine) is running with
the same Domain account
backup with command Backup-SQLdatabase succeeds but restore Restore-SQLdatabase failes
with error Login failed for NT AUTHORITY\ANONYMOUS LOGON.
Just for trial/error I added "NT AUTHORITY\ANONYMOUS LOGON" to admin group in the machine where restore have to happen but no luck.
Any clue what I am doing wrong (OR) how can I solve this problem.
Appreciate your help.
Thanks.
EDIT: will the -SQLTrustedConnection switch can solve this issue?
After trying a bit I found a trick. The machine where restore have to happen I added "NT AUTHORITY\ANONYMOUS LOGON" as a user.
How to add:
connect to the DB instance using SSMS -> expand security -> expand login -> right click on login -> create new login