Issues with RWA in SBS 2011

On December 26, 2013, in news, by

Just a fyi to all in the various communities

There are two symptoms lately with failing to connect to RWA

A 404 error message on a web site when the user is running Windows 8.1 or Windows 7 with IE11 = fix it with placing the url in the trusted site zone and in compat mode. Do not start ripping out your IIS – instead read SBS 2011’s latest update rollup is also supposed to fix this but some have reported it doesn’t and I haven’t been able to get a confirm/deny from anyone to confirm or deny it doesn’t fix it.

Next one is RWA failing to connect to desktops, but an IIS reset will temporarily fix it:

Threads in the forum:

..and more folks below reporting. The root cause is .net 4.5.1 being installed.

you can’t easily remove 4.5.1 as it pulls out .net 4 so you have to reinstall .net 4 and then fix up the pools as they will flip over to .net 2 rather than the .net 4 they need to be (see s for the grid of what IIS pool needs to be what .net


throw more ram at the box and adjust the Exchange (see

IF you are impacted can you grab the info below before stomping on Exchange please?

Could you please help to let us know the top 5 processes which consume the RAM most using the below powershell script when this out-of-memory issue happens?

(Get-WmiObject -class Win32_Process) | select Name,{$_.GetOwner().User},WorkingSetSize | sort -Property WorkingSetSize -Descending | select -First 5


4 Responses to Issues with RWA in SBS 2011

  1. I adjusted the Exchange Cache but the RWA Connect computer still stops working. It is happening on all of my SBS 2011 boxes. I adjusted the Exchange cache on one SBS box that has 32 gb of ram and now users are able to connect to their computers but the system seems sluggish.
    One SBS box with 16gb RAM stops user computer access within 24 hours. Top memory usage now is below.

    Edge transport

  2. Mark Zagorski says:

    Hi – I have a case open with Microsoft CSS / Escalation.

    Will keep this thread posted. Have this on multiple servers and had this case open for a couple of weeks in an effort to get to a decent work around. We have stomped on Exchange and SQL too but to no real avail. We have also done a web.config workaround to ignore the memory limit for /remote but are working on the .net 4.5.1 update being the culprit (we think!)

    Kind Regards,


  3. It started working after I installed Exchange 2010 SP3 and the rest of the updates.

  4. bradley says:

    If you rebooted the server it would make the ram requirements settle down. If 4.5.1 was installed you’ll see this issue again.