Barthax
asked on
MS POP3 Connector's Fatal Exception
Hi,
We have a customer's server (Win 2000 SBS, SP 4) which has been
experiencing a fatal exception in the POP3 Connector. We have succesfully
removed and re-install by following
http://support.microsoft.com/default.aspx/kb/319314/ - this had cured the
installation for about 4 hours only though and the Fatal Exceptions are
back again. Please find below a portion of the VMIMB.TXT pertinent to the
present issue. If I read correctly, there are three exceptions in the
file, but the exception-reporting process itself has failed on the first
two times.
Any pointers welcome.
========================== ========== ========== ========
Product: Microsoft Connector for POP3 Mailboxes 5.00.2195.1
Fault Date: 11/15/2006 Time: 11:23:27
========================== ========== ========== ========
Exception Code: C0000005 ACCESS_VIOLATION
========================== ========== ========== ========
Product: Microsoft Connector for POP3 Mailboxes 5.00.2195.1
========================== ========== ========== ========
Product: Microsoft Connector for POP3 Mailboxes 5.00.2195.1
Fault Date: 11/15/2006 Time: 15:51:23
========================== ========== ========== ========
Exception Code: C0000005 ACCESS_VIOLATION
Fault Address: 04041B7C 01:00040B7C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
Registers:
EAX:0111F870
EBX:00000000
ECX:0172EC20
EDX:00000000
ESI:0172ED1C
EDI:00000001
CS:EIP:001B:04041B7C
SS:ESP:0023:0172E0C0 EBP:0172E1EC
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010206
Call stack:
Address Frame
04041B7C 0172E1EC 0001:00040B7C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
04044F2C 0172E214 0001:00043F2C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
0404499D 0172E27C 0001:0004399D C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
0403E81C 0172E2A4 0001:0003D81C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
0403E252 0172E2F4 0001:0003D252 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
040378DD 0172E354 0001:000368DD C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
010BCE55 0172ECE4 0001:0000BE55 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimbcom.dll
010C962B 0172FE10 0001:0001862B C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimbcom.dll
0040DC16 0172FE74 0001:0000CC16 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
0040DE17 0172FF4C 0001:0000CE17 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
0040DA4F 0172FF6C 0001:0000CA4F C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
0040D1FF 00100000 0001:0000C1FF C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
We have a customer's server (Win 2000 SBS, SP 4) which has been
experiencing a fatal exception in the POP3 Connector. We have succesfully
removed and re-install by following
http://support.microsoft.com/default.aspx/kb/319314/ - this had cured the
installation for about 4 hours only though and the Fatal Exceptions are
back again. Please find below a portion of the VMIMB.TXT pertinent to the
present issue. If I read correctly, there are three exceptions in the
file, but the exception-reporting process itself has failed on the first
two times.
Any pointers welcome.
==========================
Product: Microsoft Connector for POP3 Mailboxes 5.00.2195.1
Fault Date: 11/15/2006 Time: 11:23:27
==========================
Exception Code: C0000005 ACCESS_VIOLATION
==========================
Product: Microsoft Connector for POP3 Mailboxes 5.00.2195.1
==========================
Product: Microsoft Connector for POP3 Mailboxes 5.00.2195.1
Fault Date: 11/15/2006 Time: 15:51:23
==========================
Exception Code: C0000005 ACCESS_VIOLATION
Fault Address: 04041B7C 01:00040B7C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
Registers:
EAX:0111F870
EBX:00000000
ECX:0172EC20
EDX:00000000
ESI:0172ED1C
EDI:00000001
CS:EIP:001B:04041B7C
SS:ESP:0023:0172E0C0 EBP:0172E1EC
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010206
Call stack:
Address Frame
04041B7C 0172E1EC 0001:00040B7C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
04044F2C 0172E214 0001:00043F2C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
0404499D 0172E27C 0001:0004399D C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
0403E81C 0172E2A4 0001:0003D81C C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
0403E252 0172E2F4 0001:0003D252 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
040378DD 0172E354 0001:000368DD C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\EDBW32.dll
010BCE55 0172ECE4 0001:0000BE55 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimbcom.dll
010C962B 0172FE10 0001:0001862B C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimbcom.dll
0040DC16 0172FE74 0001:0000CC16 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
0040DE17 0172FF4C 0001:0000CE17 C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
0040DA4F 0172FF6C 0001:0000CA4F C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
0040D1FF 00100000 0001:0000C1FF C:\Program Files\Microsoft BackOffice
\Connectivity\POP3 Connector\vmimb.exe
download a thirdparty POP3 connector and see if that would solve ur problemmm....like everything else that MS provides for free...well i wont finish this sentence....MS POP3 connector is not worth a PENNY...
ASKER
Hehe, thanks Vahik. You read my mind on the MS providing for free bit. :)
I've figured out this one for myself in the end: there existed an e-mail which was malformed having the following line (I've replaced the comma-seperated e-mail addresses with <email addresses removed>).
From: "pale\r\nContent-Type: multipart/alternative; \n boundary=aea5f692cf2c8b8c6 36e3a68eb0 f6d37\nX-M ailer: Gnus v5.7/Emacs 20.7\nSubject: recognize three types\nto: <email addresses removed>,\n <email addresses removed>\n <email addresses removed>\n\nThis is a multi-part message in MIME format.\n\n--aea5f692cf2c8 b8c636e3a6 8eb0f6d37\ nContent-T ransfer-En coding: base64\nContent-Type: text/plain\n\ncmVjb2duaXpl cyB0aGUgZm 9sbG93aW5n IGNhdGVnb3 JpZXMgcmVz aCBoYW0gaX MgYW4gdW5j dXJl\nZCBo aW5kIGxlZy BvZiBwb3Jr \n\n--aea5 f692cf2c8b 8c636e3a68 eb0f6d37-- \n.\n" <>
I've figured out this one for myself in the end: there existed an e-mail which was malformed having the following line (I've replaced the comma-seperated e-mail addresses with <email addresses removed>).
From: "pale\r\nContent-Type: multipart/alternative; \n boundary=aea5f692cf2c8b8c6
ASKER
well kido nice to see u solved this problemmm...
take care and good luck..
take care and good luck..
ASKER
Thanks Vahik. I've been at this one for a couple of days. Thinking about this Q here it seems very different.
Take care yourself, mate & thanks for contributing, regardless. :D
Take care yourself, mate & thanks for contributing, regardless. :D
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.