12-19-2011 10:43 PM
Hi Norton users,
The Norton AntiVirus 12.1 and Norton Internet Security 5.1 updater has been posted. Also posted is Symantec Vulnerability Protection 3.7 and Norton Shared Components 2.1 which updates Norton Licensing and Symantec Uninstaller. This release also serves as our Firefox 9 compatible update.
LiveUpdate will download these updates automatically so there's no action that needs to be taken. However if you the updates
now, you may run LiveUpdate manually using the Norton QuickMenu's LiveUpdate menu options.
This update is mainly a maintenance release that fixes several issues, some of which were reported or discussed here on the forums, as well as other issues reported via other support channels. Not all issues were fixed in this update; some issues we have yet to reproduce internally and others just simply didn't make the cut.
This is the first major update to Norton AntiVirus 12 and Norton Internet Security 5, but it will definitely not be the last. We plan on releasing a Firefox 10 compatibiliy update, and another mainteance release, early next year. We also plan on releasing some new products early next year, as well as the previously announced Norton One.
Enjoy!
12-20-2011 10:00 AM
Ryan,
I cannot seem to find any documentation relating to this update. Is it possible to post the release notes for 12.1 or a link to the notes? Thanks.
12-20-2011 11:26 AM
How am I suppose to get this update if I can not download updates after installing NIS 5?
12-21-2011 07:07 PM
12-22-2011 03:52 PM
Regarding what is addressed by these patches, here are the highlights:
Firefox 9 support for Norton Identity
Fixes for Deepsight community reporting, install dashboard, and error reporting
Enabled "Buy a Key" functionality
Fixed Trialware purchase problem
NAV scan engine does better reporting of archive scan totals
Fixed Location Awareness alert repeatedly appearing when connecting to VPN
12-23-2011 07:29 PM - edited 12-23-2011 07:30 PM
I'm not sure what specific error reporting fixes were made, Lee, but error reporting still isn't working on my iMac after having updated to the most recent NIS 5 software and restarting.
OS X Lion 10.7.2, NIS 5.1
12/23/11 9:23:56.614 PM Symantec Error Reporting: Symantec Error Reporting Daemon launched.
12/23/11 9:26:26.367 PM Symantec Error Reporting: Symantec Error Reporting Daemon beginning submission for domain local-domain.
12/23/11 9:26:26.371 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 36 error reports.
12/23/11 9:26:26.372 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 36 reports.
12/23/11 9:26:26.643 PM Symantec Error Reporting: Symantec Error Reporting Daemon beginning submission for domain current-user.
12/23/11 9:26:26.653 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 1 error reports.
12/23/11 9:26:26.661 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 1 reports.
12/23/11 9:26:37.846 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 0 panic reports.
12/23/11 9:26:37.847 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 0 crash reports.
12/23/11 9:26:37.847 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 1 error reports.
12/23/11 9:26:39.145 PM Symantec Error Reporting: Result of upload command: 65280
12/23/11 9:26:39.149 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Failed to submit anything.
12/23/11 9:26:39.204 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 0 panic reports.
12/23/11 9:26:39.204 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 0 crash reports.
12/23/11 9:26:39.204 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Submitting 36 error reports.
12/23/11 9:26:41.456 PM Symantec Error Reporting: Result of upload command: 65280
12/23/11 9:26:41.466 PM Symantec Error Reporting: Symantec Error Reporting Daemon: Failed to submit anything.
12/23/11 9:27:39.150 PM com.apple.launchd.peruser.501: (com.symantec.errorreporting.periodic-agent[7035]) Exited with code: 70
12/23/11 9:27:39.150 PM com.apple.launchd.peruser.501: (com.symantec.errorreporting.periodic-agent) Throttling respawn: Will start in 6978 seconds
12/23/11 9:27:41.468 PM com.apple.launchd: (com.symantec.errorreporting.periodic[7023]) Exited with code: 70
12/23/11 9:27:41.468 PM com.apple.launchd: (com.symantec.errorreporting.periodic) Throttling respawn: Will start in 6875 seconds
(FYI, the code 70 status started appearing after a mid-November LiveUpdate. The couple of months prior to that update, launchd never reported throttling ERD.)
Would love to see ERD being able to properly send reports to Symantec, to eliminate this repetitive console log spam.
12-24-2011 08:00 AM
Sorry for the problems. I'll pass this along to the folks who work on this feature. It may be a little while before you hear back, due to the holidays.
01-04-2012 06:42 AM
Hi,
One of the engineers has requested output from the following 3 commands (in /Applications/Utilities/Terminal):
/usr/libexec/PlistBuddy -c "Print :Internal" /Library/Preferences/com.symantec.errorreporting.p
/usr/bin/host macupload.symantec.com
sftp -o LogLevel=DEBUG3 macupload.symantec.com
01-04-2012 10:06 AM
Thanks for following up on this, Lee!
Here's the output that the engineer has requested:
kathryns-imac:~ kathryn$ /usr/libexec/PlistBuddy -c "Print :Internal" /Library/Preferences/com.symantec.errorreporting.p
false
kathryns-imac:~ kathryn$ /usr/bin/host macupload.symantec.com
macupload.symantec.com has address 216.10.196.81
kathryns-imac:~ kathryn$ sftp -o LogLevel=DEBUG3 macupload.symantec.com
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to macupload.symantec.com [216.10.196.81] port 22.
debug1: connect to address 216.10.196.81 port 22: Connection refused
ssh: connect to host macupload.symantec.com port 22: Connection refused
Connection closed
01-04-2012 01:53 PM
It appears that you may have trouble with port 22 being blocked. Do you know if you can SSH into any server? If you are behind a corporate or personal firewall (e.g. NPF), you may want to find out about the settings.
