Home / Announcements / Forums / TFS Work Item Manager and Project Dashboard: TFS Project Dashboard > Dashboard connection issues

• Michael

  Posted on Oct 25, 2011 (permalink)

  Certain widgets (namely Team Velocity, Code Churn, Bug History) don't always connect to TFS and give a connection error. They will sometimes come up, so I know the connection info is accurate.  On some runs of the dashboard, all widgets come up.  On other runs, one or more of the widgets will fail to load.  Is this something on the server end?  Are there any settings or timeouts I can tweak in the dashboard to make it work smoother?  The timeout seems to be set to 0 (infinite) already.
  
  2011-10-25 10:20:41,329 [5316] [12] INFO  IRC.Gear.WorkItemManager.Dashboard.TfsDataProvider.TfsWarehouse - Attempting to connect to TFS Warehouse - Connection String: Data Source=tfsreporting.mycompany.com;Catalog=Tfs_TFSReportingAnalysis;Connect Timeout=60.   
  2011-10-25 10:20:45,127 [5316] [16] ERROR IRC.Gear.WorkItemManager.Dashboard.TfsDataProvider.TfsWarehouse - TfsWarehouse.Connect returned AdomdConnectionException..  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 IRC.Gear.WorkItemManager.Dashboard.TfsDataProvider.TfsWarehouse.Connect(String connectionString)
   
  

  
  

  Reply

• Joel Joel

  Posted on Nov 1, 2011 (permalink)

  Hi Michael,
  
  By the looks of the stack trace you posted below, you currently have the timeout set to 60 seconds.  If your TFS cube is not located very close to you or is not very performant, it is possible that this could cause timeouts.  We need to retrieve a fair amount to data to produce some of the charts.
  
  One thing you can try is to increase the timeout for the ADOMD Warehouse connection string to something like 120 (seconds).  To do this, go to the configuration for your project in the dashboard and then go to the General tab.  Click the Edit Connection String button to change the connection string and test your settings.
  
  It is also possible that the server is closing the connection on you, but generally this only happens due to permissions related issues.  Since you mention that the connection sometimes works, I would be surprised if this was the issue.
  
  Regards,
  Joel
  the Telerik team

  
  Check out Telerik Trainer, the state of the art learning tool for Telerik products.

  Reply

Back to Top

Home / Announcements / Forums / TFS Work Item Manager and Project Dashboard: TFS Project Dashboard > Dashboard connection issues