L
lewisrm20
Hello. I have a VB.NET GUI (VS2005) that calls into a VB6 DLL to query MSAccess 2003 databases using DAO 3.6. Yes, I know this is not an ideal scenario, but that's the way the current application is set up. Component Checker shows MDAC 2.8 SP1 is installed. This application usually runs for a long time on our customer's Windows XP SP3 system with no issues. Occasionally (read: after 11 minutes or 11 hours or days), we experience a hang in the application, such that it needs to be ended with task manager and restarted. According to crash dumps and one lucky capture within the debugger, all threads are waiting on objects/critical sections within ntdll.dll. My specific thread gets stuck there and comes from MSJet40.dll. In the crash dumps, most threads are stuck in NTWaitForSingleObject, RtlEnterCriticalSection, etc. I've been troubleshooting this intermittent issue for months and am convinced this is a bug in MSJet40.dll. The version of the DLL is 4.0.9511 and I see there is a hotfix for 4.0.9514 on XP SP3 outlined in: http://support.microsoft.com/kb/954193. Although it doesn't directly address this issue, I would like to get this hotfix to see if it fixes the issue and speak with MS if it doesn't. I have crash dumps and procmon traces of these events. This sounds very similar to the dreaded "Jet Bug" that shows up on a Google, supposedly fixed for Windows 2003 Server SP1, but I see no mention of it on Windows XP SP3. For any knowledgeable MS personnel, I would be happy to send crash dumps and provide more information if needed. Would love to hear of anyone experiencing similar issues or with any insight as to why this could happen. Please help! Thank you!
Continue reading...
Continue reading...