Has this ever happened to you: all of a sudden you see thousands of documents that were deleted months ago back in your application. Just about everyone I know who has created an application with local replicas has seen this happen. And everyone who has seen it wants to find out who did it so they can give them 20 lashes with a wet noodle. (Or at least a replication lesson).
Read more…
Viewed 13152 times by 3028 viewers
In Lotus Notes, the Agent Manager is not the only process that can run Lotus Notes Agents. In this section, we highlight how to view diagnostic information in router and Web agents.
Because the router executes pre-delivery mail agents, the Agent Manager use Notes.ini settings for logging and debugging have no effect. Instead, use the Logging level field in the Router/SMTP – Advanced – Controls tab of the server’s Configuration Settings document to control the level of errors written to the server console for pre-delivery agents. You can set the Logging level to Minimal, Normal (the default), Informational, or Verbose.
Read more…
Viewed 12863 times by 3825 viewers
First, when troubleshooting Lotus Notes Agent problems, it’s best to start with a good understanding of how agents and the Agent Manager work. So let’s begin by reviewing how agents are invoked in detail below.
On the server, agents can be invoked by:
Read more…
Viewed 16551 times by 4476 viewers
The Design Update task is a system process that updates database design from a database template. This task’s goal is to keep the database and the template in synch. When either the database or the template have been changed, and the user did not select the “Do not update” design property for specific design elements, the Design Update task updates the database to match the template. This sometimes causes problems for agents, typically described as “something is turning off my enabled agents in the middle of the night!”
Read more…
Viewed 10406 times by 2625 viewers
Property “After new mail has arrived” agents are designed to run on the home mail server of the agent owner (signer). If the agent is replicated from your home mail server to another system, or if you are trying to run an agent that was written by someone else, your home mail server will not match the server on which you are attempting to run the mail agent, and the agent will not run.
Read more…
Viewed 11789 times by 3247 viewers
Sometime I found this error raise when I run schedule agent by manual and I think this error is generated in a server-based agent (which can be a Web agent or any other agent invoked on the server) or embedded agent (an agent called by another agent) which references UI elements as trigger/search target settings in the agent builder.
For example, suppose you create an agent that has action menu selection as a trigger and all selected documents as a search target. When you invoke the agent from the browser, you receive the unsupported trigger… error.
The “all selected documents” concept is not understood within a Web agent; this setting is meaningful only in a Notes client. To fix the problem, change the target setting, for instance, to all documents or none. The following four options are not supported in this situation:
Read more…
Viewed 12602 times by 3825 viewers
