02-02-2012 02:23 PM
Hello sintzel,
Feel free to send me a Private Message with pictures and details. Thanks!
02-02-2012 04:25 PM - edited 02-02-2012 04:27 PM
I reported my problem here in November 2011. Today, we all still have it, and different people from Symantec/Norton just keep asking us to reinstall the NIS 2012; or if the repeat installations fail, for more information and details. To what end? Even if you can talk to all of us personally and gather enough (how "enough" might depend on your IQ) information, which is unlikely, I am sure you will find that we all have different configurations, applications, and operating procedures, but we all have the same complaint. And then what will you do? This dead-end process and thread can go on until 2013 or when Hell freezes over.
I don't know if you've tried this, but just use a system with either of our configurations and have 100+ entries in the firewall to try and reproduce the "bug." Your software engineers should be able to take it from there. bsintzel is correct in suggesting that you also give us a way to import/export the rules to be able to help fix the problem.
Your bosses (probably the ones taking the huge bonuses) should be thankful that paying customers are spending time to help your company fix a broken product that these customers can always replace with another company's. Of course, at this point, we all know that the positive reviews of NIS 2012 in the computer mags are all BS.
02-02-2012 04:28 PM
Just sign into this thred ...
Since yesterday I am in the same boat as all in here ...
My system:
- i7 CPU, 8GB mem, Windows Vista 64
Before 02/Feb/2012:
- Norton AntiVirus working OK.
02/Feb/2012:
- Norton monthly report suggest that I should update to Norton 2012.
- Downloaded NAV 19.5.0.145
- After update:
-> NAV do not start; Windows message indicating "Symantec Service Framework stopped working".
-> addopted all recommendations from Norton website:
1) Removed Norton installation (finally with NRT);
2) reboot as requested;
3) After reboot it continued installation until displaying the same Windows message
4) After spinning for a wehile NAV indicated it found an error: 8504, 102 and I should restart the computer
5) Windows re-started
-> Cycle (1) to (5) where repeated several times with the same results
Firewall has standard Windows settings.
Does Symantec has a solution for it?
It seems that it is affecting a large number of users.
Thanks,
02-02-2012 05:02 PM
Hello jmason,
I'm taking this issue very seriously and am working in conjunction with the product team and with everyone in this thread to narrow down the issue and at least get one reproducible case. So far, the product team has tried to reproduce this issue but has not been able to. The reasons why we ask these questions is so we can narrow down the cause, find the bug, and correct it.
Sorry for the trouble and how this issue has been around for a few months. We're trying hard to correct it and am just having difficulty getting this error to occur on our side.
Sorry again for the inconvenience.
02-02-2012 05:28 PM
Years ago i have also random Framework Crashes with NIS , my Solution was new stabil Hardware Memory in my PC (8GB Mushkin) , after this Change these Crashes are gone.
i think it was 2009 or 2008 , i write this into this Forum as a Solution but i think no one remembers up to today ;)
02-02-2012 05:32 PM - edited 02-02-2012 05:33 PM
Tim_Lopez:
Yes, I imagine the product team should be doing that, and I appreciate it.
Presently, I can think of this. Symantec will have to produce updates, fixes, or whatever you call them. I dont know about the others, but with my past experiences with NIS 2012, you cannot convince me to give the updates/fixes a try unless I have a way to import/export the rules as bsintzel suggested. If I have free time, I am willing to reinstall the software in trying to fix the problem once and for all. I just don't want to manually input the firewall entries again in the processes.
02-02-2012 05:42 PM
HI jmason,
The suggestion to allow firewall rules/settings to be exported to a file comes up every now and then when we do our Public Betas. I would get the feedback in when we have a beta going on to make your voice heard to the development team.
I personally would like to see something added that would make it easier for advanced users to import/export settings. There are some explainations that I've heard from the team on why it would be really difficult to implement such a feature. However, it's up to the product team to figure it out. ![]()
I'm hoping we'll see such functionality in the future, and voicing your concern for such a feature can only help make the decision take place sooner.
02-02-2012 05:45 PM
WOW....And all this time, I thought I was the only person who was annoyed at this re-occurring issue.
There MUST be a way to (at a minimum) have a tool to import/export rules. I (and I think most others) can get by if just this one capability/tool was made available to us.
It takes a person roughly ten minutes to re-install NIS BUT over an hour+ to re-enter the rules-- and only if you can remember what rules you had. The 'very least' Norton can do is give us a tool to help us get by until they can figure this out. I'm a former developer and I know what Tim is saying. It's not easy to figure this out given the virtually unlimited number of configuration permutations out there...but that has nothing to do with taking the time to give us a rule import/export tool. It would take Norton a lot less time (and money) to just give us this simple capability. PLEASE...someone at Norton put some effort in this direction. You'll make a lot of (paying) customers a LOT happier.
02-02-2012 07:15 PM
All,
Any of you having this issue and would like to work closely with us to help Identify this issue, please send me a Private Message. I'll need someone who will be willing to gather some information, and possibly do a remote session so someone from Symantec can investigate.
02-03-2012 12:58 AM
Bsintzel,
Sorry we share the same problems. and Thnak you for the re-install info, save me the troubles to try that, it is a paintful step.
Will wait for another week or so for Symantec to fix the problem, if not, I will temporarily switch to Windows FW + MSE, my Windows firewall is alway setup and ready although it's not activated.
