Re: Excel 2007 connection

[Excel 2007 will not connect to SSAS]

I was not able to get it working until now.

I made a totally clean install of OS and Office 2007 and used MSXML, OLAP9
and Native Client from the Service Pack 1 version - no good.
I then went for the CTP SP2 Version. (I did check the file dates were
updated to make sure they did install) - no good. I only installed SP2 to
the client though, I left the server untouched on SP1.

I did try to re-register msolui90.dll, but that fails with an error. The
error meaning was something along the that this type of dll cannot be
registered (wrong file?)
I did repeat that on my day-to-day work machine instead of a test system,
and there it DID register the dll... very strange, the test system is a
totally clean install and *should* be more predictable than my daily work
system.

I am out of ideas really. Google seems to list quite some posts now
regarding Excel 2007 and OLAP, most of them using "sharepoint services", but
there seems to be a bigger problem somewhere.

Can someone confirm he can connect from Excel 2007 to SSAS? (on different
machines in different domains over http using Windows Authentication and
giving the credentials of a server-recognized user)


"Bjørn T" <bti@xxxxxxxxxx> schrieb im Newsbeitrag
news:1164291932.438947.154510@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The Feature pack also contains the SQL Server Client (Native Client)
tools. You should install it.

RE
BT



Akshai Mirchandani [MS] skrev:
Can you try installing the SP2 CTP2 (Tech Preview) OLE-DB Analysis 9
driver
instead? This strikes me as something that may have been fixed in SP2...

SP2 CTP2 is available from below:
http://www.microsoft.com/sql/ctp.mspx

There is a link to the feature pack from there...

One thing you may want to try is to use regsvr32.exe to re-register the
DLL
msolui90.dll -- usual warnings apply...

HTH,
Akshai

--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.

"Ralf Mayer" <Ralf.Mayer1@xxxxxx> wrote in message
news:#ML0QnVDHHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
I am afraid I do not know what software you mean...

I know I need to install the OLE-DB Analysis 9 driver, which in turn
requires the MSXML 6 driver to make Excel 2003 work.

I usually download these from Microsoft.com, I find them by typing "SQL
Feature Pack April" in search window. There is also a feature pack dated
November 2005, I do not know if these are different from the April 2006
versions, I always use April versions anyway.

But I installed them, I am quite sure about that since I wanted to test
without first, just to see if they are part of Office 2007 now. Without
them did not work, so I installed them both as I do for Excel 2003.
After
adding them, it still did not work though...

Is that what you mean? Or are these SQL 2005 some special additions to
Office 2007 already?

"Bjørn T" schrieb...
Have you installed the following:

1) SQL Server 2005 OLAP driver (SP1)
2) SQL Server 2005 Client compoment (SP1)

You should have installed both. Works real nice on my machine.

BT




Ralf Mayer skrev:
I wanted to evaluate the new features of Excel 2007 regarding cubes,
so
I
set up a test machine with it.

I do have SSAS 2005 SP1 running through IIS, and several users connect
with
Excel 2003 - works nice. The IIS is set to use Windows Authentication
only,
so my users have to enter a username and password of an account on the
server to get their data. The user accounts are enabled in SSAS with
different access settings. Works really fine!

With Excel 2007, I cannot connect anymore, I get an error 0x80040e4d.
This
error is mentioned within groups as (DB_SEC_E_AUTH_FAILED) several
times,
but no answer really fits to Excel 2007 and Olap - some are with Jet,
ADO,
ODBC but nothing "recent" pointing to Excel 2007.

I am doing nothing different that I did for almost a year with Excel
2003,
in fact I just need to take one step to the next system and can
connect
with
Excel 2003 using the same account, server, http address and all. I did
try a
couple of accounts, passwords and so on to make sure that is not my
problem
or that typing of password was wrong.

As side note, if I set the IIS to allow anonymous access (and have IIS
map
to a user the SSAS knows) I do get access with Excel 2007, so it is
REALLY
the authentification that fails.

Any explanation?





.

Relevant Pages

  • Re: generating MS-Excel report through ASP.Net without installing
    ... actually due to security and volnurable issues we decided not to install ... excel in web server machine. ... > server and I code that all upon users request from website. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Experience with 2003 & 2007 on same computer?
    ... each version of Excel uses its own set of registry keys. ... To find the correct path, open XL 2003, open VBA, CTRL G to ... Even if you install just Excel, ...
    (microsoft.public.excel.misc)
  • Re: Experience with 2003 & 2007 on same computer?
    ... each version of Excel uses its own set of registry keys. ... To find the correct path, open XL 2003, open VBA, CTRL G to ... 2007 if I install only Excel 2007? ...
    (microsoft.public.excel.misc)
  • Re: DTS Package fails when importing Excel sheet
    ... 'TypeGuessRows' under the registry path ... > You do not need to install Excel on the server as the ability to use Excel ...
    (microsoft.public.sqlserver.dts)
  • Re: Excel 2003 + 2007 on dev machine - deployment problems on Excel 2003 machine
    ... I then started developing my application, and realised when I came to the Excel part that most people would be using Office 2003. ... At this point I installed Excel 2003 alongside my Office 2007 install. ... Yes, both versions of the Excel PIAs are present - however, Excel 2007 installs with the PIAs some redirect assemblies which mean that when an application requests an Excel 11 PIA, they're redirected to Excel 12. ... I noticed yesterday that actually the file this refers to in the Properties view of this reference is the 12 version. ...
    (microsoft.public.dotnet.framework.interop)