• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 282
  • Last Modified:

Agent not working

Scenario:  I have 2 databases. We'll call them database A and database B.  I create a document in database A. Upon hitting the submit button, it calls an agent to copy the document to database B. It does this with no problem.

I have an agen in database B and it is not working.

It is set to run if New documents have been created or modified, I have 2 forms selected for it to act on, and the formula is a simple @Mailsend formula.

It is not working. Thought it might run in 30 minutes, but it never did.

Any suggestions?
0
schmad01
Asked:
schmad01
  • 3
  • 2
  • 2
  • +1
1 Solution
 
SysExpertCommented:
Did you try running it as scheduled on all new Docs, and add agent logging to see what happens ?

I hope this helps !
0
 
schmad01Author Commented:
No, didn't try that.  Will try.
0
 
HappyFunBallCommented:
There used to be bugs with agents that use the New Documents trigger and years ago I stopped trusting them to work.  You might try a scheduled agent that runs every 5 minutes instead.  
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Sjef BosmanGroupware ConsultantCommented:
Never had problems with New document agents, in the sense that the trigger always works. I never used the selection formulas with it, I used my code to find out what documents to process.

Can you simplify the agent, e.g. remove all code from it, so you can see in the agent's log that it ran? You can change those 30 minutes delay if need be, using a Notes.ini parameters.

Last option: creating a document in dbB can also be accomplished by mailing the document to a mail-in database. You could use a When new mail has arrived as trigger...
0
 
HappyFunBallCommented:
I should clarify, sjef_bosman, that the problems I had with new document triggers date back to R4 or early R5 days.  I've long since lost the technote that confirmed it, but there was a problem years ago.  I believe the recommended solution at that time was to use scheduled agents instead and I've just never looked back.  I'm glad to hear the triggers have worked for someone, though.  Maybe its time I gave them another chance ;-)
0
 
Sjef BosmanGroupware ConsultantCommented:
I always try the "right" way first, which means that my head is full of bumps banging my head into the same Notes-problems over and over again. Example: it used to be impossible to use background and UI objects in the same library. And suddenly that was possible. And more things like that. I should of course have read the release notes, but who reads them all?? Occasionallly, I miss a new function or method, but once discovered it's added quickly to the toolset ;-)

You're back in Notes business?? Good! It's gone rather quiet here lately...
0
 
HappyFunBallCommented:
Well, I'm off and on this forum still.  I go in cycles, depending on how busy it is around here.  

I remember that background agents and UI objects issue.  I figured out that declaring a UI object (dim w as NotesUIWorkspace) would stop the background agents from running.  But the way around that was to declare a Variant and then assign that Variant to the new UI object.  See, I still remember the workaround and would never have known that bug had been fixed unless you told me.  

Back to the issue at hand, though.

schmad01,

I wonder, does the agent in Database B work if you create a new document and save it manually?  Make sure to check the server logs to see if it was triggered, if the agent doesn't do anything obvious.
0
 
schmad01Author Commented:
Gave me some ideas to try. Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now