{"id":114,"date":"2014-05-06T13:49:30","date_gmt":"2014-05-06T13:49:30","guid":{"rendered":"http:\/\/www.torontohelpdesk.ca\/blog\/?p=114"},"modified":"2014-05-07T13:05:37","modified_gmt":"2014-05-07T13:05:37","slug":"rww-shared-folders-not-accessible","status":"publish","type":"post","link":"https:\/\/www.torontohelpdesk.ca\/blog\/rww-shared-folders-not-accessible\/","title":{"rendered":"RWW – Shared folders not accessible"},"content":{"rendered":"

Problem:<\/strong><\/p>\n

You log into Remote Web Workplace and you try accessing shared folders. You get the following error:<\/p>\n

The page at https:\/\/remote.yourdomain.com says:<\/p>\n

An unexpected error occurred. Please try again. If the problem continues, contact the person who manages your server.<\/p>\n

Solution:<\/strong><\/p>\n

(h\/t Blackforce)<\/p>\n

http:\/\/www.blackforce.co.uk\/2014\/01\/13\/sbs-2011-rdweb-shared-folders-an-unexpected-error-occured<\/a><\/p>\n

Had an interesting problem today with a 2011 SBS server. The problem was that when users went to the remote desktop workplace website RDWeb. They were unable to browse through the Shared Folders.
\n<\/span>
\n\"RDSweb8\"<\/p>\n

When the users clicked on a folder they were greeted by the error message :<\/p>\n

An unexpected error occurred. Please try again. If the problem continues, contact the person who manages your server<\/code><\/p>\n

\"RDSweb\"<\/p>\n

The first place to investigate was the SBS servers application event log. There were numerous errors with an event id of 3 and Source System.ServiceModel 4.0.0.0.<\/p>\n

The error below presented itself everytime you clicked on a folder.<\/p>\n

WebHost failed to process a request. Sender information : System.ServiceModel.Activation.HostedHTTPRequestAsyncResult\/17653682 Exception: System.ServiceModel.ServiceActivationException: The service '\/Remote\/BuiltIns\/RDP\/RemoteDesktopWebService.svc' cannot be activated due to an exception during compilation.<\/code><\/p>\n

The error then went on to say :<\/p>\n

The exception message is: Memory gates checking failed because the free memory (48817920 bytes) is less than 5% of total memory. As a result, the service will not be available for incoming request<\/code><\/p>\n

I have included a screenshot of the full error below as it goes on a bit..<\/p>\n

\"rdsinstall15\"<\/p>\n

So from this error we know that the reason why it wont work is because the free memory is less than 5% of the server. This must be something built into SBS as i\u2019ve never seen this before.<\/p>\n

A quick workaround to get your users up and running is to free up some memory. Restart the Information Store service and you should be good.<\/p>\n

From looking around there seem to be 2 permanent solutions.<\/p>\n

1) Set the threshold to lower than 5%
\n2) Limit the Exchange Server store.exe from taking up all the memory.<\/p>\n

I decided to go with option 2 as the server is used in a very small environment and store.exe was taking up 8gb.<\/p>\n

\"RDSweb2\"<\/p>\n

To carry this out we need to change 2 attributes in ADSIedit.<\/p>\n

MsExchESEParamCacheSizeMax and MsExchESEParamCacheSizeMin.<\/p>\n

<\/div>\n

First of all lets open adsiedit.msc. Then select \u201cselect a well known Naming Context\u201d. In the drop down box select Configuration. Then click ok<\/p>\n

\"RDSweb3\"<\/p>\n

Then drill down to the location we need.<\/p>\n

Configuration > Services > Microsoft Exchange > > Administrative Groups > > Servers > > InformationStore<\/p>\n

\"RDSweb4\"<\/p>\n

Right click on the CN=InformationStore container and click properties.<\/p>\n

\"RDSweb5\"<\/p>\n

In the Attribute Editor tab scroll down until you find the 2 attributes MsExchESEParamCacheSizeMax and MsExchESEParamCacheSizeMin.<\/p>\n

\"RDSweb6\"<\/p>\n

You now want to populate these fields with your desired values. For me I want to set the server to 6GB Max. So you have to work out the value to enter. 6GB is 6.291.456 KB then you want to divide that number by 32. This gives us a max value of 196608.<\/p>\n

I\u2019ve put some values in below pre calculated<\/p>\n

8GB = 262144
\n6GB = 196608
\n4GB = 131072
\n2GB = 65536<\/p>\n

I then set a minimum size of 4GB.<\/p>\n

\"RDSWEB\"<\/p>\n

Now restart the Information Store Service and your all good.<\/p>\n

After a while you should find the store.exe process hovers between 4 and 6GB memory usage.<\/p>\n

\"Memory<\/p>\n

\u00a0Update:<\/strong><\/p>\n

The problem was still happening so I did the following and we’ll see what happens:<\/p>\n

Edit (via NotePad) the web.config\u00a0file in “C:\\Program Files\\Windows Small Business Server\\Bin\\WebApp\\RemoteAccess<\/p>\n

“Find the line<\/strong> <serviceHostingEnvironment aspNetCompatibilityEnabled=”true” \/> (near the bottom)<\/p>\n

Change it to be (all one line) <\/strong><serviceHostingEnvironment aspNetCompatibilityEnabled=”true” minFreeMemoryPercentageToActivateService=”0″ \/><\/p>\n

Restart the World Wide Web Publishing service (which will in turn bounce the RDG service).<\/p>\n

(h\/t ema_sge<\/a>)<\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Problem: You log into Remote Web Workplace and you try accessing shared folders. You get the following error: The page at https:\/\/remote.yourdomain.com says: An unexpected error occurred. Please try again. If the problem continues, contact the person who manages your Continue reading RWW – Shared folders not accessible<\/span>→<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-114","post","type-post","status-publish","format-standard","hentry","category-sbs-2011"],"_links":{"self":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/comments?post=114"}],"version-history":[{"count":3,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/114\/revisions"}],"predecessor-version":[{"id":117,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/114\/revisions\/117"}],"wp:attachment":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/media?parent=114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/categories?post=114"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/tags?post=114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}