All:

I have implemented a web-based OLAP reporting solution using SQL Server 2000
(SP3) and AS (SP3). Everything has gone well during development but, when
migrated to test... When my ASP application attempts to execute an MSOLAP
connection string, I get the interesting error below:

"Connection Failed. Property name was not recognized, 'SSPI'"

I'm thinking that the MDAC version on the IIS machine should be upgraded
(currently 2.6 SP2). The AS server carries 2.7.

Thoughts?

TIA

MTI

You need to check your MSOLAP provider version. Are you using MSOLAP.2 ?

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================
"Michael Thompson Isaac" <mti (AT) xbagroup (DOT) com> wrote

Mosha:

Thanks for the prompt reply.

No, I'm using the MSOLAP provider parameter. I'll change to MSOLAP.2 and
retry. I guess those old OLAP Services habits die hard... 8-)

Thanks!

MTI
"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote

Mosha:

Actually, I am using MSOLAP.2 for the connection parameter. Any other ideas?

Thanks for the assistance!

MTI




"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote

Can you run MDX Sample on that same machine, and put SSPI=kerberos in the
connection string - does that work ?

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================
"Michael Thompson Isaac" <mti (AT) xbagroup (DOT) com> wrote

Hi,

Make sure you have the updated provider for Analysis Services installed on
the
IIS server. In the older version of the provider the SSPI was not
supported. Use the PTSFULL.EXE of sp3 of Analysis on this server to see if
the problem goes
away.

PTSfull.exe will upgrade pts and will install mdac2.7, PTSlite will only
upgrade PTS.

HTH,
Bas

"This posting is provided "AS IS" with no warranties, and confers no
rights."

Bas, Mohsa:

The problem was, in fact, MDAC level.

Using Component Checker, we realized that the IIS machine was at 2.6 SP2. We
installed 2.7 SP1 XP, and all was right with the world. Now, in reading Bas'
post, it seems as though PTSFULL is a "safer" way to go. Will PTSFULL on the
IIS machine facilitate connections moreso than just MDAC 2.7 SP1 on the IIS
machine?

Thanks for your help!

MTI

""Bas Kersten [MSFT]"" <bask (AT) online (DOT) microsoft.com> wrote