Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, July 18, 2012 5:56 AM
Hey guys,
we are having a strange issue with our SCCM 2012 / WSUS Server. The Server is W2k8R2 and we are installing Wsus 3.0 SP2.
Since Friday everything was working (Whole SCCM2012 with WSUS SUP installed). Then on Friday something happened and WSUS is no longer working. We already reinstalled it several times. But suddenly after the WSUS installation (tried .exe and Add or remove features) it is already broken.
- The Console only shows "Service unavailable" with a Button Reset Server Node
- All Services a Running
- When trying to open The WSUS Console the IIS Application Pool "Wsus Pool" is stopped
Here are some Event Logs:
Application Error:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
Exception code: 0xe0434352
Fault offset: 0x000000000000cacd
Faulting process id: 0x141c
Faulting application start time: 0x01cd64a70072cec1
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 3e5d5bdc-d09a-11e1-a2f5-00155d2c1824
Application Information (WAS is installed)
The description for Event ID 5002 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
WsusPool
I would really appreciate your help!!
Thanks a lot and best regards
Philipp
All replies (14)
Wednesday, July 25, 2012 7:36 AM âś…Answered | 2 votes
Hey guys.. just to let you know. There was no way to solve this. We reinstalled the Whole Server from scratch. We have still no idea what caused this issue.
best regards
Philipp
Thursday, July 19, 2012 6:42 PM
Since Friday everything was working (Whole SCCM2012 with WSUS SUP installed). Then on Friday something happened and WSUS is no longer working.
So, first question would be: What happened on Friday? What changed on this system?
When trying to open The WSUS Console the IIS Application Pool "Wsus Pool" is stopped
Well, that's certainly a fatal condition.
The description for Event ID 5002 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted.
The Windows Process Activation Service is a required component of the Web Server role on Win2008R2. It would seem it got broken. First question would be whether the service is running, or can be started. If not, then start with KB975443.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Tuesday, July 24, 2012 1:56 PM
Anyone figure this one out? The same thing is happening to us. It seems to have happened after installing a group of Windows updates made available last week.
Friday, August 15, 2014 6:14 PM | 15 votes
Hey Guys, same issue here. I wound up opening a call with MS and found a solution for my environment, try at your own risk.
1. open IIS
2. Navigate to the Application Pools
3. Right click the WSUSPool and select "advanced settings'
4. Locate the "Private Memory Limit (KB). Mine was set to "1843200" MS informed me to set this to "7843200" and restart the WSUSPOOL.
After this process, I initiated a synchronize software updates from my SCCM server and I'm back in business.
josh
Friday, August 15, 2014 11:14 PM | 6 votes
4. Locate the "Private Memory Limit (KB). Mine was set to "1843200" MS informed me to set this to "7843200" and restart the WSUSPOOL.
That does seem to be the default....Since the only digit that changed was the '1' to a '7', makes ya wonder if somebody didn't misread some guidance somewhere when they programmed the initial configuration settings for the AppPool.
So, effectively, this delays the recycle of the AppPool until it has consumed ~7GB of memory instead of recycling it at ~1GB of memory.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.
Thursday, March 19, 2015 12:42 AM
Wow, thanks guys, it works for me
Thursday, March 19, 2015 2:43 PM
Absolute genius! Worked like a charm! :)
Wednesday, April 8, 2015 1:43 AM
I had the same issue following Patch Tuesday in March.
This Wsuspool memory adjustment cleared the issue for me.
Nick.
Thursday, April 30, 2015 11:53 AM
I solved this problem by reinstalling .net framework 4.5.2
Wednesday, October 14, 2015 9:29 PM
Me funciono tal cual se explica, muchas gracias
Wednesday, November 11, 2015 12:18 AM
Appears to be working for me as well now, thanks for the tip!
Wednesday, April 13, 2016 11:41 AM | 1 vote
That looks about right, as per Microsoft's recommended settings.
The computer that hosts a software update point requires the following configurations for IIS Application Pools:
Increase the WsusPool Queue Length to 2000
Increase the WsusPool Private Memory limit x4 times, or set to 0 (unlimited)
REF: https://technet.microsoft.com/en-us/library/mt589500.aspx
I also had this issue, and it corrected the issue for me as well.
Tuesday, April 26, 2016 12:31 AM | 1 vote
A Microsoft engineer posted a blog article on some IIS app pool settings changes that were made at a customer's site to resolve a similar issue:
Friday, May 27, 2016 2:54 PM
This worked for me on Server 2012R2 WSUS.