Permission problem with ADOMD and AS2000
- From: "JJ" <jj@xxxxxxxxxx>
- Date: Fri, 13 Jan 2006 09:58:36 -0500
On one domain, I have SQL2000 and AS2000 running on the same system, and an
ASP.NET application running on another system. The ASP.NET application runs
an MDX query successfully.
If I copy the database and ASP.NET application to a different domain (using
the same setup), I get a "database xxxx does not exist" error when trying to
connect to the cube.
On both systems, I put code in the ASP.NET application to display the value
returned by System.Security.Principal.WindowsIdentity.GetCurrent().Name and
it shows "NT AUTHORITY\SYSTEM". Yet it connects on the one domain but not
on the other.
If I change the web.config of the ASP.NET application on the problem domain
to impersonate a user such as "DOMAIN2\Administrator", it then successfully
connects.
So my question is what would allow "NT AUTHORITY\SYSTEM" (the System
Account) to connect on one domain and not on the other? Is it a setup issue
in SQL2000 or AS2000? On the cube itself (the roles look the same to me)?
.
- Follow-Ups:
- Re: Permission problem with ADOMD and AS2000
- From: Darren Gosbell
- Re: Permission problem with ADOMD and AS2000
- Prev by Date: 2 Datawarehouses? 2 Datasources? Or maybe one...
- Next by Date: SSAS 2005: Contains function does not work
- Previous by thread: 2 Datawarehouses? 2 Datasources? Or maybe one...
- Next by thread: Re: Permission problem with ADOMD and AS2000
- Index(es):
Relevant Pages
|
