Domino 9 und frühere Versionen > Administration & Userprobleme

Agenten nur eingeschränkt

<< < (3/3)

MOD:
Hi steuerbert,

auf dem Applikationsserver
tell amgr quit
load amgr

Danach den Agenten neu bearbeiten.

Gruss

;D MOD

steuerbert:
Habe die Lösung in der knowledge base gefunden:

http://www-1.ibm.com/support/docview.wss?rs=475&context=SSKTWP&q=Amgr_DisableMailLookup&uid=sim16ce53ee6566365b28025672f00561bff

Amgr_DisableMailLookup=1 Does Not Disable the Lookup Check for New Mail Agents

Problem:

A New Mail Triggered agent is not running as desired, and results in the following error:

"AMgr: Agent '<AGENT NAME>' will not run.  It is intended to run on <SERVER NAME1> not <SERVER NAME2>"

Where SERVER NAME1 is the agent signer's home mail server and SERVER NAME2 is the server the agent resides on.

The error was not expected, as the server the agent resides on is using the NOTES.INI parameter:

Amgr_DisableMailLookup=1
 
Note:   New Mail Triggered agents require that the agent reside on the home mail server of the signer of the agent, unless the disable parameter Amgr_DisableMailLookup=1 is used.  For more information on this topic, refer to the Related Documents noted below.

Solution:

This issue was reported to Lotus Quality Engineering and has been addressed in Notes/Domino 5.0 (R5), 4.6.4a and 4.6.5, where the Amgr_DisableMailLookup parameter functions properly.

Excerpt from the Lotus Notes and Lotus Domino Release 4.6.4a QMU and 4.6.5 QMR fix lists:

SPR# AGRM42HHQ9 - Fix certain cases of the AMGR_DISABLEMAILLOOKUP notes.ini variable not working as intended. The problems have been present since R4.6 shipped and were recently diagnosed successfully. This notes.ini variable is intended to allow agents trigered by new mail to work on servers other than the user's home server, to support mailfile replicas. [4.6.4a, 4.6.5]

Supporting Information:



Related Documents:

Caveats with New Mail Triggered Agents on Notes/Domino Servers
Document #: 138594

Navigation

[0] Themen-Index

[*] Vorherige Sete