Impossible to activate iMessage and Facetime in Mavericks

I'm having the same problem as everyone else

This is what I have done that DOES NOT WORK:

Automatic Time Zone

Screwed around with DNS and wi-fi setting to 8.8.8.8 and 8.8.4.4

Reseted Keychain MULTIPLE TIMES

Checked if iMessage and FaceTime is working or not on the server

Checked if my Serial number was there or it was screwed up

Fresh Install OSX Mavericks many many times, then I Fresh installed Snow Leopard then upgraded to Mavericks still same issue?

Does anyone know how to fix this problem? Why hasn't apple looking into this?

AHHHHHHHHHHHHH!!!!!!!!!!

Hi,

Is the AppleGothic.ttf Font active, valid and working ?

10:05 pm Saturday; October 4, 2014

Dude, this is the worst advice. Your just saying go to apple store to see IF they can fix it, and there is no SURE SOLUTION to this. Just because it worked for you doesn't mean it doesnt work for everyone.

Hi,

Lets be clear.

Since this thread started there have been about 6 different types of error, some with error messages that have been seen over the life of Messages in Mountain Lion and Mavericks.

The first 4 are covered in this Doc FaceTime, Game Center, Messages: Troubleshooting sign in issues

Then there is the Serial Number issue that is not documented anywhere and started at the OS X 10.8.2 update and for some may have started with a Mavericks Install. This one can only be "fixed" by a visit to an Apple Store or Apple Authorised Service Provider (AASP).

Next we have the Error message that is shown that looks like this

Obviously it lists your Apple ID and gives you and individual Customer Code.

It too can only be "fixed" by contacting Apple Support. Since it was first seen in Mountain Lion/Messages 7 it has featured less to the extent some Support Staff don't know about it and try to say you have a Hardware or Software issue and try and charge you for an Out of Warranty payment.

It is actually and Account issue that only effects the Mac and the iMessages server. Ask to speak to the Level 2 person if you have no luck.

Then there is an issue where the App will not launch properly.

This is caused by the AppleGothic.ttf Font being either Off or damaged.

It is required by the Messages app to login and Register the Apple ID for the iMessages account. (it appears this is done each App Launch).

Currently the Font is held in Hard Drive Name/Library/Fonts. Required Fonts are normally held in Hard Drive Name/System/Library/Fonts.

Fixes reported have included moving the font to the System/Library/Font location. Another is to use the Finder to Duplicate the Font and then move the Original and Rename the Duplicate which seems to reactivate the font.

Checking it Validates and is On with the Font Book App is useful.

There is a issue that has changed in recent times.

You iMessages account appears to Login. However when you try to send an iMessages it turns the Contacts name Red and says they are not iMessages registered (And All Contacts show this way).

It have been seen that a Fresh Install (Erase Drive and reinstall and don't migrate anything back) and starting Messages does not cure this.

The only things not changed are the Serial Number and the Apple ID itself along with it's login to the iMessage server.

This has been reported to Feedback http://www.apple.com/feedback/ and the more that do so the better. It has also been reported to the Hosts to pass it on and Level 6 Posters can report such things in the Lounge.

There is a New error message I have only seen posted twice.

It relates to the Device "Not having the right Credentials". These might be Yosemite Beta messages but that cannot be discussed here.

It would suggest that Apple are working on something around the issues effecting apparent Login but no Messages Sending however that appears symptom-wise.

Realistically it still looks like an Account problem and I would suggest contacting Apple Support and getting them to Check the account at iMessages as there are other known issues.

All of the fixes listed so far in this thread have worked with at least one of the issues.

There is no one coverall Fix at the moment.

8:05 pm Sunday; October 5, 2014

I'm late to the party, but this thread was very helpful. I just upgraded to Mavericks today and iMessage was also telling me that there was a server error.

What WORKED for me was changing the time zone in my general settings to be automatic. Was able to log in and it works fine.

Thanks for all the help, everyone!

I had the serial number issue after upgrading to Yosemite. It may have been an issue on Mavericks, but wanted to test the Continuity features with my phone and that required iMessage and FaceTime login. The main board on my MacMini was replaced over a year ago so that would explain why it was missing. But after running the tool to write the serial number back on the board I was able to sign in again. Thanks for the awesome advice on this thread!

You're welcome.

8:58 pm Thursday; October 23, 2014

I could not login in my MacPro using my AppleID or another AppleID in Yosemite or Mavericks. So the problem was not related to the system, and probably neither to the AppleID.

I could login in my MacBookPro under Mavericks with my AppleID. This confirmed that the problem was not related to my AppleID.

So the remaining factor was the computer. But it had the correct serial number, since the logic board was never replaced, and the time zones were correct.

I reset the SMC, and now the problem is fixed. I can activate and login in Messages, and send messages through the iPhone (requieres Yosemite and iOS 8).

Intel-based Macs: Resetting the System Management Controller (SMC) - Apple Support

This thread is old, but the problem persists.

For me, the problem seems to have been that I turned on two-factor authentication and needed to generate an "app-specific password". I did this by opening Messages and trying to log in there. In fact, the two apps had been working for months since I enabled 2f, so I suspect something changed on Apple's end.

It is a shame that in Apple's rush to release a new OS (or 4 if you include phone, watch and tv) every year that they leave bugs like this unfixed.

Using app-specific passwords - Apple Support