The use of SSPI in a connection sting from SSRS to SSAS

[Reeves]

I get the following error every once in a while from users:

The connection either timed out or was lost
Unable to read data from the transport connection: An existing connection
was forcibly closed by the remote host.

This is a Load Balanced SSRS report to a SSAS server using Kerberos.
Kerberos seems to check out as we logged an issue to Microsoft about three
months ago and found no issues on the Microsoft side; we did increase the VIP
(Zeus) timeout to solve some authentication issues.

1) User is in the correct group
2) group has browser rights to the report
3) group has read rights to the cube
4) SSRS Report Execution Timeout in site settings is set to 1800 seconds (30
minutes)
5) SSAS ServerTimeout is set to the default value is 3600 seconds (60 minutes)
6) Zeus VIP settings:
connect_timeout: 600 seconds (10 seconds previous) -- Zeus def: A
connection that has not received any data should be closed after this period
of time
timeout: 600 seconds (300 seconds previous) -- Zeus def: A connection
should be closed if no additional data has been received for this period of
time

So my question is do I need to use one or both of the following within my
connection string

;SSPI=Kerberos
;Integrated Security=SSPI

My connection info in SSRS is:

Connection type: Microsoft SQL Server Analysis Services
Connection string: Data Source=<Server>;Initial Catalog="<database>"
Connect using: Windows integrated security

Thanks.

[Reeves]

Here is the error reported out of SSRS:

w3wp!processing!6!1/6/2010-08:31:11:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source '<Database Name>'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source '<Database Name>'. --->
Microsoft.AnalysisServices.AdomdClient.AdomdConnectionException: The
connection either timed out or was lost. ---> System.IO.IOException: Unable

to read data from 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.Socket.Receive(Byte[] buffer, Int32 offset, Int32
size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset,
Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset,
Int32 size)
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.DimeRecord..ctor(Stream stream)
at Microsoft.AnalysisServices.AdomdClient.DimeReader.ReadRecord()
at Microsoft.AnalysisServices.AdomdClient.TcpStream.GetResponseDataType()
--- End of inner exception stack trace ---
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.EndRequest()
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient.CreateSession(ListDictionary properties, Boolean sendNamespaceCompatibility)
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.CreateSession(Boolean sendNamespaceCompatibility)
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean
createSession, Boolean isHTTP)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
at Microsoft.ReportingServices.DataExtensions.AdoMdConnection.Open()
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource
dataSourceObj, ReportProcessingContext pc)
--- End of inner exception stack trace ---