SSRS 2008 and SSAS 2008 transport error

Question

I am testing upgrade to SSAS 2008 and checking existing work reports properly. I can get some SSRS reports that use SSAS as a datasource to run without any problems. They are simple and have only one data set. Reports that I can’t work correctly against SSAS 2008 have several data sets and have a file setting with setting the data range as a parameter. As soon as I configure this filter as a parameter and expand it, they return the message "The connection was either lost or lost. Failed to read data from the transport connection: the existing connection was forcibly closed by the remote host. The existing connection was forcibly closed by the message of the remote host."

The funny thing is that the report works fine when I run it locally in BIDS and it works fine after deployment if I point it to the SSAS 2005 server. Once I point it to the SSAS 2008 server, it does not work. I can get other reports to work but not those that have this type of filter setting. I see the start and end date parameter. MDX statements run in a trace, but that's It. After that, we get a message about the transport connection.

Another funny thing: in a production environment, reports work fine, but have SSRS 2005 and SSAS 2008. Does this make sense?
What could be the reason for this? I tried to set up a single transaction level on the data source too, but that doesn't seem to matter.

Answer 1

Turns out this is a known issue right now at Microsoft. We are at least the fourth customer to register this issue. It is specifically associated with Windows Server 2008 and uses Kerberos. It must deal with packages and checksum calculation when using Kerberos. I work with someone at Analysis Services Support at Microsoft. They are actively working on this with the Windows team to hope so. Until then, we need to run one of the components (SSRS 2008 or SSAS 2008) on a Windows 2003 server, as we will continue to use Kerberos and remain in a distributed environment. This is what I received from MS Support yesterday:

, Server 2003 . , , , , , , Kerberos - 2008 Vista. Windows, , . , 2008 , , Kerberos ( - , ).

, . SSRS 2008 Windows Server 2003.

Answer 2

, , - Kerberos Windows Server 2008 - SSAS

Answer 3

, SSAS SSRS ? , , . , , , "localhost" .

SSAS, SSRS 2008. SSRS 2008 ASPHostDirectory.com, . , .

, , . , "" , FTP . FTP-, FTP- . FTP, . , , , - ..

.

Answer 4

Kerberos Windows Server 2008 - SSAS

, Microsoft AES Kerberos, . Kerberos Windows Server 2008 - SSAS. , SSAS: Microsoft Kerberos Killing MDX,

http://support.microsoft.com/default.aspx/kb/969083

(KB) , , , . , KB 968700, , , 969083.

So, for those of you who have had to upgrade to Windows Server 2008, because of this, you can download the patch and continue updating the infrastructure. Just make sure you have tested the patch correctly before deploying it in your production environments.