08-24-2009 08:09 AM
YAY JACGAT58! YOU ARE DEE BEST! THANKS!
NORTON/TONY WEISS: Feel free to copy/paste the following Note into the hot fix instructions at http://www.symantec.com/norton/support/kb/web_view
1. Download the fix tool. Save the file to the Windows desktop.
Note: if the message "Internet Explorer cannot display the webpage" is received, reboot the computer. Then, immediately after startup - before getting the framework error, turn off the settings for (a) "Disable Smart Firewall" and (b) "Disable Anti-Virus Auto-Protect" by right-clicking on the services tray Norton Internet Security icon. Select both settings with a duration of "until system restart." Download the fix tool.
Thanks everyone for the help in getting this issue resolved! Woo-who!
08-24-2009 09:09 AM
I just had a new problem. I don't know if it's related to the hotfix, so I'll post it here in case it is.
I ran the hot fix Friday evening. I did not have any problems after that until this morning.
I booted up this morning, and everything was still ok, but upon returning to my computer an hour later, I found the One Click Support window open. It didn't say anything, but there was some kind of animated pattern in a rectangel in motion. After a while I closed the window. I'm sorry I can't remember exactly what happened next, but I think I clicked on the Norton icon in the systray, and the Norton screen showed the "At Risk" wording. I clicked Fix Now, and the Fix Now window opened with 4 items listed. It ran, but I got a red "X" over the first 2 items (Not fixed). I rebooted, and things look normal again.
08-24-2009 10:07 AM
Thanks ier80899 for your post #631,
You are really like a lot of us out here that want to help others.
I was trying to help users of NIS2009 and Symantec with this error since it really is/was a nasty little thing that appeared at first to me to be a virus that infected NIS2009. I used msconfig to try to isolate the problem by disabling various startup items with no luck. I then searched for problems with the 16.7 update and found this thread.
Since there are so many of us that have commented about the framework error with 16.7 in such a short time after the update, I am wondering just how Symantec tested this before implementation.
Granted, my Notebook with XP Home does not have this problem yet so I have not applied the hotfix to it although the hotfix is on its hard drive. Since NIS2009 runs on Vista and XP, I would think that 16.7 should have been tested on all versions of the supported platforms for a length of time to insure error free operation.
It seems that some people have noted the error within one day of the update to 16.7.
So, my question is how long was the update tested and on what?
Maybe Symantec will reward those of us that have contributed to a resolve of the “framework” error??? Well, maybe not.
08-24-2009 10:21 AM
Turns out I didn't need the hot fix, but thanks for posting it!
I went to the updates page, DLd the latest. Updated until no more were needed. Re booted. And 184.108.40.206 has been running fine for 1.5 days.
Thanks for getting after this so promptly.
08-24-2009 10:22 AM
Yes... this was a frustrating fix.
I also did my normal triaging, google research and forum reviews. Then when the download wasn't working, I read and read and read some more and noticed Norton indicated taking the hot patch down off the server since it wasn't quite fixed yet. Evidently, that was awhile back and they consequently got the fix - where my download issue was as you indicated with disabling the settings. But I didn't know that until you mentioned it... it would be nice if Norton could've gotten the info updated on their site.
I tried getting into the chat room to get with them (at various times), and even at 3 am I was the 7th in queue. So my bad... didn't want to wait around.
So I looked to see if the KB20090821103237EN.exe was available at another site... and then (um) I thought why would I download an .exe from another site? Like that's a safe thing to do, right? Then I questioned if I couldn't download the .exe from Norton because it was an .exe... but since I thought NIS wasn't running, then that couldn't be it.
~oy~vay~ instead of spinning my head revisiting this issue, let me again say THANKS JACK! Especially since you had your fix and could've easily dropped off this thread. But you're sticking it out to help the rest of us. Again, YOU DEE BEST!
08-24-2009 10:52 AM
Since this thread is becoming rather large and difficult to navigate, I have now locked it from further posting.
If you have downloaded the NIS 220.127.116.11 update and are experiencing frequent Symantec Service Framework errors or ccsvchst.exe errors, a hotfix has been released to address this issue:
Follow the directions on that document to apply the hotfix to your system. Please do not install the hotfix if you are not running the NIS 18.104.22.168 update, and are not experiencing the Framework errors. This hotfix is specific to that situation.
If you are still experiencing issues with the NIS 22.214.171.124 update, please open a new thread. If you are experiencing issues as a result of installing the hotfix, please open a new thread and let us know the issues. Be sure to include the information about the 126.96.36.199 update and the hotfix. Thanks!