I dont know from where this error is comming from?RegardsSivashiva :) All the databases are in ONLINE state.I only sees the error messages in SQL Logs. My login is successful with 'EDEALER\sqlservices' OS logins.
Hi russelSorry for the delay reply.I am using the SQL Studio for logins.
Since the login can access master, then it is either permissions, or the database isn't accessible.If, as you said, the account is sysadmin, then it is a database specific error.Make sure the db is online.Are you using Management Studio to connect, or some application? Its a local id.This id is the SQL Service account for all the SQL Services e.gSQL Server EngineSQL Server AgentSQL Server BrowserSQL Server FullText SearchSQL Server VSS WriterSQL Server Reporting ServicesRegardssiva Yes 'EDEALER\sqlservices' can access to master database.Master as the default database for this SQL logins. SPN is for domain account, not local account.Make sure the specified database exists, is online and that 'EDEALER\sqlservices' has permission to access it.Can 'EDEALER\sqlservices' access master?
#SQL ERROR 18456 LOGGING IN HOW TO#
I do not want to interupt the user.Please advice how to do the setSPN.regardssiva Now I am planned to setSPN, but I am not confident enough to do it since this system running as production now. EDEALER is the local hostname.sqlservices is local os id with administrator role and as well sysadm role in sql logins.I went thru all your posting on this matter. Reason: Failed to open the explicitly specified database. Thanks!!ĭear Guru'sI am facing the same problem.Login failed for user 'EDEALER\sqlservices'. Have you had a look in SQL Server configuration manager to see if there is a user that matches those credentials. Looks like its from an engine level connection. Thanksĭid they re-register the SPN after changing service account? are there linked servers pointing to this server? web servers using nt authentication? ( I am not sure why this is?)The server role is public and I selected also sysadmin but that didn't help.Hopefully someone could help me to get this fixed. When I use the SQL Profiler and watch to the Audit login this error is not passing by.At the login properties of this user, at the user mapping page I found that the map for master and msdb is selected with the user and a default schema. This error message is comming back every minute into my log file. Anyway, everything is working again but I have still one problem.Error: 18456, Severity: 14, State: 38.Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. I asked to the sys admins if there where any change and they told me they had to rename the administrator account :(. After my holiday I came back and I found some errors in my SQL Server 2008 R2. Hi,First of all I must say I find my way in SQL but I am not higly skilled dba. All ForumsĮrror: 18456, Severity: 14, State: 38 problem We've got lots of great SQL ServerĮxperts to answer whatever question you can come up with.
0 kommentar(er)
