Email : info@epmstrategy.com | Call Us Now : 479-373-1374
:: Home :: Sitemap ::
Follow Us

Project Server 2007 – Cube Errors

 

By: Collin Quiring

 

This is about these Project Server 2007 cube errors:

ProjectServerViewOlapDataRole

Error ID: 17004

Error ID: 26000

 

In my ongoing Project Server 2007 analysis of the cube function, I have run across a few areas where I have had to research and determine what is actually happening.  In this case, I didn’t find much information that pertained directly to my issue.  I provide this information in the hopes that it helps you with similar issues you are encountering, or at least points you in the right direction.

 

On our server, we successfully ran cubes for some time.  Then, I went into the Cube – Configuration screen and I added every “Available Field” that I found in all of the cubes (Project, Resource, Task and Assignment).  That is when the errors started.

 

The cubes stopped building with the following error message in the Cube – Build Status screen:

===== Initiating cube build process =====

[8/18/2009 1:24 PM] Cube build request message has been added to the Project Server queue

===== Verifying and running pre-build server event handler =====

[8/18/2009 1:24 PM] Verifying and running pre-build server event handler

===== Determining database and cube structure =====

[8/18/2009 1:24 PM] Cube build initialization started

[8/18/2009 1:24 PM] OLAP database and cube structure was determined successfully

===== Building database and cubes =====

[8/18/2009 1:24 PM] Cube build session started

[8/18/2009 1:24 PM] Analysis Services session started

[8/18/2009 1:24 PM] 10 of the NT accounts that correspond to users that have ‘View Olap Data’ permission could not be added to the Project Server default OLAP role ‘ProjectServerViewOlapDataRole’

[8/18/2009 1:24 PM] Analysis Services session completed successfully

===== Verifying and running post-build server event handler =====

[8/18/2009 1:24 PM] Verifying and running post-build server event handler

===== Processing OLAP database =====

[8/18/2009 1:24 PM] Process OLAP database session started

[8/18/2009 1:24 PM] Analysis Services session started

[8/18/2009 1:24 PM] Analysis Services session failed with the following error: Failed to process the Analysis Services database Project2007PWA on the ProjectDB2007 server. Error:

===== Process Completed =====

[8/18/2009 1:24 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to process the Analysis Services database ProjectServerCube on the ProjectServer2007 server. Error:

 

Yes, it ended with “Error:” and nothing else.

 

First, the NT account issue is where I thought the problem was – that the permission could not be added to the “ProjectServerViewOlapDataRole”.  The log file lists the account names so finding which accounts don’t have permission is relatively easy.  However, this does NOT cause the cube build to fail – but I didn’t realize that for a while. 

 

In the user permissions within Project Server is the “View Olap Data” permission.  This allows users to read OLAP cube output.  The permission is only checked when the cube is built – and that is part of why the message appears here during the cube build.  The cube adds the user to the ProjectServerViewOlapDataRole during the building of the cube.  The error message appears when a user has the permission but the user’s account is not found for some reason on the Project Server.  A couple of those reasons include Forms Authentication or an account that is active in Project Server, but not in the Active Directory.  In my case, the 10 users were forms authentication users.

 

So, that leaves us with the non-descriptive error message that indicates it failed.

 

Your CBSRequest job failed.  Its current state is FailedNotBlocking.  It was 0% complete.  It entered the queue at 08/18/2009 14:59:04.

 

To get more information about the job failure, please go to Project Web Access.  Select Personal Settings from the left menu.  Then select My Queued Jobs.

 

The errors returned from the queue are as follows:

 Error ID: 17004

 Error ID: 26000

 

Detailed error below – send it to the administrator for more detailed troubleshooting.

 

<?xml version=”1.0″ encoding=”utf-16″?>

<errinfo>

  <general>

    <class name=”CBS message processor failed”>

      <error id=”17004″ name=”CBSOlapProcessingFailure”

uid=”79567be2-7264-4e4e-8862-38233de84d6a” QueueMessageBody=”Setting

UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName= ProjectServer2007 ASDBName= ProjectServerCube

ASExtraNetAddress=ProjectServer2007 RangeChoice=0

PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=08/18/2009 14:55:49

ToDate=08/18/2009 14:55:49 HighPriority=True” Error=”Analysis Services session failed with the following error: Failed to process the Analysis Services database ProjectServerCube on the ProjectServer2007 server. Error: “

/>

    </class>

    <class name=”Queue”>

      <error id=”26000″ name=”GeneralQueueJobFailed”

uid=”42c3cbd6-d720-458e-8e7c-6c0348f1f2bf”

JobUID=”f1a6ac66-09a5-4f82-b83f-421c8d3afb35″ ComputerName=”PROJECTSERVER2007″

GroupType=”CBSRequest” MessageType=”CBSQueueMessage” MessageId=”2″

Stage=”” />

    </class>

  </general>

</errinfo>

 

According to Microsoft documentation the error messages mean this:

CBSOlapProcessingFailure = 17004      The OLAP cube processing failed.

GeneralQueueJobFailed = 26000     The queue job failed.

 

Again, not very descriptive. 

 

The simple solution was to undo my prior changes to the Cube-Configuration screen.  The cube then worked fine.  So, I went more slowly through the Configuration screen, adding back only a few fields at a time.  I did this until the cube broke again.  This time, I found a more descriptive error message:

A member with key ‘{52E394C4-169A-44B2-A4B4-85EABE07970C}’ was found in the fact table but was not found in the dimension ‘RBS_Resource’.

 

This led me to discover that I had a resource (long since deleted, but came in from conversion from Project Server 2003) the system couldn’t handle because it apparently existed in some places on Project Server but not in other places.  (The userid owned some SharePoint information, but nothing in PWA itself.)

 

The moral of the story is two-fold (neither of which are new thoughts):

1.        Check the logs and messages BEFORE you make a change.  If I had done that, I wouldn’t have wasted time trying to figure out the NT account issue since that was there when the cube build was working fine.

2.       Don’t make numerous changes all at once.  When I went through the changes the second time, I found the true issue with the cube build relatively easily.

 

 

Just some proof that the cube will finish successfully with the NT account error:

===== Initiating cube build process =====

[8/18/2009 3:01 PM] Cube build request message has been added to the Project Server queue

===== Verifying and running pre-build server event handler =====

[8/18/2009 3:01 PM] Verifying and running pre-build server event handler

===== Determining database and cube structure =====

[8/18/2009 3:01 PM] Cube build initialization started

[8/18/2009 3:01 PM] OLAP database and cube structure was determined successfully

===== Building database and cubes =====

[8/18/2009 3:01 PM] Cube build session started

[8/18/2009 3:01 PM] Analysis Services session started

[8/18/2009 3:02 PM] 10 of the NT accounts that correspond to users that have ‘View Olap Data’ permission could not be added to the Project Server default OLAP role ‘ProjectServerViewOlapDataRole’

[8/18/2009 3:02 PM] Analysis Services session completed successfully

===== Verifying and running post-build server event handler =====

[8/18/2009 3:02 PM] Verifying and running post-build server event handler

===== Processing OLAP database =====

[8/18/2009 3:02 PM] Process OLAP database session started

[8/18/2009 3:02 PM] Analysis Services session started

[8/18/2009 3:03 PM] Analysis Services session completed successfully

===== Verifying and running post-process server event handler =====

[8/18/2009 3:03 PM] Verifying and running post-process server event handler

===== Process Completed =====

[8/18/2009 3:03 PM] Cube build request completed successfully.

 

Comments

 

Leave a Reply

You must be logged in to post a comment.