Yes, I just fixed one the other day. A hash of meta-data is not matching up
to the safeguard column. Usually this is due to direct db changes to the AR
meta-data (that was exactly it in our case).
What I did was re-import a def of the form which reset and corrected the
safeguard data. The catch is you need another ARS server that does not have
the safeguard mismatch already or have good definition of the form because
you will most likely get the Safeguard mismatch error when trying to export
the form (or delete it for that matter).
Hope this helps.
Jason
On Wed, Aug 25, 2010 at 10:01 PM, Bhupesh Gupta wrote:
> **
>
> 390600 : Safeguard mismatch - potentially corrupted form (ARERR 8841)
>
> Supplier Order
>
> HAS anyone had an issue with the safeguard in a form ... has anyone been
> able to resolve the mismatch... does anyone know how the relationship on the
> safeguard is performed? (arschema has a safeguard column ... but not sure
> how Remedy checks the relationship between arschema and an individual form)?
>
>
> Please advise
>
> --
> Regards,
> Bhupesh Gupta
> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
