A Microsoft Outlook email forum. Outlook Banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Outlook Banter forum » Microsoft Outlook Email Newsgroups » Add-ins for Outlook
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Outlook 2007 Beta and vpmsece3.dll



 
 
Thread Tools Search this Thread Display Modes
  #21  
Old April 15th 08, 07:38 PM posted to microsoft.public.outlook.program_addins
David
external usenet poster
 
Posts: 196
Default Outlook 2007 Beta and vpmsece3.dll

Hello all,
First, thanks to everyone who made suggestions and props to Paul for posting
the solution after figuring it out. You Rarely see that on tech forrums, many
suggestions are made and the postings just stop.. you can assume they fixed
it, but its very helpful to hear that yes.. This suggestion by ____ worked.

I had this issue after migrating from Symantec 10x to Symantec Endpoint
Protection. (Server 2003 32bit server running Outlook 2003) - Along with the
annoying error though, users couldn't open some word or excel files. They'd
get the error, "the operation failed. an object could not be found". This
add-in was causing that as well.

Symantec 10x left an add-in in Outlook which caused this same error. Going
to Tools -- options, clicking on the Other tab, then advanced options..
Under "Add-ins Manager" there was an entry for Symantec 10x. and one from SEP
which autoprotect was disabled on. Removing both of these add-in's eliminates
the error.

Again thanks everyone.
David
"Paul" wrote:

Good morning!

Well, after working on this problem for at least 12 hours, I devised a
solution, and wanted to share it so that others in the same boat do not have
to go through the frustration I did.

Based on what others posting in this thread mentioned about Add-Ins, I
decided to try to "give" Outlook 2003 the file it was looking for.
Therefore, I copied vpmsece4.dll from my Symantec AntiVirus directory, and I
pasted it into the directory of the user that uses Outlook for e-mail:

c:\Documents and Settings\user directory\Application Data\Microsoft\Add-Ins

I started up Outlook 2003 (I can't remember if I
rebooted...again...first...after 12 hours at this same problem, believe me I
lost count), and Outlook said that it had encountered a serious error. It
asked if I wanted to disable the Add-In, I said yes, and voila!

Hope this helps!


"Paul" wrote:

Good afternoon, Darryl!

I'm running Outlook 2003, and also getting this error message.

- I did Help -- Detect and Repair as recommended in the error message, and
that didn't work.

- I deleted all extend.dats on the system and rebooted. That didn't work.

- I changed the registry value referred to below to 2 from 9, deleted the
extend.dats that resulted from testing, and rebooted. That didn't work.

- I reloaded Office 2003 Pro. That didn't work. I then removed and then
reloaded Office 2003 Pro. That didn't work, either. (I kept removing any
new extend.dats and rebooting in between the tests). Interestingly, neither
of these totally cleared out some of the saved values (specifically: I had
several .psts opened and the new loads kept expecting to see these referenced
.psts), so unless the shortcuts are saved in the main .pst, some of these
saved values are being saved elsewhere.

Anyway, none of this worked. HELP??? Any other thoughts? I'm pretty
desperate!!!


"Darryl A. J. Staflund" wrote:

Hi Don,

Symantec has posted a solution at the following URL:

http://service1.symantec.com/SUPPORT...pen&dtype=corp

Cheers,
Darryl Staflund


Ads
  #22  
Old May 15th 08, 04:15 PM posted to microsoft.public.outlook.program_addins
stephanie
external usenet poster
 
Posts: 25
Default Outlook 2007 Beta and vpmsece3.dll

this worked, thanks david.

"David" wrote:

Hello all,
First, thanks to everyone who made suggestions and props to Paul for posting
the solution after figuring it out. You Rarely see that on tech forrums, many
suggestions are made and the postings just stop.. you can assume they fixed
it, but its very helpful to hear that yes.. This suggestion by ____ worked.

I had this issue after migrating from Symantec 10x to Symantec Endpoint
Protection. (Server 2003 32bit server running Outlook 2003) - Along with the
annoying error though, users couldn't open some word or excel files. They'd
get the error, "the operation failed. an object could not be found". This
add-in was causing that as well.

Symantec 10x left an add-in in Outlook which caused this same error. Going
to Tools -- options, clicking on the Other tab, then advanced options..
Under "Add-ins Manager" there was an entry for Symantec 10x. and one from SEP
which autoprotect was disabled on. Removing both of these add-in's eliminates
the error.

Again thanks everyone.
David
"Paul" wrote:

Good morning!

Well, after working on this problem for at least 12 hours, I devised a
solution, and wanted to share it so that others in the same boat do not have
to go through the frustration I did.

Based on what others posting in this thread mentioned about Add-Ins, I
decided to try to "give" Outlook 2003 the file it was looking for.
Therefore, I copied vpmsece4.dll from my Symantec AntiVirus directory, and I
pasted it into the directory of the user that uses Outlook for e-mail:

c:\Documents and Settings\user directory\Application Data\Microsoft\Add-Ins

I started up Outlook 2003 (I can't remember if I
rebooted...again...first...after 12 hours at this same problem, believe me I
lost count), and Outlook said that it had encountered a serious error. It
asked if I wanted to disable the Add-In, I said yes, and voila!

Hope this helps!


"Paul" wrote:

Good afternoon, Darryl!

I'm running Outlook 2003, and also getting this error message.

- I did Help -- Detect and Repair as recommended in the error message, and
that didn't work.

- I deleted all extend.dats on the system and rebooted. That didn't work.

- I changed the registry value referred to below to 2 from 9, deleted the
extend.dats that resulted from testing, and rebooted. That didn't work.

- I reloaded Office 2003 Pro. That didn't work. I then removed and then
reloaded Office 2003 Pro. That didn't work, either. (I kept removing any
new extend.dats and rebooting in between the tests). Interestingly, neither
of these totally cleared out some of the saved values (specifically: I had
several .psts opened and the new loads kept expecting to see these referenced
.psts), so unless the shortcuts are saved in the main .pst, some of these
saved values are being saved elsewhere.

Anyway, none of this worked. HELP??? Any other thoughts? I'm pretty
desperate!!!


"Darryl A. J. Staflund" wrote:

Hi Don,

Symantec has posted a solution at the following URL:

http://service1.symantec.com/SUPPORT...pen&dtype=corp

Cheers,
Darryl Staflund


  #23  
Old May 29th 08, 06:13 PM posted to microsoft.public.outlook.program_addins
Manish Mestry
external usenet poster
 
Posts: 1
Default Outlook 2007 Beta and vpmsece3.dll

Thanks Toddy,

Your solution helped to resolved my issue..

Thanks a ton..



  #24  
Old June 25th 08, 06:15 PM posted to microsoft.public.outlook.program_addins
Duke
external usenet poster
 
Posts: 17
Default Outlook 2007 Beta and vpmsece3.dll

After migrating from Symantec 10x to Endpoint Protection, I had the same
problem. I did what you suggested, and the problem was solved. Thanks so
much, David.


"David" wrote:

Hello all,
First, thanks to everyone who made suggestions and props to Paul for posting
the solution after figuring it out. You Rarely see that on tech forrums, many
suggestions are made and the postings just stop.. you can assume they fixed
it, but its very helpful to hear that yes.. This suggestion by ____ worked.

I had this issue after migrating from Symantec 10x to Symantec Endpoint
Protection. (Server 2003 32bit server running Outlook 2003) - Along with the
annoying error though, users couldn't open some word or excel files. They'd
get the error, "the operation failed. an object could not be found". This
add-in was causing that as well.

Symantec 10x left an add-in in Outlook which caused this same error. Going
to Tools -- options, clicking on the Other tab, then advanced options..
Under "Add-ins Manager" there was an entry for Symantec 10x. and one from SEP
which autoprotect was disabled on. Removing both of these add-in's eliminates
the error.

Again thanks everyone.
David
"Paul" wrote:

Good morning!

Well, after working on this problem for at least 12 hours, I devised a
solution, and wanted to share it so that others in the same boat do not have
to go through the frustration I did.

Based on what others posting in this thread mentioned about Add-Ins, I
decided to try to "give" Outlook 2003 the file it was looking for.
Therefore, I copied vpmsece4.dll from my Symantec AntiVirus directory, and I
pasted it into the directory of the user that uses Outlook for e-mail:

c:\Documents and Settings\user directory\Application Data\Microsoft\Add-Ins

I started up Outlook 2003 (I can't remember if I
rebooted...again...first...after 12 hours at this same problem, believe me I
lost count), and Outlook said that it had encountered a serious error. It
asked if I wanted to disable the Add-In, I said yes, and voila!

Hope this helps!


"Paul" wrote:

Good afternoon, Darryl!

I'm running Outlook 2003, and also getting this error message.

- I did Help -- Detect and Repair as recommended in the error message, and
that didn't work.

- I deleted all extend.dats on the system and rebooted. That didn't work.

- I changed the registry value referred to below to 2 from 9, deleted the
extend.dats that resulted from testing, and rebooted. That didn't work.

- I reloaded Office 2003 Pro. That didn't work. I then removed and then
reloaded Office 2003 Pro. That didn't work, either. (I kept removing any
new extend.dats and rebooting in between the tests). Interestingly, neither
of these totally cleared out some of the saved values (specifically: I had
several .psts opened and the new loads kept expecting to see these referenced
.psts), so unless the shortcuts are saved in the main .pst, some of these
saved values are being saved elsewhere.

Anyway, none of this worked. HELP??? Any other thoughts? I'm pretty
desperate!!!


"Darryl A. J. Staflund" wrote:

Hi Don,

Symantec has posted a solution at the following URL:

http://service1.symantec.com/SUPPORT...pen&dtype=corp

Cheers,
Darryl Staflund


  #25  
Old June 30th 08, 03:35 PM posted to microsoft.public.outlook.program_addins
Nathan
external usenet poster
 
Posts: 30
Default Outlook 2007 and vpmsece2.dll

What worked for me was to go to Tools. Click on Trust Center and then
Add-Ins. Click on Manage (which was in the box below) and scroll in the
window to say Exchange Client Extensions. Click on Go and then Uncheck
SAVCORP90.

This did the trick for me. Hope this helps!

Nathan
  #26  
Old October 17th 08, 03:12 PM posted to microsoft.public.outlook.program_addins
Tiago Intela
external usenet poster
 
Posts: 1
Default Outlook 2007 Beta and vpmsece3.dll

I am also having same problem. I tried to follow some instructions that I got
from internet but did not work. I went to regedit and manually removed all
symantec related files. is it because I didn't restart my computer in order
for it to take effects or what?? Pls help.

Regards

Tiago

"Paul" wrote:

Good afternoon, Darryl!

I'm running Outlook 2003, and also getting this error message.

- I did Help -- Detect and Repair as recommended in the error message, and
that didn't work.

- I deleted all extend.dats on the system and rebooted. That didn't work.

- I changed the registry value referred to below to 2 from 9, deleted the
extend.dats that resulted from testing, and rebooted. That didn't work.

- I reloaded Office 2003 Pro. That didn't work. I then removed and then
reloaded Office 2003 Pro. That didn't work, either. (I kept removing any
new extend.dats and rebooting in between the tests). Interestingly, neither
of these totally cleared out some of the saved values (specifically: I had
several .psts opened and the new loads kept expecting to see these referenced
.psts), so unless the shortcuts are saved in the main .pst, some of these
saved values are being saved elsewhere.

Anyway, none of this worked. HELP??? Any other thoughts? I'm pretty
desperate!!!


"Darryl A. J. Staflund" wrote:

Hi Don,

Symantec has posted a solution at the following URL:

http://service1.symantec.com/SUPPORT...pen&dtype=corp

Cheers,
Darryl Staflund


  #27  
Old December 25th 08, 03:23 PM posted to microsoft.public.outlook.program_addins
MrHusy
external usenet poster
 
Posts: 1
Default Outlook 2007 Beta and vpmsece3.dll

Quote = "No, it does not show up in the Trust Center under Add-ins"

For those who may encounter this issue, It may not show up directly at
Add-ins screen. When you are at add-ins in Trust Center, click on the
drop-down box next to Manage below, choose "Exchange Client Extensions", then
click Go. You will see symantec there. Simply uncheck.

Regards
--
MrHusy
http://www.experts-exchange.com/M_3788926.html



"Duke" wrote:

After migrating from Symantec 10x to Endpoint Protection, I had the same
problem. I did what you suggested, and the problem was solved. Thanks so
much, David.


"David" wrote:

Hello all,
First, thanks to everyone who made suggestions and props to Paul for posting
the solution after figuring it out. You Rarely see that on tech forrums, many
suggestions are made and the postings just stop.. you can assume they fixed
it, but its very helpful to hear that yes.. This suggestion by ____ worked.

I had this issue after migrating from Symantec 10x to Symantec Endpoint
Protection. (Server 2003 32bit server running Outlook 2003) - Along with the
annoying error though, users couldn't open some word or excel files. They'd
get the error, "the operation failed. an object could not be found". This
add-in was causing that as well.

Symantec 10x left an add-in in Outlook which caused this same error. Going
to Tools -- options, clicking on the Other tab, then advanced options..
Under "Add-ins Manager" there was an entry for Symantec 10x. and one from SEP
which autoprotect was disabled on. Removing both of these add-in's eliminates
the error.

Again thanks everyone.
David
"Paul" wrote:

Good morning!

Well, after working on this problem for at least 12 hours, I devised a
solution, and wanted to share it so that others in the same boat do not have
to go through the frustration I did.

Based on what others posting in this thread mentioned about Add-Ins, I
decided to try to "give" Outlook 2003 the file it was looking for.
Therefore, I copied vpmsece4.dll from my Symantec AntiVirus directory, and I
pasted it into the directory of the user that uses Outlook for e-mail:

c:\Documents and Settings\user directory\Application Data\Microsoft\Add-Ins

I started up Outlook 2003 (I can't remember if I
rebooted...again...first...after 12 hours at this same problem, believe me I
lost count), and Outlook said that it had encountered a serious error. It
asked if I wanted to disable the Add-In, I said yes, and voila!

Hope this helps!


"Paul" wrote:

Good afternoon, Darryl!

I'm running Outlook 2003, and also getting this error message.

- I did Help -- Detect and Repair as recommended in the error message, and
that didn't work.

- I deleted all extend.dats on the system and rebooted. That didn't work.

- I changed the registry value referred to below to 2 from 9, deleted the
extend.dats that resulted from testing, and rebooted. That didn't work.

- I reloaded Office 2003 Pro. That didn't work. I then removed and then
reloaded Office 2003 Pro. That didn't work, either. (I kept removing any
new extend.dats and rebooting in between the tests). Interestingly, neither
of these totally cleared out some of the saved values (specifically: I had
several .psts opened and the new loads kept expecting to see these referenced
.psts), so unless the shortcuts are saved in the main .pst, some of these
saved values are being saved elsewhere.

Anyway, none of this worked. HELP??? Any other thoughts? I'm pretty
desperate!!!


"Darryl A. J. Staflund" wrote:

Hi Don,

Symantec has posted a solution at the following URL:

http://service1.symantec.com/SUPPORT...pen&dtype=corp

Cheers,
Darryl Staflund


  #28  
Old December 30th 08, 01:47 PM posted to microsoft.public.outlook.program_addins
Geni
external usenet poster
 
Posts: 2
Default Outlook 2007 Beta and vpmsece3.dll

it happen that u dont find the addin , the reg key or the .dat file

go: tool/trust center/ addins
there if u dont see the sav addin

go at manage: , down in the window, and select Exchange client selection,
then GO
there u can find the SAV addin.

that all



"Don Grant" wrote:

Thanks. I gave that a try and there is nothing showing up in the registry.
It looks like I should uninstall Symantec Antivirus and perhaps try a
reinstallation. Any other suggestions are welcome.


"Ken Slovak - [MVP - Outlook]" wrote in message
...
Open up regedit and go to HKCU\Software\Microsoft\Office\Outlook\Addins
and look for something there for Norton. Repeat for HKLM. Set LoadBehavior
to 2 if you find something.

Note that Norton is virus-like and often will re-enable itself despite
what you do. In that case uninstalling is the only option.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Don Grant" wrote in message
...
No, it does not show up in the Trust Center under Add-ins. I can find
it on the C: drive as noted and deleted but the same error recurs and it
puts in another file vpmsece4.dll. Since it is not in Add-Ins i don't
know how to disable it. Thanks for you input.





  #29  
Old February 26th 09, 06:11 AM posted to microsoft.public.outlook.program_addins
Prans
external usenet poster
 
Posts: 1
Default Outlook 2007 Beta and vpmsece3.dll

Hi David,

I faced this problem on 25th Feb 2009 and was searching the solution through
google. Was going through the posts and came across your posting. It worked
thanks.

Prans

"David" wrote:

Hello all,
First, thanks to everyone who made suggestions and props to Paul for posting
the solution after figuring it out. You Rarely see that on tech forrums, many
suggestions are made and the postings just stop.. you can assume they fixed
it, but its very helpful to hear that yes.. This suggestion by ____ worked.

I had this issue after migrating from Symantec 10x to Symantec Endpoint
Protection. (Server 2003 32bit server running Outlook 2003) - Along with the
annoying error though, users couldn't open some word or excel files. They'd
get the error, "the operation failed. an object could not be found". This
add-in was causing that as well.

Symantec 10x left an add-in in Outlook which caused this same error. Going
to Tools -- options, clicking on the Other tab, then advanced options..
Under "Add-ins Manager" there was an entry for Symantec 10x. and one from SEP
which autoprotect was disabled on. Removing both of these add-in's eliminates
the error.

Again thanks everyone.
David
"Paul" wrote:

Good morning!

Well, after working on this problem for at least 12 hours, I devised a
solution, and wanted to share it so that others in the same boat do not have
to go through the frustration I did.

Based on what others posting in this thread mentioned about Add-Ins, I
decided to try to "give" Outlook 2003 the file it was looking for.
Therefore, I copied vpmsece4.dll from my Symantec AntiVirus directory, and I
pasted it into the directory of the user that uses Outlook for e-mail:

c:\Documents and Settings\user directory\Application Data\Microsoft\Add-Ins

I started up Outlook 2003 (I can't remember if I
rebooted...again...first...after 12 hours at this same problem, believe me I
lost count), and Outlook said that it had encountered a serious error. It
asked if I wanted to disable the Add-In, I said yes, and voila!

Hope this helps!


"Paul" wrote:

Good afternoon, Darryl!

I'm running Outlook 2003, and also getting this error message.

- I did Help -- Detect and Repair as recommended in the error message, and
that didn't work.

- I deleted all extend.dats on the system and rebooted. That didn't work.

- I changed the registry value referred to below to 2 from 9, deleted the
extend.dats that resulted from testing, and rebooted. That didn't work.

- I reloaded Office 2003 Pro. That didn't work. I then removed and then
reloaded Office 2003 Pro. That didn't work, either. (I kept removing any
new extend.dats and rebooting in between the tests). Interestingly, neither
of these totally cleared out some of the saved values (specifically: I had
several .psts opened and the new loads kept expecting to see these referenced
.psts), so unless the shortcuts are saved in the main .pst, some of these
saved values are being saved elsewhere.

Anyway, none of this worked. HELP??? Any other thoughts? I'm pretty
desperate!!!


"Darryl A. J. Staflund" wrote:

Hi Don,

Symantec has posted a solution at the following URL:

http://service1.symantec.com/SUPPORT...pen&dtype=corp

Cheers,
Darryl Staflund


  #30  
Old June 11th 09, 05:31 PM posted to microsoft.public.outlook.program_addins
Karen L
external usenet poster
 
Posts: 1
Default Outlook 2007 Beta and vpmsece3.dll

More detailed --- You will find it in Tools Trust Center Add-Ins Select
"Exchange Client Extensions" from the drop down at the bottom of the page and
click GO.


"Patrick Schmid" wrote:

Does it show up in Tools, Trust Center, Add-Ins? If yes, disable it
there.
BTW, it wouldn't show up with this DLL, but prob. as Symantec AntiVirus
or Norton AntiVirus.

Patrick Schmid
--------------
http://pschmid.net

"Don Grant" wrote in message
:

Every time I open Outlook Beta 2007 I get the following error statement:
The Add-in "C:\Program Files\Symantec AntiVirus\umpsece3.dll" cannot be
loaded and has been disabled by Outlook. Please contact the Add-in
manufacturer for an update. If no update is available please uninstall the
Add-in.

It doesn't seem to be installed and only shows up in the refernce above.
Can anyone help me get rid of it?

Thanks.



 




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Missing MSVCR80.dll when starting Outlook 2007 Saj Kumar Outlook - Installation 6 August 14th 06 08:23 PM
Outlook 2007 Beta Mapi error msoc.dll Alphajoe Outlook - Installation 2 July 28th 06 06:31 AM
Outlook 2007 - OLMAPI32.dll Dana Outlook - Installation 0 July 13th 06 04:43 PM
Outlook 2007 beta dogcom Outlook - Calandaring 4 July 5th 06 10:14 AM
Outlook 2007 mspst32.dll crashing when using 'exchange cached mode greg Outlook - General Queries 0 June 14th 06 02:09 PM


All times are GMT +1. The time now is 06:17 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.Search Engine Friendly URLs by vBSEO 2.4.0
Copyright ©2004-2025 Outlook Banter.
The comments are property of their posters.