Share via

GetErrorFromResult. CFNetwork error code. {"ErrorCode": 15, "ErrorCode.extValue": -1001}

Anonymous
2017-02-21T02:11:31+00:00

Outlook for Mac 2016 stuck in Connecting status for 20-30 minutes few times a week. Outlook and Mac OS are both latest versions. OWA and internet works fine. Outlook on iPhone also works fine at the same time. At the same profile configured gmail account, it also can't send or receive emails. Both Exchange and gmail account starts working at the same time.

Below few logs:

Http request is timed out.

HttpRequest::SendRequestInternal {"RequestID": "***", "ConnectionID": "***", "PreAuth": false, "RetryCount": 1, "Result.value": 15, "Result.extvalue": -1001}

Calling sink on request state changed {"RequestID": "***", "RequestState": "onError", "ErrorCode": 15}

{"Details": "Request 0x6000006d23d0 on CHttpConnection 0x7fe8ef9b3be8, Host: mail.***.com, Port: 443, SSL: 1, StdAuth: 0; RS:DONE"}

Sending request is done. {"RequestID": "***", "RequestTimedOut": true, "Result.value": 15, "Result.extvalue": -1001, "RequestAborted": false}

GetErrorFromResult. CFNetwork error code. {"ErrorCode": 15, "ErrorCode.extValue": -1001}

SendMessageInternal: Failure {"ErrorCode": -1001, "Error": "An operation on the server timed out. The server may be down, overloaded, or there may be too much net traffic.", "Explanation": "", "SOAPAction": null}

CNetworkMonitor::CheckIfConnected IPv6 only

CNetworkMonitor::CheckIfConnected IP reachability check {"kSCNetworkReachabilityFlagsTransientConnection": false, "kSCNetworkReachabilityFlagsReachable": true, "kSCNetworkReachabilityFlagsConnectionRequired": false, "kSCNetworkReachabilityFlagsConnectionOnTraffic": false, "kSCNetworkReachabilityFlagsInterventionRequired": false, "kSCNetworkReachabilityFlagsConnectionOnDemand": false, "kSCNetworkReachabilityFlagsIsLocalAddress": false, "kSCNetworkReachabilityFlagsIsDirect": false, "kSCNetworkReachabilityFlagsConnectionAutomatic": false}

CNetworkMonitor::CheckIfConnected Hostname reachability check {"kSCNetworkReachabilityFlagsTransientConnection": false, "kSCNetworkReachabilityFlagsReachable": true, "kSCNetworkReachabilityFlagsConnectionRequired": false, "kSCNetworkReachabilityFlagsConnectionOnTraffic": false, "kSCNetworkReachabilityFlagsInterventionRequired": false, "kSCNetworkReachabilityFlagsConnectionOnDemand": false, "kSCNetworkReachabilityFlagsIsLocalAddress": false, "kSCNetworkReachabilityFlagsIsDirect": false, "kSCNetworkReachabilityFlagsConnectionAutomatic": false}

Exchange Get FolderIDs {"Error code": -1001}

Monitorable Autodiscover TestEWSSettings Exception {"Error": -1001}

Monitorable Autodiscover TestEWSSettings {"Error": -1001}

Outlook | MacOS | Legacy Outlook for Mac | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2017-02-22T03:08:09+00:00

    Hi Robert,

    All right. Take you time please. Feel free to post back any updates when you have time.

    Regards,

    Mouran

    0 comments No comments
  2. Anonymous
    2017-02-21T07:10:03+00:00

    Hi Mouran,

    1. Will try to create a new profile.
    2. Switching to a different network environment does not help, even switching to mobile hotspot.
    3. Version of the Outlook for Mac client is 15.31 (170216)
    4. It is not an Office 365 account, it is the Enterprise Exchange Server Version 15.0 ‎(Build 1178.4)‎. Will try to configure the same account on to another Mac machine’s Outlook for Mac client.
    5. Current account was restored from backup after a fresh installation of the Office for Mac applications.

    Regards,

    Robert

    0 comments No comments
  3. Anonymous
    2017-02-21T06:51:13+00:00

    Hi Robert,

    I’d like to share some suggestions with you:

    1. Try creating a new Outlook for Mac profile to see if there is any improvement.
    2. Try switching to a different network environment and test again. For example, if this issue happens to the Office network, you can switch to your home network to see if the issue persists.

    Meanwhile, I’d like to collect some more information to better understand the issue:

    1. The detailed version of the Outlook for Mac client.
    2. What if you configure your Office 365 account on to another Mac machine’s Outlook for Mac client, does the same issue happen?
    3. The detailed steps of how you set up your Office 365 account into the Outlook for Mac client.

    Looking forward to your updates.

    Regards,

    Mouran

    0 comments No comments