Skip to main content

Project Server 2007 ActiveX Component Can't Create Object: Cube build failure against SQL Server 2008 Analysis Services

Update: so we are getting the "cannot connect to repository" error. Having rummaged around I have just seen reference to the need for SQL 2008 Native Client install also... gonna check this out next


So, i am seriously stuck on something... hopeing to work this through today but thought I would share:

Consider....

Server Architecture:
Server 1 : DB server SQL 2008 / AS2008 / rS2008
Server 2: App server MOSS2007, Project Server 2007, 2008 Reporting Services addin for SharePoint
Server 3: WFE including 2008 RS addin for SharePoint

Configuring Server 2 for CBS
- install Native Client - OK
- Install Management Objects (XMO/AMO) - Failed (higher version aleady availble)
- Install BC

Cube run fails due with Unable to Create ActiveX component... error

http://support.microsoft.com/kb/972694

Ran the hotfix package mentioned for XMO and got the error "unable to connet to analysis services repository" - relates to native client

So as we are now in an unknown state I am now running the following action plan:-

- Revert VM lab back to stable point :)
- uninstall RS addin and reboot
- reapply Native Client, XMO/AMO, BC
- Run Cube (hopefully successfully)
- run XMO CU5 hotfix pacakge
- Run cube (hopefully successfully)
- reapply RS addin for sharepoint
- Run cube (hopefully successfully)

see you in 24hrs.....

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Restoring PWA Site to another Web App in the same Farm

The scenario is this: SharePoint 2016 Farm with Project Server Two Web Apps Development UAT One PWA on Development Web App. I want to copy the PWA Site on Development web app to UAT to support a testing cycle. As far as I knew there were two options: 1) Content Database Restore and Attach Process would be backup your Dev Content Database, Restore to a new Content Database for QA, then mount the database on the appropriate web app and your off.... Problem:  Although you can do this with the -AssignNewDatabaseID switch in Powershell (to avoid two content db's having the same database id) the Site Collection (PWA) in the db still retains its SiteID which means there is a duplicate SiteID in the Configuration Database.  This stops the PWA site being created and alllocated correctly and becomes essentially orphaned. This method is only any good for MOVING not COPYING Back to the drawing board... 2) Backup-SPSite / Restore-SPSite I didn't believe this ...
1 comment
Read more

SP2 released

Office Project Server 2007 Sp2 has now been released.  see the details here - http://blogs.msdn.com/chrisfie/archive/2009/04/28/announcing-service-pack-2-sp2-for-microsoft-project-2007-and-microsoft-project-server-2007.aspx .  see teh webcast here http://blogs.msdn.com/brismith/archive/2009/04/28/project-server-2007-service-pack-2-sp2-is-now-available.aspx Blogged with the Flock Browser
Post a Comment
Read more

Reporting from Project Server 2016 - multiple sites and userviews

Just a quickie... I've been interested in how MS have handled the "multiple PWA sites in a Content DB" thing since I read that this was their new approach.  Most of my reporting is via SSRS so i am reliant (still... in 2016) on DB queries rather than OData feeds (tsk) and this "querying a PWA DB with more than one PWA site in it is unsupported" quote was worrying me. So it looks like what is happening is this. When you create the first PWA site in a Content DB it hard-codes the SiteID into the _Userview view design elements.  This means that your first PWA Site is the default.  All the data for subsequent sites are still held in the tables against separate SiteID's but you cannot utilise the OOTB _Userview components (see below) SELECT        ProjectFields.... FROM            pjrep.MSP_TVF_EpmProject('FF19B767-CA6D-4C4C-B123-C0B5AE5354D6') AS MSP_EpmProject  LEFT OUTER JOIN         ...
Post a Comment
Read more