First, yes, I’ve read the FAQ’s.
I setup an agent on a customer’s server to run after new mail arrives. It didn’t run. I then discovered that I needed to set the AMgr_DisableMailLookup ini variable to 1 - which I did. I restarted the amgr, but still nothing. I designed this agent originally on my company server and it ran perfectly as new mail arrived. I don’t understand why it won’t run now. This is the test output…
‘CN=Robert Pozsgai/O=xyz’ is allowed to run Personal/Formula/Simple Agents on ‘CN=tmamcat/O=tro’.
Agent will be run by the Agent Manager after new mail messages are delivered.
Home mail server for ‘CN=Robert Pozsgai/O=xyz’ is ‘CN=domsvr1/O=xyz’.
Agent will not run on ‘CN=tmamcat/O=tro’ unless AMgr_DisableMailLookup ini variable is set to 1.
Any ideas?
Subject: Help, please, with “after new mail arrives” agent
I’d try signing the agent with the server ID.
kjh
Subject: agent signing fixed it
I don’t understand it, but I signed the agent with the id of the customer IT guy and now it works. I have the same agent execution rights as he does (both in the localdomainadmins group). But, something’s different because now it works.
Thanks for the tip!
Subject: RE: agent signing fixed it
Try printing the EffectiveUser with the agent signed two different ways. And run ‘test’ on both ids. There must be a difference if the agent behaves differently.
I don’t see LotusScript rights listed in the test diagnostic. Is this a LotusScript agent?
Having admin rights does not mean you have rights to run agents (only FULL admins are granted all rights!).
Do you know the drawmakes using that ini variable? (If you need more info both “Troubleshooting agents” and “out of the inbox” articles in the Agent FAQ go over this). It might be an okay thing to do but make sure. It effects everyone on the server using this trigger so everyone will experience the side effects.
Subject: Help, please, with “after new mail arrives” agent
“I restarted the amgr, but still nothing.”
What if you restart the server itself?