in reply to sysopen function call

Let's break it down to basics for now. Why would a simple sysopen fail on a directory known to exist (i.e. successful use of open confirms the directory exists)? I use a filename that exists and one that doesn't and both fail the same way. I checked the IUSR_XXXX permissions on the directory and also the current system user and both have suffice permissions. Is there another approach to determine why the sysopen is failing? Thankd again.

Replies are listed 'Best First'.
Re^2: sysopen function call
by Corion (Patriarch) on Sep 08, 2010 at 15:04 UTC

    I would test all the directories above the directory in question, and I would also inspect $^E, as you seem to be on Windows, and potentially the event log, to see whether there are other access restrictions. Also, I would look at the ACLs for whatever users are trying to access the directories.