I can't log in to Messages or FaceTime with my iCloud account.

I am having this error too!

I am also having this error. I am guessing Apple broke their registration servers? I can't login to FaceTime or iMessage on my Macbook Pro, and I need to sign in so I can release my phone number, as I'm no longer using an iPhone. iMessage/FaceTime worked until I installed Mavericks.

give it time. just busy now

Peace, Clyde

I am in the same boat. I have not been able to login to iMessage in the Mavericks Message app since I upgraded my MBP 4 1. From what I can tell the other features including those that use my Apple ID are working fine, but I have not yet tried facetime. I get a different error message than the one posted by gmdavis9 though:

i have also this problem and i want to kick out this machine... What is happing to APPLE ???? What a **** is this?

Hi,

No-one seems to have indicated where they have upgraded from.

Someone jumping Mountain Lion will be subject to the Serial Number issue if their Logic Board has been replaced in a Repair or Refurbishment and the number not "Flashed" back to the New board.

Use the About this Mac option in the Apple Icon Menu and then click twice on the current OS level.

It will change to the Build number then the Serial Number (if present).

If it is missing an Apple Store or Apple Authorised Service Provider can reinstall the info.

Also look at this item http://support.apple.com/kb/TS3970

8:51 pm Sunday; October 27, 2013

 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.4)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

Upgraded from snow leopard;

Thanks for your suggestion, I did have my logic board replaced two years ago and it appears that the technician did not reinstall the serial number. I will be getting my computer serviced to remedy this problem, and will let you know if it solves the sign in issue as well.

Cheers,

HI,

iMessages does not use iCloud.

It is like iTunes in that it logs in with your Apple ID and it's password.

It is true that the same Apple ID and password may also be your iCloud ID.

Therefore logging in to iCloud in a Web Browser actually tells us nothing about the iMessages login which is on a completely different server and in fact is separate from the FaceTime one.

Since issues with Messages 7 (Mavericks in Messages 8) I have had two public DNS servers listed in System Preferences > Network > Advanced Tab > DNS

The two I use are 8.8.4.4 and 8.8.8.8 which belong to Google.

Check the Date and Time and Zone settings on the Mac.

Make sure the router is also set to the same Time Zone and has the correct Date and Time.

Double check the Firewall on the Mac.

System Preferences > Security and Privacy > Firewall tab

If On check the Option button

Signed Software should be allowed and Messages and iMessages plus FaceTime needs to accept incoming data and be in the list.

Try a different Mac User account if you have one.

and use Messages there with the details you normally use.

8:23 pm Monday; October 28, 2013

 iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

I think you are incorrect Ralph.

I too have a LB with no serial number on it due to being replaced earlier. I found that after mavericks I cannot log into imessage and facetime. (connection just times out like everyone here has already described) I could log in with mountain lion without any issues even though my serial number was missing.

I went and grabbed the program used to burn the serial number into a new board and burned my serial number into the board. "About This Mac" now reports the correct serial number but my ability to log into imessage and facetime has not changed.

So for everyone that is suggesting that a missing serial number will keep you from being able to log in, I would say that I have proved that it is not the issue.

Interesting. Now that you mention it, I'm pretty sure that I was also able to use imessage at first after updating. Can't say about facetime since I don't really use it...

Hi,

Two things.

If Mountain Lion was not updated beyound OS 10.8.1 then the change to Messages in the 10.8.2 update never gets applied.

Additionally it seems if your kept an active login with that Apple ID (second computer for instance) then also the Login would remain in place.

Secondly the Missing Serial number is not the only cause

http://support.apple.com/kb/TS3970

As the Apple Doc says incorrect Date And Time (+ Zone) settings can be an issue.

Add in to that Daylight Saving settings.

Check your router is also matching the settings

The Doc also list an altered Host file that can block Verisign.

9:24 pm Tuesday; October 29, 2013

 iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

I didn't change motherboard, so that is not the problem. I checked time zone, date, logged in and out but the problem remains. I can log in, I do and everything seems fine. It's when I send my texts that they don't go through. When I Facetime it seems it's fine as well, it does the ringing sound, but the receiver never receives the call, nor can I receive on it other people's calls. It's driving me mad!

Any help?

I've been having the same problem and finally found a solution that worked for me.

After three calls to Apple support - and trying all of the fixes noted in these forums (serial number issues, spacing in Apple ID, time zone, didn't have two Apple IDs, reinstalling the OS, removing my Apple ID and re-adding it, starting in Safe Boot, etc. etc.) - this is what Apple Support (sort of) recommended that worked:

Logged off as myself and logged in as guest user. Tried to sign in to iMessage and it worked. Logged back out and logged in as myself - no luck. Created a new administrator called "test" and signed in as that user - tried to login again - success.

Ended up turning that test user account into my primary account and deleting the old admin account - now everything works just fine.

Good luck!