none
Failed to build the OLAP cubes (Project Server 2013) RRS feed

 , 
 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We are receiving errors when attempting to build our OLAP cubes.  We've attempted to install the 2008 version of the SQL server native client 2008 but still the error appears.  Please advise.

    Configuration:

    • Project Server 2013
    • SharePoint 2012
    • SQL Server 2012

    Error Message:

    ===== Initiating OLAP database build process =====

    [1/7/2014 2:00 AM] Cube build request message has been added to the Project Server queue ===== Verifying and running pre-build server event handler =====

    [1/7/2014 2:00 AM] Verifying and running pre-build server event handler ===== Determining database and OLAP database structure =====

    [1/7/2014 2:00 AM] Cube build initialization started ===== Building database and cubes =====

    [1/7/2014 2:00 AM] Cube build session started ===== Verifying and running post-build server event handler =====

    [1/7/2014 2:00 AM] Verifying and running post-build server event handler ===== Processing OLAP database =====

    [1/7/2014 2:00 AM] Process OLAP database session started ===== Process Completed =====

    [1/7/2014 2:00 AM] Failed to build the OLAP cubes. Error: Failed to process the Analysis Services database OLAP_FTF on the XYZ server. Error: Errors in the back-end database access module. The provider 'SQLNCLI10' is not registered.

    The following system error occurred:  Class not registered Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Project Reporting data source', Name of 'Project Reporting data source'.

    Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Project List', Name of 'Project List' was being processed.

    Errors in the OLAP storage engine: An error occurred while the 'Start Date' attribute of the 'Project List' dimension from the 'OLAP_FTF' database was being processed.

    Internal error: The operation terminated unsuccessfully.

    Server: The current operation was cancelled because another operation in the transaction failed.

    Tuesday, January 7, 2014 4:12 PM
    |

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote
    Hello, I had the same problem, solved by installing the SQL Server Native Client 2008 (http://go.microsoft.com/fwlink/?LinkId=123718&clcid=0x409) in the SQL Server 2012. After this, the cube OLAP  was build successfully.

    André Barroncas

    Tuesday, February 11, 2014 1:29 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Importek,

    Please have a look to a similar threads that has been answered.

    http://social.msdn.microsoft.com/Forums/en-US/a2696e29-e68e-45a8-8dae-fa8fa5640575/receive-the-following-error-when-trying-to-build-cube-errors-in-the-highlevel-relational-engine?forum=sqlanalysisservices

    http://social.technet.microsoft.com/Forums/projectserver/en-US/420958bd-4613-451c-ac06-a1f149f64da9/problem-when-trying-to-build-the-cube?forum=projectserver2010general

    Finally an article by Brian Smith:

    http://blogs.msdn.com/b/brismith/archive/2007/07/16/yet-another-olap-error-message-the-longest-yet.aspx

    This might be an issue of the SQL instance alias.

    Hope this helps.

    Guillaume Rouyre - MBA, MCP, MCTS


    Tuesday, January 7, 2014 4:29 PM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank Guillaume.

    I've actually reviewed several of the blogs from Brian Smith.  However, the team is apprehensive with implementing workaround which would require installing SQL Native Client 2008 on our Analysis Server running 2012 which is a shared environment. 

    Do you know if there are other workarounds or any certified solutions from Microsoft regarding this issue?

    Tuesday, January 7, 2014 5:49 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    You're welcome.

    I'm afraid that my Project Server skills don't go to this architecture technical level so I'll let other experts on the forum help you. But have you ensured that the alias is correct between SQL server and the Analysis service machine?

    Guillaume Rouyre - MBA, MCP, MCTS

    Tuesday, January 7, 2014 6:00 PM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, I've used XYZ as a placeholder for the actual server name. 
    Tuesday, January 7, 2014 6:05 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Importek

    You can keep the SQL Native Client 2012 on SQL Server 2012. 

    The SQL Native Client 2008 R2 needs to be on the front-end and middle tiers for project server.

    Cheers!

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, January 7, 2014 9:29 PM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Michael. 

    That is what we prefer to do, since our understanding is that native client 2012 is backwards compatible (apparently). We've tried only using the 2008 native client on the app and web front-end tiers but still run into this issue.   

    Tuesday, January 7, 2014 10:38 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Have you reboot servers after installation of native client  on project server.

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, January 7, 2014 11:38 PM
    |
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    You indeed do have to install SQL Native Client 2008 on your Analysis Server.

    the error is telling you that the Analysis Server cannot contact the SQL Server over the desired protocol.

    "The provider 'SQLNCLI10' is not registered" means that SSAS cannot talk to SQL using the version 10 library calls.

    simply install this component (do not uninstall any others as noted by Michael).  it will correct the problem.

    there is no issue with this being a shared resource.  other systems that wish to communicate with the 11 version library calls will find the SQL 2012 components also installed and work fine.

    this overall is due to Project Server 2013 still utilizing the 2008 R2 calls in the OLAP build process.

    It is a necessary step in all my deployments which use SQL 2012.  Clearly, a SQL 2008 R2 install will already have this component.

    this component is not required on any other servers.  (only the AS server, so it can communicate with the SQL server, even if they are on the same computer).

    Hope this helps,

    Thanks, Eric S. Pcubed

    • Proposed as answer by Ahmed Madany Thursday, March 31, 2016 9:44 AM
    Wednesday, January 8, 2014 2:09 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Importek,

    I have recently experienced this issue and as Brian Smith has already explained the reason on his blog

    http://blogs.msdn.com/b/brismith/archive/2012/11/12/project-server-2013-requirements-to-build-an-olap-cube.aspx

    Project Server 2013 still needs 2008 Native client to connect to Project database, similar as we needed earlier version of native client with OLAP via 2010. Only solution is to install SQL 2008 R2 native client on Analysys server. unfortunately no workaround

    Hrishi Deshpande Senior Consultant


    Wednesday, January 8, 2014 2:49 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    My bad.  I answered question to quickly. I looked at my SQL 2012 Server in my lab and saw 2012 Native Client installed and stop looking. I went back after reading ErockP3 answer and looked back my SQL server. I see 2008 R2 Native Client is also installed. Apparently you can install both on both on same server. Strange but true.

    Cheers!

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Wednesday, January 8, 2014 2:53 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, we bounced the servers once we installed. No luck.
    Wednesday, January 8, 2014 10:45 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you install 2008 R2 native client on every server running with Project Application service in addition to SQL and Analysis server.

    Once installed restart Project Application service before initiating OLAP cube  build.

    Hrishi Deshpande Senior Consultant

    Wednesday, January 8, 2014 10:48 PM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Hrishi, we've read this "workaround" as well.  It just seems like a band-aid solution.  We will attempt this in our DEV/FTE environment and conduct some compatibility testing.  I'm really surprised that MS hasn't issued a fix for this yet... 
    Wednesday, January 8, 2014 10:50 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I don't think this is an workaround. At the time of  Project server 2013 release , SQL server 2012 was not released. At that time current version was SQL server 2008 R2, Support for SQL 2012 was added later.

    Hence to me it makes perfect sense that though Project can work with SQL 2012 still some components requires 2008 R2 components, which is lot eaiser than re-writing the entire code.

    Hrishi Deshpande Senior Consultant

    Thursday, January 9, 2014 12:48 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    It is documented that Project Server 2013 is supported by SQL Server 2012 (64-bit) and SQL Server 2008 R2 with Service Pact 1 (SP1) (64-bit). 

    MS should have denoted that it was partially supported by using 2008 R2 components. 

    Thursday, January 9, 2014 7:00 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Tried deleting the OLAP cube if it exists and put sure that the proper accounts are setup in the AD groups on the analysis server.  Try rebuilding

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Sunday, January 12, 2014 12:01 AM
    |
    Moderator
  • Question
    Sign in to vote
    2
    Sign in to vote
    Hello, I had the same problem, solved by installing the SQL Server Native Client 2008 (http://go.microsoft.com/fwlink/?LinkId=123718&clcid=0x409) in the SQL Server 2012. After this, the cube OLAP  was build successfully.

    André Barroncas

    Tuesday, February 11, 2014 1:29 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I agree that the fix is to download and install the SQL Server Native Client 2008 or SQL server Native Client 2008 R2 on the SQL Server. 

    Cheers!

    But then I wonder if that breaks other  apps.   Talk with SQL DBA.

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Saturday, May 2, 2015 11:13 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the answer, it is working now
    Thursday, August 20, 2015 1:47 PM
    |