Hi, I managed to get the windows debug symbols to work and I get this exception: (d18.cc8): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax=0725ff5b ebx=029e76e8 ecx=00390000 edx=029e76e8 esi=03686278 edi=029e76e0 eip=774265c9 esp=0021ecbc ebp=0021ecf0 iopl=0 nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210206 ntdll!RtlpLowFragHeapFree+0x31: 774265c9 8b4604 mov eax,dword ptr [esi+4] ds:0023:0368627c=????????
And this is the stack trace (if it helps at all): # ChildEBP RetAddr Args to Child 00 0021ecf0 7742657a 0021edcc 029e76e8 01f685fe ntdll!RtlpLowFragHeapFree+0x31 (FPO: [Non-Fpo]) 01 0021ed04 76f49c46 00390000 00000000 029e76e0 ntdll!RtlFreeHeap+0x101 (FPO: [Non-Fpo]) 02 0021ed18 7718afbd 00390000 00000000 029e76e8 kernel32!HeapFree+0x14 (FPO: [Non-Fpo]) 03 0021ed2c 7718afd9 7725f6f8 029e76e8 0021ed54 ole32!CRetailMalloc_Free+0x1c (FPO: [Non-Fpo]) 04 0021ed3c 75be6efc 029e76e8 01f685fe 0021edcc ole32!CoTaskMemFree+0x13 (FPO: [Non-Fpo]) 05 0021ed54 75be6ecb 029e76e8 029e76e8 01f685fe RPCRT4!NdrPointerFree+0xb5 06 0021ed74 75c725c8 029e76e8 0021efc8 01f685fa RPCRT4!NdrPointerFree+0x91 07 0021ed9c 75c7248b 0021efc8 00000003 0021efa8 RPCRT4!NdrpFreeParams+0x150 08 0021edac 75c72429 2f79ac27 003cd940 003c91a0 RPCRT4!NdrStubCall2+0x9aa (FPO: [SEH]) 09 0021eea8 1e0ebe8e 027c4300 00000006 00000000 RPCRT4!NdrStubCall2+0x55c (FPO: [SEH]) WARNING: Stack unwind information not available. Following frames may be wrong. 0a 0021f1cc 75c7293b 003cd940 003bf940 003c91a0 python27!PyEval_EvalFrameEx+0x18fe 0b 0021f21c 7725a8c5 003cd940 003c91a0 003bf940 RPCRT4!CStdStubBuffer_Invoke+0xa0 (FPO: [SEH]) 0c 0021f264 7725aa59 003c91a0 003d6348 003cc248 ole32!SyncStubInvoke+0x3c (FPO: [Non-Fpo]) 0d 0021f2b0 7718624e 003c91a0 003d2b68 003cd940 ole32!StubInvoke+0xb9 (FPO: [Non-Fpo]) 0e 0021f38c 7718615f 003bf940 00000000 003cd940 ole32!CCtxComChnl::ContextInvoke+0xfa (FPO: [Non-Fpo]) 0f 0021f3a8 77186e75 003c91a0 00000001 003cd940 ole32!MTAInvoke+0x1a (FPO: [Non-Fpo]) 10 0021f3d4 7725a981 003c91a0 00000001 003cd940 ole32!STAInvoke+0x46 (FPO: [Non-Fpo]) 11 0021f408 7725a79b d0908070 003bf940 003cd940 ole32!AppInvoke+0xaa (FPO: [Non-Fpo]) 12 0021f4e4 7725ae2d 003c9148 003c0be0 00000400 ole32!ComInvokeWithLockAndIPID+0x32c (FPO: [Non-Fpo]) 13 0021f50c 77186c4d 003c9148 00000400 003a8ab8 ole32!ComInvoke+0xc5 (FPO: [Non-Fpo]) 14 0021f520 77186c0c 003c9148 0021f5e0 00000400 ole32!ThreadDispatch+0x23 (FPO: [Non-Fpo]) 15 0021f564 75adfd72 00080676 00000400 0000babe ole32!ThreadWndProc+0x167 (FPO: [Non-Fpo]) 16 0021f590 75adfe4a 77186b6f 00080676 00000400 USER32!InternalCallWinProc+0x23 17 0021f608 75ae018d 00000000 77186b6f 00080676 USER32!UserCallWinProcCheckWow+0x14b (FPO: [Non-Fpo]) 18 0021f66c 75ad8b7c 77186b6f 00000001 0021f68c USER32!DispatchMessageWorker+0x322 (FPO: [Non-Fpo]) 19 0021f67c 1d1adb3a 01d5cf80 0021f72c 0021f6bc USER32!DispatchMessageA+0xf (FPO: [Non-Fpo]) 1a 0021f68c 1d1ac8b6 1d1ac730 0021f6ac 00000004 _ctypes!DllCanUnloadNow+0x5a7a 1b 0021f6bc 1d1a8c48 75ad8b6d 0021f7b0 2fbd7447 _ctypes!DllCanUnloadNow+0x47f6 1c 0021f76c 1d1a942e 00001100 75ad8b6d 0021f7a0 _ctypes!DllCanUnloadNow+0xb88 1d 0021f80c 1d1a5388 75ad8b6d 02892950 00000000 _ctypes!DllCanUnloadNow+0x136e 1e 0021f864 1e07aa5c 00000000 02892950 00000000 _ctypes+0x5388 1f 00000000 00000000 00000000 00000000 00000000 python27!PyObject_Call+0x4c //Jan > -----Ursprüngliche Nachricht----- > Von: Jan Wedel > Gesendet: Donnerstag, 19. April 2012 12:45 > An: comtypes-users@lists.sourceforge.net > Betreff: [comtypes-users] Serious problem with RPC_E_SERVERFAULT (0x80010105) > > Hi, > > we have almost finished our COM server using comtypes. Once we tried to deploy > it on a Windows Server 2008, the client shows an RPC_E_SERVERFAULT > (0x80010105). We've tried three different Win XP machines which all work, Win > 2008 server and Win 7 shows the same issues. I can reproduce the issue with > two different c++ based clients and using comtypes client as well. > > The problem is, that there is no exception thrown within python code. > I've debugged my application with winpdb and neither my code nor the > surrounding comtypes python code throws an exception, as far as I can say. > However, when I attach the windows debugger to the python process and add a > breakpoint on uncatched exceptions, the debugger stops somewhere within > assembler code of PyObject_Call and shows an illegal access violation. I can't > say who is accessing which memory. For every crash, I see an entry in the > windows event console showing python.exe and ntdll.dll. > > Again, according to my previous question, probably I'm messing up some > pointers (but I'm wondering why it works under XP) and I'm still looking for > suggestion on how to debug COM. I want to see what's happening that causes the > exception... > > Any help would really be appreciated since we are pretty desperate right now. > > Thanks, > > //Jan > > ------------------------------------------------------------------------ ------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > comtypes-users mailing list > comtypes-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/comtypes-users ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ comtypes-users mailing list comtypes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/comtypes-users
