SQL Server Error while importing fob

jorgito
Member Posts: 115
Hi all.
We recently received Navision 4 SP1 and we have merged the custom modifications with SP1 functionality. We created a final fob that contains all the functionality of SP1 along with the custom modifications made for the customer.
When we try to import tha fob into the live database of the customer, we get the following error.
The following SQL Server error(s) occurred while accessing the Item Ledger Entry table: ???103.
Any idea what that means?
Thanx
Jorgito
We recently received Navision 4 SP1 and we have merged the custom modifications with SP1 functionality. We created a final fob that contains all the functionality of SP1 along with the custom modifications made for the customer.
When we try to import tha fob into the live database of the customer, we get the following error.
The following SQL Server error(s) occurred while accessing the Item Ledger Entry table: ???103.
Any idea what that means?
Thanx
Jorgito
0
Comments
-
I know that Navision in SP1 has changed the key structure in item ledger entry for better performance. This may have something to do with it.
I would do a Navision backup. Create a local fdb and restore the backup. Load/import the improvements. Do another back of the local fdb with new objects and create a new db and restore the backup.0 -
I am sorry ara3n.
I did not completely understand.
Could you be more specific?
What do you mean by improvements? New objects?
I only have one fob that contains everything.
Jorgito0 -
The 4.0 SP1 version is not just objects. You also need to make sure that the executables are updated (this is less relevant for SQL Server, but I recommend doing this nonetheless), and that the database is a 4.0 SP1 database, before you can import SP1 objects. It is possible to convert the database by opening the 4.0 database with 4.0 SP1 executables, but the right way to go about is to create a new database with 4.0 SP1 executables, and restore the 'old' database into it, which should take care of all your keys. Then it should also be possible to import new objects without getting errors.0
-
ara3n wrote:I would do a Navision backup. Create a local fdb and restore the backup. Load/import the improvements. Do another back of the local fdb with new objects and create a new db and restore the backup.jorgito wrote:What do you mean by improvements? New objects?Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions