Using Office XP / Analysis services SP3

I have created a few web pages from excel pivot table
services. In my network I have no problems.
I have created the exact replica SQL server, analysis
server and data in another office. When the other office
views the web pages, created by me and the other network's
excel, they are unable to view the "export to excel icon"
its grayed out.
The only difference is the machine, so I am guessing it is
a version issue.
My version of excel, which works, is version
10.2614.2625. Their version is higher, not sure of the
exact version.
If add:
<OBJECT CLASSID = "clsid:5220cb21-c88d-11cf-b347-
00aa00a28331">
<PARAM NAME="LPKPath" VALUE="license.lpk">
</OBJECT>
to their web pages using a key generated by my version
office it works no problem. If I generate a key off
theirs it does not work.
I checked the Microsoft kbase and didn't find anything.
Could they have a bad office XP installation or something
because the web pages are view only mode?

Thanks

Hutch

I had the same problem and I solved it a different way. For me, the way the
OWC user was being authenticated was the key. Sorry but I don't remember the
reasoning perfectly, all I know is that our current setup works.

My remote users were on a different Windows NT domain from the analysis
server. I order for them even to use the OWC I had to create local Windows
accounts for them on the analysis server (not domain accounts, local
accounts). These accounts had to have the same username and password as
their account on their own domain. I put them in the local Users group and
added them to the Role on the analysis server. This is talked about in this
very useful MS article:

http://support.microsoft.com/default...microsoft.com/
servicedesks/webcasts/wc120401/WCT120401.asp

This would allow the OWC to connect to the analysis server. I can't remember
if this had the Excel button work, or if the next step was also needed.

The next step was for any users who needed to use the 'drillthrough' button.
This never worked under the above setup. In order for this to work, those
users had to be given domain accounts on the same Windows NT domain as the
analysis server. These accounts were not added to the OLAP Role. The reason
for creating these accounts was because I found the drillthrough never
worked unless the users actually looged off their machines in their domain,
and logged on to the domain of the analysis server (yes, very annoying and
requires trusts between the domains).

There may be one other important piece to the puzzle - the connection string
for the OWC. I think I tweaked this also. Mine looks like this:

ConnectionString = "Provider=MSOLAP.2;Integrated Security=SSPI;Persist
Security Info=True;Data Source=<%= sServer %>;Client Cache Size=25;Auto
Synch Period=10000;Initial Catalog=<%= sDatabase %>"

Good luck

"hutch" <hutch (AT) nospam (DOT) com> wrote