Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
ODBC Error after LAN Cable unplugged
julkifli33
Member Posts: 1,073
hi all... i am using nav 2009 R2, using RTC
i have a case... one day my LAN cable was inadvertently unplugged....
and then after that my RTC is cannot run
i had several times happened to my computer
and for the completion is .... i restart my computer
is there any other way to solve this problem?
the error message is
The following ODBC Error occured : Error [Microsoft][ODBC SQL Server Driver] cannot generate SSPI context state ID : HY000
i have a case... one day my LAN cable was inadvertently unplugged....
and then after that my RTC is cannot run
i had several times happened to my computer
and for the completion is .... i restart my computer
is there any other way to solve this problem?
the error message is
The following ODBC Error occured : Error [Microsoft][ODBC SQL Server Driver] cannot generate SSPI context state ID : HY000
0
Comments
i had the same problem today from one client computer. basically i was receiving this message when trying to connect to nav database using classing client for sql. after reading some threads about the issue, i figured that the problem might be with the mixup in user credentials (since it's a windows login). the way i solved the problem is that i reset the user password for the user that had the issue with logging into the database and the problem was fixed.
hope this helps.