Lotus Error Script Is Busy
Training Support Forums & community Events Rational Tivoli WebSphere Java technology Linux Open source SOA and Web services Web development XML My developerWorks About dW Submit content Feedback developerWorks>Lotus>Forums & community>Notes/Domino 8 Forum Notes/Domino 8 Forum Sign in to participate Previous Next Subject: error message "Error - script is busy" Feedback Type: Problem Product Area: Notes 8 Client Technical Area: Crash Platform: Windows XP client Release: 8.0.2 Reproducible: Always I have some code in the database Postopen event which verifies the user's ability to use the database. If the user is not allowed to use this particular replica, the code closes the current database and opens a replica on a different server. The code works fine under 6.5.6, but causes the Notes 8.0.2 client to crash. The error given prior to the crash is Error - script is busy. This is the part of the code. --------------------- ' Need to close current database before opening new database. Call CurDb.Close ' Verify new database is available NewDbOpened = NewDb.OpenByReplicaID (SelectedServer, ReplicaID) ' If available, then open If NewDbOpened Then Call ws.OpenDatabase (NewDb.Server, NewDb.FilePath) End If ------------- In following the code using the LotusScript debugger, the error is being caused by the Call ws.OpenDatabase command. Interestingly, commenting out the Call CurDb.Close command prevents the error and client from crashing, but I'm left with both replicas open, which is not what I would like. Any suggestions? Thanks, Scott. Feedback number WEBB82TKXA created by Scott T Little on 02/19/2010 Return to top error message "Error - script is bu... (Scott T Little 19.Feb.10) . . Place an "Exit Sub" after the call ... (Jean-Rene Berge... 19.Mar.10) Printer-friendly Search this forum Search this forum Sign In or Register Sign In or Register Sign in Forgot your password? Forgot your user name? Create new registration Member Tools RSS Feeds RSS feeds All forum posts RSSAll main topics RSSMore Lotus RSS feeds Resources Resources Forum use and etiquette Native Notes Access Web site Feedback Lotus Support Lotus Support IBM Support Portal - Lotus software Lotus Support documents Lotus support by product Lotus support downloads Lotus support RSS feeds Wikis Wikis IBM Composite Applications IBM Mashup Center IBM Connections IBM Connections Cloud Developers IBM
return "The collection has become invalid" Error 4678; GetDocumentByKey; GetAllDocumentsByKey; regression caused by AJMO7LHMK9; The collection has become invalid; Error 4000: %a's Certification Log Technote (FAQ) Question Certain LotusScript and Java view functions like GetDocumentByKey and GetAllDocumentsByKey now return "The collection has become invalid" when accessing frequently updated views. This is a change from prior releases where your code would wait until the view was up to date and then return the most current information. Note: The change was introduced in May of 2009 (7.0.4), July of 2009 (8.0.2 Fix Pack 2, 8.5 Fix Pack 1), http://www-10.lotus.com/ldd/nd8forum.nsf/22bda8373a3a2e798525752e00727c7b/837298c2954f04ec852576cf0053f95a?OpenDocument and October of 2009 (8.5.1). What's the current status of this issue? Answer A fix is available in the following releases: 8.5.2, 8.5.1 Fix Pack 3, 8.0.2 Fix Pack 6, and 7.0.4 Fix Pack 2. In this technote, originally published on March 12th, 2010, customers were alerted to the availability of a hotfix for this issue (SPR CSCT836HFL/APAR LO49368). The issue manifests in custom Notes applications with agents http://www.ibm.com/support/docview.wss?uid=swg21424178 that access view collections and can be diagnosed by the existence of the following errors in the Domino server log: -- "Error 4000: %a's Certification Log" (in 7.0.4, 8.0.2 FP2 and 8.5 FP1) -- "Error 4678: The collection has become invalid" (in 8.5.1 and 8.0.2 FP3) What's changed? The hotfixes developed in March were recalled in April. A fix is available in 8.5.1 Fix Pack 3 and will be available in additional Fix Packs shortly (see below for detailed schedule). Updated hotfixes are available for customers unable to wait for a Fix Pack. No action on your part is required if: You are not currently impacted by this issue and you have not previously applied a hotfix for SPR CSCT836HFL. Action on your part is recommended if: You are encountering one of the errors described in this technote for SPR CSCT836HFL. Recommended Actions: If possible, IBM recommends applying a Fix Pack with the fix. This could mean waiting for the availability of a fix in a Fix Pack or Maintenance Release (see below). If you need the fix sooner, and a Fix Pack is not available for your release, request the new hotfix. Which Maintenance Release and Fix Packs contain the fi
library Troubleshooting agents This article introduces tools you can use to troubleshoot Domino 4.6 agents, and looks at some common problems with agents and their solutions. (For help with R5 and Notes/Domino 6, see the LDD Today article Troubleshooting agents in Notes/Domino 5 and http://www.ibm.com/developerworks/lotus/library/ls-Troubleshooting_agents/ 6.) Share: Julie Kadashevich, Software Engineer, Lotus Close [x] Julie Kadashevich came to Iris in March of 1997 after working at FTP Software on Java and C++ mobile agent technology. Previously, she worked in the area of applied Artificial Intelligence at Wang Labs and received five patents in the field. She has Bachelor's and Master's degrees from Boston University, both in computer science. Outside of the Agent Manager, lotus error her two main interests are photography and quilting. 02 March 1998
Table of contents Some background Debugging with Notes.ini settings Debugging using the NotesLog class Debugging at the server console Common problems Conclusion Resources Comments When you've designed a great agent, what do you do when it won't run? In my previous articles for Iris Today, we talked about the factors that affect who can run agents in lotus error script "Controlling the agents in your system," and when the agents run in "Minimizing delays in the Agent Manager." This time, we'll look at the specific steps you can take to troubleshoot agents to find out why your agents won't run. This article will first introduce you to the different tools available for troubleshooting agents, including Notes.ini settings, the LotusScript NotesLog class, and server console commands. Then, we'll look at some common problems you may run into when developing agents, and explain the possible causes and solutions for each situation. Note that this article describes troubleshooting agents in Notes/Domino 4.6. For information on troubleshooting agents in R5 and Notes/Domino 6, see the LDD Today article, "Troubleshooting agents in Notes/Domino 5 and 6." Some backgroundBefore we begin examining the tools for troubleshooting, we should review a few points about agents and the Agent Manager. Whenever you find that your agent won't run, you should first look at the Agent Log. The Agent Log will show you the last time the agent executed, and whether it completed its execution. For more detailed information, you should examine the server console or Notes Log (under Miscellaneous events) for any messages from the Agent Manager. If you don't have phys