Tim,
Thanks for the help - I have appreciated the input!
After (much) further troubleshooting, I have located the bug - completely
my fault (why aren't you more surprised? ;-) The service fails on startup
because my own derived class implemented a method that is only supported on
platforms later
On 23/01/2013 19:55, Jean Rousseau wrote:
Tim,
OK, so I restored the server VM from backup, ran the existing service
(which worked fine) and then copied across and installed my new service .py
files and installed. ALL of this still working on Python 3.2.3 and
pywin-217. I ran pythonservice with
Tim,
OK, so I restored the server VM from backup, ran the existing service
(which worked fine) and then copied across and installed my new service .py
files and installed. ALL of this still working on Python 3.2.3 and
pywin-217. I ran pythonservice with the debug switch on, and now I think
we're m
Tim,
Thanks for the feedback. Thinking back, I believe that I ran the service
without issue after installing 3.3.0 and pywin32-218, and once satisfied
that everything was working on the new release, went and uninstalled Python
3.2.3 and pywin-217. I think it was THEN that the service wouldn't
func
On 23/01/2013 15:45, Jean Rousseau wrote:
> Here's the background - platform is Win 2003 Server x86:
> 1. My test machine was running Python 3.2.3 / pywin32 build 217 and all
> was well with the service classes that I wrote and tested.
> 2. I then installed Python 3.3.0 and pywin32 build 218.
> 3.
Hi All,
I would appreciate some help with troubleshooting an error I now receive
with a pythonservice.exe / pywin32-related services.
Here's the background - platform is Win 2003 Server x86:
1. My test machine was running Python 3.2.3 / pywin32 build 217 and all was
well with the service classes
