YCAT74

Q: El Capitan - My Faith in Apple is severely dented!

Two days ago I installed El Capitan and about three hours later I could not connect the Internet receiving a message advising me that I do not have permissions and that access is denied. Having then quit all cloud based Applications I rebooted my MacBook Pro and was able to re-gain some Internet access however since then I have not been able to connect to iTunes or the App Store being advised that there is an unexpected error!

 

Each time I try to execute any cloud based software such as Dropbox, one drive, Google Drive etc. My Internet connection is interrupted and I am advised again that I do not have permission and access is denied.

 

I am also unable to access my Microsoft exchange account or my personal email which utilises Google mail when I try to use Microsoft outlook.

 

Also my MacBook Pro can no longer seem to access my Apple TV, i occasionally receive a message saying cannot connect but often it simply just hangs and I get no response!

 

Completely at a loss as to how to correct all of these problems particularly as I cannot access the App Store and therefore will not be able to access any updates that Apple intend to release.

 

I see that a number of users are having similar problems albeit they do not have the collection of problems defined above. Has anybody suffered to the same extent and does anybody have any ideas on what can be done?

MacBook Pro with Retina display, OS X El Capitan (10.11)

Posted on Oct 4, 2015 1:34 PM

Close

Q: El Capitan - My Faith in Apple is severely dented!

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Oct 4, 2015 1:58 PM in response to YCAT74
    Level 10 (207,990 points)
    Applications
    Oct 4, 2015 1:58 PM in response to YCAT74

    Launch the Console 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.

    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.

  • by YCAT74,

    YCAT74 YCAT74 Oct 6, 2015 12:25 PM in response to Linc Davis
    Level 1 (0 points)
    Oct 6, 2015 12:25 PM in response to Linc Davis

    06/10/2015 23:22:38.081 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 23.21.174.243:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:38.082 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 50.17.180.149:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:38.082 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 50.17.206.85:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:38.082 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 54.235.208.205:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:38.083 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 107.20.198.113:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:38.083 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 54.243.76.207:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:38.083 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 54.243.109.150:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:38.083 Core Sync[423]: tcp_connection_destination_perform_socket_connect 112 connectx to 23.23.122.138:443@0 failed: [1] Operation not permitted

    06/10/2015 23:22:57.000 kernel[0]: Google Chrome He[856] triggered unnest of range 0x7fff91400000->0x7fff91600000 of DYLD shared region in VM map 0x8b6b633eb9c0d74b. While not abnormal for debuggers, this increases system memory footprint until the target exits.

    06/10/2015 23:22:59.000 kernel[0]: Google Chrome He[858] triggered unnest of range 0x7fff91400000->0x7fff91600000 of DYLD shared region in VM map 0x8b6b633eb26c0f8b. While not abnormal for debuggers, this increases system memory footprint until the target exits.

    06/10/2015 23:23:11.240 Skype[726]: tcp_connection_destination_perform_socket_connect 64 connectx to 111.221.123.231:80@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.045 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 54.221.212.250:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.045 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 54.225.207.22:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.046 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 23.21.114.16:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.046 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 107.21.119.235:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.046 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 23.21.108.239:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.046 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 54.243.247.94:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.046 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 54.225.141.163:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:38.047 Core Sync[423]: tcp_connection_destination_perform_socket_connect 113 connectx to 107.20.189.185:443@0 failed: [1] Operation not permitted

    06/10/2015 23:23:41.429 WindowServer[173]: _CGXRemoveWindowFromWindowMovementGroup: window 0x40 is not attached to window 0x41

    06/10/2015 23:24:02.277 awacsd[179]: tcp_connection_destination_perform_socket_connect 36 connectx to 17.151.226.32:443@0 failed: [1] Operation not permitted

    06/10/2015 23:24:02.278 awacsd[179]: KV HTTP 0

  • by Linc Davis,

    Linc Davis Linc Davis Oct 7, 2015 1:45 PM in response to YCAT74
    Level 10 (207,990 points)
    Applications
    Oct 7, 2015 1:45 PM in response to YCAT74

    Please read this whole message before doing anything.

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

    The purpose of the test is to determine whether the problem is caused by third-party software that loads 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.

    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 login 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 the test.