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

LVL 19
BarthaxAsked:
Who is Participating?
 
DarthModConnect With a Mentor Commented:
PAQd, 500 points refunded.

DarthMod
CS Moderator
0
 
VahikCommented:
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...
0
 
BarthaxAuthor Commented:
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=aea5f692cf2c8b8c636e3a68eb0f6d37\nX-Mailer: 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--aea5f692cf2c8b8c636e3a68eb0f6d37\nContent-Transfer-Encoding: base64\nContent-Type: text/plain\n\ncmVjb2duaXplcyB0aGUgZm9sbG93aW5nIGNhdGVnb3JpZXMgcmVzaCBoYW0gaXMgYW4gdW5jdXJl\nZCBoaW5kIGxlZyBvZiBwb3Jr\n\n--aea5f692cf2c8b8c636e3a68eb0f6d37--\n.\n" <>

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
BarthaxAuthor Commented:
0
 
VahikCommented:
well kido nice to see u solved this problemmm...
take care and good luck..
0
 
BarthaxAuthor Commented:
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
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.