Bill Janssen wrote: > I'm trying to run a Python service on Windows Server 2008. It does > start up, but then faults out, leaving this message in the event viewer: > > Log Name: Application > Source: Application Error > Date: 10/15/2010 2:59:41 PM > Event ID: 1000 > Task Category: (100) > Level: Error > Keywords: Classic > User: N/A > Computer: *** > Description: > Faulting application PythonService.exe, version 2.6.214.0, time stamp > 0x4a5012a6, faulting module ntdll.dll, version 6.0.6002.18005, time > stamp 0x49e03821, exception code 0xc0000005, fault offset 0x00067580, > process id 0x10cc, application start time 0x01cb6cb4448dcbf4. > > I'm using Python 2.6.6, with PyWin32 2.6.214. > > Any ideas as to what's happening? Works fine on WS 2003, so I'm guessing > it's related to the platform :-).
There's not enough information here to tell anything. That address within ntdll.dll is the "unhandled exception" handler C0000005 is the catchall error code for addressing faults caught by the processor, like invalid addresses or access violations. So, there's probably some kind of a wild pointer issue, but we can't tell any more. You'll need to run it with a debugger, or add a printf trace log. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
