Navision-Backup Error 1185

Irchik

Navision version:

Navision DB 2.6, converted to Navision 3.7 (Native DB)


Problem description:

After an electricity failure our internal Navision backup doesn’t work any longer. The backup aborts with the error message "Error 1185 in module 19".
Seems to be a sure sign that the database space is too small and has to be extended. But the database is working at full capacity to 60 per cent.
Anyway we tried to extend the database file. Without success, the error message is still the same. This error appears also in the “Check database” function.

To detect the error we tried to check every table separate. We pinned down the error in table number 32 (“Item ledger entry”). Checking the keys for this table results in the error message shown in attachment 2.

To fix the error we tried to copy all data records into a new table. The copying process of each record has been confirmed by COMMIT to detect the corrupt records. We noticed that the error is caused by 13 related records.

The concerned records can’t be displayed or deleted neither by filter nor by code unit. Scrolling through the records produces the same error message.
We need a tool which is able to delete the concerned records directly from the Native DB respectively a recovery tool which is able to exclude the corrupt area.

I hope you can help us with this problem.

Thank you very much.
](*,)

kriki

Try this:
-Copy the DB-file(s).
-Open the copy
-remove all secondary indexes from T32
-backup the DB
-if the backup is successful, restore it in a new DB (the old one is corrupted)
-restore the secondary indexes in T32.

Irchik

thanks for your post. I'll try this.

Irchik

I've tested your solution but it do not work. db backup break whit an error.
While testing the primary key of T32 an error appears also.
Error 1185 in modul 19

Table: Item ledger entry
Company:...
Key: Entry No.

.....

[-o<

ara3n

Create a new company.
Write a routine to copy all the tables from the old company to the new company.
Exclude the corrupted records.

Now you have a company that is exactly like the old one except the corrupted
records.

Backup the new Company and restore it in a new db, and start using it.

You can research what the corrupted records are and recreate them if possible.