malajmi.27

Q: Cannot sign in for iMessage, FaceTime, App Store, iTunes

Hi

I'm facing a problem when I want to sign in for iMessage, FaceTime, App Store, iTunes in my MacBook Pro..and in my iMac also... When I try to signing, just keep signing for long time and nothing happened... my internet connection is very good... but still I cannot sign in ????

 

I faced this problem long time back...and I don't know why ...

 

 

regards.

 

<Edited by Host>

MacBook Pro, OS X El Capitan (10.11.3), null

Posted on Mar 18, 2016 3:38 PM

Close

Q: Cannot sign in for iMessage, FaceTime, App Store, iTunes

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Mar 18, 2016 6:03 AM in response to malajmi.27
    Level 10 (207,926 points)
    Applications
    Mar 18, 2016 6:03 AM in response to malajmi.27

    Please launch the Console application in any one 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.

    The title of the Console window should be All Messages. If it isn't, select

              SYSTEM LOG QUERIES ▹ All Messages

    from the log list on the left. If you don't see that list, select

              View ▹ Show Log List

    from the menu bar at the top of the screen.

    Click the Clear Display icon in the toolbar. Then take an action that isn't working the way you expect. Select any lines that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    Please don't indiscriminately dump thousands of lines from the log into this discussion.

    Please don't post screenshots of log messages—post the text.

    Some private information, such as your name or email address, may appear in the log. Anonymize before posting.

    When you post the log extract, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

    If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

  • by malajmi.27,

    malajmi.27 malajmi.27 Mar 18, 2016 6:25 AM in response to Linc Davis
    Level 1 (3 points)
    Mar 18, 2016 6:25 AM in response to Linc Davis

    this is what I get:

     

    3/18/16 5:23:15.538 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:18.838 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:21.972 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:24.973 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:28.261 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:29.045 PM Spotlight[408]: XPC connection was invalidated

    3/18/16 5:23:29.212 PM QuickLookUIHelper[940]: [17:23:29.212] <<<< Boss >>>> figPlaybackBossPrerollCompleted: unexpected preroll-complete notification

    3/18/16 5:23:29.303 PM Spotlight[408]: XPC connection was invalidated

    3/18/16 5:23:29.335 PM Spotlight[408]: XPC connection was invalidated

    3/18/16 5:23:30.093 PM Spotlight[408]: XPC connection was invalidated

    3/18/16 5:23:31.117 PM Spotlight[408]: BUG in libdispatch client: kevent[EVFILT_MEMORYSTATUS] add: "Operation not supported" - 0x2d

    3/18/16 5:23:31.349 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:34.349 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:37.626 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:40.914 PM apsd[82]: Certificate not yet generated

    3/18/16 5:23:44.203 PM apsd[82]: Certificate not yet generated

  • by Linc Davis,

    Linc Davis Linc Davis Mar 18, 2016 6:31 AM in response to malajmi.27
    Level 10 (207,926 points)
    Applications
    Mar 18, 2016 6:31 AM in response to malajmi.27

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

    The serial number is private information. Please don't post it here or on any public web page.

  • by malajmi.27,

    malajmi.27 malajmi.27 Mar 19, 2016 12:15 AM in response to Linc Davis
    Level 1 (3 points)
    Mar 19, 2016 12:15 AM in response to Linc Davis

    Hi Linc

    I know to get serial number..... why I need it ?

     

    I check the link which you sent... and I get :

     

    Valid Purchase Date

     

    Telephone Technical Support: Expired

     

    Repairs and Service Coverage: Expired



  • by chroot,

    chroot chroot Mar 19, 2016 1:52 AM in response to malajmi.27
    Level 4 (1,099 points)
    Mar 19, 2016 1:52 AM in response to malajmi.27

    iTunes, the App Store, iMessage, and FaceTime use the computer's serial number when authenticating with Apple's servers.  The serial number is also flashed onto the logic board of the computer.  If you had the computer repaired and the logic board was replaced, the serial number should've been flashed onto the new logic board.  If the serial was not flashed onto the logic board it would show as Unavailable or be incorrect when checking in About this Mac.

     

    Try isolating the issue by testing in both a new user account and safe mode.

     

    How to test an issue in another user account on your Mac - Apple Support

     

    Try safe mode if your Mac doesn't finish starting up - Apple Support

  • by Linc Davis,

    Linc Davis Linc Davis Mar 19, 2016 7:49 AM in response to malajmi.27
    Level 10 (207,926 points)
    Applications
    Mar 19, 2016 7:49 AM in response to malajmi.27

    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.

  • by malajmi.27,

    malajmi.27 malajmi.27 Mar 19, 2016 8:35 AM in response to Linc Davis
    Level 1 (3 points)
    Mar 19, 2016 8:35 AM in response to Linc Davis

    I tried all steps...same problem still there .... actually the problem is in my iMac and MacBook Pro.... I created another Apple account and I try, same problem

     

    regards

  • by chroot,

    chroot chroot Mar 19, 2016 8:53 AM in response to malajmi.27
    Level 4 (1,099 points)
    Mar 19, 2016 8:53 AM in response to malajmi.27

    If it happens on multiple computers, does it happen on other networks?

  • by Linc Davis,

    Linc Davis Linc Davis Mar 19, 2016 9:22 AM in response to malajmi.27
    Level 10 (207,926 points)
    Applications
    Mar 19, 2016 9:22 AM in response to malajmi.27

    If possible, please connect to another network, such as a public hotspot or the mobile hotspot created by a phone. Do you have the same problem while connected to that network?

  • by malajmi.27,

    malajmi.27 malajmi.27 Mar 20, 2016 9:09 AM in response to Linc Davis
    Level 1 (3 points)
    Mar 20, 2016 9:09 AM in response to Linc Davis

    I tried this also.... same issue

  • by Linc Davis,

    Linc Davis Linc Davis Mar 20, 2016 10:25 AM in response to malajmi.27
    Level 10 (207,926 points)
    Applications
    Mar 20, 2016 10:25 AM in response to malajmi.27

    1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

    The test works on OS X 10.8 ("Mountain Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

    Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

    2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

    3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

    You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

    In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.

    You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

    Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

    4. Here's a general summary of what you need to do, if you choose to proceed:

    ☞ Copy the text of a particular web page (not this one) to the Clipboard.

    ☞ Paste into the window of another application.

    ☞ Wait for the test to run. It usually takes a few minutes.

    ☞ Paste the results, which will have been copied automatically, back into a reply on this page.

    These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

    5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

    You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

    6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

    7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

    8. Launch the built-in Terminal application in any one of the following ways:

    ☞ Enter the first few letters of its name ("Terminal") 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.

    Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

    9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

    If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

    If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

    10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

        Test started
            Part 1 of 4 done at: … sec
            …
            Part 4 of 4 done at: … sec
        The test results are on the Clipboard.
        Please close this window.

    The intervals between parts won't be exactly equal, but they give a rough indication of progress.

    Wait for the final message "Please close this window" to appear—again, usually within a few minutes. If you don't see that message within about 30 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something.

    In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

    11. When the test is complete, or if you stopped it manually, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

    At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

    If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

    12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

    If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

    13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

    14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

    15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

  • by exult,

    exult exult Aug 7, 2016 6:46 AM in response to malajmi.27
    Level 1 (8 points)
    Aug 7, 2016 6:46 AM in response to malajmi.27

    Same  problem here. My IPhone 5 not sign in with iMessage and Face Time, How can solve this problem