Issue imported from Google Code: https://code.google.com/p/sequel-pro/issues/detail?id=801
Reporter:[email protected] Date:2010-08-31 16:59:25 Status:WontFix Closed:2010-08-01
What steps will reproduce the problem?
An error occured while trying to add the password to your Keychain. Repairing your Keychain might resolve this, but if it doesn't please report it to the Sequel Pro team, supplying the error code -25293.
Connections work fine when I enter the password, but they cannot be saved.
Other applications can access and write to my keychain fine. Repairing my keychain has no effect on the problem. I have not installed any Sequel Pro, MySQL, or OS X updates since it worked last.
What version of Sequel Pro are you using? What version of MySQL are you
connecting to on the server?
Thanks.
Author:[email protected] Date:2010-08-31 17:07:26
Hi kchrist,
That's an odd one… -25293 is the following system error:
errSecAuthFailed = -25293, /* The user name or passphrase you entered is not correct. */
So the problem is that Sequel Pro can't talk to the system keychain at all, because the keychain is reporting it's been given the wrong username or passphrase! As other applications aren't running into this, that however seems unlikely - more likely to be that the Keychain is just in a slightly odd state.
Are the Sequel Pro passwords stored in your login keychain, or another keychain? Either way, it might be worth selecting that keychain in Keychain Access, locking the keychain via the toolbar, and then unlocking it again - and see if that nudges it out of the current state...
Author:[email protected] Date:2010-08-31 17:18:14
Good call, simply locking and unlocking my keychain does appear to have fixed the problem. Strange. Thanks, sorry to bother you with that.
Author:[email protected] Date:2010-08-31 17:26:27
Glad that sorted it! And that's why that particular error message is there - the Keychain subsystem seems to throw up odd errors at times :)
Work for me, Thank you very much!
Most helpful comment
Author:[email protected] Date:2010-08-31 17:18:14
Good call, simply locking and unlocking my keychain does appear to have fixed the problem. Strange. Thanks, sorry to bother you with that.