.NET framework crashes when upgraded client to SEP RU5

[Ramji Iyyer]

Kindly find the symptoms & responce before & after upgradation of symantec client. 

1). PC's are working fine with 4202 cleint with installed MS .net 2.0, 3.0 & 3.5. All MS .net based applications are responding perfectly.

2). Once client is upgradaed to 5002.333 version of Symantec & restarted, .Net service stop responding. All .net base applications are stop & giving errors which shows to you.

Remidy Process we had done onsite:

1) Upgrade the client SEP version to 5002.333
2) All .net version need to uninstall.
3) Once again reinstall all .net version.

Result :

1) After reinstallation of MS .net, application runing under .net v2 start working fine.
2) Still .net V3 is not responding & applications based on v3 are not runing.

Does any one has faced this issue ?

I had opened a case with Symantec Support & awaiting for reply.

Regards...
Ramji Iyyer

[Migration User]

We've a problem with some Vista's. We've a case going on as well.. I'll let you know if anything new comes up.

[Ramji Iyyer]

We are facing this issues with some developer PC's & our web server's

OS details are as follows

Winxp with SP3
Win2k3 with SP2 & with latest patches
Windows Vista
Windows 2000 Server
Windows 2000 Advanced Server

We have stopped the rollout !!!

Regards...
Ramji Iyyer

[Ramji Iyyer]

BIG BUG in SEP RU5

Regards...
Ramji Iyyer

[Migration User]

Do you think you could post or pm your case number? I was hoping to check up on this issue.

Grant-

[Ramji Iyyer]

@Grant

Find the case ID 281-820-087

Regards...
Ramji Iyyer

[reza akhlaghy]

Hi

We encounter same problem on our developers computers and find out that problem relates to application & device control component (again!) and if you remove this component from installation everything will be fine.

[Ramji Iyyer]

@reza

Thanks...

We have tested the same with each & every component & came to conclusion that Application & device control is having the issue & that is the BUG of SEP

Once again thanks for ur comment.

Any how i want the hotfix for this issue from symantec.

Without Application & device control i will not able to monitor USB & other applications.

Regards...
Ramji Iyyer



 

[Migration User]

Hi Ramji,

It looks like, when you install a managed client, your software does not work. However, installing an unmanaged client seems to work fine. Can you try one thing, install a managed client. Disable the service called Symantec Management Client. Then reboot the computer.

Now, try to use the software. Let us know if this works.

Aniket

[Migration User]

Also, please attach a debugger to your software's service when you install a managed SEP client, so we can analyze the crash debug logs if a crash happens.

You can refer to the following link:

https://www-secure.symantec.com/connect/videos/advanced-troubleshooting-debugdiag

Aniket

[Migration User]

I suspect it has to do with a paticular set of SEP policies, as we've not seen any issues here with .net.

[Migration User]

try withdrawing the appliaction and device control policy. it resolved my issue for now. support is investigating it.

[Migration User]

I agree with Bekir. I saw an instance too where Withdrawing application & device control policy did resolve this issue.

Aniket

[Ramji Iyyer]

I had created a test group & removed all the policies except antivirus-antispyware & Liveupdate policy.

Then moved the PC's to that group & checked , same issue .net crashed.

Installed one fresh replica of the .net developper PC & given to Symantec technical support engg. he tried various times.
result was the same. .net crashed.

Regards...
Ramji Iyyer

[Migration User]

2 more options to try could be:

1. to withdraw the NTP policy as well for the same group (if resolves, you may try adding back the app. & dev. policy)
2. to uninstall NTP completely from the necessary clients.

until the issue is resolved :(

regards,

[Ramji Iyyer]

A small update !!!!


Shown demo to backline support team & they are working on it.


Regards...
Ramji Iyyer

[Migration User]

I opened new case about this issue.
After working with the tech for a little bit, we figured out it is an issue with the "Application & Device Control" in SEP RU5.

Systems I was having issues with:
Windows XP Pro SP3
Windows Server 2003 Standard R2 SP2

I was able to install the following components and .net framework is working:
Antivirus and Antispyware, Anvirus Email Protection - Pop/SMTP, Network Threat Protection, Proactive Threat - Trusacan

Right now wait for resolution to this issue, since I would like App & Dev Control.

[reza akhlaghy]

around two month passed without a solution?? Where are you symantec developers?

still having problem with application and device control component and .net applications. We need solution.

[Migration User]

After all they already got paid for the product....

[Migration User]

hello guys,

In my case, they've developed a sysplant.sys and it worked. Blue screens are gone for now.

This should probably be applied on MR6. Does anyone know when is it going to be out?

[Migration User]

Just ran into this issue with our dev team.  Glad to have found this post.  I created a group that had the same policies as before, but removed the application & Device module, rebooted the PCs and the aspnet / IIS errors were gone.

[JustinAndersen]

More info on this issue can be found in a different thread. Jon Dorset did a good job of summing up the issue.

www-secure.symantec.com/connect/forums/sep-ru5-0xc0000005-error#comment-3523601

[_Steve]

Further to Dan Carrera's comments; I too have an issue whereby some of my developers can not use their applications designed with .net framework and IIS. Please excuse my lack of terminology as I'm not a developer.

If I follow Dan's advice and create a policy without the application and device control does this have a detrimental effect on SEP protecting my developers systems?

[postechgeek]

@ Bekir,

I would be interested in this new sysplant.sys driver. We have had some issues with the BSODS here. We are currently running RU5 here. Did Symantec support give you the file?

Mike

[Migration User]

yes it would , But if that is the case you can revert back to MR4MP2.

[reza akhlaghy]

I think after 6 month of release of RU5 we requrie a fix or at least a timeline....

[Migration User]

New MR should be out this month. That's what says in the roadmap, but it may change...

A lot of changes are coming though, we'll need to do thorough testing...

[Migration User]

Yes it expected this month. and it should take care of the application crashing issue...... Hopefully :))

[Migration User]

  Please subscribe yourself to our email bulletin service to stay abreast with the latest product updates. The link for this is as follows:
http://www.symantec.com/business/support/news_bulletins/index.jsp

[Rafeeq]

There is a document too 

After migrating a Symantec Endpoint Protection (SEP) 11 client to Release Update (RU) 5 or installing RU5, .NET Framework applications fail to work properly

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2010012709305848

[Migration User]

Does RU6 correct this issue?

[Migration User]

The issue has been resolved in RU6. So please dowanlod  RU6 and upgrade to it.
Please go to the following  site :https://fileconnect.symantec.com/
 
Enter the Serial No of the product and download the product.
 
Title: 'Installing Symantec Endpoint Protection 11.0.6 (RU6) for the first time'
Document ID: 2010041310191048
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2010041310191048?Open&seg=ent
Title: 'Migrating to Symantec Endpoint Protection 11.0 RU6'
Document ID: 2010041310404248
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2010041310404248?Open&seg=ent

[Ramji Iyyer]

Got Solution in  RU6. But afraid of RU6 for any new issues.


Regards...
Ramji Iyyer