Lotus Notes Error The Collection Has Become Invalid
has become invalid" LotusScript GetDocumentByKey GetAllDocumentsByKey OIHZ7UVJ7T AJMO7LHMK9 %a's Certification Log Error 4000 Error 4678 The collection has become invalid Technote (troubleshooting) 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 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 Fix Pack 2 and 8.5 Fix Pack 1. The abnormal error message has been corrected (fixed in 8.5.1 and 8.0.2 Fix Pack 3) 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 releases, SPR# CSCT836HFL was created as a regression for this behavior. For more information and fix details about SPR# CSCT836HFL, see technote #1424178. Workaround 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. By using the "On Error" statement with error number 4000/4678 around GetDocument/Entry calls, you can trap the 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. Related information
their logs on Domino 7.0.4, 7.0.4.1, 8.0.2.2, 8.0.2.3, 8.0.2.4, 8.5.0.1, 8.5.1, and 8.5.1 FP1. This error will show in your log file as "The collection has become invalid." It is caused by a fix to another SPR where in your LotusScript or Java code, you are looping through a view, using GetDocumentbyKey(key). The original fix was designed to prevent an infinite loop, which it did by limiting the number of iterations to a fixed number, and then returning an error afterward. This in effect, broke http://www.ibm.com/support/docview.wss?uid=swg21396849 many applications, and required immediate remediation to get critical applications working. Organizations with thousands of lines of this code, faced huge issues! A hot fix was released yesterday (March 12) to address this problem. Now the algorithm still ensures that only a limited number of attempts is made to update a view. However, instead of returning the error message when http://wordpress.strongback.us/2010/03/important-hot-fix-for-lotus-domino-error-the-collection-has-become-invalid the view is unable to be brought up to date, the code will return the most recent contents of the view. This allows existing applications to work as they always have, with no modification. If you are running any of the above versions of Domino, you should submit a PMR to get the hotfix. Click here to open a service request with IBM Support. ©2016 Strongback Consulting Previous PostLotus Symphony 3.0 beta now available Lotus Notes Next Post#LotusKnows Lotus Domino 6.5 support ends in two weeks (April 30) domino Comments are closed. Recent Posts A Rosetta Stone for IBM's Jargon and Acronyms 5 Tips to Accelerate Adoption of Rational Developer for System z Easy way to manage a developer's prioritized daily backlog What do the various link types in Rational Team Concert mean? Stop manual deployment or scripting deployments to WebSphere App Server - there is a better way Archives Archives Select Month August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 October 2015 August 2015 July 2015 February 2015 October 2014 Septembe
number created by on 10/20/2016 Go back