SMO collection failed to install because of higher version...

[Leonard]

Our architecture:
Application Server - Server 2008 x64 project server 2007 + sharepoint server
2007
DB Server - Server 2008 x64, SQL 2008


Error message when building CUBE in PWA:
Failed to build the OLAP cubes. Error: Analysis Services session failed with
the following error: Failed to connect to the Analysis Services server
BriSmithSQL08. Error: ActiveX component can’t create object

Error message when trying to install SQL Server Management Objects Collection:
Installation of Microsoft SQL Server Management Objects Collection failed
because a higher version already exists on the machine. To proceed, uninstall
the higher version and then run Microsoft SQL Server Management Objects
Collection Setup again.

What we have tried:
- The SMO msi is the latest version (Dec. 2008)
- Verified in \Program Files\Microsoft SQL Server\100\SDK\Assemblies.
Assemblies directory doesn’t exist. Therefore where's the "higher version"?
- Used forced install (msiexec.exe /fvecmus) on the SMO collection msi; no
effect.

I have configured cube on project 2007 with sql2008 before following the doc
on technet and it works. Now, nothing much changed. What could cause this
error for SMO installation? We have SCOM on our application server, could
that be the reason for "high version" of SMO?

Your input is highly appreciated! Thanks in advance!

LX

 

[Martin Laukkanen]

I also had this issue today and found your post helpful, I had exactly the
same situation and error, and eventually in my case I found that it was the
"SharePoint Addin for Reporting Services 2008" that I had installed that was
causing the "a higher version already exists on the machine" error when
installing XMO, uninstalling that then reinstalling December 2008 XMO_64
fixed the cube issue!

Next week (it's too late on Friday now! :}) I'll reinstall the addin and
fingers crossed all is still good!


Martin

 

[GabrielG]

We are experiencing the sam error. Here is the link to the msdn thread, but
no solution so far.

http://social.msdn.microsoft.com/Fo...s/thread/1b5a7a88-0bf6-4f17-b596-6ba5097e7ab6

Has anyone been able to make this work 100%.

Thanks,