[ms office - o365] Extremely slow loading files from network share

[neonetman]

I've an issue with users currently where it can take over 30 seconds to load an Excel file from a network share (other Office apps are slow, but not this slow). Loading from local disk is lightning fast.

 

I've added the location to the trusted locations in Excel, and nothing seems to make a difference. Has anyone seen this, and better still has anyone managed to resolve it.

 

It seems to be an issue that has just occurred recently

 

Cheers hive mind

[chaplic]

Is there a difference between opening a file when excel is open and opening a file with an open excel (I recall there's a slightly different protocol in play). I had that issue against a netapp fileserver with a firewall locked down tighter than normal.

 

Assuming a simple file copy to the local machine vs open in excel is drastically different?

 

Are you definetly connecting (at least) SMB v2?

 

Time to get wireshark out and a google to pick through how SMB protocol works. Happy ANDXing!

[neonetman]

It is different yes - if I open the file from within Excel it's fast. It's only if I double click the file, so it opens Excel itself that it's slow.

 

I've checked both the server and workstation, and SMB1 is disabled on both, whilst SMB2 is enabled on both

[chaplic]

Might be DDE stuff then Excel slow to open second (or subsequent) file - Microsoft Q&A although the stated description is 100% the other way round

 

Try a CSV file too for comparison. What's the target fileserver?

[neonetman]

I've tried this fix, and it made no improvement. CSV files are the same sadly.

 

The server is Server 2019 standard

[chaplic]

In scenarios like that I'd be

 

a) measuring so you know what best-case looks like (time simple file copy vs opening via excel)

 

b) divide-and-conquer - can you repro it on something about as different as possible then move closer to your client (e.g. macbook, then non domain joined windows PC, server, PC not in normal OU for GPOs)

 

c) running procmon and wireshark traces to see what sticks out - though the skill can be knowing what to ignore and time box any rabbit holes you may go down. Sometimes the issue is blatantly obvious.