One folder on the server becomes slow until reboot

C

Craig Maunder

I have been looking for a solution to this issue that I have never seen before.


Scenario:

Our client has a Windows Server 2016 with a Windows server 2012 Terminal server in Hyper-V

90% of users use thin client into 2012 TS - no issues.

Only 1 PC on site. It uses TS and local access to 2016 server.
They run a program directly off the server - executable launches on a mapped drive. All users running from the TS run fine, no issues. After a couple of days the PC accessing from its mapped drive to the server ends up taking about 30 minutes before the app appears.
Adding to this... the same symptoms occur if you run the application from the local drive of the 2016 server.
More additionally - when this state occurs - if you try to change permissions etc on that folder where the application resides - it is also painfully slow. Only rebooting gets performance back and only for about a day.
Folders in same master folder or anywhere else on the drive are not affected - only this one folder (and its sub-folders) becomes slow (this folder is not the root of the mapped drive either - other folders in the mapped drive are performing normally).


I have seen reports about 'customizing' the folder (from documents or pictures etc to 'General Items') and have tried that. No affect.

The folder is only 1.3Gb in size... has 3000 files in 200 folders - no folder has more than 1000 files in it.


I would love some insight on this - seems like some kind of folder access limits or lockouts.

Continue reading...
 
Back
Top Bottom