IIS 7 and Above
Known Issues and Workarounds
Requests hangs in RequestAcquireState - unable to install hotfix KB28...
Last post May 13, 2016 11:12 AM by Markus-AD
Feb 10, 2015 03:31 AM|Markus-AD|LINK
We have the problem described here:
Unfortunately the downloaded hotfix does not work and reports:
Software Update KB2828841 Installation Wizard does not apply, or is blocked by another condition on your computer.
I guess that the hotfix does not work because we already have .NET 4.5.1 installed.
Does anybody else have the same problem and was able to solve it?
Feb 10, 2015 10:12 PM|Pengzhen Song - MSFT|LINK
You can try using .Net 4.5.2 to check if it has same issue. And I suggest that you can refer to the document to troubleshooting:
#Troubleshoot hanging requests on IIS in 3 steps
Feb 17, 2015 10:11 AM|Markus-AD|LINK
we already had .Net 4.5.2 running and the problem also appears there.
We already know what the problem is but Microsoft has to solve it:
When a request is made the session for that request gets locked and should be unlocked by the end of the request.
When it takes too long to process (e.g. longer than 30 seconds) the client may cancel the request to the server.
But the server does not fully cleanup the running request. The EndRequest is not called and therefore the session is still blocked.
More and more retries are waiting and wasting CPU which leads to other blocked sessions and suddenly the whole IIS can't do anymore.
Maybe the only solution is to uninstall everything, install the hotfix and re-install everything.
But that could not be the way. Microsoft should create a new hotfix or service pack (for .NET).
You can test it on your own:
Create an application which locks the session in the beginrequest, than wait and release the session in endrequest.
When open connection are closed by the client the Endrequest is not always called.
Aug 15, 2015 05:49 AM|lindelepalais|LINK
do someone know if there is an hotfix available for .NET 4.0?
I need to apply this hotfix but I can't update the target in the webapp in which the problem is occuring.
May 13, 2016 10:46 AM|Andy Donaldson|LINK
Did you have any luck with resolving this issue?
We are seeing similiar behaviour running 4.5.2
Were you able to get confirmation that the hotfix is indeed included in .Net 4.5.2?
May 13, 2016 11:12 AM|Markus-AD|LINK
we were not able to solve our problem.
Instead we installed a new machine with Windows 2012 R2 and have not experienced the problem again.
I think Microsoft is not interested to solve such "old" problems.