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 395 times by 118 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 780 times by 279 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 460 times by 170 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 539 times by 245 viewers
