|
this worked, thanks david.
"David" wrote:
"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:
>
> 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:
> >
> >
> > 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:
> > >
> > >
> > > 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/ent-security.nsf/pfdocs/2004060116454248?Open&dtype=corp
> > > >
> > > > Cheers,
> > > > Darryl Staflund
> > > >
> > > >
> > > >
> > > > Symantec has posted a solution at the following URL:
> > > >
> > > > http://service1.symantec.com/SUPPORT/ent-security.nsf/pfdocs/2004060116454248?Open&dtype=corp
> > > >
> > > > Cheers,
> > > > Darryl Staflund
> > > >
> > > >
| 30 Sep 2007 | Re: Outlook 2007 Beta and vpmsece3.dll | .Paul |
| 01 Oct 2007 |  Re: Outlook 2007 Beta and vpmsece3.dll | .Paul |
| 15 Apr |   Re: Outlook 2007 Beta and vpmsece3.dll | .David |
| 15 May |  Re: Outlook 2007 Beta and vpmsece3.dll | .Stephanie |
| 25 Jun | Re: Outlook 2007 Beta and vpmsece3.dll | .Duke |
| 30 Jun | Re: Outlook 2007 and vpmsece2.dll | .Nathan |
| 17 Oct | Re: Outlook 2007 Beta and vpmsece3.dll | .Tiago Intela |
All times are in (US) Eastern Daylight Time (GMT -4:00)