Norton how much longer will your customers that are experiencing Error 8921,301 or 8921,246 have to wait before you come up with valid solution for this problem?
___________________________________________________________________________________________________
cgoldman wrote:
Yes, I have exactly this problem. Sorry but I was working on 16.5 before it was released and advised Symantec of exactly this problem.
cgoldman wrote:
Dear Mijac
1. OK I had a special release of 16.5 wich forced and performed a uninstall of 16.2. LU produced the error.
_____________________________________________________________________________________________________
Norton you where made aware of this serious bug the 16.5 update created prior to it's release, yet you released it to the general public any way. This is not only ludicrous, it is completely unacceptable and falls nothing short of reckless conduct on your part.
OscarL wrote:rohit1gupta,
The LU engine was rewritten for the 2009 and up series of products, so it is very different. This was done for greater integration and higher performance.
In the meantime, you can still get updates by downloading the Intelligent Updater packages.
Cheers,
Oscar
OscarL wrote:
Hello all, We have been able to reproduce this issue locally.
The LiveUpdate engine was updated with the release of NAV/NIS 16.5 and Norton 360 v3. The new version of LiveUpdate engine will check if it receives HTTP 1.1 server responses, and explicitly reject HTTP 1.0 server responses. This was done to ensure that you are receiving updates from a valid LiveUpdate server. If you are using a proxy server, it could be configured to return HTTP 1.0 responses, and thus LiveUpdate will see this as an improperly configured connection.
A workaround for this issue is to disable the proxy server, or to reconfigure it. Most proxy servers can be configured to return HTTP 1.0 or 1.1 responses. We understand that this may not be possible for some users that are experiencing this issue. We are still working on a good solution for this issue. Thanks for your patience.
The temporary workarounds suggested to use on this forum for the problematic Error 8921,301 or 8921,246 are not acceptable by any means....
Do you expect us to waist more of our time and resources in order too have our faulty program function properly?
As it stands for those of us that have this Error, you remain to leave us high and dry with a faulty program.
Will Norton offer their customers extended time on their subscriptions in lieu of having to go through the grief that your mistake has caused for some of us or not?
Your customers are paying you good money, in return for the money that we gave you we expect that you provide us with fully functional program with out any further delay!!