Skip to main content

Navision Cannot generate SSPI context State ID HY000


Hi all,

Sometime while trying to connect database in classic client with windows authentication or connect to Role Tailored Client we face an error message.

Error -
The following ODBC error occurred:
Error: [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context 
State ID: HY000



Error Resolution -

There are multiple case due to which this error can occur so there are multiple resolutions. These are the case s that I faced, there may be other reasons for the error.

1) If you want to connect to Classic Client you can change NET TYPE to Named Pipes and try opening the database as shown in image below.



2) If you are connecting to a server, first check the server date it might set to some old date. Change it to current date and the issue is resolved.

3) Use Local IP Address 127.0.0.1 instead of computer name when connecting to the sql server.

4) Microsoft has confirmed that this is a problem in the Microsoft products and the related resolution can be found in link.

Updated ON 05-02-2016 (Suggested By +SQLSurfer 7 ) 
5) Check the Password of the Windows User Account, it may be expired. If that is the case then reset the password and then try.

6) Restart the machine.

Steps for Resolution 4-

a) Manually create a host entry on the client computer for the IP address that you want to connect.

b) Start Windows Explorer.

c) Locate the Hosts file, and then open the file in notepad. (IN Case of windows 7 Run Notepad as administrator).

d) Note You can locate the file in the %SystemRoot%\System32\Drivers\Etc path. (Type drivers in Run and the folder that get opened have etc folder which contain the hosts file.

e) Add the following at the end of the file: Random IP Computer Name

Note Random IP is a placeholder for the IP address that is not in use by another computer in the network. Computer Name is a placeholder for the name of the computer that has the SQL Server 2000 SP3 running on it. The Random IP IP address and the Computer Name name must be separated by at least one space.



f) On the File menu, click Save.
g) Close the file..

Now try to login Navision with windows login, it should work :)

Thanks & Regards,
Saurav Dhyani
http://saurav-nav.blogspot.in/

Comments

  1. Hey! Have you ever paid attention, has your writting style improved so far?

    ReplyDelete
    Replies
    1. Hi Martins,

      I guess you would be the best to answer your question.

      As per me i think NO.

      Regards,
      Saurav Dhyani

      Delete

Post a Comment

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.