Is this the same problem tye was talking about (Re: error mapping drive ('\\'))? It looked like it got resolved. What is going wrong now?
It probably isn't the permissions of the perl script that are the issue. I'm no windows expert (or even user if I can help it), but most likely IIS intentionally runs with limited permissions to prevent the kinds of things you're trying to do (i.e. exposing your network shares to the entire world).
| [reply] |
Is this the same problem tye was talking about
There were two issues raised in that earlier thread. I noticed the permission problem. tye noticed the bad path. At the time, the OP was doing offline testing, so he fixed that bad path and ignored the permission problem. Until now.
It probably isn't the permissions of the perl script that are the issue.
Correct. Services usually run as LocalSystem which doesn't have network permissions. The service and/or the script needs to run as a user with network permissions. I don't know which user that would be, or how to grant such permissions.
| [reply] [d/l] |
Yes i resolved the drive mapping problem, but I was doing that locally. I was running the perl script from the command line and mapping the a drive on my PC. So, of course no permissions issues. If I try to map a drive remotely it fails because of permissions.
| [reply] |
I figured it out.
By default the form runs as the IIS IWAM local account(which of course can't have permissions remotely). If you change this to a network account in IIS and then give the remote folder the same network account permissions, BAM... you can write remotely. Thanks for helping me brainstorm boys
| [reply] |