Wanted to connect Voyager (BO XI R3 ) and sql 2000 (MSAS).

Question

We have never used Voyager before, wanted to connect Voyager (BO XI R3 ) and sql 2000 (MSAS).
Details of my Voyager connection below:
Name: test
Provider: Microsoft OLE DB Provider for OLAP Services 8.0
Server Information:
Server Type: Server
Server: <server ip address>
Data Source:
User: <domain>\<NT account>
Password: <NT password>
Error: "No cubes were found. Please check that you have permission to view cubes on the database server."
I tried accessing the cubes using the same data connection via excel pivottable and was able to access the cubes successfully.
Badly need help!

Answer 1

Hi Everyone,
As I have been working with MSAS 2000 and I reconmmend to install SP4 on the MSAS 2000 since BO XI R3 according to Support plataform it says that it is supported from SP4.
As well verified that you have access using the security role using your Windows AD authentication since Microsoft Service Analysis does not have its own authentication mode to connect basicatly rely on Windows AD.
If you want more information check this link.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx#EXFAE
Also check the service account on the same link above.
Receive Client Security Credentials Via Middle-Tier Application
The MSSQLServerOLAPService service account is irrelevant in the typical client-server environment. In this environment, the user application connects directly to the Analysis Services computer to execute a query or create an object, and passes the user's credentials directly to Analysis Services for evaluation. Access is granted or denied by Analysis Services based on cell-level and dimension-level security.
However, if the client application attempts to connect to Analysis Services through a middle-tier server, the authentication process is not quite so simple. Normally, security credentials cannot be passed over multiple computers. However, if the middle-tier application server and the Analysis Services computer support Kerberos authentication and delegation, the client's security credentials can be passed by the middle-tier application to Analysis Services.
For Kerberos authentication, delegation, impersonation, and mutual authentication to work, the MSSQLServerOLAPService service must run under one of the following types of accounts:
u2022 Local system account (which has no network access rights).
u2022 Domain administrator account.
u2022 Domain user without administrative privileges in the Microsoft Active Directory domain, provided that a domain administrator registers the Service Principal Name (SPN) for the account separately using the setspn utility in the Windows 2000 Resource Kit.
Note   There are a number of steps you must follow to permit Kerberos authentication, delegation, impersonation, and mutual authentication to work. For information about these steps, see "Security Account Delegation" in SQL Server Books Online. Also go to Knowledge Base (support.microsoft.com) and see the article "Use Kerberos Authentication for Microsoft SQL Server 2000 Analysis Services."
Miguel Jimenez