biohazerd

Yes, by disabling I meant I set it to '0' or unlimited. Apologies for the confusion.

I'd like to preface this post by saying I've performed many SCCM/SUP installs and never had an issue like this before. We recently decided to rebuild our WSUS server and been having nothing but problems, and believe the issue may reside with IIS itself but I'm not quite sure. Our WSUS environment is not complex at all, it's a single server that connections directly to Microsoft without proxy settings. Please let me know if any other logs or information would be helpful. Any help or suggestions would be greatly appreciated! Environment Details Type: Single Primary Site Server SCCM Version: SCCM R2 SP1 CU1 (5.0.8239.1203) OS Version: Server 2012 R2 (WSUS and SCCM) Hardware: Hosted on vmWare ESX6.0 (6 Cores, 12GB RAM) WSUS DB: Default Timeline of Events Built WSUS Server Installed WSUS and IIS Roles Installed all applicable updates Installed SUP Site System Roll on WSUS Verified role was successfully installed Started WSUS Sync Sync starts successfully This is when things start going awry. The following Informational Log will be logged in the WSUS Event Log five or six times: A worker process serving application pool 'WsusPool' has requested a recycle because it reached its private bytes memory limit. Then this Error message is logged in the WSUS Event Log: Application pool 'WsusPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. Here are the full details of the WSUS WAS Event Log: Log Name: System Source: Microsoft-Windows-WAS Date: 9/16/2015 3:57:28 PM Event ID: 5002 Task Category: None Level: Error Keywords: Classic User: N/A Computer: xxx-wsus.xxxxxxxxxx.org Description: Application pool 'WsusPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="49152">5002</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-09-16T20:57:28.000000000Z" /> <EventRecordID>4099</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>xxx-wsus.xxxxxxxxxx.org</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">WsusPool</Data> <Binary> </Binary> </EventData> </Event> Log Name: System Source: Microsoft-Windows-WAS Date: 9/16/2015 3:56:28 PM Event ID: 5117 Task Category: None Level: Information Keywords: Classic User: N/A Computer: xxx-wsus.xxxxxxxxxx.org Description: A worker process serving application pool 'WsusPool' has requested a recycle because it reached its private bytes memory limit. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="16384">5117</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-09-16T20:56:28.000000000Z" /> <EventRecordID>4098</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>xxx-wsus.xxxxxxxxxx.org</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">WsusPool</Data> <Binary> </Binary> </EventData> </Event> Log Name: System Source: Microsoft-Windows-WAS Date: 9/16/2015 3:55:28 PM Event ID: 5117 Task Category: None Level: Information Keywords: Classic User: N/A Computer: xxx-wsus.xxxxxxxxxx.org Description: A worker process serving application pool 'WsusPool' has requested a recycle because it reached its private bytes memory limit. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="16384">5117</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-09-16T20:55:28.000000000Z" /> <EventRecordID>4097</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>xxx-wsus.xxxxxxxxxx.org</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">WsusPool</Data> <Binary> </Binary> </EventData> </Event> Log Name: System Source: Microsoft-Windows-WAS Date: 9/16/2015 3:54:28 PM Event ID: 5117 Task Category: None Level: Information Keywords: Classic User: N/A Computer: xxx-wsus.xxxxxxxxxx.org Description: A worker process serving application pool 'WsusPool' has requested a recycle because it reached its private bytes memory limit. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="16384">5117</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-09-16T20:54:28.000000000Z" /> <EventRecordID>4096</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>xxx-wsus.xxxxxxxxxx.org</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">WsusPool</Data> <Binary> </Binary> </EventData> </Event> Log Name: System Source: Microsoft-Windows-WAS Date: 9/16/2015 3:53:28 PM Event ID: 5117 Task Category: None Level: Information Keywords: Classic User: N/A Computer: xxx-wsus.xxxxxxxxxx.org Description: A worker process serving application pool 'WsusPool' has requested a recycle because it reached its private bytes memory limit. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="16384">5117</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-09-16T20:53:28.000000000Z" /> <EventRecordID>4095</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>xxx-wsus.xxxxxxxxxx.org</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">WsusPool</Data> <Binary> </Binary> </EventData> </Event> We can see the final error in the above Event Log occurs at 3:57:28 PM which then causes the WSUS Sync to fail soon after. Here is the wsyncmgr.log for that same time period: Synchronizing update b15b5258-cf26-4a7e-8697-18691f416d35 - Security Update for Windows Server 2008 R2 for Itanium-based Systems (KB2544893) SMS_WSUS_SYNC_MANAGER 9/16/2015 3:56:53 PM 11048 (0x2B28) Synchronizing update 1330db53-75ff-4d87-9270-6a5449a67ad7 - Security Update for Windows Server 2008 R2 x64 Edition (KB2544893) SMS_WSUS_SYNC_MANAGER 9/16/2015 3:57:41 PM 11048 (0x2B28) sync: SMS synchronizing updates, processed 969 out of 6795 items (14%), ETA in 01:29:23 SMS_WSUS_SYNC_MANAGER 9/16/2015 3:57:55 PM 11048 (0x2B28) Synchronizing update 356293c8-36ff-40f7-bb26-8b5d4822c5e8 - Security Update for Windows Server 2008 x64 Edition (KB2544893) SMS_WSUS_SYNC_MANAGER 9/16/2015 3:57:56 PM 11048 (0x2B28) Failed to sync update 356293c8-36ff-40f7-bb26-8b5d4822c5e8. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetInstallableItems SMS_WSUS_SYNC_MANAGER [b]9/17/2015 3:57:56 PM[/b] 14800 (0x39D0) Once the above errors occur the WSUS IIS App Pool is wrecked. The App Pool stops and while it can be restarted it'll eventually crash again and the WSUS console cannot be opened nor can SCCM reconnect. Finally here is the WCM.Log showing SCCM trying to reconnect to WSUS: Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 9/16/2015 4:02:48 PM 9808 (0x2650) Attempting connection to WSUS server: xxx-wsus.xxxxxxxxxx.org, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/16/2015 4:02:48 PM 9808 (0x2650) System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONFIGURATION_MANAGER 9/16/2015 4:02:48 PM 9808 (0x2650) Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 9/16/2015 4:02:48 PM 9808 (0x2650) STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=xxx-sccm1.xxxxxxxxxx.org SITE=xxx PID=13904 TID=9808 GMTDATE=Wed Sep 16 21:02:48.489 2015 ISTR0="xxx-wsus.xxxxxxxxxx.org" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 9/16/2015 4:02:48 PM 9808 (0x2650) As seen above SCCM cannot connect to WSUS because the App Pool is down. Notes I've attempted this role installation multiple times with the same results I've tried this Role install three times on fresh WSUS servers The App Pool crashes appear to happen at anytime during any phase of the synchronization I've tried disabling Private Memory Limit on the App Pool Next Steps I think next I'm going to enable logging and debugging on IIS to see if I can get more details on what's happening. If anyone has any other ideas or suggestions, please let me know. a

I've run into a strange problem and I'm not sure if it's a bug or something isn't functioning properly or if it's just the way Config Mgr Clients work. If I boot WinPE from PXE or USB media and run an OSD task sequence multicast works perfect. If I run the same OSD task sequence from the ConfigMgr Client on a machine (which just downloads WinPE and then boots into it) when it reboots into WinPE it starts downloading the OS image via unicast instead of multicast. I'm using the exact same task sequence and WinPE boot image. The OS image is even set to "Transfer this package only via multicast". The SMSTS log does not indicate that it's attempting to start a multicast session, it just starts unicast. Any ideas?

I am also interested if any has come up with a solution for this as I'm having a similar problem but I've narrowed it down a bit more. It seems that my clients start the download fine and either finish the download without problems or some just fail after a random percentage has been downloaded. Here are some error log entries from an OSD client that failed: Notice it failed at 27%, some fail at 25%, others at 89%, and some don't fail at it. It's important to remember these computers are the same model, in the same room, same switch. I downloaded the file directly from a browser, using http://XXXXX.XXXXXXX.local:80/SMS_DP_SMSPKG$/ISD0002A/sccm?/Windows.7.x64.Thick.Basic.wim, and the first time I did it it downloaded the file. On the second try it failed after only getting ~20% of the file. Does anyone have any ideas, or suggestions. What other log files can I look in? Could it be an issue with IIS?