I have written an agent that, when run interactively (On Event), runs without a problem. However, when I schedule the agent to run, it fails with a “Path not found” error, which I believe relates to the section of code that is trying to pick up a file from a network drive, via the server.
I suspect this could be a security issue, but don’t have a clue where to look. Any ideas please…
Regards,
Ruth
Subject: Run agent interactively - “Path not found” error
Ruth.
Has the agent been signed by an ID that has unrestricted access? Accessing the filesystem requires a higher level of access.
Is the network drive mapped on the server? (How are you refercing it - e.g. in windows using a drive letter or using \server\share\path.…\finemame.ext )
If you’re mapping the drive as part of your code, remember the code is being run by the server and no one maybe logged onto that server. Therefore you’re going to have to specify the userid and password to access the drive.
How to debug, I would add some print statements and on error check (that then writes out the err # and message). Then look at the log.nsf on the server.
Subject: RE: Run agent interactively - “Path not found” error
Stephen,
Thanks very much for your response.
I am accessing the network drive via a drive letter and the agent has been signed by an ID with unrestricted access. I think I’m going to have to specify the userid etc as you mentioned. Thanks for the debug suggestions; I’ll try them out. As you’ve probably guessed, I’m a bit of a novice!
Subject: RE: Run agent interactively - “Path not found” error
If you knew to have the agent signed by someone with unrestricted access you’re (IMO) ahead of the curve.
The print is the lazy method, you could always create and write to your own log. I find this makes sense if you want to keep a history of events for later debugging (vs debugging to get something to work).
Subject: RE: Run agent interactively - “Path not found” error
make sure your source server has access to the destination server or share. your source server should have a domain account. That domain account needs to be given access to the destination server or share.
domain\server
acme\app01