We have an application which uses dbodbc12.dll --- and it stays in processes after the entire exe has finished. The exe only stays in processes when dbodbc12.dll is used.
I have Process Explorer attached to it - but to me, it's just garbage information and I don't really know what it is doing.
Two threads I see are:
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x536 wow64cpu.dll!TurboDispatchJumpAddressEnd+0x17b wow64.dll!Wow64SystemServiceEx+0x26a wow64.dll!Wow64LdrpInitialize+0x435 ntdll.dll!wcscspn+0x7f ntdll.dll!LdrInitializeThunk+0xe ntdll.dll!NtFsControlFile+0xc dbodbc12.dll!DllRegisterServer+0x25678
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x536 wow64cpu.dll!TurboDispatchJumpAddressEnd+0x3a5 wow64.dll!Wow64SystemServiceEx+0x26a wow64.dll!Wow64LdrpInitialize+0x435 ntdll.dll!wcscspn+0x7f ntdll.dll!LdrInitializeThunk+0xe ntdll.dll!NtWaitForSingleObject+0xc ntdll.dll!wcsspn+0x17a ntdll.dll!wcsspn+0x196 ntdll.dll!RtlFreeUnicodeString+0xa9 ntdll.dll!RtlExitUserThread+0x30 combase.dll!CleanupTlsOleState+0x7bc ntdll.dll!RtlInitializeExceptionChain+0x85 ntdll.dll!RtlInitializeExceptionChain+0x58
My guess is that it is in GPF mode, but it's a background process and doesn't run interactively.
I wouldn't know where to begin to troubleshoot but going to Sybase/SAP support for something at this will most likely be painful.
We are an OEM for Sybase SQL Anywhere --- but our REP has gone away - doesn't answer anything since SAP took over. It's been pretty painful since SAP took over Sybase --- it seems like no one really cares about the product anymore. But, that's another story - we just need this fixed and will pay for it but I want to talk to a high level developer to work directly on this issue and not go through Level 1 support.
This problem is related to a known "Loader Lock" problem with DllMain, which can be caused by improperly written wrapper DLLs calling functions during DLL load/unload times. See the SQL Anywhere documentation and a related Microsoft document for the underlying details.
answered 17 Mar '14, 15:30