We will use the 3 rd option to fix the error. First, it is good practice to verify that the problem is actually due to permission issues. Log in to the server where you SQL Instance is running. Go to the error logs and look for the last time that the SQL service was restarted. You should find an error message similar to this:. Windows return code: 0x, state: Ping the desired server and see what reply you get. In some situations you will get this error due to SPN settings. There may be a temporary workaround that will probably allow you to get to the database.
Workaround : On each client computer trying to connect to the SQL Server, create an entry in each workstation's host file. The exact mechanism this uses to fix the issue is unconfirmed but it may be that using it overrides the need for the SPN.
While this isn't guaranteed to be fix for all cases it will most likely get you back up and running. This should not be considered a permanent fix. You should resolve the SPN or other issues in an ideal situation. However if you're having issues with old Windows machines running an unsupported operating system or if you're just doing proof of concept disaster recovery testing this should get you where you need to be to keep the lights on or production back up and running.
I've made some researches to know why this happens. It says that when you shutdown the service, you need an account with privileges do create a new SPN when it turns on again. I had a similar issue.
I was then able to access SQL Server remotely. I experienced this issue just recently. I could connect with the IP address. Once I removed this and then added it to the service account, and rebooted the SQL machine, everything worked as it should. Happy to provide more details if needed. When you are running your service account using a local account you will not have this issue, but if you run your serice accounts as an active directory user, then it will need permissions to create its own SPN.
If it does not have this permission, you should manually create the SPN. I think the easier approach is to install Kerebos Configuration Manager and run the diagnostic check. I ran into this error when my Account was Locked-Out and I wasn't aware of it yet. The content you requested has been removed. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. Howdy, Firstly, I have read through so much information on this, that my eyes are starting to bleed and I am right at the end of my rope with it all..
Active 2 years, 6 months ago. Viewed k times. Improve this question. Brian Webster Prasanna Prasanna 2 2 gold badges 6 6 silver badges 15 15 bronze badges. When I changed my DNS server back to default, it went away. Please read the comment above before going down this page. Add a comment.
Active Oldest Votes. It can also happen if your password expires. Improve this answer. Tony L. Thank you, password not expired recently. It happened long back and the password is not the problem now. Link expired, please update it. Worked like a bomb for one of our users.
Problem was everybody was able to connect except this one user. Thanks a lot. Show 2 more comments. And Windows on client and server? Local or network SQL instance? Domain or workgroup?
Changing password Local windows log errors? Any other apps affected? Thank you for your immediate response! SQL Server 2. Windows Xp 3.
0コメント