Hello,

I have a user that is having problems opening some Excel files(.xlsx) from a specific folder on the network. I can open them fine with Excel 2013 and others can as well, even at the user's location which is off-site from the main building. These files are about 2.5 to 3.5Mb in size. I could open a 62Kb file on the persons computer but the larger files Excel just sits there with the spinning cursor and the program window 'blinks', kind of like when you make it the active window then click somewhere else then back. I can go up one level then into a different folder and have no issues opening Excel files there. I've tried opening through Safe Mode but it has the same behavior, performed a repair on Office as well as an Open and Repair on the file, made sure it was a trusted location  and disabled hardware acceleration. Nothing is working. What else can I try to troubleshoot this issue?

On a side note and I'm not sure if this is helpful but when they tried opening the file, I never saw the temp file created like I do when you open any Office document.

• Edited by AJ39 Tuesday, March 31, 2015 5:38 PM extra info

I tried both and at first the xlsb file was hanging but I logged off to try other things under my account then logged back on again and it opened though pretty slow. I tried from my account as well and it is very slow but does eventually open. Under the users account I copied the file to her desktop and it opens with no problem. The permissions are the same on all similar level folders yet the user can open Excel files from them with no problem and even larger than the problem files.

Edit: My mistake, the green progress bar happens on other folders as well. Talking with one of the senior IT who installed the system, this user is the last person of a chain from microwave>switch and fiber link>another switch and fiber link so just may be a physical issue though from my experience the one folder 'seems' to have the most trouble in opening the Excel files.

Also tried disconnecting the network drive then reclogging to let the scripts recreate it. No luck with that approach either.

• Edited by AJ39 7 hours 8 minutes ago