Re: UNKNOWN REASON (-1017)
- From: "Adam" <adam@xxxxxxxxxxx>
- Date: Wed, 5 Oct 2005 10:53:53 +0100
Sorry I did not respond. This is a critical system and I focused on
resolving the problem as quickly as possible.
I did resolve it but not in the most satisfactory way.
I believe it was caused by a corruption in the dataset. I found and was able
to delete a corrupt record in one table but that did not cure the problem.
The company did not want to resort to creating a new dataset from the farm
as it had not synced for over 24 hours. I therefore I nervously ran a Repair
and Compact on the dataset. This did resolve the problem but also deleted
some records from several tables. I manually recreate these records from a
copy of the corrupt dataset and everyone was happy and still are. I believe
a safer way of correcting this would have been to create a new dataset from
the farm and manually recreate the missing records from the corrupt dataset.
.
- Prev by Date: Re: Replication, sharing and exclusive access
- Next by Date: Re: UNKNOWN REASON (-1017)
- Previous by thread: Re: Jet 4 Replication Service Pack
- Next by thread: Re: UNKNOWN REASON (-1017)
- Index(es):