Project Server 2013 Requirements to build an OLAP Cube

There appears to be an error currently on our TechNet documentation at indicating that the version of the Analysis Management Objects required when building an OLAP cube from Project Server 2013 depends on the version of SQL Server you have running Analysis Services.  In fact it does not – and like previous versions of Project Server we actually require a specific version that our code talks to – regardless of which version it will actually be building the cube on.  For Project Server 2013 we require the ‘10.xx’ release so anything from RTM SQL Server 2008 Analysis Management Objects – version 10.0.1600.60 through to the SP2 of the SQL Server 2008 R2 10.50.4000.0 will work.  The only one that does not work in my testing is the SQL Server 2012 version.

*** Update 11/13 - I should also point out that the requirement for the SQL native client is fulfilled by the SharePoint pre-requisite installer - so no need to add anything - but if you remove it then you will likely get an error like "Error: The 'SQLNCLI10' provider is not registered on the local machine" If this happens then just re-install SQL Native client 10.x such as the one from - look for sqlncli_amd64.msi. End Update ***


If you have the 2012 version, or if you haven’t loaded any Analysis Management Objects then you will see the following error when trying to build a cube.



[11/12/2012 10:17 AM] Failed to build the OLAP cubes. Error: The attempt to build the OLAP database on server BriSmithSQL failed, the SQL Server Analysis Services Analysis Management Objects (AMO) client software may not be installed on this server, please install/update the client on this server and retry. The underlying exception was: Could not load file or assembly 'Microsoft.AnalysisServices, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

The SQL Server 2008 R2 SP2 version is the most recent and can be found in the feature pack at and you are looking for SQLSERVER2008_ASAMO10_amd64.msi (which is the x64 version) (***Update *** corrected the name - thanks Adrian!).  Direct download link is here. I haven’t tried building a cube against a SQL Server 2008 instance – that may need to use the earlier SQL Server 2008 feature pack – most recent is SP2 if you find the R2 version above doesn’t work.

For those still having a hard time finding where we have hidden the cube building option (I admit it – it took me a while…) can find it either by going to Central Administration, Manage Service Applications, Project Server Service Application (or whatever you have called yours) and then use the drop down for the specific PWA site you are interested in and click Manage which will take you to the following page – and OLAP Database Management is the link you need:


Or Central Administration, General Application Settings, and click Manage under the PWA Settings header.


If you go this root you may need to change the PWA site in the upper right hand corner.


And if you are using the preview of Project Online (or you are reading this after the full release) and can’t find the link to OLAP cubes it is because that feature isn’t available in the online version.

Comments (13)

  1. Adrian says:

    Hi Brian,

    thanks for the update. I guess most us who have been around a while figured that one already.

    One point I'd like to add is that if you are using OLAP data in PerformancePoint dashboards like the Project BI Center suggests, all SharePoint application servers (running PerformancePoint service) need to have Microsoft® SQL Server® 2008 R2 ADOMD.NET installed from the aforementioned Link, again regardless of SQL Server.

    On another note:

    Is anyone else having the issue that the PWA 2012 OLAP database's only role ProjectServerViewOlapDataRole is empty? None of the PWA Administraotors, Portfolio Managers/Viewer and account with the View OLAP permission seem to be added, so currently, only SSAS Admins are allowed access in my tests.

    Kind regards,


  2. ASAMO10, not ASOLEDB10 says:

    Hello Brian,

    your download is correct and points to ASAMO10 which is the correct required feature to create OLAP cubes. However, in the text, your instruction is to install ASOLEDB10 which is not sufficient.

    Kind regards,


  3. Thanks Adrian – agreed – ASOLEDB10 is not required – I must have copied/pasted the wrong name.  I'd installed AMO so many times that day in various versions I shouldn't have made that mistake.  I have corrected the posting.  I am also seeing the empty role – I will investigate what's going on here.

    Best regards,


  4. LJB says:

    Hi Brian,

    I have the same error as above. I found the following technet article which states that the Cubes can be built on SQL 2012. Has there been any work around that you know of to get the cubes to work on SQL 2013?…/ff465339.aspx

    "Project Web App supports building OLAP cubes on SQL Server 2008 R2 Analysis Services and SQL Server 2012 Analysis Services."

  5. Sean says:

    This is ridiculous.  Why can't you have an automated installer – like SharePoint?  You guys have screwed this up for the past 10 years.  It's a g-d damn joke.

  6. Thanks for the feedback Sean – I will see that it gets to the right ears.

    Best regards,


  7. Patrick Yong says:

    Thanks for the info, but what about SQL Server, do we need enterprise edition?

  8. Hi Patrick, Enterprise version not specifically required for OLAP – Standard will work – but you may want Enterprise for some of the other benefits it delivers –…/cc645993.aspx

    Best regards,


  9. MSOLAP3 vs MSOLAP4 says:

    Hi Brian

    We have SQL2008R2 SP2 installed and PS2013 on a separate server (with SQLNCL10, ASAMO10 and ASADOMD.NET10 installed also)

    When we build cubes all the data connections to that cube are built with the MSOLAP3 provider rather than MSOLAP4, which means our Excel2013 clients cannot communicate to the Cube without updating the data connections.

    There was right at the start a rogue 2005 version of ADADOMD.NET installed on the SP server, which has since been uninstalled, server restarted, old DC's and templates deleted, and cube recreated, however this hasn't resolved the issue.

  10. Greg Besso says:

    Sean has a point, why can't Microsoft just standardize the way the companion software components are included (or not as in the case here) for the server products? Just install the software that we need to use the "real software" when we install a million prerequisites to begin with 😛

  11. Ashish Sankahla says:


    It worked after installing SQLSERVER2008_ASAMO10_amd64 and restarting the server.

  12. Harish Engolkar says:

    One thing i saw which is a significant change in Project Server 2013 is the permissions to build the OLAP cubes. It can only be done by the Farm admins unline in PS 2010. Is there a way that we can grant the PWA admins the access it used to be in PS 2010??

  13. Maignan says:

    Hi, Brian
    Technet sees SQL Server 2014 as supported by Project Server 2013. Nevertheless, even with Project Server SP1, we cannot build the 2014 cube : both cannot speak to each other. At the present time, would you maintain that SQL Server 2014 is also supported for OLAP usage, with the same SQLSERVER2008_ASAMO10_amd64.msi client . Should this client be installed on both SQL and SharePoint servers ? and with a farm admin account ?

Skip to main content