SSRS 2008 and SSAS 2008 transport error

Question

I am testing an upgrade to SSAS 2008 and verifying existing reports working properly. I am able to get some SSRS reports that are using SSAS as a datasource to run without any issues. They are simple and only have a single dataset. The reports that I am unable to get to work correctly against SSAS 2008 have multiple datasets and have a fitler setup with a data range setup as a parameter. As soon as I setup that filter as a parameter and deploy them the report returns a "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. An existing connection was forcibly closed by the remote host" message.

The funny thing is that the report works fine when I run it locally in BIDS and it works fine once deployed if I point it to a SSAS 2005 server. Once I point it to the SSAS 2008 server it fails. I can get other reports to work fine, but not the ones with this type of a filter setup. I can see that the start and end date parameter MDX statements get run in the trace, but that is it. After those run then we receive the transport connection message.

Another funny thing is that in the production environment the reports are working fine, but that has SSRS 2005 and SSAS 2008. Does this make sense?
What could be causing this? I have tried setting the single transaction level on the datasource too, but that does not seem to make a difference.

Answer 1

It turns out this is a known issue now at Microsoft. We are at least the fourth customer to log this issue. It is specifically related to Windows Server 2008 and use of Kerberos. It has to deal with the packets and the checksum calculation when using Kerberos. I am working with someone on the Analysis Service support team at Microsoft. They are actively working on this with the Windows team to hopefully resolve this. Until then we need to run one of the components (SSRS 2008 or SSAS 2008) on a Windows 2003 server since we are going to continue to use Kerberos and stay in a distribute environment. This is what I received from MS Support last night:

Thanks for confirming your test with Server 2003 as the middle tier. Unfortunately, based on the symptoms you described so far, it sounds likely this may be an ongoing issue we have been seeing when both client and server in a Kerberos authentication are 2008 or Vista. We are currently investigating that actively with the Windows team, but so far do not have a resolution, if this is the problem. We can work around the issue by using a non-2008 client as you found, or by placing the client and server on the same box, or avoiding Kerberos authentication (which requires clear text authentication in middle tier – basic authentication from the client or else anonymous authentication with specified account supplied in middle tier configuration).

Hopefully this will be resolved in the near future. For now we are planning on running SSRS 2008 on Windows Server 2003.