Forum Question: FileSyncAgent asking for login keychain password on ever boot

I am tying MobileMe’s free trial offer and an annoying issue has developed. Every time I boot my MacBook Pro, I get a message saying “FileSyncAgent wants to use the ‘login’ keychain” as it mounts my iDisk.

Once I type in my user password, everything works fine. After searching some Apple support forums, I have tried several things including repairing the keychain, deleting the keychain file, restoring an older keychain file (from before I tried MobileMe), and deleting the file.

None of the above has solved the problem. Any suggestions?

Comments: 6 Responses to “FileSyncAgent asking for login keychain password on ever boot”

    10/31/10 @ 10:15 am

    Have you tried the suggestions here:

    10/31/10 @ 3:55 pm

    I read that post but I am a bit confused. The post with the two solutions mentions a user name keychain and a session keychain. I only see a login and system keychain in the keychain access app. The login keychain is in my user library and the system keychain is in th MacBook HD library.
    My MacBook Pro is one year old and running OS X 10.6.4

      10/31/10 @ 4:05 pm

      It is hard for me to say where to go from here — I haven’t experienced the problem I have no way to know. Perhaps a visit to the Apple Store Genius Bar would help — it is much better to troubleshoot in person problems like this.

        10/31/10 @ 5:31 pm

        OK and thanks for the effort. I am a big fan of your podcasts. Keep up the great work!

    11/7/10 @ 7:11 pm

    Problem solved by removing Espionage software form MacBook that was somehow conflicting with MobileMe.

    Espionage is a program that came with some bundled software I purchased. I never used it but when I launched it to check it out it left something running that caused the problem. The Apple Phone support helped me troubleshoot by testing the iDisk on a new user account. Everthing worked fine on the new account so we checked for programs running at startup on my original account and found that Espionage was causing the problem. Everything works grate now!

    11/13/10 @ 6:53 am

    Great not grate :)

Comments Closed.