Are you running the job as a user and is the agent set to login as a user?
Remember, drive mappings are user dependent. So what you see as "S:\" drive may be someone elses "K:\" drive. Also on Windows systems drive mappings are done at login -- so you typically have to run the login script.
I always, ALWAYS recommend that you use UNC paths and never use a drive letter. Drive letters can change, and they are a pain in the rear end to diagnose. Is there a reason you don't want to use a UNC path?
I am running as a user and the agent is set to login as that user.
I want do use drive mappings as my application does not handle UNC paths. It would be simpler if I could access the drive mapping.
In my company the network drive s: is always allocated to all users. It is mapped in my current session. This would not be an issue unless the network was down.
1 of 1 people found this helpful
Hey Steve -
Fair enough, if the application requires it then not much you can do.
As I said, drive mappings are usually done via a login script. You need to make sure that the agent is running this. I've attached a screenshot of the relevant configuration checkboxes (for a v6.4.01 agent).
You could also do your drive mappings in a batch file you are calling to run the program as another option (though I generally don't like complicating jobs unless there is no other choice).
A third option is to use thre %%PRECMD variable in your Set tab (screenshot below).
Since you said that the S: drive is mapped to all users I'd recommend going with running the login script.
I'm almost there. I can't figure out how control-m knows where the login script is?
The login script is set by your network admin. Under Windows, it is picked up automatically.
Somehow I knew that's what you were going to say. I was hoping that I could point control-M at my own login script.
Thanks for all of your help.
Glad I could be of help! Drop a line anytime.