Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Windows Small Business Server > Outlook/Exchange RE-sending really old messages

Reply
Thread Tools Display Modes

Outlook/Exchange RE-sending really old messages

 
 
Wopster
Guest
Posts: n/a

 
      03-04-2008
Hello,

I've got an odd one here I was hoping I could get some help with. This
happened at one other customer about 3 months ago and I dismissed it as a
user problem.

The environment is SBS2k3 SP2, outlook 2k3 SP2, winxp Sp2.

The problem is this: Yesterday afternoon for some reason several dozen
messages that were sent (in this case) between 11/07-12/07 for several users
on the network were resent last night. We know this because recipients of
these messages were asking why we were resending them (and they were in the
SMTP log)

This is what I did last night that MIGHT've caused the problem but I don't
know why. I re-enabled all filtering options (connection,recipient, etc)
under the SMTP properities and I restarted the SMTP server (no big deal and
the server is rebooted once a week).

Because these old messages were sent out for several of our users, I don't
think this is an outlook/user related problem. It seems to me like these
messages were stuck in a queue somewhere (besides the normal queue) and
released after I restarted the services. (I've since enabled message tracking
and archiving of all incoming/outgoing messages on the store to try and track
this down)

Has anyone come across an issue like this or offer any idea on how
something like this could happen? (This has happened 1 other time at another
customer but I blew it off as a fluke)

Thanks for your time,

LT


 
Reply With Quote
 
 
 
 
Kevin Weilbacher
Guest
Posts: n/a

 
      03-05-2008
I would agree that what happened was that you had mail stuck, and restarting
the Exchange services forced them out again. You might go look at the
Message Tracking Center within ESM and see if it tells you anymore about
those messages.

Otherwise, pay close attention to the Exchange queues for awhile and see
which domain names or emails are getting stuck.

--
Kevin Weilbacher [SBS MVP]
"The days pass by so quickly now, the nights are seldom long"
*

"Wopster" <> wrote in message
news:9DC33C59-FCCE-4FD3-BDE2-...
> Hello,
>
> I've got an odd one here I was hoping I could get some help with. This
> happened at one other customer about 3 months ago and I dismissed it as a
> user problem.
>
> The environment is SBS2k3 SP2, outlook 2k3 SP2, winxp Sp2.
>
> The problem is this: Yesterday afternoon for some reason several dozen
> messages that were sent (in this case) between 11/07-12/07 for several
> users
> on the network were resent last night. We know this because recipients of
> these messages were asking why we were resending them (and they were in
> the
> SMTP log)
>
> This is what I did last night that MIGHT've caused the problem but I
> don't
> know why. I re-enabled all filtering options (connection,recipient, etc)
> under the SMTP properities and I restarted the SMTP server (no big deal
> and
> the server is rebooted once a week).
>
> Because these old messages were sent out for several of our users, I
> don't
> think this is an outlook/user related problem. It seems to me like these
> messages were stuck in a queue somewhere (besides the normal queue) and
> released after I restarted the services. (I've since enabled message
> tracking
> and archiving of all incoming/outgoing messages on the store to try and
> track
> this down)
>
> Has anyone come across an issue like this or offer any idea on how
> something like this could happen? (This has happened 1 other time at
> another
> customer but I blew it off as a fluke)
>
> Thanks for your time,
>
> LT
>
>


 
Reply With Quote
 
 
 
 
Terence Liu [MSFT]
Guest
Posts: n/a

 
      03-06-2008
Hello Customer,

Thank you for posting here. Let's also thank Kevin for the input.

According to the message, I understand that your Exchange 2003 server
resends old mails after you restart the SMTP. Is this correct?

Based on my research, the issue is most likely caused by message stuck in
Temp Folder. It is a known issue in Exchange Server. Let me explain in
details.

The Exchange Temp tables are special-purpose subfolders of the SMTP
service's logon to the Message Database. They are used for the creation of
the bifurcated messages in the message categorizer, and as temporary
storage for SendQ-submitted mail messages if SMTP cannot keep up with the
processing of SendQ mail. When the SMTP service logs in to the Message
Database, it forces an enumeration and submission of mail in the temp
tables. So when we restart the Exchange server or restart the SMTP service,
the mails in the temp tables will be resent.

Old messages may be found in the temp tables for one of the following
reasons:

- An error occurs each time the particular message is processed. For
example, the Information Store may return a retry-able error when an
attempt is made to relay the message, or the connector to the message
destination is unavailable.

- The message was categorized to go to a specific Message Database for
local delivery, but the Message Database is no longer available.

- An unknown or unexpected behavior caused by message damage.

Suggestion 1: At this time, I would suggest that we clear Temp Folder, and
then monitor this issue for some time to check if it reoccur.

Note Currently, the only version of the Mfcmapi.exe utility that is
approved for use is version 5.0.18.1978. Delete any earlier versions of
this utility. Earlier versions of this utility may cause performance issues
in Exchange 2000 Server and in Exchange Server 2003.

Note There is one TempTable for each SMTP virtual server. For example,
TempTable#1 corresponds to SMTP virtual server 1, and TempTable#2
corresponds to SMTP virtual server 2. In the following methods, change the
TempTables according to the Exchange Server configuration.

When you delete an SMTP virtual server, the TempTable that is associated
with the SMTP virtual server is not deleted. Additionally, the contents of
the associated TempTable are not deleted. If you add and then remove an
SMTP virtual server, you must manually delete the TempTable that is
associated with the SMTP virtual server.

Warning If you use the Mfcmapi.exe utility incorrectly, serious problems
may occur that may require that you reinstall Microsoft Exchange Server.
Serious problems may also occur that require that you restore Microsoft
Exchange Server. Microsoft cannot guarantee that problems that result from
using the Mfcmapi.exe utility incorrectly can be resolved. Use the
Mfcmapi.exe utility at your own risk.

Warning If you delete the SMTP TempTables, all incoming and outgoing
messages are cleared from the TempTables at the same time.

1. Stop the SMTP service, and then double-click Mfcmapi.exe.
The tool can be got here:
http://download.microsoft.com/downlo...5-9849-401cd9b
86d67/mfcmapi_bin.exe

2. Click OK to close the About Mfcmapi dialog box.
3. Click Session, and then click Logon and Display Stores.
4. Log on by using an Administrator account. If the MAPI profile is
unavailable, create one.
5. Click MDB, and then click Get Mailbox Table.
6. Confirm the server name, and then click OK.
7. Double-click the object SMTP ( Servername GUID ) mailbox.

Note In this step, Servername represents the name of the Exchange Server.
GUID represents the GUID.

8. Expand Root Container, and then click TempTable# n .

Note n represents the number that corresponds to the TempTable.

9. Right-click the TempTable# n object, and then click Delete Folder.
10. Click to select the Hard Deletion check box, and then click OK.
11. Confirm that the TempTable folder has been deleted. To do this, follow
these steps:
a. On the Hierarchy Table menu, click Refresh View.
b. Expand Root Container. Verify that the TempTable# n folder does not
appear.

12. Quit the Mfcmapi.exe utility.
13. Start the SMTP service. When you start this service, a new TempTable
is created.

For your reference:
How to use the Mfcmapi.exe utility to view and work with messages in the
SMTP TempTables in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/?id=906557

Suggestion 2: If it doesn't help, the issue can be caused by 3rd party
antivirus applications or message queued in the SMTP virtual server. Please
also try the following steps to check the effect.

Based on my knowledge, the possible cause for the behavior is Antispam and
Antivirus applications installed on your Exchange Server, which keep
running on the TCP port 25 originally used by Exchange SMTP Virtual Server.
When mail is sent through the port, this kind of applications queue the
messages for scanning and send the mail after certain interval. So please
temporarily disable/uninstall third party applications installed on this
Exchange Server and then verify the issue. If the issue persists, you can
continue with next step.

For your reference:
Overview of Exchange Server 2003 and antivirus software
http://support.microsoft.com/?id=823166

Suggestion 3: The behavior may also be caused when the message is queued in
SMTP Virtual Server. It is expected that SMTP Virtual Server tries to
resend unsuccessfully sent mails after reboot. Please perform the following
tests to verify whether the issue is related to SMTP Virtual Server.

1. Before reboot Exchange Server, stop SMTP Virtual Server.
2. Go to C:\Program Files\Exchsrvr\mailroot\vsi 1 and rename the Queue
folder as Queue.old
3. Restart the SMTP Virtual Server to refresh queues in Exchange System
Manager.
4. Then you can restart Exchange Server to verify whether the mails are
resent after reboot.

Hope this helps.

If there is any update, please feel free to get in touch!

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

================================================== ===
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Outlook/Exchange RE-sending really old messages
| thread-index: Ach+Sux55xkWrw6ITieu68tml3MBQA==
| X-WBNR-Posting-Host: 207.46.192.207
| From: =?Utf-8?B?V29wc3Rlcg==?= <>
| Subject: Outlook/Exchange RE-sending really old messages
| Date: Tue, 4 Mar 2008 14:56:04 -0800
| Lines: 35
| Message-ID: <9DC33C59-FCCE-4FD3-BDE2->
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:96364
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hello,
|
| I've got an odd one here I was hoping I could get some help with. This
| happened at one other customer about 3 months ago and I dismissed it as a
| user problem.
|
| The environment is SBS2k3 SP2, outlook 2k3 SP2, winxp Sp2.
|
| The problem is this: Yesterday afternoon for some reason several dozen
| messages that were sent (in this case) between 11/07-12/07 for several
users
| on the network were resent last night. We know this because recipients of
| these messages were asking why we were resending them (and they were in
the
| SMTP log)
|
| This is what I did last night that MIGHT've caused the problem but I
don't
| know why. I re-enabled all filtering options (connection,recipient, etc)
| under the SMTP properities and I restarted the SMTP server (no big deal
and
| the server is rebooted once a week).
|
| Because these old messages were sent out for several of our users, I
don't
| think this is an outlook/user related problem. It seems to me like these
| messages were stuck in a queue somewhere (besides the normal queue) and
| released after I restarted the services. (I've since enabled message
tracking
| and archiving of all incoming/outgoing messages on the store to try and
track
| this down)
|
| Has anyone come across an issue like this or offer any idea on how
| something like this could happen? (This has happened 1 other time at
another
| customer but I blew it off as a fluke)
|
| Thanks for your time,
|
| LT
|
|
|

 
Reply With Quote
 
Junior Member
Join Date: Mar 2011
Posts: 1

 
      03-16-2011
Even though this thread is very old, I happened upon it after encountering this very same issue yesterday. I would like to point out that the instructions that Terence supplied above were VERY good. That said when point that was left out which was the key for us is that if you have multiple Storage Groups on the server in question then there will be multiple of the object "SMTP ( Servername GUID ) mailbox". I didn't notice this at first and cleared the table as suggested with not positive results, however the table I cleared was not the one effected. Only after clearing all the tables for the server in question was our problem resolved.

Thanks again to Terence, excellent write up.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Do I really, really need vista service pack 1 Pauline Windows Update 23 09-30-2008 01:35 PM
System Restore really really slow!! BobJ@hotmail.com Windows Vista General Discussion 4 07-13-2008 07:12 PM
File Sharing between XP and VISTA is really really slow Stephan G. Windows Vista Networking 9 05-25-2007 01:59 PM
talk about reinventing the wheel! I really really dislike IE7 h4rb1ng3r Internet Explorer 7 03-25-2006 06:48 AM
Really really really NOT happy with MS Server 2003 update... Rob R. Ainscough Windows Server 11 04-17-2005 05:55 PM