none
Problem with Remote Web Workplace on SBS 2011

    Question

  • Recently we've experienced a frustrating problem with RWW on a couple of our SBS 2011 installations.

    When an end users connects to RWW and logs in, she sees the computer she wants to connect to but clicking Connect does nothing.  

    Simply by running IIS Reset on the server, the problem corrects itself temporarily.

    As I mentioned this is SBS 2011 Service Pack 1 running on a Dell PowerEdge T410 server.

    I haven't found any relevant errors in the event log, although I never know when the problem starts happening, only when an EU calls to complain they can't get in.

    This is also happening at another site running SBS 2011 as well so it doesn't seem to be specific to this server. Perhaps a windows update broke something?

    Friday, December 13, 2013 7:04 PM

Answers

  • This is an old post but I once again ran into this issue!  

    Fortunately the first ANSWER in this post:

    https://social.technet.microsoft.com/Forums/en-US/bf09abb7-ad7b-4d65-a993-6fa9d53d6235/remote-access-button-stops-working-sbs-2011-standard-event-id-3-and-1309?forum=smallbusinessserver

    SOLVES the problem.  I've used this on at least 3 SBS 2011 servers.

    here it is:

    Edit (via NotePad) the web.config file in "C:\Program Files\Windows Small Business Server\Bin\WebApp\RemoteAccess

    "Find the line <serviceHostingEnvironmentaspNetCompatibilityEnabled="true" /> (near the bottom)

    Change it to be (all one line) <serviceHostingEnvironment aspNetCompatibilityEnabled="true" minFreeMemoryPercentageToActivateService="0" />

    Bounce the WWW Pub service (which will in turn bounce the RDG service).

    • Marked as answer by TanNYC Thursday, July 7, 2016 1:57 PM
    Thursday, July 7, 2016 1:57 PM
  • Hi:

    IE 11 is not quite ready for RWA, and there are reports of dot net 4.51 on the server causing issues as well.  Can you confirm that neither of these is in play?


    Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

    Saturday, December 14, 2013 12:41 AM
    Moderator
  • "simply by running IIS Reset"

    Sounds like .net 4.5.1 to me got installed on this server


    Unfortunately TechNet isn't coming back, sorry folks :-(

    Saturday, December 14, 2013 1:22 AM
    Moderator
  • Remote Access Button Stops Working SBS 2011 Standard - Event ID 3 and 1309:

    http://social.technet.microsoft.com/Forums/en-US/bf09abb7-ad7b-4d65-a993-6fa9d53d6235/remote-access-button-stops-working-sbs-2011-standard-event-id-3-and-1309?forum=smallbusinessserver


    The install of 4.5.1 on SBS 2011 is making some of these boxes now run
    out of resources.

    I opened a case for a consultant, I'm seeing more and
    more posts in the forums about this issue.

    Issue:  .net 4.5.1 is offered
    up to SBS 2011
    .net 4.5.1 is installed
    Causes more resources on the box

    If box is 'marginal' in resources it will tip it over and start causing
    issues
    Symptoms now being seen:  RWA will stop working or have issues
    connecting to the workstations

    Resolution:
    Throw more RAM at the ox

    Or throttle down Exchange memory use manually

    http://www.thirdtier.net/2012/01/solving-the-unresponsive-exchange-sbs-server-problem/


    That second article is here: How to modify the Store Database maximum
    cache size in Exchange 2000 Server <http://go.microsoft.com/fwlink/?linkid=3052&kbid=266768>


    and the link is wrong... use

    How to modify the Store Database maximum cache size in Exchange 2000 Server:

    http://support.microsoft.com/kb/266768

    Instead.  I've pinged Amy to fix up the moved link.


    Unfortunately TechNet isn't coming back, sorry folks :-(

    Saturday, December 14, 2013 1:25 AM
    Moderator
  • Ensure that the asp.net sites that should be on .net 4 are on .net 4

    Others have reported that some may be on .net 2 and they should be on 4


    Unfortunately TechNet isn't coming back, sorry folks :-(

    Thursday, December 19, 2013 12:40 AM
    Moderator

All replies

  • Hi:

    IE 11 is not quite ready for RWA, and there are reports of dot net 4.51 on the server causing issues as well.  Can you confirm that neither of these is in play?


    Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

    Saturday, December 14, 2013 12:41 AM
    Moderator
  • "simply by running IIS Reset"

    Sounds like .net 4.5.1 to me got installed on this server


    Unfortunately TechNet isn't coming back, sorry folks :-(

    Saturday, December 14, 2013 1:22 AM
    Moderator
  • Remote Access Button Stops Working SBS 2011 Standard - Event ID 3 and 1309:

    http://social.technet.microsoft.com/Forums/en-US/bf09abb7-ad7b-4d65-a993-6fa9d53d6235/remote-access-button-stops-working-sbs-2011-standard-event-id-3-and-1309?forum=smallbusinessserver


    The install of 4.5.1 on SBS 2011 is making some of these boxes now run
    out of resources.

    I opened a case for a consultant, I'm seeing more and
    more posts in the forums about this issue.

    Issue:  .net 4.5.1 is offered
    up to SBS 2011
    .net 4.5.1 is installed
    Causes more resources on the box

    If box is 'marginal' in resources it will tip it over and start causing
    issues
    Symptoms now being seen:  RWA will stop working or have issues
    connecting to the workstations

    Resolution:
    Throw more RAM at the ox

    Or throttle down Exchange memory use manually

    http://www.thirdtier.net/2012/01/solving-the-unresponsive-exchange-sbs-server-problem/


    That second article is here: How to modify the Store Database maximum
    cache size in Exchange 2000 Server <http://go.microsoft.com/fwlink/?linkid=3052&kbid=266768>


    and the link is wrong... use

    How to modify the Store Database maximum cache size in Exchange 2000 Server:

    http://support.microsoft.com/kb/266768

    Instead.  I've pinged Amy to fix up the moved link.


    Unfortunately TechNet isn't coming back, sorry folks :-(

    Saturday, December 14, 2013 1:25 AM
    Moderator
  • Sounds like exactly the same issue I had, I've uninstalled 4.5.1 yesterday and am now back to .NET 4.5 (4.5.5079) so will report back in about 4 or 5 days (it has been happening roughly every four days) if it reoccurs under the older .NET version.  (see link to my post by Susan)

    Failing this I might look at locking down the Exchange memory usage

    Bill

    Sunday, December 15, 2013 7:12 AM
  • Hi,

    Any update?

    Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.

    Best Regards,

    Andy Qi

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Andy Qi
    TechNet Community Support

    Monday, December 16, 2013 9:45 AM
    Moderator
  • Ran into the same issue after updating to 4.51.  Is was a "recommended" update.  Serves me right to install a non "important" or "critical" update.  I tried uninstalling 4.51 and reinstalling 4.0 and it changed some code in the RWW page giving errors and no longer being able to access the page either locally or from the outside.  Had to remove an added <compilation> entry as well as changing the version of .net it was looking for.  This allowed the RWW page to load for EU's but the "connect" button still would not load anything.  Restarting IIS is one work around or restarting the server which obviously is not ideal either.  The current workaround that works for now was to create a remote desktop client file with the proper login information to get into an individual machine.  I know it is clunky but the best I could come up with for now.  I'm hoping MS sees this and replaces a patch soon.

    I also posted this in the thread with event-id-3 and id-3109 post posted above.

    I hope both of these threads get the attention of MS.

    Wednesday, December 18, 2013 8:02 PM
  • Ensure that the asp.net sites that should be on .net 4 are on .net 4

    Others have reported that some may be on .net 2 and they should be on 4


    Unfortunately TechNet isn't coming back, sorry folks :-(

    Thursday, December 19, 2013 12:40 AM
    Moderator
  • So it looks like the solution is to uninstall .net 4.5.1.  I show in Program and Features it was installed on 11/28/2013.  However, I don't see any older versions listed there or in installed updates. However I do see it in Add Features (.net 3.5.1)

    I am concerned if I uninstall .net it will break everything. Is there a proper procedure to uninstall or roll back to the older version?  What would I need to change in IIS?

    Thanks again for all the information.

    Thursday, December 19, 2013 4:25 PM
  • having the same issue with one of my servers as well. after the 4.5.1 update to .net I have to keep restarting IIS and web services to keep it working. Just the buttons to remote to systems does not work. Not sure I want to rip out .net 4.5.1 with out hearing what it will do.

    Thanks,

    JPS

    Friday, December 20, 2013 5:01 PM
  • Troubleshooting “An unexpected error occurred” message when using Remote Web Access to connect to computers - The Windows Server Essentials and Small Business Server Blog - Site Home - TechNet Blogs:
    http://blogs.technet.com/b/sbs/archive/2014/01/13/troubleshooting-an-unexpected-error-occurred-message-when-using-remote-web-access-to-connect-to-computers.aspx

    Unfortunately TechNet isn't coming back, sorry folks :-(

    Monday, January 13, 2014 5:29 PM
    Moderator
  • I had the same problem with a customer server, restarted 'IIS ADMIN', 'WWW Publishing' & 'Remote Desktop Gateway' service and I could then connect to machines again successfully.
    Thursday, July 17, 2014 11:29 AM
  • This is an old post but I once again ran into this issue!  

    Fortunately the first ANSWER in this post:

    https://social.technet.microsoft.com/Forums/en-US/bf09abb7-ad7b-4d65-a993-6fa9d53d6235/remote-access-button-stops-working-sbs-2011-standard-event-id-3-and-1309?forum=smallbusinessserver

    SOLVES the problem.  I've used this on at least 3 SBS 2011 servers.

    here it is:

    Edit (via NotePad) the web.config file in "C:\Program Files\Windows Small Business Server\Bin\WebApp\RemoteAccess

    "Find the line <serviceHostingEnvironmentaspNetCompatibilityEnabled="true" /> (near the bottom)

    Change it to be (all one line) <serviceHostingEnvironment aspNetCompatibilityEnabled="true" minFreeMemoryPercentageToActivateService="0" />

    Bounce the WWW Pub service (which will in turn bounce the RDG service).

    • Marked as answer by TanNYC Thursday, July 7, 2016 1:57 PM
    Thursday, July 7, 2016 1:57 PM