We have connection problems between a .NET application and a BI(Analysis/Reporting)server
I'll describe our setup:
We have a web application on server X (Windows Server 2008 Enterprise SP2) with IIS 7.0
and a BI configuration on server Y (Windows Server 2008 R2 Enterprise SP1) with SQL Server 2008 R2 installed.
Windows updates are installed monthly.
The servershave multiple network adapters andare connected directly withcrosscable (no switch) with each other and via switch with internet.
At the web server we run a web application written in .NET (v4.0). For certain parts of the web site we use a cube as data source. This cube is hosted at the BI server.
A connection is set up to the analysis services with standard NTLM authorization. We use a Windows user at the BI server that is configured properly.
Also, at the BI server, we use the Reporting Services. The connecting issue also exists when connecting to the web service of reporting services at this machine.
The problem is that a small amount of calls does not reach the BI server and result in a time-out.
Because a whole lot of calls actually does reach the BI server and return the expected result, we've concluded that the problem is not in the configuration of the authorization.
We tried several things to pinpoint the problem, but unfortunately we haven't found it yet.
We tried to keep open a network connection by continuously pinging the other machine (both sides), but this couldn't prevent the time-outs from appearing.
We also watched the network traffic with wireshark on the BI server. At the moments a time-out appears, there seems to be no corresponding traffic at the BI server.
Also, we changed the speed and duplex from the network adapters from auto to 1 gbps full duplex to 100 mbit full duplex, nothing changed…..
Normal(internet)traffic seems not to have this problem.
Does anyone have an idea of why we have this problem?
Stacktrace:
2012-12-06 17:00:18.5608 | WARN | BI.AdoMD.CubeConnectionAttribute | Microsoft.AnalysisServices.AdomdClient.AdomdConnectionException: A connection cannot be made. Ensure that the server is running. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.x.x:x at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) --- End of inner exception stack trace --- at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) at Microsoft.AnalysisServices.AdomdClient.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo) at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession) at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA) at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open() at BI.AdoMD.CubeConnectionAttribute.OnActionExecuting(ActionExecutingContext filterContext) in <FileNameInProject>
2012-12-06 17:19:23.7568 | WARN | BI.AdoMD.CubeConnectionAttribute | Microsoft.AnalysisServices.AdomdClient.AdomdConnectionException: A connection cannot be made. Ensure that the server is running. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.BufferedStream.FlushWrite() at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count) at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ForceRead(Stream stream, Byte[] buffer, Int32 length) at Microsoft.AnalysisServices.AdomdClient.DimeRecord.ReadHeader() at Microsoft.AnalysisServices.AdomdClient.DimeReader.ReadRecord() at Microsoft.AnalysisServices.AdomdClient.TcpStream.GetResponseDataType() --- End of inner exception stack trace --- at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession) at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA) at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open() at BI.AdoMD.CubeConnectionAttribute.OnActionExecuting(ActionExecutingContext filterContext) in <FileNameInProject>
Thnx in advance,
Randy