Re: Connect to AS from another workstation
- From: Darren Gosbell <xxx@xxxxxxx>
- Date: Fri, 28 Oct 2005 11:06:31 +1000
You can also work around this by setting up a local account on the AS2k
server that has the *identical* username and password to a local account
on your workstation (it must be a local account on your machine)
Make sure that the local account on the server is in role in AS that
will allow it access to the OLAP database and log on to your workstation
using the local machine account and you should be able to get access.
I have used this scenario at client sites where they used Novell Netware
and we did not have an NT domain.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
In article <edzMdIx2FHA.3628@xxxxxxxxxxxxxxxxxxxx>,
dennyglee@xxxxxxxxxxx says...
> Hmm - it may be. When you connect to the SQL server, are you connecting via
> "domain" of sorts or using the SQL login? SQL has its own authentication
> system that allows you to "bypass" windows authentication. In the case of
> Olap, though, you need to utilize windows authentication. Saying this, you
> may be able to work around it by using basic authentication where you would
> need to have your pivot pass in username and password in clear text and then
> have your OLAP server be able to recognize and allow access to that user.
> But in general, the preferred option is having a domain such that the OLAP
> server can use Windows auth instead.
>
>
.
- References:
- Re: Connect to AS from another workstation
- From: Denny Lee
- Re: Connect to AS from another workstation
- Prev by Date: Re: MSAS 2002 to MSAS 2005 Migration: DSV Question.
- Next by Date: Re: Cube very slow to querying when in the middle of a process
- Previous by thread: Re: Connect to AS from another workstation
- Next by thread: Re: How to return Null in IIF (MDX)
- Index(es):
Relevant Pages
|