Analysis Services on SQL2000 SP4

"unable to browse the dimension [dimension name].

Provider cannot be found. or Unknown Error.

Everything else looks good, like processsing, looking at the tables,fields, datasource is connected.

Dear,

Did u used a shared dimension in the cube.

from

sufian

|||

I tried both, shared and not shared. Input is from Access db. It fails already in the Create Dimension Wizard screen. Data should be populated on the screen

|||

Can you please describe your situation in bit more details.

What version of Analysis Services you are using?
What relational database are you using?
What OLEDB provider ?
What is the exact error message you are getting and at what stage?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Analysis Services Version 8.0.194

Input Database MS Access2000

Provider = MS Jet 4.0 OLE DB Provider

OS = Windows 2000 Professional with SP4

Error appears already on the Finish the Dimension Wizard Screen

"Unable to browse the dimension [dimension name]. Unspecified Error.

I have processed the cube and the dimension. I get the count on all records processed.

Also if I try to browse data on individual dimension(s)I get ;

"Unable to browse the dimension [dimension name]. Provider not found or not properly installed" however testing the database connection works fine.

|||

What happens if you try to browse your cube after your processed it? Do you see dimensions and measures?

I suspect you just having problem browsing dimension. Is that so?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

FYI - I am using Professional SQL Server 2000 Programming by Robert Vieira (WROX) See page 920 top(data is already displayable for the Customer Dimension at creation time. I fail right there.

To answer your questions: I cannot browse the cube after processing - Same error "Unable to browse the cube - unspecified error".

Same applies to the dimensions.

Validate dimension, Count Dimension members and metadata all check out. Processing is going to normal end for both cube and individual dimensions and I get the correct number of members that I am supposed to get with no errors in processing.

|||

It is possible that you got some client components installation corrupted.

Try installing "Microsoft SQL Server 2000 PivotTable Services " from http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks again, but no cigar. To install pivot tables I had to de-install Analysis Services, Install the pivot tables and re-install the Analysis. However I can't browse the results and/or the cube.

I went a step further installing SQL Server 2000 and Analysis Services on a different PC, using Windows XP with the same negative results.

Unable to browse the Cube [cube name] or

Unable to browse the dimension [dimension name]

Unspecified error. It will help how to find and read the OLAP server error logs or dump for a better understanding of what is wrong.

Since I am using the same version of the SQL Server (developer edition 8.00.760(SP3) from Microosoft) on both PC's I tend to believe there is a limitation on it. I have no other logical explanation.

|||

Are you talking about SP3 or SP4? The title suggests you'd like to install SP4.

Is that so?

Please make sure your run the same service pack version of the server and client.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Veo,

Is the Access database stored on a network drive? The Analysis Services service would normally be installed to run as a system account which would not have access to network resources.

|||

I am the administrator of my PC. Acces is installed on the same PC with the SQL Server.

Operating system Windows2000 has SP4 applied and SQL Server has SP3 applied.

My next step will be to import Access data base into SQL 2000 to see if that makes a difference

|||

I think you should be better off with keeping your database in SQL Server.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.