I'm starting an MSO deployment to 400+ machines. So far I've only installed it on 4 machines in the IT team, but 2 of the 4 are exhibiting the same problem since MSO was installed.
On existing Outlook 2003, get an Outlook 2003 error message saying:
DDE Server Window: OUTLOOK.EXE - Application Error
The instruction at "0x0f703a41" referenced memory at "0x016b756c". The memory could not be "read".
Click on OK to terminate the program
During the day Outlook 2003 and MSO appear to work perfectly, the error only exhibits on exiting Outlook. The client machines are all Windows XP Pro SP3 (32bit), with Sophos Anti-Virus and Microsoft Office 2003 SP3. Sophos is configured not to monitor the C:\Program Files\Mimecast\ folder.
Screen-shot of the error is attached. All the obvious diags have been done such as re-installing with Sophos disabled, etc.
Any help would be appreciated.
In case anybody else is getting this problem, here's how I solved it ........
After installing MSO to around 400 workstations we were getting more and more calls from users who's Outlook would crash on exit. Symptoms as above, this got gradually worse until it was affecting around 10% of the client machines. Opening Outlook after a crash inevitably went through the "Outlook repairing your mailbox" process as it hadn't closed cleanly. Very frustrating.
The root cause appears to be a file called "OUTCMD.DAT" which Outlook creates in the users profile at "C:\Documents and Settings\\Application Data\Microsoft\Outlook". This file contains Outlook toolbar customisations, and according to a number of forum posts is generally prone to getting corrupted.
Deleting this file (while Outlook is not running of course) stops Outlook from crashing on-exit. If you are happy not to keep any Outlook toolbar customisations, you can delete this file at every logon as part of the logon script. A new "OUTCMD.DAT" will automatically be create by Outlook the next time it runs.
Since doing this, all seems to be well in the world of MSO.