Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Reboot causes messages to be resent

1 view
Skip to first unread message

Jesse Bethel

unread,
Jul 13, 2000, 3:00:00 AM7/13/00
to
We are running Exchange Server 5.5 on NT Server Standard. We send out a
newsletter through mass emailing - our web server generates the
newsletter and email addresses, then forwards them to this exchange
server.
In general this has worked, but sometimes (and I couldn't tell you
when - I've tried to track down a cause, but haven't found it) when I
reboot, Exchange resends the newsletter, and, I believe, only the
newsletter.
Can anyone give me an idea of what is happening here, maybe why?
Jesse
----------
Jesse Bethel
jesse....@the451.com00009

Kirill S. Palagin

unread,
Jul 13, 2000, 3:00:00 AM7/13/00
to

Anything interesting in App Event log at the time of reboot?

Jesse Bethel wrote:

--
If you feel that anything in my post needs correction - feel free to do so
(in group).
And please, keep all discussions in NG, so that everybody can participate.

Kirill

Jesse Bethel

unread,
Jul 13, 2000, 3:00:00 AM7/13/00
to

"Kirill S. Palagin" wrote:
You know, I thought I had covered everything - yes there is an interesting
message - "The inbound message queue is corrupt. Both inbound and OUTBOUND
queues will be destroyed and rebuilt. This may cause DUPLICATE OUTBOUND
deliveries" (My emphasis). Sorry I didn't see that before.
I'm not exactly sure how to respond to this. Is there a utility to correct
this spcific problem (I have run eseutil and isinteg now and again to check
for corruption of the databases, but I don't think that helps - besides,
there weren't any errors).
Thanks for making me go back over the log.

Rich Matheisen [MVP]

unread,
Jul 13, 2000, 3:00:00 AM7/13/00
to

Jesse Bethel <jesse....@the451.com> wrote:

> You know, I thought I had covered everything - yes there is an interesting
>message - "The inbound message queue is corrupt. Both inbound and OUTBOUND
>queues will be destroyed and rebuilt. This may cause DUPLICATE OUTBOUND
>deliveries" (My emphasis). Sorry I didn't see that before.
> I'm not exactly sure how to respond to this.

Stop the IMS service and delete the file IMDCATA\QUEUE.DAT. Then
delete any files from the imcdata\in and imcdata\out directories that
have already been delivered (usually that'd be anything that's more
than two days old). Then restart the IMS service and it'll rebuild the
queue.dat file.

------------------
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm

0 new messages