Hello all,
I have a problem concerning an agent not doing all it is supposed to do. I test my agent on my dev server (Domino 7) and it works as expected to.
On my customer’s server (Domino 6.5), the agent runs and no error is raised. But some operations done by the agent don’t appear to take effect. There are 2 pairs of fields that should be synchronized between 2 documents, but agent doesn’t seem to do it like expected to.
I am not using any new feature only available in Domino 7. I sent a copy of my dev database to my customer. They tried my copy on their server and it works.
I’m a bit puzzled why it does that. I have looked at logs on both servers and have found nothing suspicious.
Any advice will be greatly appreciated.
Subject: Agent problem
Remi,
You just have to debug more. Sorry, no silver bullet for this description.
regards,
raphael
Subject: Agent problem
I finally solved the problem. I’m still puzzled as to why Domino was using a backup copy of my agent instead of the actual working agent. There is no way Domino could have gotten gotten confused between the 2 agents (the backup had a very different name with no alias and the working copy had the right name with a unique alias) I simply moved the backup copy of the agent to a backup NSF file and things started working as expected to.
If someone has a detailed explanation as to why Domino got confused between my 2 agents, I would really love to know.
Thanks for all the help
Subject: Agent problem
This problem occurs when your busy server (production) behaves differently as on a test or small data set.Check your agent if it updates key fields in the view you are using to get to the next document. It will cause rebuilt of the sequence in the view and it may skip some documents.
Or you may be deleting documents from the same view that will cause the same effects of skipping a few docs.