HiTek Software Home
 
Title Accessing mapped drives: Task fails to run after users logoff.
Date Updated 03/28/2006
Versions affected Automize 4.0+ & JavaScheduler 4.0+ 
OS affected Windows 
Description User is using the NT service module.  Task runs correctly when the user is logged on.  When the user logs off, the task fails to run due to a file access issue.
Causes Task is trying to access a mapped drive after logout.  Normally mapped drives disconnect at logout and reconnect at logon.  Hence, your task runs correctly when logged on, but fails to run after you logoff.
Solution For the remote directory path, use shared drive naming system instead of normal mapped drive naming

example 1:
Remote System = win1
Remote mapped Folder for task = c:\test1
Mapped drive name for c:\test1= k:\
Share Name = test1

Use shared drive  =  \\win1\test1

example 2:
Remote System = win2
Remote mapped Folder = c:\test2
Mapped drive name for c:\test2 =  m:\
Share Name = test2

Remote directory for task = c:\test2\temp
Mapped drive name for c:\test2\temp = m:\temp

Use shared drive  =  \\win2\test2\temp

We have tested these examples to work using a copy task to a remote folder under the following conditions:
1) Automize NT service started under either local user account or administrator account
2) Task runs correctly when logged on, logged out, or on system startup.
Output Log The system cannot find the file or path specified
Debug Log FileNotFoundException