E: is just a local harddrive. The full python install and files under
the E: drive is accessible for both the local SYSTEM user, my user and
administrator.
It is configured to run as the Local System Account.
I am successfully able to install the service initially via admin
command prompt, a
On 2024-01-11 5:46 p.m., Jacob Nolan via python-win32 wrote:
I performed a custom install for all users on my E: drive
(E:/installs/python3). Added it to the path. It is not under my
specific user account. My understanding is this is a global install.
What exactly is E:? If anything other th
I performed a custom install for all users on my E: drive
(E:/installs/python3). Added it to the path. It is not under my specific
user account. My understanding is this is a global install.
I then run it under administrator privileged cmd and successfully
install the service.
Looking at sec
The ""
part sounds like it is failing to find Python itself. Where is Python
installed? Is it possible the user running the service can't access that
location? I believe Python being installed in the default location could
cause this if the server is running as any other other than the user
wh
