Database structure error

tinik
Member Posts: 22
Hi to anyone,
I have encountered a msg 'there is an error in the database structure.' I already identified the corrupted data in the G/L entry table. Everytime this particular entry is accessed even just by 'find', the msg always appears. So i have come up with a codeunit to identify the exact entry and a dataport to filter the good data. Then deleting all data in the G/L table but in a back-up database, then restoring it. My question is.. what could have caused this data corruption? :-k
Regards,
Tinik
I have encountered a msg 'there is an error in the database structure.' I already identified the corrupted data in the G/L entry table. Everytime this particular entry is accessed even just by 'find', the msg always appears. So i have come up with a codeunit to identify the exact entry and a dataport to filter the good data. Then deleting all data in the G/L table but in a back-up database, then restoring it. My question is.. what could have caused this data corruption? :-k
Regards,
Tinik
0
Comments
-
There could be many reasons that could cause such an error, e. g. if you write from outside into the database (C/ODBC, C/FRONT).
Do you have a error message like "Internal error xxx in module yyy"?Timo Lässer
Microsoft Dynamics NAV Developer since 1997
MSDynamics.de - German Microsoft Dynamics Community - member of [clip]0 -
Great to here from you Timo!
Actually the message is.. 'The error (1213 in module 19) may have been caused by the computer or program.'
Table: G/L Entry
Company:
Key Fields: Entry No.
According to our other technical guy, the entry may have been a 'Credit Memo' posted. But here are other tables affected.. G/L Register (No.)
Ledger Entry Dimension (Table ID, Entry No., Dimension Code)
Purchase Line (Document Type, Document No., Line No.)
Purch. Inv. Line, Document Dimension (Table ID, Document Type, Document No., Line No., Dimension Code)
Detailed Vendor Ledg. Entry (Entry No.)
Would appreciate your input.
Thanks again.
Tinik0 -
Internal Error 1213 in Modul 19
Modul 19 means Database Error
Description: #Err_DB_RecSizeError
One reason could be aborting building keys while restoring a database backup.
Other possibilities are:
- hardware problems
- network problems
- corrupted *.zupTimo Lässer
Microsoft Dynamics NAV Developer since 1997
MSDynamics.de - German Microsoft Dynamics Community - member of [clip]0 -
how did you solved this ?0
-
air_wolf wrote:how did you solved this ?
Open the database with parameter "dbreadonly" and create a backup.
Restore this backup into a new database.Timo Lässer
Microsoft Dynamics NAV Developer since 1997
MSDynamics.de - German Microsoft Dynamics Community - member of [clip]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