Databases
StackOverflow2013
Postsdbo
POAppFabric Cache - An existing connection was forcibly closed by the remote host
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAppFabric Cache - An existing connection was forcibly closed by the remote host
    primarykey
    data
    text
    <p>I'm trying to get AppFabric cache up and running on my local development environment. I have <strong>Windows Server AppFabric Beta 2 Refresh</strong> installed, and the cache cluster and host configured and started running on Windows 7 64-bit. I'm running my MVC2 website in a local IIS website under a v4.0 app pool in integrated mode.</p> <pre><code>HostName : CachePort Service Name Service Status Version Info -------------------- ------------ -------------- ------------ SN-3TQHQL1:22233 AppFabricCachingService UP 1 [1,1][1,1] </code></pre> <p>I have my web.config configured with the following:</p> <pre><code> &lt;configSections&gt; &lt;section name="dataCacheClient" type="Microsoft.ApplicationServer.Caching.DataCacheClientSection, Microsoft.ApplicationServer.Caching.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" allowLocation="true" allowDefinition="Everywhere"/&gt; &lt;/configSections&gt; &lt;dataCacheClient&gt; &lt;hosts&gt; &lt;host name="SN-3TQHQL1" cachePort="22233" /&gt; &lt;/hosts&gt; &lt;/dataCacheClient&gt; </code></pre> <p>I'm getting an error when I attempt to initialize the DataCacheFactory:</p> <pre><code> protected CacheService() { _cacheFactory = new DataCacheFactory(); &lt;-- Error here _defaultCache = _cacheFactory.GetDefaultCache(); } </code></pre> <p>I'm getting the ASP.NET yellow error screen with the following:</p> <p><strong>An existing connection was forcibly closed by the remote host</strong></p> <p>Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. </p> <p>Exception Details: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host</p> <p>Source Error: </p> <pre><code>Line 21: protected CacheService() Line 22: { Line 23: _cacheFactory = new DataCacheFactory(); Line 24: _defaultCache = _cacheFactory.GetDefaultCache(); Line 25: } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USWallace Breza
    1. USWallace Breza
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAppFabric Cache - An existing connection was forcibly closed by the remote host
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAppFabric Cache - An existing connection was forcibly closed by the remote host
      1. USkindasimple
      1. VTFavorite
    3. VO
      singulars
      1. POAppFabric Cache - An existing connection was forcibly closed by the remote host
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthe real question is if your account did not have access, why didnt the server tell you that instead of "An existing connection was forcibly closed by the remote host"
      singulars
      1. POAppFabric Cache - An existing connection was forcibly closed by the remote host
      1. USfelickz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload