Reply
Contributor
mfc1456
Posts: 25
Registered: ‎01-25-2009
Accepted Solution

Symantec Service Framework errors with N360 3.5.2.10

[ Edited ]

Hi

 

Others appear to have similar problems. The 3.5.2.10 update was loaded yesterday afternoon and did not seem to cause any problems. Again I used the computer this morning: nothing extraordinary; all functioned correctly. However, on starting up  my computer this afternoon (6 hours later) I am repeatedly encountering the following error:

 

"Symantec Service Framework has encountered a problem and needs to close"

 

Details as follows:

 

Error signature

 

"szAppName : ccSvcHst.exe szAppVer : 108.1.1.10 szModName : msvcr80.dll

szModVer : 8.0.50727.3053 offset : 00014500. My computer is running Windows XP Professional SP3; Only Web browser installed is IE8

 

Have rebooted several times; problem still persists.

 

I would appreciate some feed back.

 

Thank You

 

Michael

 

<<Edit: Subject edited for clarity>>

Message Edited by TomV on 08-20-2009 01:10 AM
Visitor
Silke
Posts: 6
Registered: ‎08-20-2009

Norton 360 Framework crashing & now completely disabled

I've had the framework crashing on Vista Ultimate for a few days.

This morning I logged in and N360 is disabled completely.

OneClick Support hangs itself up solid, so I'm not sure what the problem is.

Nothing changed, except that Windows 7 Compatibility update I'm guessing.

 

I've got a 2 year subscription for 3 pc's and now this...

 

So far Vista Home hasn't crashed yet, but I don't use the laptop much, it still might.

Keylogger Crusher
reactivate
Posts: 387
Registered: ‎05-24-2009

Re: Symantec Service Framework errors with N360 3.5.2.10


mfc1456 wrote:

Hi

 

Others appear to have similar problems. The 3.5.2.10 update was loaded yesterday afternoon and did not seem to cause any problems. Again I used the computer this morning: nothing extraordinary; all functioned correctly. However, on starting up  my computer this afternoon (6 hours later) I am repeatedly encountering the following error:

 

"Symantec Service Framework has encountered a problem and needs to close"

 

Details as follows:

 

Error signature

 

"szAppName : ccSvcHst.exe szAppVer : 108.1.1.10 szModName : msvcr80.dll

szModVer : 8.0.50727.3053 offset : 00014500. My computer is running Windows XP Professional SP3; Only Web browser installed is IE8

 

Have rebooted several times; problem still persists.

 

I would appreciate some feed back.

 

Thank You

 

Michael

 

<<Edit: Subject edited for clarity>>

Message Edited by TomV on 08-20-2009 01:10 AM

  Nightmare on Norton street.

Visitor
Silke
Posts: 6
Registered: ‎08-20-2009

Re: Symantec Service Framework errors with N360 3.5.2.10

What I need to know is how do I roll it back?

I cannot update, because it has disabled all of Norton, and it won't let me reenable it.

Luckily I have a router with a good firewall and don't have to rely on Norton 360 to do it, but this is not acceptable, as now every virus out there can get on my system if I'm not careful.

Just moving the posts isn't helping, because I wouldn't look for Service Framwork Errors, I looked for something that disabled Norton and assumed no one else is having problems because no one reported this.

I find the lack of response rather disconcerting.

We need a fix or a rollback of this, fast.

delphinium
Posts: 9,680
Kudos: 2,856
Solutions: 283
Registered: ‎11-21-2008

Re: Symantec Service Framework errors with N360 3.5.2.10

Silke and Reactivate:

 

Please look for PM (personal message) orange envelope top of the page on the right.

Under certain circumstances profanity provides relief denied even to prayer.
Mark Twain
Regular Visitor
NAO
Posts: 3
Registered: ‎08-20-2009

Re: Symantec Service Framework errors with N360 3.5.2.10

[ Edited ]

I'm getting the same error, and Norton keeps disappearing from my dashboard. Oddly, when I open my control panel security center it says that the 360 Firewall is working even though it has ostensibly shut down. Also, I am on a wireless network of 2 computers, both of which use 360. The main computer is having no trouble at all, while I at the back end get these service framework errors constantly. I hope this is resolved soon because I am a longtime user and fan of Norton software. I don't feel safe right now with my firewall and anti-virus software malfunctioning as it is :-(

 

Edit: further info: Safe Search has disappeared from my browser but  Norton Site Safety is still on. I hope some of this information helps the troubleshooters track down and eliminate this problem.

Message Edited by NAO on 08-20-2009 04:46 PM
Message Edited by NAO on 08-20-2009 04:46 PM
Newbie
Bovah
Posts: 2
Registered: ‎05-09-2009

Re: Symantec Service Framework errors with N360 3.5.2.10

I am also getting the exact same symantec service framework errors.  I get multiple pop up errors about it, and they do nothing when i click ok. But then eventually the norton icon will remove itself from my windows task bar and I can only re-open norton if i restart my pc. Im using windows xp sp3.
Regular Contributor
fuss7749
Posts: 109
Registered: ‎12-01-2008

Re: Symantec Service Framework errors with N360 3.5.2.10

Hi guys,I had the same problem so I contacted smart chat and they fixed the problem for me.Seems the files that Norton downloaded to us were corrupted.Try uninstalling your norton and then reinstalling it.It worked for me.
Newbie
sanjiv_trivedi
Posts: 2
Registered: ‎08-20-2009

Re: Symantec Service Framework errors with N360 3.5.2.10

This error started for me too a couple of days back

 

"szAppName : ccSvcHst.exe     szAppVer : 108.1.1.10     szModName : msvcr80.dll"

 

My Norton 360 has been disabled and my computer now stands unprotected. I downloaded latest update but no help! :(

 

Any help ASAP will be appreciated!!!

 

Contributor
mfc1456
Posts: 25
Registered: ‎01-25-2009

Re: Symantec Service Framework errors with N360 3.5.2.10

I contacted Norton Chat. Norton program was removed and reinstalled. All was fine. Was running version 3.0.0.135 without any problems. I notice that 3.5.2.10 has now again been installed. I shall await the outcome tomorrow. In the first instance, it took around 24 hours before the Symantec Service Framework errors surfaced.

 

Michael