Can OWC 11 work with SSAS 2005 cubes?

Can OWC 11 work with SSAS 2005 cubes?

• sheriffdaone

  Sounds to me like it might be a connection string issue.

  Have you tried tracing the connection via SQL Profiler (an AS trace) to see what credentials (and error message) is occuring on the server

  If you're using OWC from within a browser, I'd also like to suggest you temporarily put the target server into your trusted sites, so that you're assured that the browser isn't blocking anything. Once you have it working, then you can back it off.

  
  
  

• ipcoken

  Let me try to trace it using SQL Profiler, will post the result here. I have try to put the target server as the trusted site, still problem

  Alex

  
  

• Ralph Gasser

  Per the support engineer:

  I think our ISV has got the answer. The MSOLAP 9.0 provider is the main reason of the issue.

  We can get provider from:

  Feature Pack for Microsoft SQL Server 2005 - November 2005

  http://www.microsoft.com/downloads/details.aspx displaylang=en&FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc

  -brenda (ISV Buddy Team)

  
  
  

• Mr. Greg

  Hi Dave,

  Currently i am trying developing web application using OWC11 and SSAS 2005. It works fine when it is accessed from intranet using TCP/IP connection, however, it fails when it accessed from internet users.

  I have tried using http access (msmdpump.dll), it fails. My SSAS machine is separate from web server, and it is located behind firewall.

  Do you have any idea what's wrong with it

  Any suggestion will be very appreciate, thanks.

  
  

• tobis

  This followup was posted and I wanted to share the engineer's response as well in case anyone finds it helpful.

  Question:

  When I try to use OWC11 in ASP.NET. the control is disable and cannot use. can you explain me how I can do that Is it possible to use similar last version of Visual Studio 2003

  Response:

  As the OWC is an activex control, it can be used in ASP.net in some way. If more detail information is provided, we can analysis why the control is disabled.

  On the other side, the sample:

  ASP.NET Server-Side Charting with OWC11 By ravie gopal

  http://www.codeproject.com/aspnet/owc11article.asp

  I love this sample, it utilizes the OWC in great way.

  -brenda (ISV Buddy Team)

  
  
  

• jazg

  per the engineer:

  The basic use of OWC connecting SSAS is very simple.

  1. Create a windows application
  2. Drag a Pivot table to a form
  3. Config a connect string of the OLAP server by wizard

  -brenda (ISV Buddy Team)

  
  
  

• bfox

  Got the solution from another forum Dave.
  
  - In SQL Configuration Manager, SQL Native Client Configuration->Client Protocols enable TCP/IP if it is disabled
  
  - In the OWC data change the Connection string from "Provider=MSOLAP.2" to "Provider=MSOLAP.3"
  
  That works.
  
  I still have another problem with the Office Report View Pivot table that uses the OWC.
  
  Can't see a Save button in the webpart, so the pivot table gets reset with no fields on a page reload.
  
  Have posted it at
  http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=127501&SiteID=1
  
  Could somebody look into this.
  

  
  
  

• Danny Tsai

  May i ask where i can get the sample on using OWC11 to connect to AS2005

  I having been trying to search for sample codes on it but seem no luck yet

  I have got one sample that connect to AS2000, but seems can't change to work wtih AS2005

  Thanks

  
  
  

• tarheit

  Hi

  How about for error "No connection is made because target server actively refused it" in OWC I am using OWC 11 connecting to SSAS 2005 in intranet environment. When view locally (in the server), the error didn't occur. Only when connecting from client machine. Also when using MS Excel 2003 to connect, the error didn't occur. Appreciate any help

  Alex

  
  

• nickc

  Per one of our support engineers:
  

  Since you're running this on a beta product, I can not confirm everything on the beta version. < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

  But, since SQL Server 2005 RTM has been released I have tested that we can use OWC 11 to connect the OLAP Services of SQL Server 2005. Please go ahead and install the RTM version. If this does not resolve the issue, please provide us with the detail steps to reproduce the issue.
  
  I hope this helps resolve the issue,
  -brenda (ISV Buddy Team)
  

  
  
  

• Packiyanath

  First, OWC 11 works fine with SSAS 2005. I have it running on a full internet server (locked down, port 80 only, etc, etc.). To verify, try using the sharepoint web parts (WSS 2003).
  
  As to your problem, the likely error is the connection string and/or a version incompatibility with the PTS services. You must make sure you're using the right version(s).
  
  Note: as an aside, I'd recommend you move forward to at least the June CTP. There were a number of bug fixes, wich could resolve your problem. The Sept CTP ave a number of reported problems with certain cubes (out of memory error) which is supposed to be fixed in time for the current release. Haven't tested it yet.   
  
  

• Cyndi

  Depends on the specifc error. But I can offer a few ideas:

  • Check the version dependancies. In the early, beta versions, compatibility between version wasn't maintained. Incorrect installs / setups would break it quite easily.
  • AS depends on Windows integrated authentication. (There's no HTTP style authentication mechanizm.) That means you need to review your security chain / setup very carefully. Try adding credentials directly to the connection string (which isn't an ideal set up) to see if that resolves your connection problems.
  • I believe that because of the AS security limitation, your AS server needs to sit in the same domain as your Web Server. Therefore they must either exist in the same DMZ, or the appropriate ports must be opened between the Web Server DMZ and the AS DMZ.
  • Remember that OWC is a direct connect object, so needs the associated AS driver on the client PC.

  As you're no doubt discovering, the security set up options are currently quite limiting in the current model, in particular when you must provide the highest degree of security around your AS server. My impression is that msmdpump is the weakest link in the archtecture, and would benefit from a redesign. It's something I'm looking at and/or looking for a 3rd party solution.

  Let me know how it goes.

  
  
  

• mallikarjun

  Hello Sharathps,

  Currently i have the same problem with yours, do you find any solution Any help will be appreciate

  
  

• Roberto Jimenez

  I am using OWC 11 to configure pivottables and charts on a sharepoint portal. I can view the data fine on the server which has both SSAS 2005 (where the cubes are built) and the sharepoint portal installed. If i view the same portal from a remote machine without SQL Server 2005 installed, I get the error "The Query could not be processed. The data provider didn't supply any further error information". I can however view data that is drawn from SQL Server 2000 Analysis Manager cubes.

  Is this an issue with the remote machine not having MSOLAP9.0 installed on it Or is there something else that is causing it I even tried creating a PivotTable from Excel 2003 on the client machine. It lets me connect to and create pivottables from SQL Server 2000 cubes but not SQL Server 2005 cubes. Please advise.

  
  
• Can OWC 11 work with SSAS 2005 cubes?