Question : Problem: Problem with reply to all on outlook 2003

Currently running Outlook 2003 and all office updates applied as a clean new install.  Now here is whats happening.  In production mode when initially replying to all on an email the user can send emails.   However, when the application is closed and re-opened an error message of The messaging interface has returned an unknown error appears when clicking replying to all.  The reply and forward continues to work but not the reply to all.

We have done the following:
1-      Removed all add-ins and performed a detect and repair Works once then error returns.
2-      Uninstalled Office 2003 and reinstalled with every update  
3-      Installed CCleaner and removed Outlook 2003 with this utility as well
4-      Disable Antivirus and windows firewall
 
We are currently running (this one and only PC) in Outlook safe-mode where the replying to all works without problems even after closing the application.  

Outlook is setup to connect to our internal exchange server (2007).  


The only step left is blow out the PC and start from scratch  PS this is a new PC and has a few programs load in the past but was working fine.  If anyone has any ideas it would be greatly appreciated.  

Background:  Outlook 2007 previously installed and removed.  Reason: The User (Sr Management VP) believed it was causing a problem with his Treo 650p.  Totally unrelated since Outlook was not linked to the Treo in any way.  Both the PC and the Treo used independent internet connections to access the exchange server.  Therefore, it was uninstalled as per his request.  The Treo has a problem with versamail which has been fixed and working correctly.  

Answer : Problem: Problem with reply to all on outlook 2003

Hi,

Probably not what you want to hear but I would deinfately suggest re-imaging this machine especially seeing Outlook 2007 was uninstalled and the Outlook 2003 installed onto it. This could certainly cause strange issues such as this. Before doing this I would setup this user on another PC even if temporarily in order to test this first. If the problem doesn't follow the users to the new PC you can be pretty sure that its a local Windows/App issue that will be fixed with a re-build.