Brian-

We haven't gotten any reports of Keychain problems with Spanning Sync
3, but here's what we usually tell people with Keychain issues:

You can replace your Spanning Sync keychain items:

* Quit out of System Preferences (if open)
* Open Keychain Access (in /Applications/Utilities)
* Select "All Items" from the Category list on the left
* Search for "spanning"
* Delete all matching items
* Open the Spanning Sync pref pane
* Enter your account information

You may also need to reset the certificate policy:

*Open Keychain Access (located in /Applications/ Utilities).
*Go to Preferences.
*Click the Certificates tab.
*Set the OCSP and CRL popup menus to Off.

If that doesn't work, the keychain may be damaged.  To fix it you can
run 'Keychain First Aid':

*Open Keychain Access
*Click on the Keychain Access menu
*Select 'Keychain First Aid' from the menu
*Enter your password and select 'Repair' on the right
*Click the 'Start' button
*Sign into Spanning Sync
*Sync

Please let me know if you have any questions or run into any
problems.

Thanks,
Charlie


On Aug 11, 3:04 pm, Brian <[email protected]> wrote:
> Hello,
>
> I just upgraded to Spanning Sync 3.0 today.  I have Spanning Sync
> configured to update every 10 minutes.  I keep my OS X Keychain fairly
> tightly locked down so that it locks itself every 5 minutes.  For some
> reason now, Spanning Sync isn't remembering the fact that it can
> access my Keychain, and thus is requesting to have me type my password
> every 10 minutes.  This was never an issue with Spanning Sync 2.
>
> Is there something I am doing wrong, or is this a bug in Spanning Sync
> 3.0?
>
> Thanks for your help!
>
> Brian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Spanning Sync" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/spanningsync?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to