Andres Hidalgo

Q: Impossible to activate iMessage and Facetime in Mavericks

've just instaled Maverick upgrade and now iMessage and Facetime try to connect with my Apple ID but iMessage is not responding and Facetime finally returns a connection error.

 

I tried to find someone with the same issue, but I couldn't find any. I would appreciate any help.

 

Best regards,

 

Andres

Posted on Oct 23, 2013 3:56 AM

Close

Q: Impossible to activate iMessage and Facetime in Mavericks

  • All replies
  • Helpful answers

first Previous Page 4 of 10 last Next
  • by mrtn_PL,

    mrtn_PL mrtn_PL Oct 28, 2013 7:02 AM in response to Andres Hidalgo
    Level 1 (0 points)
    Oct 28, 2013 7:02 AM in response to Andres Hidalgo

    The same problem with IMessage and FaceTime after upgrade from ML and "clean" installation as well.

     

    I think the problem is KeyChain. Take a look on the picutere. zd.jpg

     

    I tried to fix it using First Aid, but it didn't work.

     

    Any ideas?

  • by DKGill,

    DKGill DKGill Oct 28, 2013 7:25 AM in response to Andres Hidalgo
    Level 1 (5 points)
    Oct 28, 2013 7:25 AM in response to Andres Hidalgo

    Hum! mine's different.

    Here's the result. Plus FT doesn't wait for a password when launched.

     

    • 10/28/2013 10:18:23.742 AM VDCAssistant[448]: AVF error: AVDLoadAllAccelerators machine not supported
    • 10/28/2013 10:18:24.492 AM FaceTime[445]: Retrieving server bag 1, 0x600000016540, 0, 0
    • 10/28/2013 10:18:37.561 AM apsd[59]: Certificate not yet generated
    • 10/28/2013 10:18:37.561 AM apsd[59]: Certificate not yet generated
    • 10/28/2013 10:18:37.564 AM apsd[59]: Certificate not yet generated
    • 10/28/2013 10:18:37.570 AM apsd[59]: Certificate not yet generated
    • 10/28/2013 10:18:37.661 AM identityservicesd[222]: [Warning] Tried to disable an account we don't know about, ignoring...
    • 10/28/2013 10:18:38.883 AM com.apple.kextd[12]: kext com.rogueamoeba.InstantOn  600019000 is in exception list, allowing to load
    • 10/28/2013 10:18:49.937 AM com.apple.SecurityServer[24]: Session 100018 created
    • 10/28/2013 10:18:50.172 AM apsd[59]: Certificate not yet generated
    • 10/28/2013 10:18:50.173 AM apsd[59]: Certificate not yet generated
    • 10/28/2013 10:18:50.189 AM apsd[59]: Certificate not yet generated
    • 10/28/2013 10:18:51.800 AM FaceTime[445]: Retrieving server bag 1, 0x600000016540, 1, 0
    • 10/28/2013 10:19:50.225 AM identityservicesd[222]: [Warning] Tried to disable an account we don't know about, ignoring...
  • by DW039,

    DW039 DW039 Oct 28, 2013 8:04 AM in response to DKGill
    Level 1 (0 points)
    Oct 28, 2013 8:04 AM in response to DKGill

    I am running into the same situation.  I created a new user account on the same MBP and I can log in and use Messages and Facetime with my iMessage account.  I tried recreating the .plist files associated with Messages and Facetime in my original user account but that did not fix the issue

  • by VisualPro,

    VisualPro VisualPro Oct 28, 2013 8:11 AM in response to iggipop
    Level 1 (0 points)
    Oct 28, 2013 8:11 AM in response to iggipop

    1) download the dmg from site

    2) plug in USB stick that you are about to erase with the DMG data... so use a stick that you don't need the data on anymore

    3) open up disk utilities

    4) If this usb was formatted as fat32 you will need to click the erase tab and format the usb stick as Mac OS Extended (Journaled)

    5) Once this is done... click the restore tab and for the source drag in the dmg for the destination drag in the USB stick... then click the Restore button at the bottom

     

    That's it.  You now can boot your system and hold down the Option key until you get the selection of boot drives.... select the USB drive you just made and follow the instructions.

     

    Good Luck.

  • by iggipop,

    iggipop iggipop Oct 28, 2013 8:40 AM in response to mr_ngiau
    Level 1 (0 points)
    Oct 28, 2013 8:40 AM in response to mr_ngiau

    mr_ngiau can u help me?!? i downloaded the Blank Board Serializer, than i burned with disk utility: when i boot i have only a black screen with an underscore

     

    any suggestion

     

    thx in advance

  • by iggipop,

    iggipop iggipop Oct 28, 2013 9:18 AM in response to VisualPro
    Level 1 (0 points)
    Oct 28, 2013 9:18 AM in response to VisualPro

    THX VISUAL i followed your valuable guidance, the usb stick is bootable but, when i boot from the usb stick, i have only a black screen with an underscore. any suggestion?

     

    your help is really remarkable!!!

  • by VisualPro,

    VisualPro VisualPro Oct 28, 2013 9:41 AM in response to iggipop
    Level 1 (0 points)
    Oct 28, 2013 9:41 AM in response to iggipop

    iggipop,

     

    Unfortunately no.  You could email Roger... the gentlemen that created the software and send him your findings. 

    He did have some cavets which are:

     

    Some caveats:

    • This is unsupported and I’m not responsible for anything.
    • The tool can only set the serial number on a main board that has no serial number, so if you set the wrong serial number you wont be able to correct the error and will have to visit an Apple Support Service.
    • Some older computers many not be supported by the Blank Board Serializer, so if it does not work, write it in the comments.

     

    If any of the above applies to you then maybe that is why you are having some issues.  If it is an older board you may want to write a comment on his site to let him know that it is not working.

     

    Just an FYI.... Apple can do this via their Apple Service Toolkit software.  If you google it... you will find many download versions.... I never used this so you have to do this at your own risk.   With that said you may have to bite the bullet and just go to the apple store and tell them this is what you want done.

     

    Hope that helps.

  • by iggipop,

    iggipop iggipop Oct 28, 2013 9:45 AM in response to VisualPro
    Level 1 (0 points)
    Oct 28, 2013 9:45 AM in response to VisualPro

    VisualPro

    my computer is so old, is a macbook pro 2009...

    thanks anyway for your patience and your kindness ...

  • by Andres Hidalgo,

    Andres Hidalgo Andres Hidalgo Oct 28, 2013 9:45 AM in response to Andres Hidalgo
    Level 1 (0 points)
    Oct 28, 2013 9:45 AM in response to Andres Hidalgo

    From my point of view, this been my first experience using this forums has been fantastic, with very remarkable solutions, very technical some of them, where important and sensible information were provided. But after read all the opinions, workarounds, similar issues but with different tones, the real feeling is fear. Clearly there is a bug (or severals) in Mavericks, but Apple is still silent. No notices, no news. This is not the best user experience ever that I was expecting.

  • by VisualPro,

    VisualPro VisualPro Oct 28, 2013 10:01 AM in response to iggipop
    Level 1 (0 points)
    Oct 28, 2013 10:01 AM in response to iggipop

    iggipop,

     

    Sorry to here about that... my MacbookPro is a Early 2007 and the software worked for me.  Well at this point I would say time to pack up your mac and head to the Apple Store.

  • by mrtn_PL,

    mrtn_PL mrtn_PL Oct 28, 2013 11:50 AM in response to chattphotos
    Level 1 (0 points)
    Oct 28, 2013 11:50 AM in response to chattphotos

    Thank You ! You were right. The problem was timezone settings. IMessage works again

  • by plasmawipes,

    plasmawipes plasmawipes Oct 28, 2013 1:29 PM in response to mrtn_PL
    Level 1 (0 points)
    Oct 28, 2013 1:29 PM in response to mrtn_PL

    the time zone fix didn't work for me cause I am in the correct time zone what is the purpose of commenting and no will help me out as if I do not exist I have the same problem as all of you and no one has took the time and said:

    "Hey Plasmawipes here is how you can possibly fix your iMessage problem"... No one has helped.

    Microsoft and Ubuntu Communites aren't this cruel. Can anyone help me with my iMessage please???????????????

     

    Message was edited by: plasmawipes

  • by DKGill,

    DKGill DKGill Oct 28, 2013 1:44 PM in response to plasmawipes
    Level 1 (5 points)
    Oct 28, 2013 1:44 PM in response to plasmawipes

    Same here. Time zone changes do nothing! Where's Apple techies in all of this?

  • by Paul Schleuse,

    Paul Schleuse Paul Schleuse Oct 28, 2013 2:13 PM in response to Andres Hidalgo
    Level 1 (21 points)
    Oct 28, 2013 2:13 PM in response to Andres Hidalgo

    Another unhappy upgrader—timezone is correct, serial number is correct, and I'm not savvy enough to start mucking about with hackerware.

     

    Usually there's an Apple techie tuned in to long support discussions like this one. Where are they now?

  • by VisualPro,

    VisualPro VisualPro Oct 28, 2013 3:37 PM in response to plasmawipes
    Level 1 (0 points)
    Oct 28, 2013 3:37 PM in response to plasmawipes

    plasmawipes,

     

    After reading about what everyone is going through... it seems to me there are a multitude of issues that could cause the problem of iMessage and Facetime not working.  I don't think anyone is going out of there way not to answer you because no one really knows what is happening.   I will do my best to put the synopsis of what the main issues are and how to go about trouble shooting this issue. 

     

    First off I definitely believe that everyones issue has to do with the shared certificate that gets generated when connecting to these services.  This is obvious to what people are posting from the log files.  The problem is that it is different issues causing the certificate problems for the individual user which makes it all the more hard to track down.  With that said here is a list of fixes that solved peoples problems.

     

    1) Remove the apple id from imessage preferences and close and reopen. Seems to have fixed some users issues.

    2) Changing the time zone to automatic.  Making sure your icloud account is set to the same time zone at www.icloud.com. Seems to have fixed some users issues.

    3) Making sure your serial number is not blank within OSX.  Not only that... make sure that the serial number is the same as what is printed on your MAC... One user had his mac motherboard changed by Apple and they put a malformed serial number on the MAC... once he changed it to be correct.... it worked for him.

    4) Some users did a fresh install and it worked for them (however... I have only seen a few people say this has worked for them)

    5) Remove any alternate Apple ID's associated with your icloud.com account and reboot.  This has worked for some people.

    6) Try logging in with a alternate apple ID associated with your icloud.com account... ie if you have a username@mac.com  try using username@icloud.com or username@me.com  which were assigned to you when you created a icloud account.... depending on how long you have had it you may not have a @me address.  You need to check appleid.apple.com. Click on Manage my account.

    7) Some users have removed there imessage key chain private and public keys and rebooted and it worked for them.  I would be very careful on doing this as you don't want to mess anything up with your key chain. or you may be doing step 4 anyway.

     

    Again,  These are the things that have worked for other people... your situation may be different.... as I don't think Apple totally knows what is happening either.  I spend most of the other afternoon working with a senior apple tech over the phone... and it came down to him not knowing what was the issue... He didn't believe that the wrong or malformed serial number could cause this.... which in my case it did.  If you read the system.log it is basically screaming at you saying the "Certificate is not valid"  So my guess is that the new iMessage and Facetime uses your unique serial number to help generate a ssh shared certificate.  For I we know it may use the date and time  of the server for syncing imessages as well... so the time of your computer has to be in line with apple icloud.

     

    People have also gone to the Apple store and the Geniues were unable to help.... I am sure Apple is trying to figure this out... however... if it is like I suspect it is a multitude of issues that can cause the certificate to become invalid.... If that is the case they are the only ones that can fix the issue.

     

    All we can do is let them know.

     

    Hope this helps you a bit plasmawipes.

first Previous Page 4 of 10 last Next