I had a support request open for this same issue and we discovered that the key does get saved to the database even though the error occurs on the admin page.  How this issue made it to a released product I don't understand.  Every release has bug(s) like this...making it impossible to get on a stable release.