error msg - MS Visual C++ Debug Library "abnormal program terminat

C

cc

This is to verify as of 11/23/04 the recommended Microsoft work-around for
the above error message you see when attempting to open Outlook 2002 in
multi-desktop XP environment while running Norton internet Security.

I spent hours working with both Symantec and Microsoft. Symantec's
front-line tech support is not aware of the problem. After determining the
error message was not a "Norton" problem he told me to contact Microsoft. I
explained to the supervisor that the problem surfaced only upon my installing
Symantec Norton Internet Security so it was indeed a Symantec problem. I was
still told to go to Microsoft. Infuriated, I had no choice.

I was able to convince the Microsoft front-line call center agent to give me
a grace call bypassing the $35 charge because it was a prompt by the SP2
upgrade saying my computer was at risk which made me buy the Norton package 2
days ago.

Kim from Microsoft was very good and Bill Gates should give her a raise!

The work around is indeed to "disable" the "msouplug.dll" file by changing
the file extension to ".old" This particular file is the plug-in for the
Norton Anti-Spam feature which sorts spam emails into the Norton Anti-Spam
Folder in your personal files. This is what is breaks when Norton Internet
Security is installed in multiple-desktop XP Office 2002 environments.

The path is important because it the "msouplug.dll" file is a hidden file,
and even if you enable "look for hidden files and folders" in Windows
Explorer you may not find it.

The path is C:\Program Files\Common Files\Symantec Shared\Anti Spam

Find the "msouplug.dll" file, right-click, and rename to "msouplug.old"

Restart Computer and open Outlook. You will notice the Norton Toolbar is
gone from Outlook. The "Anti Spam" has been turned-off.

I was hesitant to do this at first because it made me mad to realize I had
to disable part of the security package I just bought! But I did call
Semantec back and talked to another supervisor who is promising there will be
a fix coming. I was promised i will get a call in 48 hours. I am not
counting on it, but when a fix does come, all I have to do is go back to that
"msouplug.out" and change it back to ".dll" And, the fix might just do that
automatically.

The Semantec Tech Supervisor did seem to be earnestly working on trying to
replicate the error and he did promise he would raise awareness on the issue.

We can only hope. Maybe they should put some of those yellow-jacketed guys
to work in the call center :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top