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

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

TPG Apps Highlights - Risk Matrix #projectonline #projectserver #risk

This post is the first of a series to highlight the apps available for Project Server and Project Online from the SharePoint store  ( https://store.office.com/search.aspx?productgroup=SharePoint&qu=tpg ) and direct via your local TPG office. The first of this series will look at the s imple plug-and-play apps that all users of Project Online can make use of quickly and easily.   T hese are: Risk Matrix  Milestone Trend Analysis (MTA) WBS Chart viewer Next we will focus on the challenge of  Resource Request Supply and Demand by demonstrating our more recent TeamLink and TeamManager apps. Team Manager App is a Resource Manager/Owner app for allocating resource supply to Projects and BAU activities and monitoring demands against commitments Team Link App is a PM tool for monitoring Project demands vs the supply provided by the Resource Managers  Finally I will highlight some of the benefits of our integration tools when used i...
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