Invalid argument

LNJ has asked for the wisdom of the Perl Monks concerning the following question:

my $destDIR = 'Y:/';
opendir( NTDIR, $destDIR )
|| die "Unable to access NT upload directory. $!";
closedir(NTDIR);
[download]

I'm using the above code to check the access to a network drive. When I run the above code using a windows scheduler I'm randomly getting an error message "Invalid argument at.."

FYI, most of the time the code works and I was not able to find any issue accessing the network drive

Advise if there are any issue or disadvantage in the above code...thanks in advance

Comment on Invalid argument Download Code

Replies are listed 'Best First'.
Re: Invalid argument by NetWallah (Canon) on Sep 08, 2011 at 04:50 UTC
Wise words from http://www.arcanadev.com/support/kb/I02000003.aspx: Programs run by the Scheduler generally will not have access to network drive letters unless those letters are mapped by the Scheduler (see next section). This is because drive letter mappings (e.g., those assigned using Windows Explorer) are defined at the user level, not the system level. These drive mappings are only valid while the user who made them is logged into the computer interactively. Even if you are running scheduled programs under an account for which drive mappings are defined, the programs will not have access to those mappings, because the Scheduler does not load them when it logs on to that user account. For Windows Network resources, if you are running the job under a user account, and that user account is also logged into the computer interactively, the drive letters for that user account may be available to scheduled programs. However, you should not rely on this being the case, because your scheduled programs will then fail if the user is not logged in interactively, or if another user is logged in. Instead you should always use UNC designations for network resources, or have the Scheduler map the drive letters. There is more well-written, useful info at that site.. "XML is like violence: if it doesn't solve your problem, use more."	[reply]
Re: Invalid argument by davido (Cardinal) on Sep 08, 2011 at 04:48 UTC
What comes after "`at..`"? If the network drive is inaccessible have you been able to verify that it fails as you want it to? (ie, with the message "`Unable to access NT upload directory. ...`") How are you invoking the script; I mean what command is the scheduler sending to invoke it? Dave	[reply] [d/l] [select]