I am testing an upgrade in SSAS 2008 and existing reports are working properly. I am able to obtain some SSRS reports which are running SSAS as a source for any issue without issue. These are simple and have only one dataset report that I am right against SSAS 2008 I am unable to work, has multiple datasets and as a parameter, there is a Fitler setup with Data Category setup as soon as I setup that filter as a parameter and deploy it The report gives a return "the connection was either expired or was lost. Unable to read the data from the transport connection: an existing connection was forcibly closed by the remote host. Forced by an existing connection remote host" message Was closed.
The funny thing is that when I run it locally at bids and it works fine, when I point it to any SSAS 2005 server, once I get it on SSAS 2008 server It indicates it fails. I can get other reports to work fine, but not with this kind of filter setup. I can see that the start and end date parameters run in the MDX statement trace, but it is. After those runs, we receive the transport connection message.
Another interesting thing is that the report is working well in the production environment, but it has SSRs 2005 and SSAS 2008. Does this make sense?
Why can this be the reason? I have also attempted to establish a transaction level on the data source, but it does not make any difference.
It is revealed that this is a known issue on Microsoft. We are at least four customers to log on to this issue. This is especially related to the use of Windows Server 2008 and Kerboos when using Kerberos it will have to deal with calculation of packet and checksum. I am working with anyone on the Analysis Services support team on Microsoft. They are actively working on this with the Windows team so hopefully solve it. Till then, we need to run a part of the server (SSRS 2008 or SSAS 2008) in 2003 2003 because we will continue to use Kerberos and remain in distributed environments. Last night I got what I got from MS Support:
Thank you, as an intermediate part to confirm your trial with server 2003. Unfortunately, based on the characteristics you have so far described, it probably seems that this could be an ongoing issue which we were seeing when both servers and servers in both Kerberos authentication are 2008 or Vista, we are currently active with the Windows team We are investigating the form, but there is no solution yet, if this is the problem, we can use a non-2008 client, or by putting the client and the server in a single box, or by using Kerberos
Hopefully it is near by avoiding the mechanism (which requires clear text authentication in the middle level for the original level authentication from the client)
Will be resolved in the future. We are now planning to run SSRS 2008 on Windows Server 2003.
Comments
Post a Comment