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.GetCurre nt().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)?

Can you try running the following MDX on the first domain against the
foodmart database to see what it returns?

select {measures.user} on columns
from [Sales]
I did not think that NT AUTHORITY/SYSTEM had any rights outside of the
local machine. So I am guessing that something is configured on the web
server to use a different identity. Possibly something in the
machine.config or in the application pool if you are using Win2k3. The
above MDX will show you which user the Analysis Server is seeing which
may tell you why the setup on the second domain is not working.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <e6MhRHFGGHA.1032 (AT) TK2MSFTNGP11 (DOT) phx.gbl>, jj (AT) nospam (DOT) com
says...