![sql error 18456 severity 14 state 38 sql error 18456 severity 14 state 38](https://i.stack.imgur.com/OkSYt.jpg)
I noticed that there are multiple ways I can fix this error.ġ) Create the user and grant dbowner to the user.Ģ) Else execute the sp_changedbowner and make this use the owner. The calling program is Delphi5 Reply Ben says: Maat 12:59 am Im seeing error state 23 repeatedly in my logs: Error. Reason: Failed to open the database tpcc configured in the session recovery object while. 23:18:28.490 Logon Login failed for user SQL2016-SA-03Administrator. So there was no way it would not work after we crawl back to PROD. 23:16:47.690 spid52 Setting database option SINGLEUSER to ON for database for tpcc. The database could be offline, shutdown, deleted, dropped, renamed, auto-closed, or inaccessible for some other reason. Since this account was working fine before we failed over to DR. The account is xxxx\Admin and is coming from the SQL Server machine itself.
SQL ERROR 18456 SEVERITY 14 STATE 38 WINDOWS
When we failed back we had the same error so I was puzzled. If you have installed Windows SharePoint 3.0, Error: 18456, Severity: 14, State: 38, caused SQLSERVERAGENT does not start. However, on the DR server I had to create this user in the database and grant it dbowner. Hence, I didn't have to explicitly create the user in the database. I noticed that on production this account was listed as the DB OWNER since this was used to create the database.
![sql error 18456 severity 14 state 38 sql error 18456 severity 14 state 38](http://sql-articles.com/images/media/articles/error_18456_3.jpg)
State 38 means 'Login valid but database unavailable (or login not permissioned)'. The event had my domain name and computer name in there.
![sql error 18456 severity 14 state 38 sql error 18456 severity 14 state 38](https://i.stack.imgur.com/XVx6i.png)
Reason: Could not find a login matching the name provided.
However, today I noticed this on a new server that I configured as a Disaster Recovery. Here is the error: Login failed for userI have seen this error multiple times and typically it involves creating a user for that login.