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
- 264 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
SQL Error "Optional feature not implemented"
BorisK
Member Posts: 45
For one of our customers we are trying to upgrade Navision SQL client version from 3.60 to 4SP3. We successfully created a test database for vanilla 4SP3 but they decided that they wanted to go further and take it to 4SP3 Update 6. We restored their live SQL backup into a test database and converted it. On the surface it looks OK but they came across a SQL error which we can't understand. For some Tables when attempting to insert a record (whether in code or manually) an error pops up:
[Microsoft][ODBC SQL Server Driver]Optional feature not implemented
State ID: HYC00
When trying again a different one appears:
[Microsoft][ODBC SQL Server Driver]COUNT field incorrect
State ID: 07002
We can't see anything common for the Tables where the error occurs.
Any ideas anyone?
[Microsoft][ODBC SQL Server Driver]Optional feature not implemented
State ID: HYC00
When trying again a different one appears:
[Microsoft][ODBC SQL Server Driver]COUNT field incorrect
State ID: 07002
We can't see anything common for the Tables where the error occurs.
Any ideas anyone?
0
Comments
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
The cause of this error is usually that your query contains a reference to a field which does not exist. You should verify that the fields included in your query exist and that you have specified their names correctly.
recompile all the objects. Or Export and then import all the objects.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n