exchangefreaks.com Forum Index
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Bad message keeps getting queued

 
Post new topic   Reply to topic    exchangefreaks.com Forum Index -> MS Exchange 2000 Connectivity
Author Message
Russ Iwanchuk



Joined: 06 Aug 2007
Posts: 1

PostPosted: Sun Nov 02, 2003 2:36 pm    Post subject: Bad message keeps getting queued Reply with quote

Hi, all. Sorry in advance for the long message.

I've got this pesky message on an Exchange 2000 server that
gets queued every time I restart SMTP. And when it gets
queued, I can see from the logs that an SMTP session is
started with the recipient server, but the session never
finishes. My server says DATA, the other answers "OK, End
with." but even after days, no "Message accepted for
delivery" and definitely no QUIT. I can see in netstat
there's a connection to the recipient server and it just
stays that way. This has the result of blocking all other
outgoing messages to that particular mail domain.

We are otherwise fine for sending and receiving. I can do
a "manual" SMTP session to the domain in question, so
connectivity seems fine. I can see from the logs that it's
getting to the right server, etc. If I add a connector for
this domain after SMTP has restarted (and the persistent
connection gets set up), I can successfully queue up and
send mail to the domain.

I can delete this message from the queue in ESM, but the
stuck connection (as seen in netstat) doesn't go away. I
stop SMTP and of course the stuck connection goes away, but
once SMTP is restarted, even though I'd cleared the queue,
the server tries once again to send this message, again
blocking the queue. I've also tried renaming the vsi 1
directory before restarting SMTP but I get the same thing.
I've methodically restarted Exchange services after
restarting SMTP and this message doesn't show up until I
start the Information Store.

So, where is this message coming from? I don't need to get
it sent; I'd just LOOOOVE to not have it show up in the
queue again, as all other messages to this mail domain seem
to be fine. Is there another queue I'm missing?

Thanks!
--Russ

P.S. For e-mail remove the "XXXX" in my address.

Archived from group: microsoft>public>exchange2000>transport
Back to top
View user's profile Send private message
Danny Luong [MSFT]



Joined: 06 Aug 2007
Posts: 3

PostPosted: Mon Nov 03, 2003 2:38 pm    Post subject: Re: Bad message keeps getting queued Reply with quote

Hello Russ

Use a program called MFCmapi to delete the temptable. The message might be
corrupt and persistently re-sends itself from the Store to the queues with
every service re-start. Keep in mind, by deleting your root temptable, you
will remove all messages currently in queue.

To obtain the progra, go to: 291794 SAMPLE: MFCMAPI Demonstrates MAPI Client
Code

NOTE: Incorrect usage of this program may serious cripple your Exchange,
back up all vital datas first

Steps to clear out pesky mail using MFCmapi:
1.
No services need to be stopped unless MFCmapi crashes upon launch.
Run MFCmapi anywhere on the desktop
Session - Logon and display store - Profile Settings (choose one with
Exchange service admin privileges or create one by hitting new)
MDB - Get mailbox table - under display name, find "SMTP {hex}" hex GUID
should match "SystemMailbox {GUID}"
In "SMTP {GUID}"
Select temptable, right click Delete folder, place checkmark on hard
deletion, OK

Re-start your SMTP and Routing Engine services
Temptable will re-create itself


--
Regards,
Danny Luong

Exchange Enterprise Messaging Connector Engineer
v-dannyl@online.microsoft.com
Please do not send email directly to this alias. This is for newsgroup
purpose only.

This posting is provided "AS IS" with no warranties, and confers no rights."
--------------------------------
"Russ Iwanchuk" wrote in message$c8ca2420$a501280a@phx.gbl...
> Hi, all. Sorry in advance for the long message.
>
> I've got this pesky message on an Exchange 2000 server that
> gets queued every time I restart SMTP. And when it gets
> queued, I can see from the logs that an SMTP session is
> started with the recipient server, but the session never
> finishes. My server says DATA, the other answers "OK, End
> with." but even after days, no "Message accepted for
> delivery" and definitely no QUIT. I can see in netstat
> there's a connection to the recipient server and it just
> stays that way. This has the result of blocking all other
> outgoing messages to that particular mail domain.
>
> We are otherwise fine for sending and receiving. I can do
> a "manual" SMTP session to the domain in question, so
> connectivity seems fine. I can see from the logs that it's
> getting to the right server, etc. If I add a connector for
> this domain after SMTP has restarted (and the persistent
> connection gets set up), I can successfully queue up and
> send mail to the domain.
>
> I can delete this message from the queue in ESM, but the
> stuck connection (as seen in netstat) doesn't go away. I
> stop SMTP and of course the stuck connection goes away, but
> once SMTP is restarted, even though I'd cleared the queue,
> the server tries once again to send this message, again
> blocking the queue. I've also tried renaming the vsi 1
> directory before restarting SMTP but I get the same thing.
> I've methodically restarted Exchange services after
> restarting SMTP and this message doesn't show up until I
> start the Information Store.
>
> So, where is this message coming from? I don't need to get
> it sent; I'd just LOOOOVE to not have it show up in the
> queue again, as all other messages to this mail domain seem
> to be fine. Is there another queue I'm missing?
>
> Thanks!
> --Russ
>
> P.S. For e-mail remove the "XXXX" in my address.
>

Back to top
View user's profile Send private message
Display posts from previous:   
Related Topics:
OWA Loading Message I am looking for some help. I rebuilt a fresh server with Windows 2003 Standard R2 with Service Pack 2. I then installed Microsoft Exchange 2003 SP2. The install went fine. Previously we were on Microsoft Exchange 2000 with the latest service packs.

message bouncing Hello I have problems with two exchange servers After I installed new Exchange 2003 Server on Exchange 2000 Organization I get NDR message when I send messages from the old server (or from the Internet) to the new one (Old server is Exchange 2000 and a ne

MSExchangeDSAccess 2115 Warning message I had logging turned up on the service (to verify proper GC discovery) and noticed these warnings in the logs... Process INETINFO.EXE (PID=1656). DSAccess needs to close a connection to the Domain Controller due to error

Message flow between two Exchange 2003 Servers My situation has been driving me crazy for the past two months. This is the setup within my office. We have three sites which are all connected with VPN over the internet. Two of these sites are in the UK and one is in Sweden. We have four domain controll

The e-mail system was unable to deliver the message, but did I am currently migrating from Exchange 5.5 to Exchange 2003. After moving some user mailboxes from 5.5 to 2003 Exchange server, a few users have started receiving the following errors: on 5/15/2007 10:37 AM The e-mail system was unable
Post new topic   Reply to topic    exchangefreaks.com Forum Index -> MS Exchange 2000 Connectivity All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group