You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as described in more detail in the forum I can no longer start the shotgun event handler service on windows 10.
I thought it might be because I was still using Python2 so I uninstalled it and reinstalled using Python 3 via these steps:
pulled the latest shotgunEvents framework from github
installed Python 3.7.7
installed win32 via " D:\Python37_7\python.exe -m pip install win32"
installed service in an elevated powershell via: D:\Python37_7\python.exe D:\SG_Event_Daemon\src\shotgunEventDaemon.py install
tried to start the service via the "Services" window but got this error in the event viewer:
"The Shotgun Event Handler service terminated with the following service-specific error:
Incorrect function."
When trying to start the service from the powerline I don't get an error but it won't start anyway D:\Python37_7\python.exe D:\SG_Event_Daemon\src\shotgunEventDaemon.py start
I tried the same thing with (Active)Python 2.7 (the very same one that had worked for a couple of years on htis machine) but am getting the same error.
EDIT: Running the service in the foreground in a powershell work just fine.
Any ideas how to fix or at least debug this?
Cheers,
frank
The text was updated successfully, but these errors were encountered:
Hi,
as described in more detail in the forum I can no longer start the shotgun event handler service on windows 10.
I thought it might be because I was still using Python2 so I uninstalled it and reinstalled using Python 3 via these steps:
"The Shotgun Event Handler service terminated with the following service-specific error:
Incorrect function."
When trying to start the service from the powerline I don't get an error but it won't start anyway
D:\Python37_7\python.exe D:\SG_Event_Daemon\src\shotgunEventDaemon.py start
I tried the same thing with (Active)Python 2.7 (the very same one that had worked for a couple of years on htis machine) but am getting the same error.
EDIT: Running the service in the foreground in a powershell work just fine.
Any ideas how to fix or at least debug this?
Cheers,
frank
The text was updated successfully, but these errors were encountered: