Drive mappings don't really happen unless the 'explorer' shell is loaded.
That's not loaded when programs are run as a service. You need to use UNC
paths.
On Monday, July 8, 2013 1:03:38 PM UTC-7, David S wrote:
>
> I'm running web2py 2.4.5 (yes I know I need to upgrade) on a network
> server. For ease of installation I've chosen to deploy my application as a
> service. It's been working great until now. Some of the data my app needs
> is located on a network folder, so I mapped the folder to the U:\ drive. I
> should be able to access it just like the C:\ drive. But that isn't
> happening.
>
> When I run web2py from the command line (see picture) I can do import os
> and do os.listdir('U:\\') and it works. I can launch web2py from the
> command line, then open the shell via appadmin and again it works fine.
> When I start the web2py service it simply doesn't find the U:\ drive. It
> works for C:\, D:\, and E:\ (all local, physical drives).
>
> I've checked the service's permissions and tried running it under
> usernames which definitely have access to the network folder. It seems the
> issue is running web2py as a service.
>
> Any ideas how to fix this, or what could be causing the issue?
>
> David
>
> Edit: I can access the U:\ drive remotely if web2py isn't being run as a
> service and is instead being run from the command line.
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
