Navision Odbc Error
Contents |
2010-9-23 2:24 PM Replies 7 replies Subscribers 341 subscribers Views 6362 views Classic Client ODBC SQL Server Options Share RSS Tags More Cancel Click here to login or become a odbc cannot generate sspi context hy000 member to ask questions and reply in our fourms. ODBC Error Hi
Cannot Generate Sspi Context Navision
all I was trying to login to Navison classic client through SQL server when i got this error " The cannot generate sspi context sql server 2008 r2 following ODBC error occured " Error: [Microsoft][ODBC SQL Server] Timeout Expired State ID: HYT00 How can i solve the issue? Please help me out?? Thanks Subha subhavn Cancel Reply Ravi 0 2010-9-23 2:31 PM Hi subhavn I think its a sink Problem.. just synchronise the login once and check. Ravi Dhan Raj Bansal 0 2010-9-23 2:41 PM Hi, Is it SQL 2005? If yes, then please refer following link: http://mibuso.com/blogs/kriki/2008/04/05/local-sqlserver-2005-with-windows-authentication/ Dhan Raj Bansal subhavn 0 2010-9-23 2:55 PM In reply to Dhan Raj Bansal: no it SQL 2008 subhavn Dean McCrae 0 2010-9-24 12:17 PM In reply to subhavn: Is it a local server or remote? Can you connect from SQL Management Studio with the same server name? Dean McCrae Karthik.D 0 2011-4-18 11:03 AM In reply to Dean McCrae: Yes it is a local server. I can connect it from QL Management Studio with the same server name. Karthik.D Amol 0 2011-4-18 11:09 AM In reply to Karthik.D: Hi, Just try with IP address in Server name. I hope it will resolve ur problem. -Amol Amol | Blog | LinkedIn | Facebook | Twitter Karthik.D 0 2011-4-18 11:25 AM In reply to Amol: Yes I found that by using IP Address Karthik.D Click here to login or join to be able to reply and post new questions. Related DUG Home Contact DUG Dynamics AX Users Forums Blogs Events Documentation, videos and downloads AX Partners Group Dynamics NAV Users Forums Blogs Wikipedia Events Books NAV partners group NAV freelancers group Dynamics CRM Users Forums Blogs Dynamics GP Users Forums Blogs Dynamics 365 Users Forums Blogs Documentation, videos and downloads Jobs and careers Jobs and Careers Forum Dynamics Jobs Offer
5, 2012 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 https://dynamicsuser.net/nav/f/users/35605/odbc-error 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 http://saurav-nav.blogspot.com/2012/04/navision-cannot-generate-sspi-context.html Microsoft products and the related resolution can be found in link. Updated ON 05-02-2016 (Suggested By+SQLSurfer 7) 5) Check thePasswordof 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 forResolution4- 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
Not https://www.navug.com/communities/alldiscussions/viewthread?GroupId=49&MID=1440 a valid date Posted by HomeJoin TodayChapters Find a ChapterMy Chapter CommunityMy Chapter RegistrationsMembership Levels & PricingNetworking http://www.kopija.in.rs/dynamicsnav/94/ BenefitsEducation BenefitsVisitor CenterMy ProfileCommunities Open ForumChapter CommunitiesSIG CommunitiesMy CommunitiesAll CommunitiesLearn & Engage Special Interest GroupsUpcoming WebinarsWebinar cannot generate RecordingsNAVUG AcademyOpen ForumVolunteerPartner Company DirectoryConferences NAVUG SummitSummit EMEAFocus 2017News & Resources Acronym GlossaryBlogsNAV 2016 ResourcesMagazineNewsCredentialed ProfessionalsAbout Us Board of AdvisorsContact UsAbout NAVUGFrequently Asked QuestionsShop NAVUG Store Open Forum Community Home Discussion 7.4K Library cannot generate sspi 167 Blogs 136 Members 8.2K sort by most recent sort by thread Topic: HomeJoin TodayChaptersFind a ChapterMy Chapter CommunityMy Chapter RegistrationsMembershipLevels & PricingNetworking BenefitsEducation BenefitsVisitor CenterMy ProfileCommunitiesOpen ForumChapter CommunitiesSIG CommunitiesMy CommunitiesAll CommunitiesLearn & EngageSpecial Interest GroupsUpcoming WebinarsWebinar RecordingsNAVUG AcademyOpen ForumVolunteerPartner Company DirectoryConferencesNAVUG SummitSummit EMEAFocus 2017News & ResourcesAcronym GlossaryBlogsNAV 2016 ResourcesMagazineNewsCredentialed ProfessionalsAbout UsBoard of AdvisorsContact UsAbout NAVUGFrequently Asked QuestionsShop NAVUG Store Copyright © 2016 Dynamic Communities, Inc. All rights reserved. Contact NAVUG| FAQ | Privacy Policy | Code of Conduct Site designed by Brightfind Powered by Cobalt xRM and Higher Logic Powered by Higher Logic
setup NAS server for client to do the nightly Job Queue events we were stuck with the problem of NAS failing to do anything after starting up. In the event log there were three Event ID 20010 Warnings: The following ODBC error occurred: Error: [Microsoft][ODBC Driver Manager] Function sequence error State ID: HY010 The following ODBC error occurred: Error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state State ID: 24000 The Application Server for Microsoft Dynamics NAV NAVSRVAPL-SQL could not initialize properly. The server will attempt to initialize every 30 seconds until this is successful. When starting without any jobs in the Ready state NAS would initialize but didn't have these warnings because it had nothing to do. The Resolution After series of investigations we came up with the clue to investigate further. I created the test table that had only two fields: 1. Primary key, 2. Datetime. As the primary key field was setup as Autoincrement we managed to recreate the error we saw with NAS using the same user that was used to start NAS. This was strange because this user had dbo role in SQL server that is required for user when using Autoincrement property - as NAV Development Documentation states. When removing Autoincrement property from the primary key field the error didn't appear anymore. We setup simple codeunit, that would increment this simple table, in Job Queue but the problem reappeared again. After "digging deep" in the NAS initialization process in standard NAV codeunits we found out that the two tables that are used in this process also had Autoincrement property set to YES. These are tables 405 Change Log Entry and 474 Job Queue Log Entry. Because inserting records in these two tables were failing the NAS failed to do anything but to report error. We removed Autoincrement property and added code to populate primary keys of these two tables incrementaly. After that the NAS started normally and was executing jobs in Job Queue. The Conclusion We believe that the problem is, still, with the assigned SQL rights for the user that is running NAS, although it had db_owner rights on that database, but we could not investigate further because this was production environment. All the other NAS implemenations were working properly without this "intervention" on the standard Microsoft Dynamics NAV code or tables. But this is the workaround we had to implement to overcome this situation. Update After moving client's database to another SQL server this problem went away (as did the few other). This encourages me to believe that the db_owner rights were messed up somehow on initial SQL server. errorfunct