![sql error 18456 severity 14 state 5 sql error 18456 severity 14 state 5](https://blog.sqlauthority.com/wp-content/uploads/2016/10/login-failed-18456-04-350x350.jpg)
In other words, disk access would be almost continuous. If this was a production server, SQL would be spending I/O time writing the same message to the Error Log.The reason I wanted to dig deeper was because the error was happening many times, almost every ten seconds, and in my view it had these potential problems:
![sql error 18456 severity 14 state 5 sql error 18456 severity 14 state 5](https://blog.sqlauthority.com/i/c/login-failed-18456-01.jpg)
The server was running an instance of SQL Server 2008 and although it was a test instance, I decided to spend some time to find out what database was being accessed by this account. It could also be the default database for the login where explicit permission was not given. The database could be offline, shutdown, deleted, dropped, renamed, auto-closed, or inaccessible for some other reason. As I found out later, States 38 and 40 (in SQL 2008 and later) and States 16 and 27 (before version 2008) mean that there is an issue with the database being connected to. Like other error messages, it also has a State number and there are different State numbers associated with it, each having a different meaning for the failure. Įrror 18456 generally means a failed login attempt. It turns out I had to add it in Spanish as NT AUTHORITY\Servicio de red, which is wierd because the app pool has its Identity in English.11:22:08.76 Logon Error: 18456, Severity: 14, State: 38. Something else that tripped me up when I was looking originally to add the NT AUTHORITY\Network Service login was that I couldn't find it. I basically decided to add any logins that were in my normal SQL Server instance that I was using for the regular SharePoint databases and that weren't in the SQL Server instance I was using for SharePoint Reporting Services to the latter. Ok, even though the error said: Login Failed for user 'Domain\Servername$' and I added that login to the problematic SQL Server instance per what I'd seen described on the internet, it seems that the login I ALSO needed to add was NT AUTHORITY\Network Service. If you have a SQL Server Instance with logins that have been working for you when accessed by application pools and the like, you might want to check which logins are not in the troublesome SQL Server instance and that you might need. If you are working in a Spanish environment try adding NT AUTHORITY\Servicio de Redįor steps on adding logins see links in question. Why am I getting this error if I've already added the login Domain\ServerName$? Any ideas or workarounds?Īdd BOTH Domain\Servername$ login and NT AUTHORITY\Network Service login to SQL Server instance giving you above problem and give both logins the right permissions. Just to get some more information I look at the SQL Server Error Logs using Management Studio and I can see that ther error ID is 18456, Severity 14 State 5 and the Reason for the error is Could not find a login matching the name provided. So, I add the login for Domain\Servername$ and give it server roles: dbcreator, public, securityadmin and sysadmin and then just to be on the safe side I give it db_owner permissions for each database in the SQL Server 2012 Evaluation instance I have. This makes sense since the account that is used for database provisioning for the new Reporting Database that needs to be created behind the scenes as part of Step 3 is the Identity for the Application Pool of SharePoint Central Administration which I currently have set as Network Service.Īnyhoo, the agreed upon solution is to add the login Domain\Servername$ to the SQL Server Instance that's giving me trouble and give it the right permissions ( links for similar problems: and.
![sql error 18456 severity 14 state 5 sql error 18456 severity 14 state 5](https://blog.sqlauthority.com/wp-content/uploads/2018/03/dup-ip-err-01-600x271.jpg)
When I get to the end of Step 3: Create a Reporting Services Service Application and press OK, I get the following error: Login Failed for user 'Domain\Servername$'.Īccording to what I've found on the interweb this means that "a process running as NETWORK SERVICE or as LocalSystem has accessed a remote resource, has authenticated itself as the machine account and was denied authorization."
#Sql error 18456 severity 14 state 5 install#
Ok, so I'm going through the steps to Install Reporting Services Sharepoint Mode for Sharepoint 2013 that can be found at.
![sql error 18456 severity 14 state 5 sql error 18456 severity 14 state 5](https://i2.wp.com/blog.sqlauthority.com/wp-content/uploads/2016/12/clus-sp-err-01.jpg)