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.....

Comments

Popular posts from this blog

Issues update on #projectserver2013 - Timesheets and Publishing

Reporting Publish ** updated with links to other related discussions, and a VBA macro ** the following issue has been noted on publish since June 13 CU was applied: ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='4d869e56-f625-e311-bb41-005056b90052' QueueMessageBody='Project UID='e3f49977-b2bc-e211-8559-005056b90052'. PublishType='ProjectPublish'' Error='Object reference not set to an instance of an object.'. I have seen this noted previously on a similar issue: http://nearbaseline.com/blog/2013/06/ms-reporting-project-publish-jobs-failed-after-aprilcu/comment-page-1/#comment-14741 This is  caused by Baselined Milestones having NULL Baseline Cost values Original bug note with potential workaround is here: http://blogs.msdn.com/b/brismith/archive/2012/05/23/project-server-2007-reporting-project-pu...

#projectserver2013 VIEW FAILURE: The view failed to load. Press OK to reload this view with the default settings. Press cancel to select another view.

** UPDATE ** includes notes relating to secondary bug where Timesheet is created without Administrative tasks. Does this ring any bells? This has been bugging me for months, but finally I have a repro for this: Issue Summary:  When a task is deleted from a plan that is approved into a previous or current timesheet - even when there are no actuals on the task - you can no longer view the timesheet The following repro has been proven: - Setup system with Single Entry Mode, with enforced Status Approval before Timesheet Approval - Create resource as own timesheet manager - Create new project - Create two tasks in the same week, starting monday with 5 days duration:  1) Task to assign actuals, 2) Task to delete post submission - Assign Resource to tasks - publish project - as Timesheet User, go to the appropriate timesheet period for the tasks created - Assign actual work to one task (task 1), leaving task 2 with no actual work - Submit timesheet - as Project ...

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 ...