Can OWC connect to AS 2005 Cube?

[Angi]

Hi

Does pivot table of "Office 2003 add-in Web and Components" support
connecting to AS 2005 Cube?
When connecting to AS 2005 Cube responses the error message:
Cna't connect to Server 'Localhost'. Server is busy or inactive.

My AS server is working.
So, want to make sure the Office 2003 add-in webpart can't connect to AS
2005 Cube!

Thanks!
Angi

 

[badlydressedboy]

Try giving the full name of your AS server - not just localhost - sometimes
this shortcut name will not work.

 

[Angi]

Thanks for badlydressedboy.
I've been tried to use Domain Name(full name), but still no work.
Any advice? Thanks!

Angi

 

[mat_net]

Angi, did you finally get a solution for this

 

[Antoine Prevot]

Angi, did you finally get a solution for this?

Hi there,

I managed to connect "locally" to AS 2005 with a PivotTable (OWC11). It's
quite simple :

- In sql server configuration manager (network & native client
configuration) : enable TCP/IP (disabled by default).
- In your connection string, use MSOLAP.3 protocol instead of MSOLAP.2,
that's all !

I have another problem now, i cannot connect to my cube with a remote client
....

Remote connections are enabled in the SQL Server2005 Surface Area
Configuration, but i still get an "Unspecified Error" in my pivot table

Any idea ? Angi ???

Tonio

 

[Alvin Bruney - ASP.NET MVP]

You will get more detailed error information from the pivot table if you
create a windows application project with the OWC. Then use the design mode
feature to try to connect to the remote site. The error failures that occur
there are more verbose than what is generated thru the API itself. See if
that helps any.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006

 

[Antoine Prevot]

You will get more detailed error information from the pivot table if you
create a windows application project with the OWC. Then use the design mode
feature to try to connect to the remote site. The error failures that occur
there are more verbose than what is generated thru the API itself. See if
that helps any.

Hi Alvin, thanks for your concern !

I'm already testing with a "minimal" windows application. It's juste a form
including a PivotTable and two textboxes (ConnectionString & CommandText). By
"use the design mode feature", you mean "forcing the ConnectionString
directly in the property panel" ? That's what i have done, but the error
generated remains the same : "Query could not be processed: The data provider
didn't supply any further error information".

I'll look further since i cannot see any "login rejected" log entries ...
i'm now trying to use a data pump, as described here :

http://www.microsoft.com/technet/prodtechnol/sql/2005/httpssas.mspx

I'll post later if anything works fine, but any help would be appreciated

And please, excuse my poor english, that's not my native language ...

Regards,

Tonio

 

[mat_net]

Thanks Tonio.
Solution was perfect.
Managed to connect the OWC pivot to the cube

Infact, TCP/IP was already enabled, but the Provider=MSOLAP.3 did th
trick.

Thanks!

and your english is good, no problem

 

[duwayne.willett]

I am getting very similar error, when trying to connect directly from
Excel using the Data-> PivotTable and PivotChart Reports... file menu.

We normally connect this way to our AS2000 cubes, format the chart or
table, then do a "save as web page" to create the OWC. Then we edit
the OWC as needed (in Visual Studio or even FrontPage).

Have an AS2005 cube deployed and built, which can be viewed from within
the BI Development Studio (and the browser is basically OWC, I
understand).

But when trying to connect with Excel 2003 I get the following error:

"Unable to open connection. Cannot connect to the server "server name
here." The server is either not started or too busy."

Using a fully-qualified domain name doesn't change the error.

Is there a way to get Excel 2003 to connect to an AS 2005 cube? Has
anyone done that yet?

Am probably overlooking something obvious....

Thanks,
DuWayne

 

[Antoine Prevot]

Hi mat, i'm glad i could help you, enjoy

But when trying to connect with Excel 2003 I get the following error:
"Unable to open connection. Cannot connect to the server "server name
here." The server is either not started or too busy."

DuWayne : your problem seems to be a "bad protocol" issue.

While connecting to AS2005, you must explicitely use the brand new protocols
: MSOLAP.3 (if provided in a connection string) or OLE DB for AS 9.0 (if
provided in a connection builder, ie: in excel).

Be sure that the protocol you're usin is "Microsoft OLE DB Provider for
Analysis Services 9.0". The other providers - Micosoft OLE DB Provider for
OLAP (8.0)? - won't work.

You'll find these drivers in your SQL2005 installation disc, look for a file
named "pts9.msi" if they are missing. If they still are missing after
installation, register properly the DLL with something like that : regsvr32
"c:\program files\common files\system\ole db\msolap90.dll".

Oh, and i finally managed to connect remotely, by re-re-re-installing office
2003 & PTS9, and of course, rebooting ... don't ask me why it works now,
since it's Monday, i'll take any good news "asis" ))