Retour
-
Titre
Baseline Archive Set Goes to Error Status -
Description
The baseline archive sets are going to error status in particular scenario as below:
Having two CSRs. In the first it has objects locked. In the second we add same objects that get a reserve.The user thinks to unlock an object in the first CSR so the second shows the object status as 'Wait for lock', even if it was in reservation.After this the user thinks he doesn't need that object anymore so he removes the object and gets the error in the archive log tab saying inserting...Checking the server.log, you can note a part of this error 'Inserting...' and also that Stat is trying to delete and update ST_%SHADOW table that don't exists anymore.
Connexion requise
Vous devez être connecté et disposer d'un contrat de maintenance en cours pour afficher les articles de la base de connaissances avancés.