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 Converting 2013 to2013R2
colrees
Member Posts: 3
Hi
I am getting an error when trying to open my 2013 database in 2013R2 Dev environment, to start conversion.
"Invalid Column Name Hash" in Object Metadata table
Then...
"Field number 30 is not defined in the Object Metadata table"
I can see that it doesnt exist in 2013 but does in 2013R2 but surely this is taken care of during the conversion?
Does anyone know why this would happen, or how I can get round this?
Thanks
C
I am getting an error when trying to open my 2013 database in 2013R2 Dev environment, to start conversion.
"Invalid Column Name Hash" in Object Metadata table
Then...
"Field number 30 is not defined in the Object Metadata table"
I can see that it doesnt exist in 2013 but does in 2013R2 but surely this is taken care of during the conversion?
Does anyone know why this would happen, or how I can get round this?
Thanks
C
0
Comments
The "Object metadata" table is a default table in NAV 2013 .
If this table does not exist something is very wrong.
Try to import this table from somewhere else.
After this compile all objects, this will re-create all entries in the Object Metadeta table.
Try to convert the database now.
I hope this helps.
Thank.s
Problem solved!
I had a (totally unrelated) database in my sql server that was corrupt
I deleted this and hey presto! all was hunky dory!!
Col