| Author |
Message |
Pooorboy
Guest
|
Posted:
Tue Jan 25, 2005 9:37 pm Post subject:
IMC Service Stops |
|
|
Running Exchange 5.5 Enterprise on windows 2000.
Every so often our internet mail connector stops unexpectantly. Error 7031
(no help there). I have narrowed it down to certain messages in the out
bound queue. Removing these messages allows normal operations. Adding these
messages back into the queue and restarting the service crashes the the
service. So, I know that these messages are causing the problem. What can I
do about it? I running service pack 4. I have openned the messages in
notepad to see if I can tell where they are coming from, but I can't seem to
figure out where they are coming from. It must be some malformed message,
but I would think there would be a patch for this. I have set the service to
restart if it stops but sometimes it will hang in a starting state. Which
then requires a reboot. Any ideas?
|
|
| Back to top |
|
 |
Guest
|
Posted:
Wed Jan 26, 2005 1:59 am Post subject:
Re: IMC Service Stops |
|
|
Pooorboy wrote:
| Quote: | Running Exchange 5.5 Enterprise on windows 2000.
Every so often our internet mail connector stops unexpectantly. Error
7031
(no help there). I have narrowed it down to certain messages in the
out
bound queue. Removing these messages allows normal operations. Adding
these
messages back into the queue and restarting the service crashes the
the
service. So, I know that these messages are causing the problem. What
can I
do about it? I running service pack 4. I have openned the messages in
notepad to see if I can tell where they are coming from, but I can't
seem to
figure out where they are coming from. It must be some malformed
message,
but I would think there would be a patch for this. I have set the
service to
restart if it stops but sometimes it will hang in a starting state.
Which
then requires a reboot. Any ideas?
|
I am seeing the same problems. I have seen a few other messages in the
groups about it. I have the PostSP4 rollup and NDR hot-fix installed.
The NDR hot-fix that people are talking about has been on my system
and working up until now for 3 months and not matter what
SupressNDROption I sent it has had a crash. I was sucessfully runing
SuppressNDROption=1 since installation of the hot-fix up until this
weekend.
The service will not recover if I set it to in Services. I do not
have to reboot but since Saturday I have had about 7-8 MSEXCIMC.EXE
crashes. I do agree it is something in the message but nobody has
definate answer at this point.
I just installed HotFix 884874 about 30 minutes ago. It mentions some
of the same basic errors that I have been seeing in event viewer. No
crashes at this point but it does include a newer build of
07-Dec-2004 23:04 5.5.2658.28 209,680 Imcmsg.dll
07-Dec-2004 21:20 5.5.2658.28 505,104 Msexcimc.exe
Someone reported that this fixed their issue. Hopefully that is the
case!
Gary |
|
| Back to top |
|
 |
Pooorboy
Guest
|
Posted:
Wed Jan 26, 2005 3:16 am Post subject:
Re: IMC Service Stops |
|
|
Pleae report back on your findings. Did you have to call microaoft for this
fix?
<ghensley@sys-tec.com> wrote in message
news:1106683184.680937.93130@f14g2000cwb.googlegroups.com...
| Quote: |
Pooorboy wrote:
Running Exchange 5.5 Enterprise on windows 2000.
Every so often our internet mail connector stops unexpectantly. Error
7031
(no help there). I have narrowed it down to certain messages in the
out
bound queue. Removing these messages allows normal operations. Adding
these
messages back into the queue and restarting the service crashes the
the
service. So, I know that these messages are causing the problem. What
can I
do about it? I running service pack 4. I have openned the messages in
notepad to see if I can tell where they are coming from, but I can't
seem to
figure out where they are coming from. It must be some malformed
message,
but I would think there would be a patch for this. I have set the
service to
restart if it stops but sometimes it will hang in a starting state.
Which
then requires a reboot. Any ideas?
I am seeing the same problems. I have seen a few other messages in the
groups about it. I have the PostSP4 rollup and NDR hot-fix installed.
The NDR hot-fix that people are talking about has been on my system
and working up until now for 3 months and not matter what
SupressNDROption I sent it has had a crash. I was sucessfully runing
SuppressNDROption=1 since installation of the hot-fix up until this
weekend.
The service will not recover if I set it to in Services. I do not
have to reboot but since Saturday I have had about 7-8 MSEXCIMC.EXE
crashes. I do agree it is something in the message but nobody has
definate answer at this point.
I just installed HotFix 884874 about 30 minutes ago. It mentions some
of the same basic errors that I have been seeing in event viewer. No
crashes at this point but it does include a newer build of
07-Dec-2004 23:04 5.5.2658.28 209,680 Imcmsg.dll
07-Dec-2004 21:20 5.5.2658.28 505,104 Msexcimc.exe
Someone reported that this fixed their issue. Hopefully that is the
case!
Gary
|
|
|
| Back to top |
|
 |
Guest
|
Posted:
Wed Jan 26, 2005 3:59 am Post subject:
Re: IMC Service Stops |
|
|
Yes you have to call them. It is free though since it is a hotfix and
not fully supported, regression tested.
So far so good, I will know by tomorrow AM I bet to see if that fixed
it. I will let you know though. |
|
| Back to top |
|
 |
Guest
|
Posted:
Wed Jan 26, 2005 7:03 pm Post subject:
Re: IMC Service Stops |
|
|
No crashes since I installed Hotfix #: 884874. At this point things
look promising. I was averaging a crash every 12 hours or so and none
for nearly 20 hours. |
|
| Back to top |
|
 |
Pooorboy
Guest
|
Posted:
Wed Jan 26, 2005 7:53 pm Post subject:
Re: IMC Service Stops |
|
|
Thats good news. Could you email me that patch? Or is it something you just
have to get from microsoft?
<ghensley@sys-tec.com> wrote in message
news:1106744589.700649.122450@c13g2000cwb.googlegroups.com...
| Quote: | No crashes since I installed Hotfix #: 884874. At this point things
look promising. I was averaging a crash every 12 hours or so and none
for nearly 20 hours.
|
|
|
| Back to top |
|
 |
|
|
|
|