Here’s the scenario:I’ve two databases on unconnected servers. They transfer data by means of a mail-in setup (established before I came around & working correctly until recently.) The transfer involves some text conversion, but that’s immaterial here.
The sending server is Win-tel. The receiving server is AIX. (It used to work when it was also Win-tel.)
The development client has been one of Win2K and XP using 5.0.12 dev client.
What’s happening is this:
The receiving (mail-in) db is on AIX and will not trigger its agent when the documents are received.
I’ve tried several options for getting the agent to respond, but to no avail. Triggers have included both When mail is received and When and documents are created or modified, with and without naming the specific folder for finding the documents.
There were no issues when the receiving server was Win-tel.
Are there any issues with agent triggers on AIX when compiled by a Win-tel client?
TIA,
Collin
KC8TKA
Subject: Re: Agents & AIX
Looks like I’ve got another issue to resolve as well.Here’s the agent log when manually RunOnServer:
08/19/2004 08:05:34: Error Exit 4005 107Notes error: Cannot write or create file (file or disk is read-only) (\import.txt)
08/19/2004 08:05:34: 11
Ran LotusScript code
Done running agent ‘Import From Text File’ on 08/19/2004 08:05:34
Subject: RE: Re: Agents & AIX
Looks like security is different on two servers. All other differences are completely invisible to the agents. I would start by running “test” diagnostic from designer and see what it tells you. You need to have the highest priviledges to operate on files. For more info on security, please refer to Agent FAQ ‘Troubleshooting agents’. It has a lot of info on security as well as info “test” diagnostic if you are not familiar with it.
Subject: RE: Re: Agents & AIX
Julie,I executed some tests by having my ROS agent execute the target agent via .RunOnServer.
From that I was able to diagnose the first basic error – file extraction was done to “c:.…”. That has been changed to employ a simple file name and use the current directory. This solution works fine for this aspect, though it does not affect the triggering problem.
I also built 2 test databases using the same template. Db #1 is a “sender” like the original remote db; db#2 is the “receiver”.
The Sender-Export and it’s complement Receiver-Import agents use the same script library but execute different functions within that library. Interestingly the Sender-Export agent works fine (triggers as it should), as it always has and does so on any platform.
I’ll also take a look @ the FAQ. Thanks.
Collin
KC8TKA