HNickM
Level 1 (9 points)
Mac OS X

Q: Error trying to sign-in

When I try to login (to download an app), I get:

"An unexpected error occurred while signing in."

"AMD-Action:authenticate:SP"

 

Any help appreciated.

Mac mini, OS X El Capitan (10.11.2), 16 GB, iPhone 6, iPad mini

Posted on Jan 1, 2016 8:51 AM

by HNickM,Solvedanswer
HNickM HNickM
Level 1 (9 points)
Mac OS X
A:

Solved the problem. For those who may have the same problem:

I run a Sandbox to protect my root drive system files.

In creating the sandbox, an alias of the /Users file is put on the sandbox.

Apparently, there is a bug in ElCap (really?).

It's supposed to be following the symlink, but is not.

The solution is to replace the alias with a copy of the original file.

Enjoy.

Posted on Jan 24, 2016 6:37 AM

Close
HNickM

Q: Error trying to sign-in

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Jan 1, 2016 3:26 PM in response to HNickM
    Level 10 (207,963 points)
    Applications
    Jan 1, 2016 3:26 PM in response to HNickM

    Can you sign in to the iTunes Store, or the iBooks Store?

  • by HNickM,

    HNickM HNickM Jan 1, 2016 5:13 PM in response to Linc Davis
    Level 1 (9 points)
    Mac OS X
    Jan 1, 2016 5:13 PM in response to Linc Davis

    Hi Linc Davis,

    Thanks for your reply trying to help.

    Yes, my login works for iTunes and this discussion page.

  • by Linc Davis,

    Linc Davis Linc Davis Jan 1, 2016 5:31 PM in response to HNickM
    Level 10 (207,963 points)
    Applications
    Jan 1, 2016 5:31 PM in response to HNickM

    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 HNickM,

    HNickM HNickM Jan 8, 2016 8:19 AM in response to Linc Davis
    Level 1 (9 points)
    Mac OS X
    Jan 8, 2016 8:19 AM in response to Linc Davis

    Hi Linc Davis,

    I went to the App Store. Clicked on "Purchased". Message said I had to login. Did. Got the same error "Unexpected error…".

    Password woks for iTunes and this forum.

    Thanks for helping,

    Nick

     

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-read-data /Volumes/Macintosh HD1/Users/Shared/adi/adi.pb

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-read-data /Volumes/Macintosh HD1/Users/Shared/adi/adi-000001F5.pb

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-read-data /Volumes/Macintosh HD1/Users/Shared/SC Info/SC Info.sidd

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-write-data /Volumes/Macintosh HD1/Users/Shared/adi/adi.pb.lck

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-write* /Volumes/Macintosh HD1/Users/Shared/adi/adi.pb

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-write-data /Volumes/Macintosh HD1/Users/Shared/adi/adi.pb

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-write* /Volumes/Macintosh HD1/Users/Shared/adi/adi-000001F5.pb

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-write-data /Volumes/Macintosh HD1/Users/Shared/adi/adi-000001F5.pb.lck

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-write* /Volumes/Macintosh HD1/Users/Shared/adi/adi-000001F5.pb

    1/8/16 11:14:31.000 AM kernel[0]: Sandbox: storeaccountd(410) deny(1) file-write-data /Volumes/Macintosh HD1/Users/Shared/adi/adi-000001F5.pb

  • by HNickM,

    HNickM HNickM Jan 14, 2016 5:45 PM in response to HNickM
    Level 1 (9 points)
    Mac OS X
    Jan 14, 2016 5:45 PM in response to HNickM

    You may be interested to know that my AppleCare second level CSR couldn't fix it either. They forwarded my case to "Engineering'.

    Perhaps back to Yosemite.

  • by HNickM,Solvedanswer

    HNickM HNickM Jan 24, 2016 6:37 AM in response to HNickM
    Level 1 (9 points)
    Mac OS X
    Jan 24, 2016 6:37 AM in response to HNickM

    Solved the problem. For those who may have the same problem:

    I run a Sandbox to protect my root drive system files.

    In creating the sandbox, an alias of the /Users file is put on the sandbox.

    Apparently, there is a bug in ElCap (really?).

    It's supposed to be following the symlink, but is not.

    The solution is to replace the alias with a copy of the original file.

    Enjoy.