daeup

Q: could not sign in to iMessage

Somehow I can't use Message on my macbook. When I check the account of iMessage, error message comes up:

" could not sign in to iMessage

the server encountered an error processing registration. Please retry again later. "

 

But with same account, I have no problme on my iMac.  I tried to remove preference file of iMessage but it didn't help.

Any idea welcome.

 

thanks

MacBook Pro, OS X Mountain Lion (10.8.2)

Posted on Jan 14, 2013 8:57 PM

Close

Q: could not sign in to iMessage

  • All replies
  • Helpful answers

first Previous Page 4 of 4
  • by bcassid,

    bcassid bcassid Aug 2, 2016 1:54 PM in response to Ralph Johns (UK)
    Level 1 (4 points)
    Mac OS X
    Aug 2, 2016 1:54 PM in response to Ralph Johns (UK)

    How could it be at the server level if I can use the same Apple ID from the problem computer just fine on other computers? Also, the problem computer won't work with ANY Apple ID. Seems that pretty much narrows it down to the hardware or software on the computer, unless I'm missing something.

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Aug 2, 2016 2:07 PM in response to bcassid
    Level 9 (72,994 points)
    Applications
    Aug 2, 2016 2:07 PM in response to bcassid

    hi,

     

    You are missing something.

     

    The Login is made up of three things.

    The Apple ID

    It's Password

    and the Serial Number.

     

    The issue tends to be that for a random reason the iMessages Server dos not like logins from your Mac - no matter which Mac User Account using the same Apple ID  or what ever other Apple IDs you use.

     

    To a certain extent it is like when a particular light bulb blows and just happens to trip the fuse at the same time.

    You can change the bulb to can flick the switch as many times as you want.

    You will have to go and reset the fuse.

     

    In this case as it is the Server end that does not like your Mac (meaning the Serial Number as if someone else was trying to spoof your Mac/Apple ID) you need to get Apple to reset it.

     

    Deleting the Keychain (or rather the IDS:your Apple ID-Auth Token where the Apple ID is the email used) will not work as the Apple ID used by the Mac has been Flagged at the iMessages Server.

     

    EDIT See this post that came in whilst I was writing the above Re: iMessage

    3Sigcopy2.png

    10:05 pm      Tuesday; August 2, 2016

     

    2nd Edit It is late where I am and I will be back in 20 hours

     

      iMac 2.5Ghz i5 2011 (El Capitan)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     iPhone and an iPad (2)
  • by bcassid,

    bcassid bcassid Aug 2, 2016 2:08 PM in response to Ralph Johns (UK)
    Level 1 (4 points)
    Mac OS X
    Aug 2, 2016 2:08 PM in response to Ralph Johns (UK)

    So something at Apple's end doesn't like the serial number. That makes sense. Thanks for explaining it. So what exactly do I ask Apple to reset?

  • by Eric Root,

    Eric Root Eric Root Aug 3, 2016 8:00 AM in response to bcassid
    Level 9 (69,813 points)
    iTunes
    Aug 3, 2016 8:00 AM in response to bcassid

    Take it to an Apple Store or Apple Authorized Repair Center and explain that the serial number isn't registering. They will then need enter it on the logic board.

  • by bcassid,

    bcassid bcassid Aug 3, 2016 8:39 AM in response to Ralph Johns (UK)
    Level 1 (4 points)
    Mac OS X
    Aug 3, 2016 8:39 AM in response to Ralph Johns (UK)

    I'm assuming that my problem is different than polarbreeze1 because his problem seems to be related to his Apple ID and not a serial number. Does that make sense?

  • by bcassid,

    bcassid bcassid Aug 3, 2016 8:40 AM in response to Eric Root
    Level 1 (4 points)
    Mac OS X
    Aug 3, 2016 8:40 AM in response to Eric Root

    This contradicts what Ralph said about it being a server problem. I work at a school that has a program with Apple that is an Apple Authorized Repair Center just for the school district and we have access to the tool that let's you write serial numbers onto logic boards, but that only works on replacement logic boards that don't have serial numbers already. You can't use it to change or re-enter a serial number. I already tried that.

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Aug 3, 2016 12:33 PM in response to bcassid
    Level 9 (72,994 points)
    Applications
    Aug 3, 2016 12:33 PM in response to bcassid

    Hi,

     

    I think Eric may have got lost in the replies going back and forth.

     

    The first check is to find if the Serial Number is there.

    The next is to check in other Mac User  Accounts (or other Apple IDs) whether the Mac can Login.

     

    The Serial number is a stopper which has to be resolved first.

    The second proves whether it is the Mac or the User account/Apple ID  (it is better to use a Different Mac User account).

     

    Then try non standard maintenance that are less destructive.

    NVRAM reset and Safe Boot.

     

    AT this point you will have a Mac that should login as it has a Serial Number.

    Something the iMessages Server does not like about the login has been triggered preventing ANY Apple ID from Logging in.

    On the whole most people are testing with One Apple ID and it is this we refer to as being Blocked at the iMessages Server.

     

    THE ONLY FIX is to Contact Apple Support and jump though the hoops and Data gathering (Apple know it happens but not why) until such time they say they will reset the server.

    Reinstalling, Upgrading (Yosemite to El Capitan for Instance) or Updating (OS X 10.11.3 to OS X 10.11.5 for instance) do not work.

     

    NOTES.

    As you have tried several Apple IDs in the same User Account I would also delete

    com.apple.ids.service.com.apple.madrid.plist  from ~/Library/Preferences as this will hold all the Apple IDs you have ever tried and also any Alternatives linked to the Apple ID such as iPhone Numbers.

     

    You may want to consider also deleting com.apple.imessage.bag.plist

    This one holds the Server you have been connected to.

     

    In Keychain Access (Applications/Utilities) set Login top left, Passwords lower left then find

    IDS: your appleID-Auth Token where the Apple ID is the email listed (Most likely the last Apple ID you tried).

     

     

     

    3Sigcopy2.png

    8:33 pm      Wednesday; August 3, 2016

     

      iMac 2.5Ghz i5 2011 (El Capitan)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     iPhone and an iPad (2)
  • by bcassid,

    bcassid bcassid Aug 3, 2016 12:37 PM in response to Ralph Johns (UK)
    Level 1 (4 points)
    Mac OS X
    Aug 3, 2016 12:37 PM in response to Ralph Johns (UK)

    Thanks Ralph. Your help is greatly appreciated. Do you have any suggestions as to what to say to Apple? What server do I tell them to reset?

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Aug 3, 2016 12:56 PM in response to bcassid
    Level 9 (72,994 points)
    Applications
    Aug 3, 2016 12:56 PM in response to bcassid

    Hi

     

    Back in Mountain Lion when Messages 7.0.1 came out at the OS X 10.8.2 update users were seeing this.

    Apple_ID_7_0_1.png

     

    At this point the Level 2s who were taking over the calls  were the ones resetting the server.

     

    Since then it seems things have got tighter as less level 2s know about it and Apple have seemingly made a push to solve this (but two OSes later they are still data grabbing from those that will help them).

     

     

    Level 1s are reported to have a high turn over and work to Scripts.

    You need to politely ask to speak to someone higher if they mention costs (tell them it is an Apple ID issue) or insist you try Restarting, deleting .plists or "fixing the Keychain".

     

    Once you have a  Level 2 you need to judge their knowledge on the subject.

    As some know of the issue then they are likely to ask to collect some data from you.

    As you work in a school with server computers with similar issue you may want to get out of that.

    Be insistent.

     

    I have suggested in the past that people actually ask they look at the server and see if the Apple ID is Blocked based on the login from the Mac.

    As I said the Login is device specific and is reality it is probably the Serial number that it blocked but it easier for them to spot the Apple ID.

     

    For about a year now it seems the engineers have the final say on resetting the server.

    Insist the server is reset for you.

     

    People who have posted back have quoted 24 hours to 5 days and often say it is sorted before that time.

     

     

     

     

    3Sigcopy2.png

    8:56 pm      Wednesday; August 3, 2016

     

      iMac 2.5Ghz i5 2011 (El Capitan)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     iPhone and an iPad (2)
  • by bcassid,

    bcassid bcassid Aug 3, 2016 1:15 PM in response to Ralph Johns (UK)
    Level 1 (4 points)
    Mac OS X
    Aug 3, 2016 1:15 PM in response to Ralph Johns (UK)

    So the server to ask them to reset is the iMessage / Facetime / Apple ID server?

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Aug 3, 2016 1:30 PM in response to bcassid
    Level 9 (72,994 points)
    Applications
    Aug 3, 2016 1:30 PM in response to bcassid

    Sorry,

     

    iMessages.

     

    Whilst the ID works in other apps (iTunes, Games Centre, iBooks, FaceTime etc) then you don't need to do the Apple ID

     

    IF the FaceTime server is effected it should clear up at the same time.

    However if it sis both then it is more likely to be something like the missing Serial Number.

     

     

    3Sigcopy2.png

    9:30 pm      Wednesday; August 3, 2016

     

      iMac 2.5Ghz i5 2011 (El Capitan)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     iPhone and an iPad (2)
  • by bcassid,

    bcassid bcassid Aug 3, 2016 4:33 PM in response to Ralph Johns (UK)
    Level 1 (4 points)
    Mac OS X
    Aug 3, 2016 4:33 PM in response to Ralph Johns (UK)

    I'm on hold with Apple right now. The level 1 tech was pretty insistent that it's a hardware problem and I need a new motherboard! He said no escalation was needed because he can see and fix any blacklisting from his end on the server. Now I'm talking to the level two guy. I think he's going to escalate.

  • by bcassid,

    bcassid bcassid Aug 3, 2016 4:38 PM in response to bcassid
    Level 1 (4 points)
    Mac OS X
    Aug 3, 2016 4:38 PM in response to bcassid

    Level Two saying it will take about 2 days to escalate! Argh!

  • by bcassid,

    bcassid bcassid Aug 3, 2016 5:08 PM in response to Ralph Johns (UK)
    Level 1 (4 points)
    Mac OS X
    Aug 3, 2016 5:08 PM in response to Ralph Johns (UK)

    Ralph, do you happen to know of any cases I could refer to, preferably online, of this same problem that was fixed by Apple resetting the server? It would be great if I could show that to Apple support. I've searched, but am not finding any. The sad thing is that replacing the logic board would fix the problem because it would change the serial number! That would be a sad waste of money!

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Aug 4, 2016 11:45 AM in response to bcassid
    Level 9 (72,994 points)
    Applications
    Aug 4, 2016 11:45 AM in response to bcassid

    Hi,

     

    Changing the Logic Board does not change the Serial Number.

    It has a special chip that can be written to once to put back the Serial Number of the Machine you have.

     

    Example threads

    iMessage not working after 10.10.5 update.. HELP!

    Second one iMessage suddenly decides to stop working

     

    A long way down this one on the 16th Nov 2015 Can't activate iMessage on iMac with El Capitan

    Realistically this thread ranges all over the place covering several issues.

     

    My last reply in this one is actually marked Helpful in the box at the bottom  but the Original Poster ahs not come back to say either way.

    Activation of iMessage and Facetime failed on El Capitan after Update

     

    This covers Linc Davis' 16 point approach

    Another iMessage/Facetime activation glitch?

    Whilst This does cover every fix we have come across fro all the similar looking issues since Mountain Lion it does not hone them down to follow one issue over another.

    Although I have added into this the "shorter" steps the Original Poster again has not come back to say it worked or it didn't

     

    One with a Solved marking Unable to sign in imessage: An error occurred during activation. Try again.

     

    3Sigcopy2.png

    7:45 pm      Thursday; August 4, 2016

     

      iMac 2.5Ghz i5 2011 (El Capitan)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     iPhone and an iPad (2)
first Previous Page 4 of 4