Lotus V8

[cpateyron]

Bonjour,

j'ai un agent qui passe en erreur depuis la migration du serveur en 8.02
erreur :
20/05/2010 09:48:47 Agent Manager: Agent printing: ERREUR AU PAS 50 >> erreur 4678: The collection has become invalid.

ligne : Set docauto=viewauto.GetDocumentByKey(Mid(docmaj.List_modif(i),15,7),True)

Il semblerai que ce soit lié à l'exécution d'un autre agent au même moment. En effet, les seules fois ou il a planté, un autre agent s'exécutait.

Avez vous des infos la dessus ?

Des pistes ?

Merci
@ + christophe

[AlexandreV]

Et hop !

Problem
You have a LotusScript agent that uses the NotesView GetDocumentByKey/GetAllDocumentsByKey or GetAllEntriesByKey/GetEntryByKey method and are seeing this error message:
Error 4000: %a's Certification Log
or
Error 4678: The collection has become invalid

Symptom
LotusScript agent resulting in error: "Error 4000: %a's Certification Log" or "Error 4678: The collection has become invalid"

Cause
Error 4000: %a's Certification Log was caused by the fix for SPR # AJMO7LHMK9.

Resolving the problem
"Error 4000: %a's Certification Log" was caused by the fix for SPR # AJMO7LHMK9. This abnormal error message was reported in SPR # OIHZ7UVJ7T. Affected versions include: 7.0.4, 8.0.2 FP2 and 8.5 FP1.
The abnormal error message has been corrected (fixed in 8.5.1 and 8.0.2 FP3) to "Error 4678: The collection has become invalid". This error can occur when performing a GetDocumentByKey/GetAllDocumentsByKey or GetAllEntriesByKey/GetEntryByKey on a view that is constantly being updated by the server. After a certain number of unsuccessful attempts to perform the GetDocument/Entry call, the error is returned preventing an infinite loop/hang.

Because these LotusScript methods did not throw this error in previous Domino releases, SPR # CSCT836HFL (NotesView GetDocumentByKey and GetAllDocumentsByKey methods fail when a view needs to be refreshed more than 10 times) was created as a regression for this behavior.

SPR # CSCT836HFL is currently being investigated by Lotus Development.

If you have an agent (or more than one) that is encountering either of these errors, one way to work around this is by adding custom error handling to your agent to handle this error. Using the "On Error" statement with error number 4000/4678 around your GetDocument/Entry calls, you can trap this error and perform the necessary actions. For example, you can call "Sleep" on the agent for a certain number of seconds and then retry the GetDocument/Entry call.

[cpateyron]

Bonjour,

oui j'ai vu après.
En fait nous sommes en FP4 et on a toujours le problème.
Ils parlent de mettre en attente un agent , on fait comment ?
A priori la solution c'est de faire un goto dans le gestionnaire de cette erreur précise.
Avez vous des idées ?

@ + christophe