Re: Analysis Services in a mixed Novell/Windows environment
From: Dave Wickert [MSFT] (dwickert_at_online.microsoft.com)
Date: 10/12/04
- Next message: Rob C: "Re: Cannot Open Connection"
- Previous message: Dave Wickert [MSFT]: "Re: Cannot Open Connection"
- In reply to: RaVaGe: "Re: Analysis Services in a mixed Novell/Windows environment"
- Next in thread: RaVaGe: "Re: Analysis Services in a mixed Novell/Windows environment"
- Reply: RaVaGe: "Re: Analysis Services in a mixed Novell/Windows environment"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 12 Oct 2004 13:07:33 -0700
It is on the connectstring. See BOL under PTS Properties. You can enter
username as "domain\user" and pwd as the password. If using http access make
sure that you always run SSL (and specify https://
basic authentication headers are encrypted, otherwise the username and
password are only lightly modified when sent over the wire.
--
Dave Wickert [MSFT]
dwickert@online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"RaVaGe" <RaVaGe@discussions.microsoft.com> wrote in message
news:0CD11FAC-8FE6-4964-9604-0C87AE438BBC@microsoft.com...
> Thanks for this info. But is there a way to tell the pivottable wizzard to
> use a certain, username, password en domain? That would solve my problem,
but
> I don't how to do that, if at all possible.
>
> Ralf
>
> "Dave Wickert [MSFT]" wrote:
>
> > See the security configuration section in the SSAS Operations Guide:
> >
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
> >
> > --
> > Dave Wickert [MSFT]
> > dwickert@online.microsoft.com
> > Program Manager
> > BI SystemsTeam
> > SQL BI Product Unit (Analysis Services)
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "RaVaGe" <RaVaGe@discussions.microsoft.com> wrote in message
> > news:70D6245D-6EDE-45A3-90B0-7E98A1EFB70A@microsoft.com...
> > > Hi
> > >
> > > I have a serious issue that I would like some help with.
> > >
> > > My customer has a combined Novell/Windows networking environment.
Through
> > a
> > > set of tools both environments are kept in sync as far as users and
> > passwords
> > > are concerned. None of the workstations is a member of the Windows
Domain.
> > >
> > > The customer's workstations are all logging into the Novell
environment.
> > > When I try to connect to an Analysis Cube (SQL Server 2000/Analysis
> > Services
> > > Standard Edition SP3a) from Excel 2000 using a pivottable I get an
error
> > > message saying that authentication is not possible.
> > >
> > > In fact I presume that Excel is picking up the User ID and Password
from
> > the
> > > workstation and is passing that on to SQL Server/Analysis Services.
Since
> > the
> > > Userdomain of the workstation is the workstation itself this seems to
go
> > > wrong. When I make the workstation a member of the windows Domain it
works
> > > fine. However, this is not really an option for the customer.
> > >
> > > I there any way to get this to work? Can I have Excel prompt me for
the
> > > userid, password and Domain? Or is there a workaround? Or any other
> > solution
> > > or remark?
> > >
> > > Thanks
> > >
> > > Ralf
> > >
> > >
> > >
> >
> >
> >
Relevant Pages
... then I think it is important that the workstation environment support ... It may or may not be worth adding here, that Fujitsu is RELATIVELY unusual ... to be "migration inhibitor" for some IBM mainframe COBOL customers. ...
(comp.lang.cobol)
... The username and password for Bob gives access to the folder Bob's ... No matter what user is logged on to the workstation, ...
(microsoft.public.windows.server.networking)
... I did with SP2 Servers and Workstation, the patch work fine and it did ... For your environment, better do it in a none production environment first, ...
(Full-Disclosure)
... workstation and uses a valid domain account name but enters a bad ... Failure Code 24.By reviewing each of your DC Security logs ... providing the username and domain name, ... address of the system from which the logon attempt originated. ...
(microsoft.public.win2000.security)
... I also have a local user on the server ... I went to a workstation browsed ... There is nor reason to have the username or password ... >> give you access to that folder. ...
(microsoft.public.windows.server.networking)