> ...an orphaned Critical Section, or Critsec, that the thread using > the critsec exited without releasing the critsec...
Chances are that that the unreleased CS is a symptom, not the cause of your problem. Armed with this possibility, Ipswitch could do a quick code review and check to make sure that all CSs are released in "normal" operation. But any application making use of objects like CSs can create orphans if it crashes before functions complete and clean up after themselves. > Their suggestions: 1: install the Appverifier tool, to winXP and > test the POP3D32.EXE service for a lock test. This tool only runs on > XP. The test's purpose is to test the critsecs. Yeah, yeah. Sounds like a good way to make you move to XP. > 2: upgrade or downgrade the following: > d:\imail\ODBCUSER.dll (aug 2002) > d:\imail\mailbox.dll (aug 2002) > d:\imail\Imailsec.dll (aug 2002) There is a slightly later ODBCUSER.DLL, I believe. Contact Ipswitch for it. > Any ideas guys? Review your observed symptoms for us: - Are you still seeing multiple POP3D services, as you once mentioned? - Any consistency to the last successful session before a hang? - What happens when you Telnet on 110 during these situations and attempt a manual session? - Is POP3 becoming unbound from the IP altogether? - What DB are you using, and have you tried using another DB for testing? - What MDAC version? - What ODBC driver version? -Sandy To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
