Hello. If anybody has a minute, we are experiencing a weird phenomena…
I have a java agent that is accessing a text file shared network drive. It runs ok running manually. The security setting is set to “2” on the agent.
On the OS level, “Everyone” seems to have all permissions to the drive.
Yet I recieve a FileNotFound IO exception when the scheduled agent runs.
The filename is hardcoded as “H:/my_text_file.txt”.
I then hardcoded the file name in the scheduled agent to be “notes.ini” and the scheduled agent accesses and prints the contents of the server notes.ini without problem…
so I am thinking there is some screwy access deal with scheduled agents on a server and shared drive access. has anybody experienced this before? Thank you very much for reading.
Subject: Domino agent and access to shared os drive
Probably your Domino server is running as a service on the server using the system account so that the domino console is visible. Then the windows OS will not allow access to network resources, this is part of the windows server security model and not an issue with Domino.So the java agent should connect the network resource using a username and password, but my experience with Java agents is not so much that I can tell you how to do that, hopefully someone else can.
Subject: RE: Domino agent and access to shared os drive
Thanks a lot for the info. The really weird thing about it is the access failures are intermittent. The agent was crusing one day and then it failed suddenly about 1:00 AM with the access failure. We couldn’t get it working again all the next day…then it decided working again about 10:00 AM two days later. Would the access stuff for a service on an xp server possibly be cached? It is really weird…
Subject: RE: Domino agent and access to shared os drive
V. close but actually because services do not log in, do not map network drives, so do not see network drive letters. Modify your agent to access the file via a UNC
\myservername\myfile.txt
and it will work as long as the service has access.
(Hmmm. Maybe the variability could be if someone is logged into the server console at the time as a domain admin?)