Value Entry already exists error in SQL but not in Native

Amitava_Mitra
Member Posts: 35
Hi,
One of our customer is using Navision 4.0 SP3 LS Retail on SQL Database at their stores for quite sometime. Suddenly their is an error coming "The Value Entry already exists. Identification fields and values:Entry No.='1079462'" while posting statement (I am sure most of you knows, basically day-end posting process in LS Retail, similar to sales invoice posting). I tried to debug the error, and found no value entry exists with that entry, and also there is no customization in codeunit 22, or no COMMIT function used.
I took the back up and restored the same in Native and tried to post the same statement in the Native database, but the error didnot occur and the statement and all other statements posted sucessfully. So, it seems to be an issue with SQL (may be something related to indexing, or cache, or something else, not sure), and I have been trying to resolve the same ](*,) ](*,) but no luck.
Can anyone help me out with some solution / idea? Thanks a lot in advance.
Thanks,
Amitava
One of our customer is using Navision 4.0 SP3 LS Retail on SQL Database at their stores for quite sometime. Suddenly their is an error coming "The Value Entry already exists. Identification fields and values:Entry No.='1079462'" while posting statement (I am sure most of you knows, basically day-end posting process in LS Retail, similar to sales invoice posting). I tried to debug the error, and found no value entry exists with that entry, and also there is no customization in codeunit 22, or no COMMIT function used.
I took the back up and restored the same in Native and tried to post the same statement in the Native database, but the error didnot occur and the statement and all other statements posted sucessfully. So, it seems to be an issue with SQL (may be something related to indexing, or cache, or something else, not sure), and I have been trying to resolve the same ](*,) ](*,) but no luck.
Can anyone help me out with some solution / idea? Thanks a lot in advance.
Thanks,
Amitava
0
Comments
-
Okay, finally got a solution \:D/ somehow. I set the MaintainSQLIndex property to 'No' for all the secondary keys of "Value Entry" table (in primary key it does not allow), and now the statements are getting posted properly.
Still it would be good if any SQL champ can elaborate the exact reason.
Thanks,
Amitava0
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