none
Thread deadlock, using Coversant.SoapBox.dll, when trying to Login RRS feed

  • Question

  • I'm using Coversant.SoapBox.dll from Coversant, but have a problem using it on different PCs. One PC Logins with no problem and the other one experiences a deadlock on Login I suppose: no TimeoutException or SocketException is thrown. It just hangs and I don't know what's the reason of hanging. This must be Windows configuration problem I guess or even a Windows bug.

    The call stack is the following:

    0013bf70 7c90df4a 7c809590 00000002 0013bf9c ntdll!KiFastSystemCallRet (FPO: [0,0,0])

    0013bf74 7c809590 00000002 0013bf9c 00000001 ntdll!ZwWaitForMultipleObjects+0xc (FPO: [5,0,0])

    0013c010 7e4195f9 00000002 0013c038 00000000 kernel32!WaitForMultipleObjectsEx+0x12c (FPO: [Non-Fpo])

    0013c06c 7752ebd6 00000001 0013c0b4 000003e8 user32!RealMsgWaitForMultipleObjectsEx+0x13e (FPO: [5,13,4])

    0013c094 7752ecfd 0013c0b4 000003e8 0013c0c4 ole32!CCliModalLoop::BlockFn+0x80 (FPO: [3,0,4])

    0013c0bc 7760179e ffffffff 001b2eb0 0013c1bc ole32!ModalLoop+0x5b (FPO: [1,2,4])

    0013c0d8 776011a6 00000000 00000000 00000000 ole32!ThreadSendReceive+0xa0 (FPO: [1,1,4])

    0013c0f4 7760108a 0013c1bc 001b2eb0 0013c218 ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x13d (FPO: [1,1,4])

    0013c1d4 7752edaa 001b2eb0 0013c2e8 0013c2d8 ole32!CRpcChannelBuffer::SendReceive2+0xc8 (FPO: [3,50,4])

    0013c1f0 7752ed53 0013c2e8 0013c2d8 001b2eb0 ole32!CCliModalLoop::SendReceive+0x1e (FPO: [3,0,0])

    0013c25c 7752cdb2 001b2eb0 0013c2e8 0013c2d8 ole32!CAptRpcChnl::SendReceive+0x6f (FPO: [3,19,4])

    0013c2b0 77ef4db5 001b2eb0 0013c2e8 0013c2d8 ole32!CCtxComChnl::SendReceive+0x113 (FPO: [3,13,4])

    0013c2cc 77ef4ead 001d1f7c 0013c314 0600015b rpcrt4!NdrProxySendReceive+0x43 (FPO: [2,0,0])

    0013c6a8 77ef4e42 774e6228 774e94fc 0013c6e0 rpcrt4!NdrClientCall2+0x1fa (FPO: [Non-Fpo])

    0013c6c8 77e8a83b 00000014 00000004 0013c73c rpcrt4!ObjectStublessClient+0x8b (FPO: [2,0,4])

    0013c6d8 7751eaed 001d1f7c 00000000 0013cb80 rpcrt4!ObjectStubless+0xf

    0013c73c 7751ebba 0013cb80 0013d0cc 002d0039 ole32!CRpcResolver::CreateInstance+0x13d (FPO: [2,16,4])

    0013c988 775110b3 77607114 00000000 00000000 ole32!CClientContextActivator::CreateInstance+0xfa (FPO: [4,4,0])

    0013c9c8 77510ef8 0013cb80 00000000 0013d0cc ole32!ActivationPropertiesIn::DelegateCreateInstance+0xf7 (FPO: [3,7,4])

    0013d178 77500575 26f01bfc 00000000 00000017 ole32!ICoCreateInstanceEx+0x3c9 (FPO: [8,50,0])

    Here http://support.microsoft.com/kb/319579 there is a description of a bug with a similar call stack ending, but it was fixed in Windows 2000. Maybe this is a new Windows bug from the same area.


    Who knows what should be repaired or reinstalled or uninstalled to make my second PC also to Login, because this is definetly not a problem of Coversant?


    Thank you,

    Sergey L.



    PS I've posted my issue to Coversant, but had no response yet. Unfortunately I'm unable to create a new topic on their forum, because of some error.

    Sunday, July 11, 2010 3:35 PM

Answers

  • Hi,

       Thanks for your post. I am not familiar with the Conversant products. Please take a look at the following reference, it could help you with debugging the application hanging.

        .NET Hang Debugging Walkthrough


    Please mark the right answer at right time.
    Thanks,
    Sam
    • Marked as answer by SamAgain Tuesday, July 20, 2010 12:40 AM
    Tuesday, July 20, 2010 12:40 AM