Trying to connect message when Saving in Excel 365

We implemented this workaround. It seemed to resolve the issue temporarily. The web client service is still disabled, but the "connecting to server..." issues still appears.

Hopefully this can be fixed soon. Users constantly asking if I have fixed this on our network blaming their connection to our server, which is not.

TLDR

• Issue was present for us on 2207 (Build 15427.20194).
• Issue is still present for us on 2207 (Build 15427.20210).

---

BEHAVIOR

We have been fighting with the "Trying to connect to" issue for a few weeks.

End users are quite frustrated.

Can navigate to a file share and open an Excel document fine.

Can confirm it occurs when initially trying to Save As or Browse to a network share through Excel.

If I wait and let it figure itself out and connect, which takes anywhere from 15-60 seconds (roughly), I can do another Save As right away without issue (no pop up). But if I let it sit for awhile (exact time unknown) or open the file again later in the day - it will go through the "Trying to connect to" process all over again.

We have DFS + Redirected Desktop and Documents folders.

Concerned about the long-term effects of disabling WebClient service but will give it a test today.

For those that have implemented this workaround - have you run into any issues?

---

VERSIONS

Issue was present for us on 2207 (Build 15427.20194).

Updated to 15427.20210 on a few machines yesterday.

Seemed better at first but the "Trying to connect to" message cropped up again today.

Might be my imagination but the "Trying to connect to" message seems to clear quicker on 2207.

Issue is still present for us on 2207 (Build 15427.20210).

---

Unfortunately, we also have the same issue that started with O365 version 2206 back in mid of July, with Excel, Outlook, and PowerPoint (word appears to be fine). I had to revert back to the Monthly channel which was version 2205 and it was working fine. Hoped they will push fix for it soon but unfortunately, the monthly channel now updated in Aug to 2206, and that broke it again. Reverting back to the semi-annual 2202 and it's working fine. for now. However, also disabling the WebClient (WebDAV) service seems to help, as I do not see that issue on a few computers where we disabled this service, but the problem is I cannot push it to all as many of my users also use SharePoint map network location (which is on WebDav), and disabling this service breaks this Sharepoint map.

Hello all together,
we are having the same issue with two of our customers with Version 2207 (Build 15427.20210). The users have the folderredirect mapped as UNC path. It would be nice to know if MS work on that thing and when the fix for that is planned to be released. We also don't want to break the Sharepoint map so the WebDAV workaround is no possibility for us.

I rolled back two the may version of office. I have no issues present now. This is 100% a bug in office with UNC paths.

I have ticket open with Microsoft, will update if issues is resolved.

I rolled back two the may version of office. I have no issues present now. This is 100% a bug in office with UNC paths.

I have ticket open with Microsoft, will update if issues is resolved.

I had a ticket opened with Microsoft for this issue. With the tech's assistance, we rolled back a test machine to Office version 2205 Build 15225.20288 and the UNC path issue disappeared.

His recommendation was to Disable Updates (Open WORD, File > Account > Update Options > Disable Updates) **** in that version of Office until a fix is released. He could not give me a time frame on a fix, nor would he relay the ticket notes to developers to make them aware. He sent me a feedback link to go in and put my own notes to developers.

I have been testing the rolled back version of Office for two days, and can 100% say that the UNC issue is not there.