none
WAS entries in sytem logs

    Question

  • I was getting the well known was errors for the sccm wsus app pool issue stopping, etc., and I applied the necessary hotfixes, worked with Microsoft Pro services and the whole schmear and got it taken care of. THen with one of the more recent CB upgrades I started having similar issues so I bumped up the IIS private memory and queue settings and resolved the issue again. Unfortunately I am now getting WAS warnings on the following app pools: ccm clien deployment pool, default app pool, sms distribution points pool, configmgr service portal pool and configmgr application web service pool. I would get these warnings occasionally, but am now getting a handful a day for each app pool. It's kind of like wsus turfed off the load to these other app pools. Is this something I need to be concerned about or is this just their average recycling processes after inactivity or something along those lines? Thanks.
    Monday, June 18, 2018 10:40 PM

All replies

  • Have you also cleaned up the WSUS catalog?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, June 19, 2018 1:09 AM
  • Sorry just now getting to this, never got the notification that this had been responded to.  Also tried to log in with above account and now M$ says it doesn't exist.  Anyway, if you are talking about going into wsus and choosing the 5 or 6 options like cleaning up outdated updates and accounts that haven't reported in for a while and that kind of thing, the answer is yes.
    Friday, July 06, 2018 7:09 PM
  • No, that does little to nothing in the way of cleaning of WSUS in the context of ConfigMgr.

    Have you
    - Declined all superseded updates directly in WSUS?
    - Adjusted the private memory limit on the WSUS IIS App Pool?
    - Adjusted the queue length on the WSUS IIS App Pool?
    - Reindexed the DB and rebuilt its statistics?
    - Applied the latest CU to the OS hosting the WSUS instance?
    - Declined version Next updates?
    References:
    - https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/
    - http://blog.ctglobalservices.com/configuration-manager-sccm/kea/house-of-cardsthe-configmgr-software-update-point-and-WSUS/
    - https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/
    - https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/
    - https://support.microsoft.com/en-us/help/4163525/high-bandwidth-use-when-clients-scan-for-updates-from-local-wsus-serve


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, July 10, 2018 11:10 PM
  • Actually I have done all of the above in addition to running the wizard to clean out wsus.
    Wednesday, July 11, 2018 2:43 PM
  • So, then your system may be undersized for its load.

    Whether you should be concerned or not is up to you though and whether it's affecting your environment's ability to manage your systems.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, July 11, 2018 2:50 PM
  • I worked directly with a Microsoft consultant (contracted an engagement) when standing up this environment and we addressed right sizing.  I have not experienced negative repercussions, I just keep seeing these entries in the logs. We even had a follow up engagement not too long ago and ran the rap tool and it didn't find anything in regard to this particular issue, other than to check the indexing of the databases, which we did with our DBAs and it is up to snuff.  Perhaps I am concerned over erroneous entries. 
    Wednesday, July 11, 2018 2:59 PM