Gee, that's almost as good as the hamsterdance!
Joseph Ambrose
System and Network Manager
The Conference Board
Phone : 001-212-339-0443
Fax : 001-212-836-3802
Email : [EMAIL PROTECTED]
Visit our Award Winning Web Site: www.conference-board.org
-----Original Message-----
From: Lefkovics, William [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 6:05 PM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
Did someone say developers?
www.ballmerdance.com
-----Original Message-----
From: Martin Blackstone [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 3:03 PM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
Damn developers
-----Original Message-----
From: David James [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 3:12 PM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
I was able to start both services successfully, but I did find some more
messages that were sitting in the queue which might choke it later
tonight. They had abnormal header information, but were all related to
the same application, primarily developer machines sending "buildall"
reports with numeric characters with a - before them. I'm not sure if
that's relevant, but it seems to choking on those messages only.
DJ
-----Original Message-----
From: Marty Richards [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 4:59 PM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
Interesting. I have seen this or similar on 4 unrelated sites in 5
weeks, all Exchange 5.5 SP4.
It looks like a delivery notification returning from xyz chokes in the
IMC and results in a DrWatson in Store.exe. Restarting the IS is simple,
but restarting the IMC gives another DrWatson and halts the IS.
The fast fix has been to clear out imcdata/in, remove imcdata/queue.dat
and restart the services.
The suspect delivery notifications look normal except for a large chunk
of ms-tnef stuff appended. I'm resisting the temptation to post an
example to the list ;)
Anyone else seeing this?
Cheers,
Marty
-----Original Message-----
From: David James [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 13 September 2001 7:33 AM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
Thanks for your help.
It seems that one of the developers did a buildall in VC++ and had the
results mailed to him. For some reason that message wouldn't move
through the server. I'm not sure what to look for when he does it
again, but I'm going to use the MDB viewer tool to see what I come up
with.
Thanks again.
DJ
-----Original Message-----
From: Don Ely [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 4:14 PM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
IMC stops IS worked for me...
http://support.microsoft.com/support/kb/articles/Q232/2/79.ASP
-----Original Message-----
From: David James [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 2:07 PM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
Don,
Malformed email header search didn't produce anything. Is there a more
"Microsoft encyclopedia" name for malformed?
DJ
-----Original Message-----
From: Don Ely [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 3:26 PM
To: MS-Exchange Admin Issues
Subject: RE: IMS stoppage
Search technet on malformed email headers, I'm sure you will find some
nice results and resolutions to your problem. There is a tool on the
Exch CD called MDBVU32.EXE which should help resolve the issue.
D
-----Original Message-----
From: David James [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 1:22 PM
To: MS-Exchange Admin Issues
Subject: IMS stoppage
I came in this morning and the IS and the IMS services had stopped last
night. The event log is saying that there was a BAD message. Summary of
events in order are as follows:
Event Type: Error
Event Source: ESE97
Event Category: Performance
Event ID: 0
Date: 9/11/2001
Time: 11:53:55 PM
User: N/A
Computer:
Description:
MSExchangeIS (396) Unexpected Win32 error: 0x79
Event Type: Error
Event Source: ESE97
Event Category: Logging/Recovery
Event ID: 126
Date: 9/11/2001
Time: 11:53:56 PM
User: N/A
Computer:
Description:
MSExchangeIS (396) Unable to write to section 0 while flushing the log.
Error -1022.
Event Type: Error
Event Source: ESE97
Event Category: Logging/Recovery
Event ID: 193
Date: 9/11/2001
Time: 11:53:57 PM
User: N/A
Computer:
Description:
MSExchangeIS (396) The database engine failed with error -510 while
trying to log the commit of a transaction. To ensure database
consistency, the process was terminated. Simply restart the process to
force database recovery and return the database to a consistent state.
Event Type: Error
Event Source: MSExchangeIMC
Event Category: Internal Processing
Event ID: 4182
Date: 9/11/2001
Time: 11:55:54 PM
User: N/A
Computer:
Description:
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 R9JGKTFZ will be retried when the
server is restarted.
Data:
0000: 73 05 01 00 15 01 04 80 s......EUR
Event Type: Warning
Event Source: MSExchangeIMC
Event Category: Internal Processing
Event ID: 3039
Date: 9/11/2001
Time: 11:55:54 PM
User: N/A
Computer:
Description:
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.
Data:
0000: 67 06 14 00 15 01 04 80 g......EUR
Event Type: Error
Event Source: MSExchangeIMC
Event Category: Internal Processing
Event ID: 4116
Date: 9/11/2001
Time: 11:55:58 PM
User: N/A
Computer: DELL_SERVER_3
Description:
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.
Data:
0000: 5f 00 0f 00 1d 01 04 80 _......EUR
If anyone has seen this or can tell me what is going on, I would
appreciate it. Just a Q article would be fine too. I get so many hits
on Q articles I'm not real sure what which one is describing what is
going on. Thanks in advance.
David James
This is Exchange 5.5, SP4, running on NT4, SP6. Could it just have been
a message in the queue that caused it???
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
