Outlook 2002 Crashes on System with Lots of Memory

[John Miller]

I've run Outlook 2002 since it came out, but recently encountered an exasperating problem when I installed it on my new system (Abit IC7-MAX3 motherboard, P4-3.0, 1 GB RAM) which has two users (both administrators).

If one user runs Outlook, then when the second user runs it, it crashes with the error message labeled, "Microsoft Visual C++ Runtime Library", and stating, "Runtime Error! Program: C:\Program Files\Microsoft Office\OUTLOOK.EXE abnormal program termination". After clicking "OK" to close the dialog box, Outlook exits. Then it is possible to start Outlook normally, and it runs fine. But then when the other user runs it, it goes through the same crash-and-burn. It doesn't matter whether the first user is still logged in, nor does it matter whether the first user still has Outlook running or not. Nor is it a faulty installation, since I've reinstalled my entire system twice (for other reasons) since first discovering this problem.

The only thing I can see that's unique is the large memory complement on this new system. Has anyone else experienced this? Better yet, does anyone have a solution?

Thanks.

- John

 

[Roady [MVP]]

1GB of memory isn't that much these days ;-)

It's caused by an add-in that you've installed; this add-in gets disabled if
it crashed Outlook so Outlook will start the next time without error.
Wild guess; you are running McAfee as your virusscanner? Disable the
Exchange Scan add-in (unless McAfee has updated it and then you should do
that of course);
Tools-> Options-> tab Other-> button Advanced Options...-> button Add-In
Manager...

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I've run Outlook 2002 since it came out, but recently encountered an
exasperating problem when I installed it on my new system (Abit IC7-MAX3
motherboard, P4-3.0, 1 GB RAM) which has two users (both administrators).

If one user runs Outlook, then when the second user runs it, it crashes with
the error message labeled, "Microsoft Visual C++ Runtime Library", and
stating, "Runtime Error! Program: C:\Program Files\Microsoft
Office\OUTLOOK.EXE abnormal program termination". After clicking "OK" to
close the dialog box, Outlook exits. Then it is possible to start Outlook
normally, and it runs fine. But then when the other user runs it, it goes
through the same crash-and-burn. It doesn't matter whether the first user
is still logged in, nor does it matter whether the first user still has
Outlook running or not. Nor is it a faulty installation, since I've
reinstalled my entire system twice (for other reasons) since first
discovering this problem.

The only thing I can see that's unique is the large memory complement on
this new system. Has anyone else experienced this? Better yet, does anyone
have a solution?

Thanks.

- John

 

[John Miller]

Yeah, I agree that 1 GB isn't huge, but that was the only thing I could
think of that was different from previous installations.

I'm not running McAfee, but rather Norton Internet Security, which includes
Norton Anti-Virus. The only Outlook add-ins listed are "Exchange Extensions
property pages" and "Fax Server Extension". Since I never use the services
provided by Exchange Extensions, and I never fax from Outlook, I'll try
disabling them, then re-enabling one at a time, to see what happens.

Thanks for your suggestions. I'll let you know how I make out.

- John

 

[John Miller]

I tried disabling both of the add-ins, but it made no difference. Any other
suggestions?

- John

Yeah, I agree that 1 GB isn't huge, but that was the only thing I could
think of that was different from previous installations.

I'm not running McAfee, but rather Norton Internet Security, which includes
Norton Anti-Virus. The only Outlook add-ins listed are "Exchange Extensions
property pages" and "Fax Server Extension". Since I never use the services
provided by Exchange Extensions, and I never fax from Outlook, I'll try
disabling them, then re-enabling one at a time, to see what happens.

Thanks for your suggestions. I'll let you know how I make out.

- John

message news:[email protected]...

1GB of memory isn't that much these days ;-)

It's caused by an add-in that you've installed; this add-in gets

disabled

if
it crashed Outlook so Outlook will start the next time without error.
Wild guess; you are running McAfee as your virusscanner? Disable the
Exchange Scan add-in (unless McAfee has updated it and then you should do
that of course);
Tools-> Options-> tab Other-> button Advanced Options...-> button Add-In
Manager...

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I've run Outlook 2002 since it came out, but recently encountered an
exasperating problem when I installed it on my new system (Abit IC7-MAX3
motherboard, P4-3.0, 1 GB RAM) which has two users (both administrators).

If one user runs Outlook, then when the second user runs it, it crashes with
the error message labeled, "Microsoft Visual C++ Runtime Library", and
stating, "Runtime Error! Program: C:\Program Files\Microsoft
Office\OUTLOOK.EXE abnormal program termination". After clicking "OK" to
close the dialog box, Outlook exits. Then it is possible to start Outlook
normally, and it runs fine. But then when the other user runs it, it goes
through the same crash-and-burn. It doesn't matter whether the first user
is still logged in, nor does it matter whether the first user still has
Outlook running or not. Nor is it a faulty installation, since I've
reinstalled my entire system twice (for other reasons) since first
discovering this problem.

The only thing I can see that's unique is the large memory complement on
this new system. Has anyone else experienced this? Better yet, does anyone
have a solution?

Thanks.

- John

 

[Roady [MVP]]

Disable the Outlook integration from within Norton Anti-Virus

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----

I tried disabling both of the add-ins, but it made no difference. Any
other
suggestions?

- John

Yeah, I agree that 1 GB isn't huge, but that was the only thing I could
think of that was different from previous installations.

I'm not running McAfee, but rather Norton Internet Security, which includes
Norton Anti-Virus. The only Outlook add-ins listed are "Exchange Extensions
property pages" and "Fax Server Extension". Since I never use the services
provided by Exchange Extensions, and I never fax from Outlook, I'll try
disabling them, then re-enabling one at a time, to see what happens.

Thanks for your suggestions. I'll let you know how I make out.

- John

message news:[email protected]...

1GB of memory isn't that much these days ;-)

It's caused by an add-in that you've installed; this add-in gets

disabled

if
it crashed Outlook so Outlook will start the next time without error.
Wild guess; you are running McAfee as your virusscanner? Disable the
Exchange Scan add-in (unless McAfee has updated it and then you should do
that of course);
Tools-> Options-> tab Other-> button Advanced Options...-> button
Add-In
Manager...

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I've run Outlook 2002 since it came out, but recently encountered an
exasperating problem when I installed it on my new system (Abit
IC7-MAX3
motherboard, P4-3.0, 1 GB RAM) which has two users (both administrators).

If one user runs Outlook, then when the second user runs it, it crashes with
the error message labeled, "Microsoft Visual C++ Runtime Library", and
stating, "Runtime Error! Program: C:\Program Files\Microsoft
Office\OUTLOOK.EXE abnormal program termination". After clicking "OK" to
close the dialog box, Outlook exits. Then it is possible to start Outlook
normally, and it runs fine. But then when the other user runs it, it goes
through the same crash-and-burn. It doesn't matter whether the first user
is still logged in, nor does it matter whether the first user still has
Outlook running or not. Nor is it a faulty installation, since I've
reinstalled my entire system twice (for other reasons) since first
discovering this problem.

The only thing I can see that's unique is the large memory complement
on
this new system. Has anyone else experienced this? Better yet, does anyone
have a solution?

Thanks.

- John

 

[John Miller]

By that, are you recommending that I disable all e-mail scanning and
protection from within Norton AntiVirus? That would seem to leave me at
substantial risk. Or am I misinterpreting you?

- John

Disable the Outlook integration from within Norton Anti-Virus

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----

I tried disabling both of the add-ins, but it made no difference. Any
other
suggestions?

- John

Yeah, I agree that 1 GB isn't huge, but that was the only thing I could
think of that was different from previous installations.

I'm not running McAfee, but rather Norton Internet Security, which includes
Norton Anti-Virus. The only Outlook add-ins listed are "Exchange Extensions
property pages" and "Fax Server Extension". Since I never use the services
provided by Exchange Extensions, and I never fax from Outlook, I'll try
disabling them, then re-enabling one at a time, to see what happens.

Thanks for your suggestions. I'll let you know how I make out.

- John

"Roady [MVP]" <newsgroups_DELETE_@_DELETE_sparnaaij_NO_._SPAM_net>

wrote
in

message 1GB of memory isn't that much these days ;-)

It's caused by an add-in that you've installed; this add-in gets disabled
if
it crashed Outlook so Outlook will start the next time without error.
Wild guess; you are running McAfee as your virusscanner? Disable the
Exchange Scan add-in (unless McAfee has updated it and then you

should
do

that of course);
Tools-> Options-> tab Other-> button Advanced Options...-> button
Add-In
Manager...

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I've run Outlook 2002 since it came out, but recently encountered an
exasperating problem when I installed it on my new system (Abit
IC7-MAX3
motherboard, P4-3.0, 1 GB RAM) which has two users (both administrators).

If one user runs Outlook, then when the second user runs it, it crashes
with
the error message labeled, "Microsoft Visual C++ Runtime Library", and
stating, "Runtime Error! Program: C:\Program Files\Microsoft
Office\OUTLOOK.EXE abnormal program termination". After clicking

"OK"
to

close the dialog box, Outlook exits. Then it is possible to start Outlook
normally, and it runs fine. But then when the other user runs it, it goes
through the same crash-and-burn. It doesn't matter whether the first user
is still logged in, nor does it matter whether the first user still has
Outlook running or not. Nor is it a faulty installation, since I've
reinstalled my entire system twice (for other reasons) since first
discovering this problem.

The only thing I can see that's unique is the large memory complement
on
this new system. Has anyone else experienced this? Better yet, does
anyone
have a solution?

Thanks.

- John

 

[Guest]

The problem is caused by the Norton AntiSpam-plugin.
Until Symantec updates this component the only way to disable the AntiSpam function completely is to rename the file "msouplug.dll".
If you give it a new name like "msouplug.dll.old" it will be easy for you to find it at a later time when a permanent solution to the problem has been released.
(The file mentioned can be found in the folder "C:\Program Files\Common Files\Symantec Shared\Antispam\")

Kraesten

By that, are you recommending that I disable all e-mail scanning and
protection from within Norton AntiVirus? That would seem to leave me at
substantial risk. Or am I misinterpreting you?

- John

Disable the Outlook integration from within Norton Anti-Virus

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----

I tried disabling both of the add-ins, but it made no difference. Any
other
suggestions?

- John

Yeah, I agree that 1 GB isn't huge, but that was the only thing I could
think of that was different from previous installations.

I'm not running McAfee, but rather Norton Internet Security, which
includes
Norton Anti-Virus. The only Outlook add-ins listed are "Exchange
Extensions
property pages" and "Fax Server Extension". Since I never use the
services
provided by Exchange Extensions, and I never fax from Outlook, I'll try
disabling them, then re-enabling one at a time, to see what happens.

Thanks for your suggestions. I'll let you know how I make out.

- John

in
message 1GB of memory isn't that much these days ;-)

It's caused by an add-in that you've installed; this add-in gets
disabled
if
it crashed Outlook so Outlook will start the next time without error.
Wild guess; you are running McAfee as your virusscanner? Disable the
Exchange Scan add-in (unless McAfee has updated it and then you should
do
that of course);
Tools-> Options-> tab Other-> button Advanced Options...-> button
Add-In
Manager...

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I've run Outlook 2002 since it came out, but recently encountered an
exasperating problem when I installed it on my new system (Abit
IC7-MAX3
motherboard, P4-3.0, 1 GB RAM) which has two users (both
administrators).

If one user runs Outlook, then when the second user runs it, it crashes
with
the error message labeled, "Microsoft Visual C++ Runtime Library", and
stating, "Runtime Error! Program: C:\Program Files\Microsoft
Office\OUTLOOK.EXE abnormal program termination". After clicking "OK"
to
close the dialog box, Outlook exits. Then it is possible to start
Outlook
normally, and it runs fine. But then when the other user runs it, it
goes
through the same crash-and-burn. It doesn't matter whether the first
user
is still logged in, nor does it matter whether the first user still has
Outlook running or not. Nor is it a faulty installation, since I've
reinstalled my entire system twice (for other reasons) since first
discovering this problem.

The only thing I can see that's unique is the large memory complement
on
this new system. Has anyone else experienced this? Better yet, does
anyone
have a solution?

Thanks.

- John

 

[Roady [MVP]]

Yes, you are misinterpreting me. At this point we are troubleshooting
Outlook and finding the cause of your issue. Since Outlook is running
without issues in a clean environment (/safe) it's most likely caused by an
add-in. Enabling/disabling them one by one finds the cause.

Also note that a virusscanner that integrates with Outlook 2002 is not a
direct need as Outlook blocks all executables and scripts and doesn't allow
scripts to be executed in the Preview Pane. In worst case scenario your on
access scanner will stop virusses as well.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----

By that, are you recommending that I disable all e-mail scanning and
protection from within Norton AntiVirus? That would seem to leave me at
substantial risk. Or am I misinterpreting you?

- John

in
message news:[email protected]...

Disable the Outlook integration from within Norton Anti-Virus

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----

I tried disabling both of the add-ins, but it made no difference. Any
other
suggestions?

- John

Yeah, I agree that 1 GB isn't huge, but that was the only thing I
could
think of that was different from previous installations.

I'm not running McAfee, but rather Norton Internet Security, which
includes
Norton Anti-Virus. The only Outlook add-ins listed are "Exchange
Extensions
property pages" and "Fax Server Extension". Since I never use the
services
provided by Exchange Extensions, and I never fax from Outlook, I'll
try
disabling them, then re-enabling one at a time, to see what happens.

Thanks for your suggestions. I'll let you know how I make out.

- John

in
message 1GB of memory isn't that much these days ;-)

It's caused by an add-in that you've installed; this add-in gets
disabled
if
it crashed Outlook so Outlook will start the next time without
error.
Wild guess; you are running McAfee as your virusscanner? Disable the
Exchange Scan add-in (unless McAfee has updated it and then you should
do
that of course);
Tools-> Options-> tab Other-> button Advanced Options...-> button
Add-In
Manager...

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I've run Outlook 2002 since it came out, but recently encountered an
exasperating problem when I installed it on my new system (Abit
IC7-MAX3
motherboard, P4-3.0, 1 GB RAM) which has two users (both
administrators).

If one user runs Outlook, then when the second user runs it, it crashes
with
the error message labeled, "Microsoft Visual C++ Runtime Library", and
stating, "Runtime Error! Program: C:\Program Files\Microsoft
Office\OUTLOOK.EXE abnormal program termination". After clicking "OK"
to
close the dialog box, Outlook exits. Then it is possible to start
Outlook
normally, and it runs fine. But then when the other user runs it,
it
goes
through the same crash-and-burn. It doesn't matter whether the
first
user
is still logged in, nor does it matter whether the first user still has
Outlook running or not. Nor is it a faulty installation, since I've
reinstalled my entire system twice (for other reasons) since first
discovering this problem.

The only thing I can see that's unique is the large memory
complement
on
this new system. Has anyone else experienced this? Better yet,
does
anyone
have a solution?

Thanks.

- John

 

[John Miller]

Kraesten -

Thank you!! I went through all manner of contortions trying to blow away
the Norton anti-spam plug-in, and it always kept getting re-enabled. Even
disabling anti-spam from within Norton Internet Security had no apparent
effect. I guess they figure nobody in their right mind would want to dump
any aspect of their product (talk about arrogance!). I don't find their
anti-spam stuff of much use, anyway, since my ISP (AT&T WorldNet) does a
pretty good job of snuffing most of it before it gets to me.

- John

The problem is caused by the Norton AntiSpam-plugin.
Until Symantec updates this component the only way to disable the AntiSpam

function completely is to rename the file "msouplug.dll".

If you give it a new name like "msouplug.dll.old" it will be easy for you

to find it at a later time when a permanent solution to the problem has been
released.

(The file mentioned can be found in the folder "C:\Program Files\Common

Files\Symantec Shared\Antispam\")

Kraesten

By that, are you recommending that I disable all e-mail scanning and
protection from within Norton AntiVirus? That would seem to leave me at
substantial risk. Or am I misinterpreting you?

- John

message news:[email protected]...

Disable the Outlook integration from within Norton Anti-Virus

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I tried disabling both of the add-ins, but it made no difference. Any
other
suggestions?

- John

Yeah, I agree that 1 GB isn't huge, but that was the only thing I could
think of that was different from previous installations.

I'm not running McAfee, but rather Norton Internet Security, which
includes
Norton Anti-Virus. The only Outlook add-ins listed are "Exchange
Extensions
property pages" and "Fax Server Extension". Since I never use the
services
provided by Exchange Extensions, and I never fax from Outlook, I'll try
disabling them, then re-enabling one at a time, to see what happens.

Thanks for your suggestions. I'll let you know how I make out.

- John

in
message 1GB of memory isn't that much these days ;-)

It's caused by an add-in that you've installed; this add-in gets
disabled
if
it crashed Outlook so Outlook will start the next time without error.
Wild guess; you are running McAfee as your virusscanner? Disable the
Exchange Scan add-in (unless McAfee has updated it and then you should
do
that of course);
Tools-> Options-> tab Other-> button Advanced Options...-> button
Add-In
Manager...

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Creating Signatures
-Create an Office XP CD slipstreamed with Service Pack 3

-----
I've run Outlook 2002 since it came out, but recently encountered an
exasperating problem when I installed it on my new system (Abit
IC7-MAX3
motherboard, P4-3.0, 1 GB RAM) which has two users (both
administrators).

If one user runs Outlook, then when the second user runs it, it crashes
with
the error message labeled, "Microsoft Visual C++ Runtime

Library",
and

stating, "Runtime Error! Program: C:\Program Files\Microsoft
Office\OUTLOOK.EXE abnormal program termination". After clicking "OK"
to
close the dialog box, Outlook exits. Then it is possible to start
Outlook
normally, and it runs fine. But then when the other user runs it, it
goes
through the same crash-and-burn. It doesn't matter whether the first
user
is still logged in, nor does it matter whether the first user

still
has

Outlook running or not. Nor is it a faulty installation, since I've
reinstalled my entire system twice (for other reasons) since first
discovering this problem.

The only thing I can see that's unique is the large memory complement
on
this new system. Has anyone else experienced this? Better yet, does
anyone
have a solution?

Thanks.

- John