I used the sample OLAP application from MSDN magazine Oct 2003 to develop a
similar application connecting to a cube (RIMS) created in a local SQL
Analysis database. The code from the application works for 'Foodmart 2000'
but in the application I modified for my cube, I get the error message when
I run the program "Database RIMS does not exist". Stepping through the code
doesnot generate any error messages. Is there something I've overlooked in
the code or configuration of Analysis Services? A pivot table in Excel
connects to the database RIMS.

Thanks.

Dan

Might you have not updated your client-side PTS OLEDB provider?
If you were still using the SQL 7 version, you can see databases so long as
they don't use new SQL 2000 features.
This happens frequently with Foodmart since it is a fairly simple database.
Particularly when you mix older copies of Office, e.g. Office 2000 since
they ship and install SQL 7 PTS.

I would go to your SP3 Analysis Services folder and run ptslite.exe located
in the msolap\install\pts folder.
Make sure your connection string says MSOLAP;2 as the provider.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Dan Slaby" <dslaby3 (AT) comcast (DOT) net> wrote

I have SQL Analysis 2000 with SP3a running on my XP SP2 and am unable to
install ptslite.exe ( KBA 829747) because Analysis is already installed. I
am able to see my data cubes in an Excel 2003 pivot table, but not able to
in code. I get the error message when I use this connection string (using
the computer name doesn't help):

Set cat = Server.CreateObject("ADOMD.Catalog")
Set cst = Server.CreateObject("ADOMD.CellSet")
OLAPServerName = "LOCALHOST"
cat.ActiveConnection = "Data Source=" & OLAPServerName & ";Initial
Catalog=RIMS;Provider=msolap.2;"

Any other suggestions?

"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

Problem solved. I have a local logon and a network logon. Creating a
security role with the appropriate user enabled the connection string to
work correctly. Thanks for the support.

Dan

"Dan Slaby" <dslaby3 (AT) comcast (DOT) net> wrote