Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iMessages not working since upgrade to El Capitan

Hi Everyone,

When I was running yosemite, iMessages was working great. Since upgrading to El Capitan, things have gone AWL. When Trying to sign in I get these errors in console


11/2/15 8:38:24.517 AM accountsd[1168]: AIDA Notification plugin running

11/2/15 8:38:24.614 AM accountsd[1168]: AIDA Notification plugin running

11/2/15 8:38:24.616 AM imagent[1185]: [Warning] IMDAccountController: Could not find an account for service: (null)

11/2/15 8:38:24.616 AM imagent[1185]: [Warning] IMDAccountController: Could not find an account for service: (null)

11/2/15 8:38:24.681 AM imagent[1185]: [Warning] SMSServiceSession: Error no IDS Service available for SMS Relay

11/2/15 8:38:24.681 AM imagent[1185]: [Warning] SMSServiceSession: Error no IDS Service available for SMS Relay

11/2/15 8:38:24.681 AM imagent[1185]: [Warning] SMSServiceSession: Error no IDS Service available for SMS Relay

11/2/15 8:38:24.681 AM imagent[1185]: [Warning] SMSServiceSession: Error no IDS Service available for SMS Relay

11/2/15 8:38:25.214 AM accountsd[1168]: AIDA Notification plugin running

11/2/15 8:38:41.000 AM kernel[0]: IO80211AWDLPeerManager::monitorAWDLState Disabling AWDL due to no services and no active sockets

11/2/15 8:38:41.000 AM kernel[0]: ARPT: 2255.114546: AWDL Sync Enabled 0, data path state[1]

11/2/15 8:38:45.000 AM kernel[0]: ARPT: 2259.484413: AWDL Sync Enabled 1, data path state[1]


I also get some of this.


11/2/15 8:38:25.856 AM com.apple.xpc.launchd[1]: (com.apple.xscertd-helper[4017]) Service exited with abnormal code: 1

11/2/15 8:38:25.857 AM com.apple.xpc.launchd[1]: (com.apple.xscertd-helper) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

11/2/15 8:38:27.603 AM com.apple.xpc.launchd[1]: (org.openldap.slapd[4018]) Service exited with abnormal code: 1

11/2/15 8:38:27.603 AM com.apple.xpc.launchd[1]: (org.openldap.slapd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

11/2/15 8:38:35.876 AM xscertd-helper[4025]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting


11/2/15 8:43:38.824 AM servermgr_dirserv[2334]: idle exit

11/2/15 8:43:39.467 AM screensharingd[4148]: Authentication: FAILED :: User Name: N/A :: Viewer Address: 155.133.19.19 :: Type: VNC DES

11/2/15 8:43:40.000 AM kernel[0]: process com.apple.WebKit[4076] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback

11/2/15 8:43:40.741 AM screensharingd[4148]: Authentication: FAILED :: User Name: N/A :: Viewer Address: 155.133.19.19 :: Type: VNC DES


This Mac Pro 5,1 works as my home server as well which is why you see the servermgr active here. So I have a few issues but I have no idea on where to get started addressing them. My biggest concern is iMessages. It may also help to know that i get prompted for my iCloud password regularly on this machine but not on my MacBook Pro, iPhone or iPad.

Thank you in advanced!

Mac Pro (Mid 2010), OS X El Capitan (10.11.1), nVidia GTX 980 SC, 3.46Ghz Westmere

Posted on Nov 2, 2015 6:49 AM

Reply
7 replies

Nov 2, 2015 1:56 PM in response to claywdittman

Please read this whole message before doing anything.

This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

Step 1

The purpose of this step is to determine whether the problem is localized to your user account.

Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Step 2

The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Please take this step regardless of the results of Step 1.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

Nov 2, 2015 6:42 PM in response to claywdittman

The instructions were not intended to solve the problem, as I wrote above.

This could be a complicated problem to solve, as there are many possible causes for it. Test after taking each of the following steps that you haven't already tried. Back up all data before making any changes.

Before proceeding, test on another network, if possible. That could be a public Wi-Fi hotspot, if your computer is portable, or a cellular network if you have a mobile device that can share its Internet connection. If you find that iMessage works on the other network, the problem is in your network or at your ISP, not in your computer.

Step 1

Check the status of the service. If the service is down, wait for it to come back up. There may be a localized outage, even if the status indicator is green.

Step 2

Sign out of iMessage and FaceTime on all your Apple devices. Log out and log back in. Try again to sign in.

Step 3

Restart your router and your broadband device, if they're separate. You may have to skip this step if you don't control those devices.

Step 4

Follow these instructions to display the machine's serial number. If the number is missing or invalid according to this web form, take the machine to an Apple Store or other authorized service center to have the problem corrected.

Step 5

Take the steps suggested in this support article. If you don't understand some of the steps or can't carry them out, ask for guidance.

Step 6

From the menu bar, select

System Preferences... Network

If the preference pane is locked, click the lock icon in the lower left corner and enter your password to unlock it. Then click the Advanced button and select the Proxies tab. If the box marked SOCKS Proxy is checked, uncheck it. You don’t need to change any other settings in the window. Click OK and then Apply. Test.

The result may be that you can't connect to the Internet at all. Revert the change if that happens, or if iMessage still doesn't work. Remember that you must Apply any changes you make in the preference pane before they take effect.

Step 7

Select from the menu bar

 ▹ System Preferences… ▹ Flash Player Storage

and click

Block all sites from storing information on this computer

Close the preference pane.

Step 8

Make sure you know the ID and password you use with iMessage. Launch the Keychain Access application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Use the search box in the toolbar of the Keychain Access window to find and delete all items with "iMessage" or "com.apple.idms" in the name. Log out and log back in.

Step 9

Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

If iMessage worked in the guest account, stop here and post your results.

Step 10

Start up in safe mode and log in to the account with the problem.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start and run than normal, with limited graphics performance, and some things won’t work at all, including sound outputand Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. After testing, restart as usual (i.e., not in safe mode) and test again.

If iMessage worked in safe mode, but still doesn't work when you restart in "normal" mode, stop here and post your results.

Step 11

Triple-click anywhere in the line below on this page to select it:

/Library/Preferences/com.apple.apsd.plist

Right-click or control-click the highlighted line and select

Services Reveal in Finder (or just Reveal)

from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash. You may be prompted for your administrator login password. Restart the computer and empty the Trash.

*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select

Go Go to Folder...

from the menu bar and paste into the box that opens by pressing command-V. You may not see what you pasted because a line break is included. Press return.

Step 12

Reset theNVRAM.

Step 13

Reset the System Management Controller (SMC).

Step 14

Reinstall OS X.

Step 15

If none of the above steps resolves the issue, make a "Genius" appointment at an Apple Store, or contact Apple Support. When you set up a support call, select "Apple ID" as the product you need help with, not the hardware model. That way, if you're not under AppleCare, you may be able to talk your way out of being charged for the call.

Nov 3, 2015 6:30 AM in response to Linc Davis

I wasn't implying that I expected to solve the issue, but rather that iMessage did not indicate any change or act any differently during either trial.


Reinstalling has already occurred. A fresh install did absolutely nothing to help the situation. 😟 I have now restored from my bootable backup.


I have checked the Wifi and Network settings, both are fine.


I most certainly will not be making a genius appointment. Apple really needs to get their act together and fine tune their software. Besides that, I'm using:

  1. An upgraded processor that they didn't offer to their customers because it wasn't available at the time.
  2. I am also using an nVidia graphics card with web drivers, which they do not fully support.
  3. Lastly, I have upgraded the airport card to support continuity and handoff.


All their gonna do is blame the hardware... The only hardware the iMessage system needs it my board-id, serial number and uuid if it even needs that much. None of these upgrades affect the performance of Messages in Yosemite, so I know it's not the hardware but I can't convince Apple of that.


I do appreciate your trying but I need to keep trying. Something has got to give here.

iMessages not working since upgrade to El Capitan

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.