PGP Desktop Corrupts Outlook 2010 Recover Deleted Items

Mark Berry September 8, 2011

This one has driven me mad for weeks. Finally tracked it down to PGP Desktop. Here are the symptoms and a workaround.

Outlook 2010 Can’t Send Email to Explicit Address

Mark Berry April 20, 2011

This Outlook 2010 issue has me stumped so far. Looking for feedback/suggestions.

I have a contact in Outlook that has two names, e.g. John Doe and Jane Smith. Only John’s email is in the contact record:

Outlook Does Not Finish Send and Receive of OAB

Mark Berry March 18, 2011

This week, the Send and Receive task in Outlook 2007 SP2 and Outlook 2010 started hanging while trying to download from Exchange Server 2007 SP3 on SBS 2008. If I highlighted the stuck process, I could see that it wasn’t able to get the Offline Address Book:

Outlook 2010 Repeated Logon Prompts

Mark Berry March 18, 2011

I’ve been using Outlook 2010 under Window 7 for a few months, connected to Exchange 2007 SP3 running under SBS 2008. I have three Exchange accounts set up in my Outlook profile. Suddenly this week I couldn’t get email: I got one credential prompt after another, no matter how many times I entered the password.

Fixing Outlook 2007 Rules after Backup Exec Mailbox Restore

Mark Berry July 27, 2008

I'm using Outlook 2007 to connect to Exchange 2003 under SBS 2003. All of my rules are server-side. The rules are still in Outlook 2003 format, though I'm not sure if that matters for this issue. 

Recently I used a third-party program to restore a backup to my aging MPx220 SmartPhone. Upon connecting with ActiveSync, it overwrote my Inbox, Tasks, and Calendar in Outlook and thus Exchange. Bad.

Fortunately, my daily Exchange backup with the Backup Exec 10d Exchange option had run that morning, so I was able to restore the mailbox in short order.

Unfortunately, this messed up my rules in Outlook 2007. The rules were there, and they ran fine manually, but they would not run automatically when mail was received.

Article 232585 in the Symantec knowledge base pointed me in the right direction, but was not a full solution. It recommends exporting and importing the rules. When I did that, nothing seemed to change. All the rules were there, but only a couple of them were firing automatically. 

I thought maybe I could fix the server-side rules by looking at them in Outlook Web Access (OWA). It turns out that none of my rules can be editing in OWA (apparently because OWA can't handle the “stop processing more rules” directive). What's interesting is that OWA showed me that each rule appeared twice. The export/import must have duplicated them.

This gave me the idea for the following solution:

1. Print the list of rules from OWA in case you might need to recreate them manually.
2. Export the rules from Outlook 2007 to a .rwz file on your desktop.
3. Close Outlook 2007. From the command line, run “outlook /cleanrules” to delete all your server- and client-side rules. Close Outlook again.
4. Start Outlook normally. Import the rules that you exported in step 2 above.

Now you should only see one copy of the each rule in OWA, and they should be triggered automatically!

Outlook 2007 Crashes on Exit Due to WinFax Module dccmsp32.dll

Mark Berry May 15, 2008

Problem

I have a workstation running Windows XP SP2 on an SBS 2003 domain with Exchange. Yesterday I upgraded it from Office 2003 SP3 to Office 2007 SP1.  All security patches have been applied.
 
When logged on to this machine as an administrative user, Outlook crashes 100% consistently whenever I exit Outlook. Starting as “outlook.exe /safe” did not help. Running Office Diagnostics did not help.

Here is some information from the error that is sent to Microsoft:
 

Error signature
AppName: outlook.exe
AppVer: 12.0.63000.5000
appStamp: 4760725d
ModName: dccmsp32.dll
ModVer: 10.0.2000.929
ModStamp: 39d4133c
fDebug: 0
Offset: 00005346
 

Exception Information
Code: 0xc0000005
Flags: 0×00000000
Record: 0×0000000000000000
Address: 0×0000000010005346

The faulting module, dccmsp32.dll, is part of WinFax Pro 10.03. Disabling the Outlook integration on the WinFax side and the Outlook side did not solve the problem. 

Solution 

I eventually found this Symantec post:

How to integrate WinFax PRO 10.02 and Outlook 2002 on a limited basis
http://service1.symantec.com/support/faxprod.nsf/docid/2001110911391704

In the end, I wound up following the instructions at the very end of that document (“If the problems persist…”):  saving my Winfax data and cover subfolders, uninstalling WinFax, doing a Custom reinstall (deselecting External Phonebooks and send fax by email), copying my data and cover subfolders back, and renaming these four files:

C:\Program Files\Winfax\Wfxext.dll
C:\Program Files\Winfax\Wfoladin.dll
C:\Windows\system32\Dccmsp32.dll
C:\Windows\system32\
Dccwfp32.dll

After that, Outlook exits with no problems, and WinFax works by starting the Message Maanger (not the Controller).