Trying to connect message when Saving in Excel 365

Anonymous
2022-07-12T23:03:31+00:00

Split from this thread.

Same issue in our office. All users with O365. It started over this past weekend (07/09/2022). Only Excel files when doing a Save As, Browse. Some users experience it with File Open.

All other applications work without issue. Nothing in event viewer shows any problems.

Microsoft 365 and Office | Excel | For business | Windows

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

121 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-07-18T13:40:53+00:00

    Thanks for this info. We set our group policy to this channel and we are looking better.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-20T09:39:26+00:00

    I had to roll back to version 2022 June 14 Version 2205 (Build 15225.20288) to get this issue sorted. I hope this issue can be sorted out in the next update.

    Versions:

    Current Channel, Build 2206, Version 15330.20246 and 15330.20230 are still having issues.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-07-20T20:28:03+00:00

    I'm having the same issue within Word and Excel version 2206 build 15330.20230 throughout our office. Trying to open or save files to a UNC path causes a delay of 30 seconds or more while "contacting" or "trying to connect" to the path. Meanwhile Outlook and File Explorer can access UNC paths instantly. Never had this problem previously, and our entire office uses UNC paths. Many users throughout our office are complaining. Updated to 2206 build 15330.20266 and the problem persists. Will probably need to revert entire company to use monthly or semi-annual channel if this is not fixed promptly.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-07-20T20:42:30+00:00

    Switching to the semi-annual channel (version 2202) solved the issue temporarily for me.

    https://docs.microsoft.com/en-us/deployoffice/change-update-channels

    https://docs.microsoft.com/en-us/deployoffice/overview-update-channels

    1. Configure group policy setting
    2. Run gpupdate on a client computer
    3. Manually run the "Office Automatic Updates 2.0" task
    4. Manually check for updates within any Office application

    With the above steps, Office automatically downgraded to 2202 which fixed the problem temporarily.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-07-22T17:40:03+00:00

    The issue is with the WebClient service (Webdav).

    A wireshark trace shows that the client is attempting to reach the file server on port 80 instead of port 445.

    Disabling the WebClient service resolves the issue, and is a simple matter to push out via GPO, but of course is only a workaround.

    I confirmed this is only happening in the latest build of office. In previous versions of office, the client does not attempt port 80, and opening or saving files to the file server happens quickly and without any issue.

    This needs to be patched.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments