Saturday, February 25, 2012
Remote Connection to Analysis Services using VPN
Authentication (thus requiring windows user accounts), is it possible for a
remote client PC, connected to a network using a VPN, to be authenticated on
an Analysis Server if it is not part of the host domain? If so, how can this
be achieved?
Is there a way of using the anonymous login account?
If not, is this not a strange inconsistency with SQL server, and are there
plans to address this with Yukon?
Many Thanks
Simon Kirk
I am running into the same problem. Currently we are kludging this by
creating a "pass-thru" user on the server with the same uid/pwd as the
client. Also, the user has to be an admin on the Analysis Server box. I'd
love to know if anyone has found a more direct way to remotely register an
Analysis Server.
Ken Collier
"Simon Kirk" wrote:
> Given that MS Analysis Services does not support standard SQL Server
> Authentication (thus requiring windows user accounts), is it possible for a
> remote client PC, connected to a network using a VPN, to be authenticated on
> an Analysis Server if it is not part of the host domain? If so, how can this
> be achieved?
> Is there a way of using the anonymous login account?
> If not, is this not a strange inconsistency with SQL server, and are there
> plans to address this with Yukon?
> Many Thanks
> Simon Kirk
>
Remote Connection to Analysis Services using VPN
Authentication (thus requiring windows user accounts), is it possible for a
remote client PC, connected to a network using a VPN, to be authenticated on
an Analysis Server if it is not part of the host domain? If so, how can this
be achieved?
Is there a way of using the anonymous login account?
If not, is this not a strange inconsistency with SQL server, and are there
plans to address this with Yukon?
Many Thanks
Simon KirkI am running into the same problem. Currently we are kludging this by
creating a "pass-thru" user on the server with the same uid/pwd as the
client. Also, the user has to be an admin on the Analysis Server box. I'd
love to know if anyone has found a more direct way to remotely register an
Analysis Server.
Ken Collier
"Simon Kirk" wrote:
> Given that MS Analysis Services does not support standard SQL Server
> Authentication (thus requiring windows user accounts), is it possible for
a
> remote client PC, connected to a network using a VPN, to be authenticated
on
> an Analysis Server if it is not part of the host domain? If so, how can th
is
> be achieved?
> Is there a way of using the anonymous login account?
> If not, is this not a strange inconsistency with SQL server, and are there
> plans to address this with Yukon?
> Many Thanks
> Simon Kirk
>
Monday, February 20, 2012
Remote connection to Analysis Service giving problem.
Hi,
I am stuck up with one of the deployment scenario. I have web application through which we can invoke reports. Reports are developed in SQL Server 2005 Reporting Service.
The reporting service project sets data source connection with Analysis Services database.
If we have all this on the same machine, we are able to integrate and see the results end to end.
However we are stuck up with the following deployment scenario.
Say our web application is on A machine
SQL Server 2005 database on B machine
SQL Server 2005 Analysis Services on C machine
SQL Server 2005 Reporting Services on D machine.
so analysis services C machine pointing to database on B machine. and reporting services D machine pointing to analysis services C machine.
So in Reporting Service project when we set the data source connection to a remote Analysis services machine (C)
it gives us the following error that "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running."
Is this a known issue? I searched on google and this forum but dint get much help. I did check that for analysis service remote connection is enabled.
What exact steps do I have to follow?
First of all is this scenario ok that analysis services and reporting services on different machine?
This is very urgent for our project. Please help me find the solution.
Thanks in advance!
Note: I have posted a similar post in Reporting Services forum.
Ann.
This problem relates to the fact that two separate servers cannot identity a user without that you use Kerberos for authentication. If you have a network with Active Directory it is configuration issue. This feature is already in place.
Search on Windows 2003, Active Directory and Kerberos.
Mosha have a post on this regarding SSAS2005 here:
http://www.mosha.com/msolap/articles/kerberos_delegation.htm
HTH
Thomas Ivarsson