IMAP Server in Enterprise 3.52 Crashes

Discussion forum for Enterprise Edition.
taylort
Posts: 80
Joined: Wed Jan 24, 2007 7:43 pm
Location: Louisville, KY

IMAP Server in Enterprise 3.52 Crashes

Post by taylort »

We performed an upgrade from Enterprise 3.51 -> 3.52 about 4 hours ago. Since then the IMAP server has crashed 4 separate times. Is anyone else experiencing issues?

nccng2001
Posts: 16
Joined: Tue Aug 21, 2007 12:57 pm

Post by nccng2001 »

Yes, we are also experiencing this problem.

Here is the error message from event log and this came out several times a day:

Code: Select all

Event Type:	Information
Event Source:	Application Error
Event Category:	(100)
Event ID:	1004
Date:		01/08/2008
Time:		11:51:41 AM
User:		N/A
Computer:	SUPERMICRO-250
Description:
Reporting queued error: faulting application MEIMAPS.EXE, version 1.0.0.55, faulting 
module ntdll.dll, version 5.2.3790.3959, fault address 0x000210c8.

For more information, 
see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Any Help

Markuz
Posts: 21
Joined: Fri Dec 21, 2007 7:59 pm

Hotfix available

Post by Markuz »

Gents,

We have to same issue. I found a hotfix on http://www.mailenable.com/hotfix/

We have installed it, so let's take a look if it's okay now.

Greets
Mark

Markuz
Posts: 21
Joined: Fri Dec 21, 2007 7:59 pm

Post by Markuz »

The error is still there, only now as 'information'-type within the eventviewer. The services doesn't crash anymore it seems like.

BEFORE hotfix
=========
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 1-8-2008
Time: 12:28:33
User: N/A
Computer: x
Description:
Faulting application MEIMAPS.EXE, version 1.0.0.55, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0000eef0.


AFTER hotfix
========
Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 1-8-2008
Time: 12:42:23
User: N/A
Computer: x
Description:
Reporting queued error: faulting application MEIMAPS.EXE, version 1.0.0.55, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0000eef0.


So no we have to wait for a new version that gives a structural solution right?

Mark

scngan
Posts: 446
Joined: Fri Dec 30, 2005 1:27 pm

Post by scngan »

Markuz wrote:The error is still there, only now as 'information'-type within the eventviewer. The services doesn't crash anymore it seems like.

BEFORE hotfix
=========
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 1-8-2008
Time: 12:28:33
User: N/A
Computer: x
Description:
Faulting application MEIMAPS.EXE, version 1.0.0.55, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0000eef0.


AFTER hotfix
========
Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 1-8-2008
Time: 12:42:23
User: N/A
Computer: x
Description:
Reporting queued error: faulting application MEIMAPS.EXE, version 1.0.0.55, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0000eef0.


So no we have to wait for a new version that gives a structural solution right?

Mark
the hot fix should fixed the problem. it fixed my problem.

taylort
Posts: 80
Joined: Wed Jan 24, 2007 7:43 pm
Location: Louisville, KY

Post by taylort »

The hotfix prevented the service from crashing every 20 minutes but it's still crashing.

Code: Select all

Event Type:	Error
Event Source:	Application Error
Event Category:	(100)
Event ID:	1000
Date:		8/1/2008
Time:		1:42:27 PM
User:		N/A
Computer:	NOZONE-B964306B
Description:
Faulting application , version 0.0.0.0, faulting module msxml3.dll, version 8.90.1101.0, fault address 0x0006637f.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 20 30 2e   ure   0.
0018: 30 2e 30 2e 30 20 69 6e   0.0.0 in
0020: 20 6d 73 78 6d 6c 33 2e    msxml3.
0028: 64 6c 6c 20 38 2e 39 30   dll 8.90
0030: 2e 31 31 30 31 2e 30 20   .1101.0 
0038: 61 74 20 6f 66 66 73 65   at offse
0040: 74 20 30 30 30 36 36 33   t 000663
0048: 37 66                     7f      

scngan
Posts: 446
Joined: Fri Dec 30, 2005 1:27 pm

Post by scngan »

wat about the IMAP log itself?Can you get and post something out ?

rfwilliams777
Posts: 1370
Joined: Thu Nov 11, 2004 5:26 pm
Location: Kingsville, Texas

Post by rfwilliams777 »

I also set up in Services (Under Administrative Tools on the server) set it for all three retries to restart on the Recoveries tab. Since then, no crash.
Robert Williams, Owner
www.WilliamsWebSolutions.com
#1 in MailEnable Business-Class Email Hosting - Switch to Williams Web Solutions and we will migrate your accounts to us for FREE!
We can be hired to help you with your Mail Enable server, too!

Markuz
Posts: 21
Joined: Fri Dec 21, 2007 7:59 pm

Post by Markuz »

scngan wrote:wat about the IMAP log itself?Can you get and post something out ?
I can't find error details in de IMAP-log.
After installing the hotfix and rebooting my server, the service didn't crash anymore. Only one entry of type "information" has been written to the eventlog:

Reporting queued error: faulting application MEIMAPS.EXE, version 1.0.0.55, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0001bd02.

Mark

scngan
Posts: 446
Joined: Fri Dec 30, 2005 1:27 pm

Post by scngan »

Markuz wrote:
scngan wrote:wat about the IMAP log itself?Can you get and post something out ?
I can't find error details in de IMAP-log.
After installing the hotfix and rebooting my server, the service didn't crash anymore. Only one entry of type "information" has been written to the eventlog:

Reporting queued error: faulting application MEIMAPS.EXE, version 1.0.0.55, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0001bd02.

Mark
then that means it has fixed the issue :)

rheel
Posts: 28
Joined: Mon Jun 09, 2008 8:56 pm

still crashing

Post by rheel »

48 hours ago we upgraded to enterprise v3.52 restarted and imap service was crashing so installed the patch ME-10042: Wednesday, August 06, 2008. Since then we have continued to have imap problems, possibly even more problems than before the upgrade.
Outlook users (2003 and 2007 versions) are having issues, their mail is not coming down into their inbox but is available on webmail.
Thunderbird users are also having issues with emails coming in very late, there are no queues holding up the mail that i can see.


Error in the event viewer form the last crash was.

Faulting application MEIMAPS.EXE, version 1.0.0.55, faulting module msxml3.dll, version 8.90.1101.0, fault address 0x0000c254.


Any ideas if there is another patch coming out or known issues currently ?

weshsu
Posts: 7
Joined: Mon Apr 21, 2008 6:56 pm

Re: still crashing

Post by weshsu »

rheel wrote:48 hours ago we upgraded to enterprise v3.52 restarted and imap service was crashing so installed the patch ME-10042: Wednesday, August 06, 2008. Since then we have continued to have imap problems, possibly even more problems than before the upgrade.
Outlook users (2003 and 2007 versions) are having issues, their mail is not coming down into their inbox but is available on webmail.
Thunderbird users are also having issues with emails coming in very late, there are no queues holding up the mail that i can see.
I'm having similar issues. On Aug 2, I applied ME-10042 (Aug 1) which reduced the number of IMAP service crashes. I still had a lot of issues connecting through SSL. The IMAP service wouldn't crash in this case, but I did have to restart it every time my clients couldn't connect. Yesterday I applied ME-10042 (Aug 6). The IMAP service would crash even more, and Mail.app (OS X) has a real hard time freshing (usually it won't, even when I tell it to refresh), but if I close the app and restart, it'll get the latest. So I reverted back to the Aug 1 version. I don't think that took because Mail.app still refuses to refresh. Throughout all this, my iPhone has never had a problem. Of course, webmail doesn't have any issues either.

I'm _this_ close to switch to a different mail server software. Since I upgraded to 3.5, the IMAP service has been crashing multiple times per day on a relatively low load server. Email is pretty critical for many people these days, and my patience is running thin. If these issues are not addressed in short order, I'll have to switch even though I just paid for the upgrade. But that upgrade fee is nothing compared to the amount of time I waste dealing with these issues.

This makes my Yahoo graylisting issue seem insignificant now. :)

taylort
Posts: 80
Joined: Wed Jan 24, 2007 7:43 pm
Location: Louisville, KY

Re: still crashing

Post by taylort »

weshsu wrote:
rheel wrote:48 hours ago we upgraded to enterprise v3.52 restarted and imap service was crashing so installed the patch ME-10042: Wednesday, August 06, 2008. Since then we have continued to have imap problems, possibly even more problems than before the upgrade.
Outlook users (2003 and 2007 versions) are having issues, their mail is not coming down into their inbox but is available on webmail.
Thunderbird users are also having issues with emails coming in very late, there are no queues holding up the mail that i can see.
I'm having similar issues. On Aug 2, I applied ME-10042 (Aug 1) which reduced the number of IMAP service crashes. I still had a lot of issues connecting through SSL. The IMAP service wouldn't crash in this case, but I did have to restart it every time my clients couldn't connect. Yesterday I applied ME-10042 (Aug 6). The IMAP service would crash even more, and Mail.app (OS X) has a real hard time freshing (usually it won't, even when I tell it to refresh), but if I close the app and restart, it'll get the latest. So I reverted back to the Aug 1 version. I don't think that took because Mail.app still refuses to refresh. Throughout all this, my iPhone has never had a problem. Of course, webmail doesn't have any issues either.

I'm _this_ close to switch to a different mail server software. Since I upgraded to 3.5, the IMAP service has been crashing multiple times per day on a relatively low load server. Email is pretty critical for many people these days, and my patience is running thin. If these issues are not addressed in short order, I'll have to switch even though I just paid for the upgrade. But that upgrade fee is nothing compared to the amount of time I waste dealing with these issues.

This makes my Yahoo graylisting issue seem insignificant now. :)
I could not agree more. ME's IMAP implementation is nothing but false hope and endless headaches. The good thing is if we switched fairly soon, I can still claim a refund with our credit card provider to get our upgrade fee refunded.

How does the competition's IMAP services stack-up to MailEnable?

weshsu
Posts: 7
Joined: Mon Apr 21, 2008 6:56 pm

Re: still crashing

Post by weshsu »

taylort wrote:How does the competition's IMAP services stack-up to MailEnable?
It's not appropriate to discuss the competition in these public forums, but I would be interested to hear from people with recommendations as my search has yielded very few options. I'm sure I'm just not looking in the right places. Please send me a PM me to discuss.

rheel
Posts: 28
Joined: Mon Jun 09, 2008 8:56 pm

no reply

Post by rheel »

So far no reply from Mailenable.
Getting a touch frustrated, have lodged support request 24 hours ago and no word.....
Mean while duplicates coming through, imap issues a plenty and lots of un-happy customers.
Does anybody else have any idea what is going on to resolve this major defect in 3.52 ?
Should i just roll back to 3.14 ? Anyone tried this ?

Post Reply