Connection problems

Hi,

I am trying to connect to a simple cube in SQLAS2005 from a Webpart "SQL Server 2005 analysis filter" in SharePoint 2007.
I have entered a reference to the cube in the sharepoint connection library,
but when I try to configure the filter webpart, just before selecting
dimension and hierarchy, I get the following error:

The connection either timed out or was lost

The inner error from the sharepoint logs show this:
Unable to read data from the transport connection: An existing connection
was forcibly closed by the remote host

I have tried to give permissions to both myself and the sharepoint server as
admin in both the sql server 2005 and created an admin role in the analysis
server 2005. The firewall is turned off.

Nothing works, please advise

Regards,
P?l B?rseth-HansenEdward Melomed posted a good article on his blog about troubleshooting Analysis Services connection issues. Have a read and see if it helps http://www.sqljunkies.com/WebLog/edwardm/archive/2006/05/26/21447.aspx|||

Hi Darren,

Thanks for suggestion. I have read the article and tried som things:

1. The odc connection string works fine from excel 2007, that is it can connect and browse the analysis cube.

2. Wen trying the same connection string in office 2007 the eventlog shows first a sharepoint user (which I have called MOSS2007). This user has cube rights. But then it seems to try anonymous connection, which the article you describe says will not work.

3. I have tried to temporay enable anonymous on the AS2005 server and am tracing in the profiler to see that I get a step further. In fact the trace suggest I do get a step further, but is then denied on a cube level...

So it seems for some reason that the webpart in 2007 uses an anonymous connection?

Is this right, if so: can I change it?

Regards,

P?l

|||

MOSS2007 must have some new web parts that are not based on the OWC components.

I have not had a good look at MOSS2007 myself yet (B2 was too slow on a VPC, I am downloading B2TR now )

There are a couple of ways that ASP.NET web applications (like MOSS) can be configured. If it is set up for identity impersonation, (which it sounds like it might be) it will execute on the web server using the credentials of the end user. However NTLM authentication has a security feature that will not let credentials be passed more than once. So while the users credentials are passed to MOSS, MOSS cannot then pass them on to SSAS. So if MOSS and SSAS were on the same machine it would work. But the only way to get this to work with MOSS and SSAS on separate machines is to set up Kerberos authentication.

There is a good article on setting up Kerberos here: http://sqljunkies.com/WebLog/mosha/archive/2005/01/25/6905.aspx

If MOSS is not using identity impersonation then MOSS would connect to SSAS using the account that is configured in the MOSS application pool (and you should not see the anonymous connection attempts)

|||

I am facing this problem too. Did you get a solution for the problem yet?

Thanks,

C K