You mean you cant just call them and say "its broken"?
What kind of service is that for $250?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Daniel Chenault
Sent: Friday, September 07, 2001 10:51 AM
To: Exchange Discussions
Subject: Re: inbound message crashed IMC and Information Store
And if you do call PSS the first thing they will ask for is the message
itself. Without the message NO troubleshooting is possible, only
conjecture.
----- Original Message -----
From: "Durkee, Peter" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Friday, September 07, 2001 12:39 PM
Subject: RE: inbound message crashed IMC and Information Store
> I had the same thing happen last week, and as in your case, rebooting
fixed it and it's been fine ever since. I haven't called PSS yet as I'm
of the opinion that it takes two incidents to make a trend, but if you
do I'd be curious to hear what they say.
>
> -Peter
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 07, 2001 9:41
> To: Exchange Discussions
> Subject: RE: inbound message crashed IMC and Information Store
>
>
> Thanks everyone for your help. My question really is: can I prevent
> this
in
> the future? Rebooting the box took care of the problem, so I don't
> see
any
> need to call PSS. But I don't like the idea that a bad message can
> take
the
> IMS down. Any suggestions?
>
> -----Original Message-----
> From: Hunter, Lori [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 07, 2001 8:18 AM
> To: Exchange Discussions
> Subject: RE: inbound message crashed IMC and Information Store
>
>
> I have SP4 and this happens here occasionally. The event log gives
> you
the
> exact file name of the offending message. Search for it, delete it or
move
> it, start the IMS, you're back in business. You can open the message
> in notepad if you really want to make sure it gets delivered. Or you
> can blindly whack it away if you've just gotten off a boat, had a few
> beers,
and
> really just want to go home.
>
> Guess which method I use.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 06, 2001 6:50 PM
> To: Exchange Discussions
> Subject: inbound message crashed IMC and Information Store
>
>
> Exchange 5.5 SP4, NT 4 SP6a
>
> Today the IMS on one of our Exchange servers puked. It seems that a
> malformed incoming message caused the IMS to die, in turn causing the
> Information Store to die. My users started having problems connecting
> to the server, so I looked in the event log and found the following
> errors
(see
> below). Rebooting the box took care of the problem and now it's
> happy,
but
> I'd like to get a better idea of what happened - especially because
> this exact scenario happened on another of our Exchange servers about
> a week
ago.
>
> Article #Q293288 in the MS KB seems to describe exactly what happened.
But,
> article #Q278320 indicates that this problem was fixed in SP4, which
> we have. (I also checked the version #'s for the pertinent files, and
> they
are
> definitely all at SP4.)
>
> I've poked around in various newsgroups and the knowledge base and
> haven't found anything helpful. I realise that this isn't much
> information to go
on.
> If anyone has any insights, I would be very grateful. Or, if you
> happen
to
> know which utility is used to look at messages in the "BAD" folder,
> that would be great.
>
> -Kirsten Petersen
>
>
> Event ID: 4182
> An error was returned from the messaging software the Internet Mail
Service
> uses to process messages on the Microsoft Exchange Server. As a
> result,
the
> message in spool file PKLPP9YR will be retried when the server is
restarted.
>
>
> Event ID: 3039
> The error 0x80040115 was encountered while trying to communicate with
> the message store. An attempt to refresh the connection will be made.
> If not successful, the service will be shut down.
>
> Event ID: 4116
> An error was returned from the messaging software the Internet Mail
Service
> uses to process messages on the Microsoft Exchange Server. It is
> possible that the piece of mail being processed at the time will be
> returned to the sender as a failed delivery instead of being
> delivered. The message will
be
> moved to the "BAD" folder, if possible, and the error is not a
> temporary error. Otherwise it will be retried when the service is
> restarted. Use the appropriate utilities found in the SUPPORT
> directory of your Exchange CD
to
> view and manipulate messages that have been moved to the "BAD" folder.
>
> Event ID: 4094
>
> The error 0x8004011d occurred while trying to refresh network
> connections
to
> the Information Store. The Internet Mail Service is being shut down.
>
> Event ID: 4102
> A serious error has occurred while trying to send mail into the
> Exchange Information Store. The Internet Mail Service is being shut
> down.
>
> Event ID: 270
> A permanent error has occurred with Entity blah blah blah...=MICROSOFT
> PRIVATE MDB. Entity is a Message Object is a Normal Priority
> Message.
> Object: 0600015E. Message ID: blah blah blah ... Content length: 4767,
> External Trace information (first 100 bytes) = blah blah blah..., PDU
dump
> reference 250 [MTA SUBMIT 17 74] (14)
>
> Event ID: 4182
> An error was returned from the messaging software the Internet Mail
Service
> uses to process messages on the Microsoft Exchange Server. As a
> result,
the
> message in spool file PKLPP9YS will be retried when the server is
restarted.
>
>
> Event ID: 3039
> The error 0x80040115 was encountered while trying to communicate with
> the message store. An attempt to refresh the connection will be made.
> If not successful, the service will be shut down.
>
> Event ID: 7
> An unexpected error [0x80040115] occurred in maintenance thread.
>
>
> _________________________________________________________________
> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
> Archives: http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin: [EMAIL PROTECTED]
>
> _________________________________________________________________
> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
> Archives: http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin: [EMAIL PROTECTED]
>
> _________________________________________________________________
> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
> Archives: http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin: [EMAIL PROTECTED]
>
> ______________________________________________
> This message is private or privileged. If you are not the person for
> whom this message is intended, please delete it and notify me
> immediately, and please do not copy or send this message to anyone
> else.
>
>
>
> _________________________________________________________________
> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
> Archives: http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin: [EMAIL PROTECTED]
>
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
