ligerdynomite
5/1/2008 10:26:00 PM
Thanks for your response.
So far I have found that there is a component on Symantec Endpoint 11.0
called "application and device control" that seems to be causing the issue.
Using the custom install option, I made sure that this component was marked
to "not" install. It is a work around for now, hopefully Symantec will fix
this.
"PvdG42" wrote:
> "ligerdynomite" <dasboots07@nospam.nospam> wrote in message
> news:B88039A6-7F67-4175-8CF9-571E0E77C3F1@microsoft.com...
> > Hello,
> >
> > We have a few laptops, different Dell models using Windows XP SP2, that
> > are having a problem with .Net 2.0 and Symantec Endpoint. Whenever a
> > program
> > that uses .NetFramework attempts to launch we receive errors, different
> > errors depending on the program. An example is when I try to launch
> > Virtual
> > Infrastructure Client 2.0 (VMware client), I receive the error
> > "VPXClient.exe
> > - Fatal error".
> >
> > CLR error: 8007000b.
> > The program will now terminate.
> >
> > I know that it has something to do with the permissions between Symantec
> > Endpoint and .NetFramework because I can run the program using "run as"
> > and
> > using the domain administrators credentials. Also, If I uninstall Endpoint
> > all the programs that were affected launch without any issue.
> >
> > I have already put a ticket in with Symantec and hope that they are able
> > to
> > resolve this issue. I just want to stay ahead of the game in case they say
> > that it is not there issue. Just thought that maybe someone in here might
> > have a clue.
> >
> > Please be gentle as I am not a programmer.
> >
> >
> > Appreciate any help,
> > Matt
>
>
> I'm going to give you my honest opinion, bases on several negative
> experiences with Symantec products over the years.
> Get the Symantec stuff off the PC's and prevent existing and future
> potential problems.
> Symantec *will* (I predict) close your ticket as "not our problem". At
> minimum, you will have to persist and escalate the issue by demanding to be
> put in contact with supervisors and managers to get any real action at all.
> If they finally do acknowledge the problem (which will not happen unless
> *many* customers with the same issue get up in arms) resolution will be
> slooooow.
> I've been down this road with Symantec more than once. Result: I will not
> allow a Symantec product on any of the 300 machines in the college
> department I chair.
>
>