Steve Smith's Blog

Musings on Software and the Developer Community

Outlook Send Mail Infinite Loop – Message in Outbox

Last week I encountered a problem with Outlook that I’m happy to report I’ve just solved.  I found a bunch of things on the Interwebs that looked like they might be useful, but none of the fixes there did the trick for me (of the ones I tried – some fixes were more extreme than I wanted to attempt).  Here are some resources that may help you if my fix does not:

The Problem

I tried to send an email on Sunday and for whatever reason it got stuck in my outbox.  It was italicized, and if I tried to open or delete it, it would inform me that Outlook was already trying to send the message and thus I couldn’t do anything to it.  This was a minor annoyance, at first.

However, this became much more of an annoyance when Outlook would, from time to time, get into some kind of an infinite loop while trying to send messages.  It would generate “Successful” account synchonrization messages over and over again (racking up hundreds of such messages per minute).  Some of my online research suggested this might mean that my Address Book was out of sync with my contacts, but following the steps in that post revealed that this wasn’t my issue.  While this loop was going on, Outlook was unusable and the Send/Receive dialog would flicker, taking focus from other windows, which basically forced me to close OULOOK.EXE from Task Manager.

I downloaded MDBVU32.EXE on the advice of some other blogs, which let me view my PST file and attempt to manipulate its contents.  I was able to see the message in the outbox but attempting to delete it did nothing, and attempts to abort sending the message resulted in an error.

I tried switching to Offline mode, but that didn’t help.  In fact, the infinite loop still occurred (I wasn’t really sure why it was still trying to connect to anything, but it was).  Some of the possible solutions I’d found online suggested that I create a new PST file and delete all of my accounts and re-create them in the new PST file, and then move over my messages.  That definitely seemed like overkill and really at that point I was starting to consider just giving up on Outlook altogether.  Luckily, I found the solution today before resorting to anything that drastic.

The Solution

Thanks to Outlook guru Alon Brown, the solution was pretty straightforward.  Restart Outlook in safe mode, switch to Offline mode, then restart Outlook in safe mode again (while still offline), and delete the message. This worked!

I’d tried safe mode, and I’d tried offline mode, but I hadn’t tried restarting Outlook with these settings in place.  I’m not sure if it was necessary to be in safe mode each time or not, but those are the steps that worked for me.  To get outlook into safe mode, simply browse to the path where OUTLOOK.EXE is located (e.g. C:\Program Files\Microsoft Office\Office12\OUTLOOK.EXE) and run it from the command prompt with the /safe switch.  Then you should be able to navigate to the Outbox and delete any messages found there.

    kick it on DotNetKicks.com

Monday, 04 May 2009

Comments

 avatar

David Coveney said on 07 May 2009 at 8:52 AM

Excellent tip there and did just the trick - Outlook had been driving me mad all morning. Now to get on with some work once more!


 avatar

Robz said on 16 May 2009 at 6:44 PM

Another trick. Shut down Outlook and turn off the "internets." Then start Outlook. Then you can delete the thing.

Then turn the "internets" back on.


 avatar

robzfan said on 07 Jun 2009 at 10:12 PM

robz ur a genius


 avatar

Jim Lucas said on 28 Dec 2009 at 11:40 PM

Thank you so much, this was driving me crazy.

I had a lttle trouble typing in the full path to Outlook, but I found this helpful alternative as a way to start MS Office programs in safe mode. Hold down the Ctrl key while starting the program from the Start Menu.


 avatar

Em said on 27 Jan 2010 at 5:06 AM

THANKYOU! I can finally get on with some work!


 avatar

Dave Wolken said on 09 Feb 2010 at 12:09 PM

Thanks for the hint, even our IT guy couldn't figure it out.