Problem with Scheduled agent accessing Network file

I have just set up a test environment for 6.5.1 in preparation to migrating from 5.0.12.

I came across a problem with a scheduled agent which I cannot solve. The agent is scheduled to run weekly to create a Excel 97 report.

When it runs it Excel come up with the following error:

“File cannot be accessed. The file may be read only, or you may be trying to acces a read only location. Or the server the document is stored on may not be responding.”

The code snippet is…

Set xlApp = CreateObject(“Excel.application”)

xlApp.Visible = True

Set xlWorkbook = xlApp.Workbooks.Add “g:\hr_it\leavetem.xls” )

  1. The agent runs fine when run via the Client on the server.

  2. The file is not Read only

  3. we have full access to folder and files

  4. Agent is signed by the Notes Administrator

  5. Notes Administrators group has rights to run Restricted/Unrestricted agents in Server doc

  6. Run time security level is set to 3

  7. If I move the xls to c:\ the scheduled agent runs correctly

  8. Excel.Application is the correct name for the application

  9. This all ran fine on 5.0.12

It has to be a problem with Network File system access, but I am at a lost to what needs to be altered.

I would appreciate any assistance or suggestions.

Thanks

Kerry

Subject: Problem with Scheduled agent accessing Network file

Your domino service is probably running on the default “SYSTEM” account, and not using a named account.Shared drives are only available for a logged-on named user.

The SYSTEM account has complete access to all local resources, but not in the Windows network. Check if it’s possible to update security settings for your network share to allow access for the server/computer account and update your agent to use the full UNC path instead of the drive mapping. (note: I’m not sure if that’s going to work)

Another option is running the Domino Service as a named account, but at that point you lose the console.

cheers,

Bram

Subject: Problem with Scheduled agent accessing Network file

is “g” drive a mapped network drive by any chance?After certain amount of time the connection to the mapped network drive it lost.

You can try mapping a network drive on ur machine. After a while (dont know exactly in minutes), u will notice a red cross on the mapped drive. This means that the connection is lost, but when u click on the drive the connection is established again.

hope this helps!!

Subject: RE: Problem with Scheduled agent accessing Network file

if it’s in fact a problem of mapped drive, you could use the following code:—

Set scriptobj = CreateObject(“WScript.Shell”)

Set shellobj = scriptobj.Exec(“net use G: /DELETE”)

Set shellobj = scriptobj.Exec(“net use G: \HOSTNAME\MAPNAME”)


NB. “Run” method is probably better than “Exec”

Check what u need and exct syntax over there:

regards,

H.

Subject: More Info - Problem with Scheduled agent accessing Network file

Domino does not start as a service, it is in Startup.

The network drives are accessible, the server has not lost its connection.

We are running the same OS, Network logon etc as in the production envirnoment, only difference is version of Domino 6.5.1 vs 5.0.12. It seems to be an issue with Domino accessing Network drives, but I cannot fing the problem.

Help I am getting confused.

Subject: RE: More Info - Problem with Scheduled agent accessing Network file

Hi, I have exactly the same problem.

I think it linked to the migration from 5.011 to 6.51.

It worked like a charm before.

The agent is opening a text file on a network drive to import its contents into the database. No rocket science…

I suspect Domino 6.51 is NOT able to handle network drives/maps neither UNC . Why is that ?

Can someone address this issue ?

Does anyone else noticed this issue ?

Thanks

Christian