NIS 2009: Symantec Service Framework Stopped Working and was Closed

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

sOulbAit,

 

I've sent you a Private Message with instructions on how to gather a little more info about this issue - look for the  in the upper-right corner of the page.

 

Thanks,

Mike

Message Edited by MikeO on 09-29-2008 09:21 AM
2 Likes

I  have the same problem - but I am running XP SP3

 

After several unsuccessful trials with support - just removing and reinstalling Nis 2009 - I went back to NIs 2008

 

No problems

 

Is really dissapointing - both the performance of NIS 2009 and the level of support

Hi,

 

I have exactly the same problem as sOulbAit mention. The only difference is that i run a 32bit version of Windows Vista Ultimate.

It occured today, no issues before. The  "Symantec Service Framework Stopped Working" happens as soon as i start poping my e-mails via Outlook 2007.

 

Symantec staff, please PM me or send a public respons in this thread.

 

Many thanks in advance!

 

 

 

sOulbAit,

 

I appreciate your patience and willingness to work with us.  The information you provided was extremely helpful.  The issue you've encountered has been fixed for the next maintenance release of NIS/NAV 2009.  At this time, however, I cannot provide any specific dates for the release.

 

Regards,

Mike

 

 

1 Like

shutterbug, danariel,

 

In order to isolate the exact cause of the problem you have encountered, can you please perform the following steps.  Note this applies to Windows Vista only.

 

1) Open Control Panel, click on "System and Maintenance", then on "Problem Reports and Solutions"

2) Find any instances of "Symantec Service Framework" in the list

3) Double click an entry

3) At the bottom left corner, there is a link that says "Copy to Clipboard" - click this link.

4) Send me a "Private Message", and paste the details into the body of the message.

 

Thanks,

Mike

Hi MikeO:

 

Thank you very much. I will reinstall NIS2008 until the next release is issued. Will I know (by an email or message) when it is going to be release or should I check back here in the forums? Or on the download site and notice a change in the downloadable .exe file name?

 

Thanks again. Yall are great. :)

 

sOulbAit

Thanks MikeO

 

However I am running XP Sp3

 

Also I have reverted back to NIS 2008 - works perfectly

 

I would like to know when this fix will be released so I can reinstall Nis 2009

 

Dan

When the update has been released for Norton Internet Security 2009, we will be posting a thread to this board with the update information. As MikeO has stated, we cannot provide specific dates of product updates. We are working to get this released as soon as possible, and we are testing the update to ensure that it resolves issues as well as not causing others. Thank you for your patience as we continue to test this update.

I'm in the same boat as Danariel - running XP w/ SP3. 

 

Other than that - same exact problem as original poster.

 

Mike0 or others - anything you're looking for on our end or do you have all the info you need at this point?

 

Thanks,

 

- Joe

danariel, jcmcmann,

 

Collecting this information on XP is not as straight forward.  It has to be done when Windows reports a problem occurred.  I've posted a sample screenshot of the Error dialog.  The information We're most interested in is the AppName, Module Name, Module Version, and Module Offset.  You can find this information by clicking on the link next to "To see what data this error report contains...".

 

After you collect this information, you can post it.  Be sure to click "Send Error Report", which will submit further details of the issue if necessary.  We can generally correlate the information you post (like module offset) with the details of the report.

 

 

 

Additional information that is useful is to click on "To view technical information about the error report...", and then the first field is "Exception Code", i.e. c0000005.  This further helps us track down the issue.

 

There are several other steps you can take to submit the information directly to us, but they are a bit more complicated, so I'll hold off on those unless absolutely necessary.

 

Regards,

Mike


shutterbug wrote:

Hi,

 

I have exactly the same problem as sOulbAit mention. The only difference is that i run a 32bit version of Windows Vista Ultimate.

It occured today, no issues before. The  "Symantec Service Framework Stopped Working" happens as soon as i start poping my e-mails via Outlook 2007.

 

Symantec staff, please PM me or send a public respons in this thread.

 

Many thanks in advance!

 

 

 


shutterbug,

 

Thanks for providing the additional information to us.  This issue has been fixed in the next NIS/NAV 2009 maintenance release.

 

Regards,

Mike

 

Thanks for providing the additional information to us.  This issue has been fixed in the next NIS/NAV 2009 maintenance release.

 

Regards,

Mike


Has been or will be?

 

Mike, are you saying that a maintenance release is now ready?  If so, would you share with us the following info:

1.  What is a "maintenance release"?

2.  How is it disseminated?

3.  What (major) fixes can we expect in this one?

4.  When will we get it?

 

 

mijcar,

 

This is why I'm an engineer and not an english major... english can be much more ambiguous than a programming language and it appears I've still got some bugs with my english :smileyhappy: 

 

To clarify:

"Has been" meaning the team was already aware of this specific issue, and have fixed it.  The info shutterbug provided allowed us to correlate the reported problem with a known issue. The title of this thread is very general, so I'm trying to make sure anyone who reports an issue gets the issue addressed.  Each issue could be different, or they could all be the same.  With out individual details from each report, I cannot say "It will be fixed, it has been fixed, it won't be fixed".

 

For the rest of your questions, Tony has already answered them (to the extent they can be answered) here.

Regards,

Mike

MikeO, hi.

 

I wasn't trying to be pushy about this.  I was actually just seeking clarification.

 

I know there are different levels of fixes, but I don't know how they work with Symantec.

 

For example, some fixes are patches delivered by a standard behind the scenes update practice (for example, Windows Update in its automatic mode or Live Update in its automatic mode).

 

And some fixes are almost new builds that actually require customer action (for example, much of Adobe Reader products).

 

And some fixes are not just fixes, but actual new builds that require full installation of a product (like Microsoft's Service Packs).

 

And some fixes are actually new generations of software (NIS 2009 over NIS 2008).

 

Each of the above fixes have different strategies of notification, installation, and customer expectation associated with it.  That's the kind of thing I was asking about.  And I can understand it if you say, well, yes, Mij, I got what you're saying, but even though we know the problem and even how to repair it, we haven't yet decided or worked out the means of getting it to the consumer.  I was just asking if you DID know the answer.  :-)

Hi

 

 

I too am experiencing issues with NIS 2009 and regularly encounter the error "symantec Service Framework has stopped working and was closed".  However, my problems do not seem to follow those of the previous thread entries i.e. when my system is idle and following a norton insight scan. 

 

Typically I encounter a problem soon after I have received a pulse update or I conduct a manual live update.  I have tried re-installing NIS 2009 to see if this makes any difference, but to no avail.

 

I'm hoping that the maintenance fix is able to rectify what problems I'm having but in the meantime would like to know what to do next (?)

 

I've checked 'problem reports and solutions' on control panel/system and maintenance and it seems that each time there is an error message it is caused by the same fault (ccSvcHst.exe/ccL80U.dll)

 

I'm running Windows Vista Home Premium SP1.

 

Thanks for your time

MisterSim76,

 

In order to isolate the exact cause of the problem you have encountered, can you please perform the following steps.  Note this applies to Windows Vista only.

 

1) Open Control Panel, click on "System and Maintenance", then on "Problem Reports and Solutions"

2) Find any instances of "Symantec Service Framework" in the list

3) Double click an entry

3) At the bottom left corner, there is a link that says "Copy to Clipboard" - click this link.

4) Send me a "Private Message", and paste the details into the body of the message.

 

Thanks,

Mike

 

Hi,

 

I too am receiving this problem.  I have recently reformated my drive and done a clean install of NIS2009 and am still regularly getting these errors. After the second or third error, NIS closes down completely and I need to restart my computer to get it back again.

 

 I am desperately awaiting a solution!

 

Thank,

Neil

Neil,

 

Which version of windows are you using?

 

Thanks,

Mike

Hi,

 

I am using Vista Home Premium SP1 32bit and I only get the error when I am not at the computer - it is on screen when I return to the PC.

 

Neil

Message Edited by nrestell on 10-08-2008 10:13 AM