Hi,
I have a agent which opens a “,” delimited text file, reads from the file and generates document in my LN db. The agent works fine and documents get generated. But the same agent does not work when scheduled.
Any idea?
Hi,
I have a agent which opens a “,” delimited text file, reads from the file and generates document in my LN db. The agent works fine and documents get generated. But the same agent does not work when scheduled.
Any idea?
Subject: Scheduled Agent for Txt File.
Are you using any UI-classes, like NotesUIWorkspace? These frontend classes are not available in the background. Or are you waiting for a MessageBox?
Subject: Check server/system level access to the network shares
Check server/system level access to the network shares. The agent runs under the server’s authority. If Domino is running as a service look at Services control panel applet for the name that is used to run Domino. I think by default it is “SYSTEM”, change this to an ID that has access to the shares that you wish open in your agent.
Subject: Scheduled Agent for Txt File.
On the second tab of the Agent Properties box, check the runtime security level. It has to be at least level 2: Allow Restricted Operations. Access to the local file system on the server is a “restricted operation.”
Subject: RE: Scheduled Agent for Txt File.
Hi Stephen,
I have changed the runtime security level to level 3. Allow Restricted Operations with full Administrative access. But still the agent failed. Does the server settings from the need to be changed from administration? The txt file is in a network folder.
Subject: RE: Scheduled Agent for Txt File.
“Network folder”… That gives me a hint:
When an agent is run on schedule it is the SERVER that executes the agent. This means that the SERVER needs to have access to the network folder and the folder has to be mapped for the SERVER.
I also recall that there is an issue when the domino-server is run as a service vs. run as an application… But right now I don’t remember exactly what the issue was; Something about that services isn’t allowed to use netowrk paths/folders…
Subject: RE: Scheduled Agent for Txt File.
I would think it’s either UI methods in your script, or how you are calling the network folder. When I do this for a scheduled agent, I use the UNC instead of drive letter, because it’s usually different when the server is running it than when you’re running it through the client.
Instead of
g:\folder_or_sharename
I use
\servername\folder_or_sharename