Norton for Mac

[elf]

I just migrated from one Mac to a new Mac (also 10.4.11 to 10.6.1). I *think* that the updates and protection are working ok, but I'm not entirely sure. Several times a day I get a dozen prompts, one right after the other, for a password for the Symantec keychain. I didn't create the keychain--I tried following Apple help info on keychains and deleted one labeled Symantec, but it keeps right on prompting me.  I've tried every password I can think of that I've used for anything. It's extremely annoying. How can I fix this?  Thanks.

[ryan_mcgann]

Wow, that is annoying. This keychain is used by our products to store sensitive information, so that malicious programs can't look at your settings, etc. It should be setup to allow any Symantec application access it without warning you, but perhaps migrating to Snow Leopard broke that.

Contact me privately, and I'll set you up with a fix. 

[gmc455]

Hi There

I've just gone from a PowerBook G4 to a MacBook Pro running Snow Leopard and am having the same problems. 

I rang support last night, and the problem still hasn't gone away.

Any help would be great appreciated.

Kind regards

[elf]

Ryan helped me out with a special script for uninstalling and I reinstalled and everything's fine now.

[gmc455]

Thanks Elf for the reply - I will try and contact ryan to find out the solution, like you......it's driving me crazy!!!

Cheers

[dsilverla]

Dear Ryan

I am having the same problem of repeated keychain password prompts from LiveUpdate and IRtool upon migrating to OS 10.6.  A fix would be appreciated.  Regular Norton help first tried deleting some keychain access items and when this did not work suggested waiting until a patch is issued.  They did not know when this would be.  I tried deleting my login keychain and starting over but that did not help, either.

Thanks,

Dan 

[ryan_mcgann]

For future posters—if you are having this problem, please contact me privately via the forums. Include your e-mail address, and I will attempt to help you.

Also, we are trying to reproduce this problem in-house, but so far haven't had any luck. If you could post/send your computer's configuration (Intel or PowerPC, operating system, etc.) it would be useful. Many people are reporting recently upgrading to Mac OS X 10.6.1, but that has been out for a while, and this problem just started cropping up this week, so anything you can provide us would be helpful. 

Sorry about the problems.

Ryan 

[elf]

FYI, my configuration: Migrated from a G4 running 10.4.11 to a new Mac Mini Intel with 10.6 preinstalled--I don't remember whether 10.6.1 was preinstalled or whether I actually had to download an update to get to 10.6.1. 

I used the migration tool, not on the first start-up of the new system, but after two or three startups. 

I'm using Norton AntiVirus; get info says it's currently 11.0.3, created Nov 27, 2007. 

I do not use Symantec Scheduler.

LiveUpdate using get info says it's version 5.1.1 (same creation date).

Don't know whether those were the same version on the previous mac, but I believe so.

Trying to think of anything else that might be useful-- Let me know if you have any questions. I do still have the old system and could hook it up again if you needed info from there.

-ellen

 P.S. I always received 12 prompts in a row--I didn't write down what they were for/from, but seems to me that it prompted twice in quick succession, then a brief pause, then the next 10.

Message Edited by elf on 10-15-2009 11:28 AM

[ryan_mcgann]

Thanks for this information. Did anybody else who is experiencing this problem use the Migration Assistant? That might cause problems with the keychain, and its not something we tested for Snow Leopard, so perhaps the Snow Leopard migration assistant is a bit smarter than it used to be before.

Thanks,

Ryan 

[eraether1]

I used the migration assistant and transferred my wife's data to a new 27" iMac. I am experiencing the keychain problems and would like to know if there is an update coming to fix it? I even tried reinstalling NIS and this did not help.