I have an ASP.NET application that is connecting to an Analysis Services
2005 database.  When the connection is attempted the IIS server returns the
following SocketException.  When the site is browsed on the local michine
the error never is raised.  But when anyone browses the sire from  remote
computer the error persists.  Can anyone help me with a resolution to this
issue.

There seems to be alot of traffic on the Internet related to this error
message but I can't find a root cause or resolution.

Thanks,
Steven

An existing connection was forcibly closed by the remote host
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.

Exception Details: System.Net.Sockets.SocketException: An existing
connection was forcibly closed by the remote host

Source Error:

Line 100:            #region Get the chart data
Line 101:
Line 102:            chartData.Connection.Open();
Line 103:Line104:            // Filter the Chart Measure info to get the measures for the chart
selected

Source File: C:\Inetpub\Charts\ChartDetail.aspx.cs    Line: 102

Stack Trace:

[SocketException (0x2746): An existing connection was forcibly closed by the
remote host]
  System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32
size, SocketFlags socketFlags) +438
  System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32
size) +108

[IOException: Unable to read data from the transport connection.]
  System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32
size) +156
  Microsoft.AnalysisServices.AdomdClient.DimeRecord.ForceRead(Stream
stream, Byte[] buffer, Int32 length) +38
  Microsoft.AnalysisServices.AdomdClient.DimeRecord.ReadHeader() +36
  Microsoft.AnalysisServices.AdomdClient.DimeRecord..ctor(Stream stream)
+50
  Microsoft.AnalysisServices.AdomdClient.DimeReader.ReadRecord() +77
  Microsoft.AnalysisServices.AdomdClient.TcpStream.GetDataType() +78

[AdomdConnectionException: The connection either timed out or was lost.]
  Microsoft.AnalysisServices.AdomdClient.XmlaClient.EndRequest() +785
  Microsoft.AnalysisServices.AdomdClient.XmlaClient.SendMessage(Boolean
endReceivalIfException, Boolean readSession, Boolean
readNamespaceCompatibility) +31
  Microsoft.AnalysisServices.AdomdClient.XmlaClient.DiscoverWithCreateSession(String
discoverType, ListDictionary properties, Boolean
sendNamespacesCompatibility) +176
  Microsoft.AnalysisServices.AdomdClient.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection+IXmlaClientProviderEx.DiscoverWithCreateSession(String
requestType, Boolean sendNamespaceCompatibility) +131
  Microsoft.AnalysisServices.AdomdClient.AdomdConnection.RetrieveSchemaRowsets(Boolean
createSession) +42
  Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean
createSession, Boolean isHTTP) +144
  Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open() +601
  Microsoft.WinSE.Dashboard.ChartDetail.displayChart() in
C:\Inetpub\Charts\ChartDetail.aspx.cs:102
  Microsoft.WinSE.Dashboard.ChartDetail.Page_Load(Object sender, EventArgs
e) in C:\Inetpub\Charts\ChartDetail.aspx.cs:23
  System.Web.UI.Control.OnLoad(EventArgs e) +67
  System.Web.UI.Control.LoadRecursive() +35
  System.Web.UI.Page.ProcessRequestMain() +750

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET
Version:1.1.4322.2300