In Lotus Notes Client, we can create new replica by manual but it was a lot of databases, decided to create a copy of our agents to run. But we are not a copy, a replica. We, NotesDatabase.CreateCopy method (it only copies the design) does not copy the documents found. Our method can not obtain a handle to all documents in the source database are copied to the destination database that could have been. But instead we had to use another approach. Then we have a unique replica and create a new replica ID of the database decided to change. This creates a copy of the database.
Read more…
Viewed 22535 times by 7670 viewers
Notes 6 agents introduced the ability to run a client agent in a background thread. This is a very powerful feature, but you have to know how to properly use it. First off, you cannot perform any UI tasks. However, this is not a drawback. Print statements do work – the results go to the status bar just like any other agent running on the client. The MessageBox LotusScript statement also works. A message will be popped up for the user, and you can proceed in your agent based on the answer (your agent waits until the box is clicked).
Read more…
Viewed 7508 times by 2565 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 10936 times by 3324 viewers
For enterprise company with use many Domino Server for share load. If you create an agent you intend to deploy on multiple systems, you may find:
- The server names on which you need to deploy are different from the name of your server. In addition, you may not know the server names in advance.
- The agent developer’s signature is different from the end user’s signature.
- The development server does not have a certificate in common with the production server.
We will look at several approaches to solving the first two issues, which in turn, will make the certification issue irrelevant.
Read more…
Viewed 13021 times by 3626 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 14349 times by 4014 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 10082 times by 2809 viewers
I think Replication conflicts created by agents are no different from replication conflicts created by other means and they happen because more than one entity (a person, a process, or an agent) modified the same note at the same time same as create document by user. Some common situations to check for:
- Agents with the wild card Any Server specified as the server to run on
- “After new mail has arrived” agents running on the server whose Notes.ini file contains the variable AMgr_DisableMailLookup, which suppresses the check for the home mail server (thus, making it possible for an agent to run on more than one server)
- A local replica with an agent modifying the same documents as the server-based agent
- Different events triggering agents that modify the same document (for example, QueryOpen and QuerySave)
Viewed 6339 times by 1961 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 10710 times by 3355 viewers
In order for “After new mail has arrived” triggered agents to run on Notes/Domino Servers, the following must be true:
1. The signer of the agent (the last person to save or enable the agent) must have their mail file located on the same server as where the agent will run. The server determines this by taking the name of the last person to save the agent, performing a person lookup into the Domino Directory and retrieving the Mail Server from that user’s Person document. If the Mail Server in the Person document is different than the current server, the agent will not run. If the person is not found in the directory, the agent will not run. This person lookup is performed every time the agent loads to run. Remember, if the User ID is hierarchical, the user name in the Person document must also be hierarchical. This is stored in the field “FullName” in the Person document.
Read more…
Viewed 6221 times by 2091 viewers
If you have created a scheduled agent and want run scheduled on locally. However, the agent does not run according to schedule. You are able to run the agent manually.
1. For scheduled agents to run locally, you must enable the User Preference “Enable scheduled local agents.” The exact steps to enable this option are as follows:
Read more…
Viewed 7209 times by 2635 viewers
