I had turned oplocks off on this share and made no difference. I opened a case with Support and supplied them with PCAP log from a session with that client. I was instructed to turn oplocks back on and run the test again. The performance was what I would consider "much much faster". That PCAP log was uploaded and am still waiting for feedback. I'm also looking for another user to see if the problem persists with all users who acces this file or some.
While I would encourage you to open a case, what you've described leads me to think that your clients may benefit by disabling oplocks. There are quite a few considerations to gauge before taking that step, though, including OneFS revision and how other clients using that share would react to disabling oplocks. Another thing to look at is packet signing, as well as your OneFS configuration w.r.t. random I/O handling.
The ultimate way to determine is to get a packet capture and see if any STATUS_INVALID_HANDLE responses are being sent during oplock dialogue, amongst other things. But again I would encourage you to open a ticket.
Check the office version you are running is updated with latest MS office patch bundle. I've had this issue before and patch update fixed it. I've also experienced issues with excel when the files are placed in "my documents" folder with offline filesync enabled (MS-sync center), try storing the files directly on NAS and check the performance.
These are the issues I've run into for different versions of excel and the solutions.
DHoffman2
2 Intern
•
306 Posts
0
January 21st, 2015 12:00
I had turned oplocks off on this share and made no difference. I opened a case with Support and supplied them with PCAP log from a session with that client. I was instructed to turn oplocks back on and run the test again. The performance was what I would consider "much much faster". That PCAP log was uploaded and am still waiting for feedback. I'm also looking for another user to see if the problem persists with all users who acces this file or some.
peglarr
99 Posts
1
January 9th, 2015 13:00
While I would encourage you to open a case, what you've described leads me to think that your clients may benefit by disabling oplocks. There are quite a few considerations to gauge before taking that step, though, including OneFS revision and how other clients using that share would react to disabling oplocks. Another thing to look at is packet signing, as well as your OneFS configuration w.r.t. random I/O handling.
The ultimate way to determine is to get a packet capture and see if any STATUS_INVALID_HANDLE responses are being sent during oplock dialogue, amongst other things. But again I would encourage you to open a ticket.
Cheers
Rob
Narahari1
2 Intern
•
127 Posts
1
January 12th, 2015 13:00
Check the office version you are running is updated with latest MS office patch bundle. I've had this issue before and patch update fixed it. I've also experienced issues with excel when the files are placed in "my documents" folder with offline filesync enabled (MS-sync center), try storing the files directly on NAS and check the performance.
These are the issues I've run into for different versions of excel and the solutions.
http://support.microsoft.com/kb/324491
http://support.microsoft.com/kb/813973
http://support.microsoft.com/kb/2589410
http://social.technet.microsoft.com/Search/en-US/office?query=access%20denied%20contact%20your%20administrator%20error&Refinement=8&ac=4