![]() Now I do not yet understand why it uses more than the defined limit for Private Memory bytes. ![]() For whatever reason however the pool did not properly recycle within that 90 seconds, so it tried again and again with the error message below being logged 3 times in total.įinally after not being able to restart the WSUSPOOL, IIS simply gives up and leaves it in a stopped state and logs the error below. IIS then attempted to comply with this request, and the default timeout is set to 90 seconds. I found that initially you would see that IIS was requesting a recycle of the WSUSPOOL due to it reaching it’s private bytes memory limit. I spent a little time investigating it so I could find a solution. I feel that I’ve noticed this more frequently on WSUS 4.0 which runs on Windows Server 2016 than ever before to be honest. I’ve noticed on Windows Server 2016 with WSUS Server Role installed, that the WSUS console will often go into the “Reset Server Node” screen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |