We are having a issue with a batch file when it does a full process of OLAP Cubes, we are getting an error that states:

Step Error Source: DSO
Step Error Description:Your permissions on the server computer do not allow you to administer this Analysis server.

Error:
Step Error code: 80040026
Step Error Help File:
Step Error Help Context ID:1000440


This was working fine when it was running on the SQL Server before we migrated the SQL Server to a new domain. We just upgraded the SQL Server's OS to Windows 2003 and migrated it to the new domain. We kept the OLAP server on the old domain and it is running windows 2000 SP4. How the batch file gets started is that the iSeries launches it and then it runs on the SQL Server using the DTSRun command. The batch file calls a package that has DTS packages, ActiveX Scripts and an OLAP Task. All the task execute except for the OLAP Task. I have talked to the Network Analysts at my company regarding the if the two domains and they are trusted and there is a two way trust already set up because I am able to grant permissions to the OLAP Cubes to users on either one of the domains. Also the SQLSERVERAGENT and MSSQLSERVER has Windows Domain account as the service and the account is an administrator on the SQL Server. The same windows Domain Account runs the MSSQLSERVEROlapService and that domain account is in the OLAP Administrators Group as well as the Administrators group within the OLAP Server. Any Ideas? Do the SQL Server and the OLAP Server need to be on the same domain in order for the process to work correctly?

The OLAP Server OS is Windows 2000 SP4 and Microsoft Analysis Manager Enterprise Edition 2000 SP3.
The SQL Server OS is Windows 2003 and Microsoft SQL Server 2000 Enterprise Edition SP3.

Thanks for your help!
Phil

In message <1CEFDEF9-4BAD-44B4-9ABB-82C0EE1F93D4 (AT) microsoft (DOT) com>, Phil
<Phil (AT) discussions (DOT) microsoft.com> writes
The windows account context running the package needs to be a member of
the OLAP Administrators group on the OLAP sever machine. Not sure what
the context is in the case of your iSeries scheduler setup, but if you
can find this and grant permissions it should solve the issue. You say
the various SQL Server related service accounts are members of OLAP
Admins, but is this the same as the context calling the job via iSeries.
No idea what iSeries is, so execse me if I have missed the point.

To prove the security context used via DTS, try logging it, e.g.

Global variable diagnostic script
(http://www.sqldts.com/default.aspx?303)


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Darren thanks, I had to change a service a program to run as a windows NT
Account instead of a LocalSystemAccount. By the way the iSeries is the
AS/400.

"Darren Green" wrote: