Skip to main content

How to Configure Project Server 2007 Analysis Services with SQL 2008 SharePoint Addon for Reporting Services

SQL 2008 analysis services for mops2007

Well we sorted it

It’s a bank holiday today but here’s the route we took

Installed SQL 2005 components from dec2005 feature pack on app server

Native client

Bacwards compatibility

  • note: xmo not installed due to SQL 2008 reporting services addon for sharepoint wouldn’t let it

Installed the following bits on app server to get things working

SQL 2008 native client

Xmo 2005 sp 3 cu5 - to get around the previous issue noted KB 972511

Ta daaa everything worked!!!

Only took a week :(

edit - postback to Brian Smith’s blog http://blogs.msdn.com/b/brismith/archive/2010/06/15/project-server-2007-analysis-services-issues-when-using-reporting-services-add-in-for-sharepoint.aspx

Labels:

Comments

  1. Geraint PughJanuary 17, 2012 at 1:37 PM

    Hi Carl,

    I know its been a long while since you posted this but the dreaded problem has crept up again when I have rebuilt a customers SP & Project 2007 environment. I have followed Brian's very detailed article and also followed the updates above caused by RS Add in.

    The XMO installer runs fine however I still get an issue with the Cube Builder service complaining about Application Server needs to have Analysis Services server DSO Component installed.

    Does the server need a reboot after installation of the XMO tools to take effect?

    Many Thanks

    Geraint

    ReplyDelete

Post a Comment

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...
4 comments
Read more

#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 ...
6 comments
Read more

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