Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 298 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
Upgrade to NAVW15.00: ODBC SQL Server Driver error
ronvdw
Member Posts: 16
Hello,
I just finalized the upgrade of a NAVW14.00.03 application to NAVW15.00. Unfortunately I cannot import the object file because a SQL Server Driver error occors.
Error: [Microsoft][ODBC SQL Server Driver]String data, right truncation
State ID: 22001
I noticed the problem is caused by a field name with the following name:
Enabled Field No. Field Name Data Type Length Description
Yes 7 Cleanup Action Outbound Option
If I rename this field to "Cleanup Action Outboun" (without the last character) it works. It seems to be caused by the length of the field name. If I remove the table and import the fob file it works ok.
Does anyone suffer the same problem?
I just finalized the upgrade of a NAVW14.00.03 application to NAVW15.00. Unfortunately I cannot import the object file because a SQL Server Driver error occors.
Error: [Microsoft][ODBC SQL Server Driver]String data, right truncation
State ID: 22001
I noticed the problem is caused by a field name with the following name:
Enabled Field No. Field Name Data Type Length Description
Yes 7 Cleanup Action Outbound Option
If I rename this field to "Cleanup Action Outboun" (without the last character) it works. It seems to be caused by the length of the field name. If I remove the table and import the fob file it works ok.
Does anyone suffer the same problem?
Connectivity Studio for Microsoft Dynamics NAV - Where Microsoft Dynamics NAV meets the world
0
Comments
Known bug...please check post:
http://www.mibuso.com/forum/viewtopic.php?p=104781#104781
Vice President, Deployment Operations
Symbiant Technologies, Inc.
http://www.symbiantsolutions.com