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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 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
Error in NAV 2018 on Export-NAVData/Import-NAVData
Armonds
Member Posts: 66
When I try to export company in event viewer I get error: "Data is Null. This method or property cannot be called on Null values"
On import error is: "SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM"
I think in both cases error is raised by the same field or property.
On export error occurs almost immediately, but on import after all data is imported end on the finalization phase.
I tried to check for some exceptions with SQL Profiler, but didn't found anything suspicious.
What could cause this error or how to find/source if it?
Other NAV functionality works without errors, database is synchronized...
On import error is: "SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM"
I think in both cases error is raised by the same field or property.
On export error occurs almost immediately, but on import after all data is imported end on the finalization phase.
I tried to check for some exceptions with SQL Profiler, but didn't found anything suspicious.
What could cause this error or how to find/source if it?
Other NAV functionality works without errors, database is synchronized...
0
Best Answer
-
OptionsArmonds
Member Posts: 66
I found what caused Import/export error.
Tables 6701,6703..6705, 6707 from NAV 2009 are replaced with new tables in NAV 2018, but in NAV 2018 this tables TableType != Normal.
Even after successful synchronization in table "Object Metadata Snapshot" are left obsolete records from NAV 2009 with NULL value in columns Base Metadata and Base Hash, after manually deleting this records import/export works.
So it's crucial to delete this tables in NAV 2009 before migration to NAV 2018.2
Answers
I checked all global tables in SQL but didn't found any date field with NULL.
And also, if i'm not wrong, in NAV date field are not null by default (except taskscheduler system table)
Tables 6701,6703..6705, 6707 from NAV 2009 are replaced with new tables in NAV 2018, but in NAV 2018 this tables TableType != Normal.
Even after successful synchronization in table "Object Metadata Snapshot" are left obsolete records from NAV 2009 with NULL value in columns Base Metadata and Base Hash, after manually deleting this records import/export works.
So it's crucial to delete this tables in NAV 2009 before migration to NAV 2018.
I have the same issue on Event Viewer when trying to export navdata. You said that "Tables 6701,6703..6705, 6707 from NAV 2009 are replaced with new tables in NAV 2018", but in NAV 2009 R2 I do not have the tables 6701,6703..6705, 6707 ... it is 6.00.33277 build .. How can I check the tables that bother me?
Thank you and have a great day !