Exchange 2010 randomly re-sends messages

CecilAdmin
CecilAdmin used Ask the Experts™
on
Hello everyone,

over the past month we have had a few users report that random old (2-5 weeks old) e-mails getting re-sent.  It has been anywhere from 1 to 10 e-mails per user and thus far we've had 3-5 users report the problem.

I have not been able to identify any common ground for the messages which were re-sent.  I have looked through the message tracking logs and have not seen anything strange there either.  The most recent issue the user was not even at work or using her computer so I do not think this is a client/outlook issue.

I have a DAG configuration that has been up/running for over a year now with no problems.  About 6 months ago we implemented ForeFront & ForeFront for Exchange - I have excluded the Exchange folder, DB folder, & public folders from the ForeFront file scan.  About 4 months ago we updated to Exchange SP1.

I have tried searching on Google and I am starting to wonder if this is an issue with the Exchange Temp-Tables?

I'm looking for any other suggestions or ideas.  Also any information regarding this Exchange Temp-Tables would be great.

Thanks,
Ian Cooper
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
jrhelgesonSolutions Architect

Commented:
I'd start by doing a mailbox integrity check. You do not need to take the server offline.
From the Exchange Management Shell - run the following (obviously you'll need to replace the "Mailbox Database 01529..." with your mailbox db name):
New-MailboxRepairRequest -Database "Mailbox Database 0152909091" -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

It will run the scan - it will take the individual mailboxes offline while the mailboxes are being scanned/repaired.

If that does not take care of it, then I'll need to know what type of machine this is running on. Is this installed to a physical box or virtual machine? Direct Attach storage or SAN, if SAN, what is the connection, FC, iSCSI, NFS, etc.

Joel
Any chance all of those users have a similar mobile device setup? (Blackberry in particular, but anything else could qualify)

Author

Commented:
Thanks for the replies!  Sorry I was not able to respond in a more timely manor.

I apologize that I did not note any more detailed information regarding my exchange setup.  Below has more more specifications.
- DAG is configured
- 2 Hub/Cas servers (virtual)
     + 2 CPU's, 8GB ram, 14GB free on c-drive, SAN connection to host servers is iSCSI 1GB
     + Task manager shows 6GB RAM being used, 0 to 3 % CPU being used
- 2 Mailbox DB servers (physical)
     + Dell R710, 2 quad-core CPU's, 24GB ram, 90GB free on C-drive, 150GB free on DB drive,
        500 GB on recovery drive
     + I do not recall if the DB's are stored on local drive or SAN, if on SAN then iSCSI 1GB connections
     + Task manager is showing 20-21GB of RAM being used, and 0-5% CPU

I have not done a mailbox integrity check - that is a great suggestion!

Many of the users who noted this problem have a Droid.  One users has both a Droid and iPad2.  All devises are connected via an Exchange connection.  I will note though that we have many other Droid/iOS users who have not experienced this problem.

Thanks for the suggestions!

Ian Cooper
     
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
I ended up opening a ticket with Microsoft to assist with this problem.

In the end the technician said that the normal cause for this problem is a corrupt mailbox or anti-virus programs.

I have run the command to fix the 1 user's mailbox according to the MS technician.  Now I guess it is time to wait and see.

Commented:
can you tell us the commands he had you run to fix the mailbox? Thanks!!
Solutions Architect
Commented:
The commands you use depend on the version of exchange.

If it is Exchange 2003, you dismount the store and run the following from the command line:
ISINTEG -S {servername} -FIX -TEST ALLTESTS -VERBOSE

(ISINTEG is found in the Exchange Server \bin directory)

If it is Exchange 2010, you run the powershell command to repair the mailbox folder:

To repair the Database run the following exchange powershell command:
New-MailboxRepairRequest -Database "Mailbox Database 91234567890" -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

To repair a mailbox run the following exchange powershell command:
New-MailboxRepairRequest -Mailbox bart@simpson.com -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

Joel

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial