Common Error Messages when Building Cubes with Project Server 2007


I am reproducing some common errors, both from the USL logs and the Application Event logs to assist with troubleshooting cube building issues.  These are in a sort of order that follows my previous article – so first I will give a description of the problem and the errors you will see.  Note that the same Application Event log can appear for multiple failure modes (1 to 3 listed below all have the same error in the application event log) – but the ULS logs tend to be more indicative of the real problem.  Another common error I have not listed and potentially the first you will see is “ActiveX component can’t create object” which is usually related to missing components detailed in KB921116.

So here are the 5 errors:-

1. SSPAdmin is not an admin in Analysis Services

ULS Logs

·         Microsoft.Office.Project.Server

·         0x0924

·         Project Server                

·         Project Server Analysis Cube Bu

·         8swn

·         Medium  

·         PWA:http://<server>/PWA, SSP:SharedServices1, User:DOMAINUser, PSI:   [CBS] ProjectServerOlapCubeGenerator status: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server <SERVER>. Error: The connection string to repository needs to be specified in the 9.0 server properties (see <DSO>…</DSO> section in msmdsrv.ini file from Analysis Services 9.0).

Application Event Log

·         Event Type:        Error

·         Event Source:    Office SharePoint Server

·         Event Category:                Project Server Analysis Cube Building

·         Event ID:                              7682

·         Date:                     2/7/2007

·         Time:                     11:01:09 AM

·         User:                     N/A

·         Computer:          <SERVER>

·         Description:

·         Standard Information:PSI Entry Point:

·         Project User: DOMAINUser

·         Correlation Id: 69521947-e064-4bff-88e9-2176674a766f

·         PWA Site URL: http://<server>/PWA

·         SSP Name: SharedServices1

·         PSError: CBSASConnectionFailure (17003)

·         Cube build failed to connect to the Analysis Services server. Verify the data source connection is valid. Error: Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=<SERVER> ASDBName=PSCube ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=02/07/2007 11:00:39 ToDate=02/07/2007 11:00:39 HighPriority=TrueFor more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

2.            If you don’t restart the Analysis Server service after adding the SSPAdmin as an admin then you may see:-

ULS Logs

·         Microsoft.Office.Project.Server

·         0x0EAC

·         Project Server

·         Project Server Analysis Cube Bu

·         8swn

·         Medium  

·         PWA:http://<server>/PWA, SSP:SharedServices1, User:DOMAINUser, PSI:   [CBS] ProjectServerOlapCubeGenerator status: ProjectServerOlapCubeGenerator failed with exception: Microsoft.Office.Project.PI.CBSCommon.CBSProcessException: Failed to connect to the Analysis Services server <SERVER>. Error: Your permissions on the server computer do not allow you to administer this Analysis server.      Error:  —> System.Runtime.InteropServices.COMException (0x80040026): Your permissions on the server computer do not allow you to administer this Analysis server.      Error:      at Interop.Dso.ServerClass.Connect(String ServerName)     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.ConnectToAnalysisServer()     — End of inner exception stack trace —     at ProjectServerO…lapCubeGenerator.OlapDatabaseBuilder.ConnectToAnalysisServer()     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.GenerateOlapDatabase()     at ProjectServerOlapCubeGenerator.CMain.Main(String[] args)

Application Event Log

·         Event Type:        Error

·         Event Source:    Office SharePoint Server

·         Event Category:                Project Server Analysis Cube Building

·         Event ID:              7682

·         Date:                     2/7/2007

·         Time:                     2:32:56 PM

·         User:                     N/A

·         Computer:          <SERVER>

·         Description:

·         Standard Information:PSI Entry Point:

·         Project User: DOMAINUser

·         Correlation Id: 87a08e57-822e-4ec9-9a47-671f14679d6e

·         PWA Site URL: http://<server>/PWA

·         SSP Name: SharedServices1

·         PSError: CBSASConnectionFailure (17003)

·         Cube build failed to connect to the Analysis Services server. Verify the data source connection is valid. Error: Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=<SERVER> ASDBName=PSCube ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=02/07/2007 14:32:23 ToDate=02/07/2007 14:32:23 HighPriority=TrueFor more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

3.            If the SSPAdmin does not have access to the repository for Analysis Services then you will see the following.  This was on a single server – you may see MSOLAPRepository$ rather than the full path.

ULS Logs

·         Microsoft.Office.Project.Server

·         0x0CAC

·         Project Server                

·         Project Server Analysis Cube Bu

·         8swn

·         Medium  

·   &nbsp

Comments (87)

  1. Common questions and answers on AS 2K5 permissions for EPM 2007: Getting Cube to Build 1. Which application

  2. Mike says:

    Hi Brian,

    The error we’re getting is:

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

    [5/8/2007 8:40 AM] Verifying and running pre-build server event handler

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

    [5/8/2007 8:40 AM] Cube build initialization started

    [5/8/2007 8:40 AM] OLAP database and cube structure was determined successfully

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

    [5/8/2007 8:40 AM] Cube build session started

    [5/8/2007 8:41 AM] Analysis Services session started

    [5/8/2007 8:41 AM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server Hqsql2005dev01. Error: Path not found

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

    [5/8/2007 8:41 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server Hqsql2005dev01. Error: Path not found

    AS is set up on the default instance & is using a SQL db.

    Any ideas?

  3. Hi Mike,

    The error appears to suggest that the path to the repository is not working – so I would check the settings through Management Studio and look at the properties for the repository.

    Brian.

  4. Pavel says:

    Hi Brian,

    The error we’re getting is:

    Standard Information:PSI Entry Point:

    Project User: DOMAINUSER

    Correlation Id: 57cf2e18-c555-4933-8721-93139e2414b1

    PWA Site URL: http://project/PWA

    SSP Name: SharedServices2

    PSError: CBSOlapDatabaseSetupFailure (17007)

    Project Server failed to generate an OLAP object. CBS queued message: Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=SERVER ASDBName=ProjectAnalyseDb ASExtraNetAddress= RangeChoice=1 PastNum=2 PastUnit=2 NextNum=2 NextUnit=2 FromDate=05/24/2007 18:32:03 ToDate=05/24/2007 18:32:03 HighPriority=False. Error: Analysis Services session failed with the following error: Failed to delete the Olap database: ProjectAnalyseDb. Error: Your permissions on the server computer do not allow you to administer this Analysis server.

  5. It looks like you need to add the user running your SSP as an admin within Analysis Services.  Assuming this is 2005 go to Management Studio, connect to Analysis Services then right click the server name and go to properties.  You should be able to add the user as an admin there.

  6. Eric Dennis says:

    I am having the same problem. How do I determine which user is running the SSP?

  7. The best way is to go to the Shared Services Administration in SharePoint Central Administration then select the drop down for the SSP you want to identify the user for and select edit properties. The user shown under SSP Service Credentials will be the one running this SSP.

  8. trb says:

    Hi Brian,

    This is the out put from the Build Tracking Comments. This had been working, any ideas?

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

    [6/19/2007 10:36 AM] Cube build request message has been added to the Project Server queue

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

    [6/19/2007 10:37 AM] Verifying and running pre-build server event handler

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

    [6/19/2007 10:37 AM] Cube build initialization started

    [6/19/2007 10:37 AM] OLAP database and cube structure was determined successfully

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

    [6/19/2007 10:37 AM] Cube build session started

    [6/19/2007 10:37 AM] Analysis Services session started

    [6/19/2007 10:38 AM] Analysis Services session failed with the following error: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.

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

    [6/19/2007 10:38 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.

  9. Generally this error means that the cube you are trying to overwrite with this new cube was created by a different instance of PWA.  If nothing has changed and you are just rebuilding then I would suggest loggin a support call.  I assume using a different cube name still works?

  10. Hi Brian,

    We are trying to build our cube, obviously, but get the following error.

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

    [6/27/2007 3:14 PM] Cube build request message has been added to the Project Server queue

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

    [6/27/2007 3:14 PM] Verifying and running pre-build server event handler

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

    [6/27/2007 3:14 PM] Cube build initialization started

    [6/27/2007 3:14 PM] OLAP database and cube structure was determined successfully

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

    [6/27/2007 3:14 PM] Cube build session started

    [6/27/2007 3:14 PM] Analysis Services session started

    [6/27/2007 3:15 PM] 2 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’

    [6/27/2007 3:15 PM] Analysis Services session completed successfully

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

    [6/27/2007 3:15 PM] Verifying and running post-build server event handler

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

    [6/27/2007 3:15 PM] Process OLAP database session started

    [6/27/2007 3:15 PM] Analysis Services session started

    [6/27/2007 3:15 PM] Analysis Services session failed with the following error: Failed to process the Analysis Services database ProjectServer_AnalysisServices on the STBLBIZI server. Error: Server: The operation has been cancelled.

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

    [6/27/2007 3:15 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to process the Analysis Services database ProjectServer_AnalysisServices on the STBLBIZI server. Error: Server: The operation has been cancelled.

    The cube used to build just fine.

    But then we did the following:

    1) We added the Timesheet view to the cube View.

    2) Attempted to rebuild cube (never completed, was terminated 13 hrs after submission with a reboot.)

    3) Deleted Timesheet View

    4) Attemped to rebuild cube (assumed we were back to where things were able to build)

    5) Received the error noted above.

    We are stumped.

    Any suggestions.

    thanks,

    jeff

  11. Hi Joe,

    Not sure why the timesheet addition broke your cube but to get back to a working system I would suggest deleting the cube through Analysis Services (or buidling a cube with a different name) as some of the metadata may be corrupt if the system previous build was ended abnormally.

    Best regards,

    Brian.

  12. PAUL says:

    Hi Brian,

    The error we’re getting is:

    Standard Information:PSI Entry Point:

    Project User: DOMAINUSER

    Correlation Id: 57cf2e18-c555-4933-8721-93139e2414b1

    PWA Site URL: http://project/PWA

    SSP Name: SharedServices2

    PSError: CBSOlapDatabaseSetupFailure (17007)

    Project Server failed to generate an OLAP object. CBS queued message: Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=SERVER ASDBName=ProjectAnalyseDb ASExtraNetAddress= RangeChoice=1 PastNum=2 PastUnit=2 NextNum=2 NextUnit=2 FromDate=05/24/2007 18:32:03 ToDate=05/24/2007 18:32:03 HighPriority=False. Error: Analysis Services session failed with the following error: Failed to delete the Olap database: ProjectAnalyseDb. Error: Your permissions on the server computer do not allow you to administer this Analysis server

  13. Probably your administrative account for SharedServices2 needs to be in the administrators group for Analysis Services.

  14. Ray says:

    Hi, I have the same problem 🙁

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

    [8/6/2007 11:00 PM] Cube build request message has been added to the Project Server queue

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

    [8/6/2007 11:00 PM] Verifying and running pre-build server event handler

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

    [8/6/2007 11:00 PM] Cube build initialization started

    [8/6/2007 11:00 PM] OLAP database and cube structure was determined successfully

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

    [8/6/2007 11:01 PM] Cube build session started

    [8/6/2007 11:01 PM] Analysis Services session started

    [8/6/2007 11:04 PM] Analysis Services session failed with the following error: Failed to create the Olap database: CUBO_PCS. Error: Unable to save object.  The object has been modified by another application.

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

    [8/6/2007 11:04 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to create the Olap database: CUBO_PCS. Error: Unable to save object.  The object has been modified by another application.

    Can you please help me!!!

  15. Hi Ray,

    This error sounds like something has been done through SQL Management Studio against your analysis services database and it is no longer recognised.  Or your metadata in the repository has been changed.  I would try a new cube name to see if this works.

    Best regards,

    Brian.

  16. Bill Murphy says:

    Brian

    PS 2007

    We have the ;

    ‘Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site’

    error on the build cube

    The SQL server / Analysis server combination is common to two(2) PWAs one for Production and one Training i.e. the Cube names are diferent but it is  still thowing the error.  Naturally its the Production cube that’s failing.

    Can you suggest any actions that might ‘switch ownership’ so the Production cube gets built not the train.  Or any thing at all which will get us out of the problem.

    The PWA / Project 2007 has been installed on separate servers i.e. one for the Web and one for the App ONLY the SQL server is shared.

  17. Hi Bill,

    *** Correction *** I said queue in place of cube in the original comment posting – sorry for the confusion.

    This shouldn’t happen unless both are trying to write to the same Cube name – whcih is not allowed.  I have heard a few reports of this message so there may be some other reason it is appearing.  Generally using a new cube name will resolve the issue – but if it keeps recurring then this can be very inconvenient.  Log a support incident if it recurs and you can see no reason for the clash of names with your other server,

    Best regards,

    Brian.

  18. Bill Murphy says:

    Brain

    Thanks for your response.  The two installs of the PS2007 where on separate servers so you would think there would be totally separate queues.  We have raised a case with MS and are waiting for support.  If we get a solution I will post it back here.

  19. Michael Patrick says:

    I am getting the same issue with the ‘Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site’ message when having two PWA sites hook up to the same Analysis server.  Please let me know if you get a resolution from MS!

  20. Michael Santos says:

    Hi Brian,

    Not sure if you can help here, but I am getting this error message… basically I’m seeing that some of the cubes are built but then it fails and gives the following error… any ideas???

    Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to process the Analysis Services database Rincon_ProjectServerCube on the SEVENSEAS server. Error: Errors in the OLAP storage engine: The linked measure group with the ID of ‘EPM Timesheet’, Name of ‘EPM Timesheet’ cannot be processed because it contains MG dimension with the ID of ‘Task Is Overallocated’, Name of ‘Task Is Overallocated’ with different granularity attribute than its source object.

  21. Dan Knowles says:

    We are getting the following error and have figured out why.  If we change the name of the database to be created it works fine.  However, is there any way to recover/reuse the original database name (the one that threw the error)?

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

    [9/12/2007 3:00 PM] Cube build request message has been added to the Project Server queue

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

    [9/12/2007 3:00 PM] Verifying and running pre-build server event handler

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

    [9/12/2007 3:00 PM] Cube build initialization started

    [9/12/2007 3:00 PM] OLAP database and cube structure was determined successfully

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

    [9/12/2007 3:00 PM] Cube build session started

    [9/12/2007 3:00 PM] Analysis Services session started

    [9/12/2007 3:00 PM] Analysis Services session failed with the following error: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.

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

    [9/12/2007 3:00 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.

    Thanks!

  22. Hi Dan,

    I am preparing a blog posting on this exact scenario.  The quick and dirty way is to delete a row from the repository that contain the cube name you are trying to overwrite – but this does then leave some orphaned rows in the database.  Another way is to edit the data in the ObjectDefinition column for that row.

    The ObjectDefinition for the row actually contains the Site UID that causes the conflict – for example:–

    <DATABASE Name="CubeDe" Description="

    Project Server Site UID: 1d59d459-90fc-4518-b6a5-f5a7fdb3c204" LastUpdated="10:01:02 09/11/2007"><CUSTOMPROPERTIES><PROPERTY Name="RESERVED_DATABASE_LOCALE_UPDATED2" DataType="0" Value="B"></PROPERTY></CUSTOMPROPERTIES></DATABASE>

    So potentially you could replace the Site UID to overcome the issue, rather than deleting.  The Site UID can be found in several different ways – going to the Manage PWA page under the SSP and then choosing to Edit your site and getting the ID from the URL is probably easiest.

    http://brismith260:10988/ssp/admin/_layouts/createpwa.aspx?task=Edit&id=ea8ecdc7-bc0c-4788-9abd-5744605d2974

    This is easier if you have your repository in SQL Server – I haven’t tried this when the repository is an mdb file but potentially you could do this with Access.

    I am interested in hearing of scenarios that lead to this error.

    Best regards,

    Brian.

  23. Bianca says:

    I hope you can help.

    I have a single server implementation of Project Server 2007, SQL Server 2005 and Analysis Services 2005. Every time I try to run the cube build I get the following error:

    Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server <ServerName>:<Port><InstanceName>. Error: A connection cannot be made to redirector. Ensure that ‘SQL Browser’ service is running.

    The SQL Browser service is running, nuder the same account as the Analysis Services. Any ideas?

  24. Hi Bianca,

    The string you enter for the analysis server and instance should follow the pattern <ServerName>:<Port><InstanceName> but will actually read something like server1, or server1:1234, or server1proj – so should be the real name of your server – and in a single server install you probably don’t have multiple instances so it will very likely be just the server name.  I think this is the problem as I can repro the error you get by putting in the literal string <ServerName>:<Port><InstanceName>.

    I hope this helps.

    Brian.

  25. Setting up OLAP cubes for Project Server 2007 on SQL Server 2005 Analysis Services can be a real pain.I followed the TechNet article and all guidelines on Brian Smith’s Project Support WebLog (which contains all possible errors you might run into when

  26. Bianca says:

    I didn’t mean to suggest that the literal string <ServerName>:<Port><InstanceName> was used. That is the pattern of the analysis server string.

    My problem is the rest of the error, the part about not being able to connect to the redirector. The SQL Browser service is running, and it is running under the same login as the Analysis Services so it shouldn’t be an access problem.

  27. dfknowles says:

    Hi Brian,

    Thank you for the information on reclaiming the cube name (http://blogs.msdn.com/brismith/archive/2007/02/14/common-error-messages-when-building-cubes.aspx#4895343).  The installation has the repository in an access database (msmdrep.mdb) as opposed to having it in SQL Server.  I was able to find the record in the mdb and modify the Database tag in ObjectDefinition field to contain

    Description=”Project Server Site UID: 1d59d459-90fc-4518-b6a5-f5a7fdb3c204″

    as an attribute.

    The following is an attempt to provide some background regarding how we got into this situation.  A second instance of project server was brought up to do some proof of concept.  As part of the proof of concept the cube was built with the database name being OLAP.  However, we did not wish to use this instance of project server, but we wanted to reclaim the OLAP name.

  28. OK, I would suggest using another client tool to try and access the same server.  It may be a name resolution issue, or a permissions issue, or a firewall issue stopping connection.

  29. Thanks for the feedback DF, I can understand how this can happen.  I think there are also some other circumstances that can "break" the site id in the repository even when things come from the same PWA instance.  Any repros gladly reviewed…

  30. Mvanwyk says:

    Hi I’m new at this,

    I get the following error, please assist.

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

    [2007/09/25 02:28 PM] Cube build request message has been added to the Project Server queue

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

    [2007/09/25 02:28 PM] Verifying and running pre-build server event handler

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

    [2007/09/25 02:28 PM] Cube build initialization started

    [2007/09/25 02:28 PM] OLAP database and cube structure was determined successfully

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

    [2007/09/25 02:28 PM] Cube build session started

    [2007/09/25 02:28 PM] Analysis Services session started

    [2007/09/25 02:28 PM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server IGSP1. Error: The connection string to repository needs to be specified in the 9.0 server properties (see <DSO>…</DSO> section in msmdsrv.ini file from Analysis Services 9.0).

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

    [2007/09/25 02:28 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server IGSP1. Error: The connection string to repository needs to be specified in the 9.0 server properties (see <DSO>…</DSO> section in msmdsrv.ini file from Analysis Services 9.0).

  31. Hi Brian,

    We are picking the following two erros at a couple of places:

    _____________________________________________________

    Analysis Services session failed with the following error: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.

    _____________________________________________________

    Analysis Services session failed with the following error: Failed to create the Olap database: CUBO_PCS. Error: Unable to save object.  The object has been modified by another application.

    _____________________________________________________

    This seems to occur only where the following is true:

    1.  SQL 2005 Analysis Services is used (And related, the bug which prevents you from deleting AS databases through Management Studio)

    2.  There are multiple PWA sites on the server

    We confirmed that one PWA site is not trying to build on another’s name.

    I am wondering about your comment RE the Queue Names – would this be something we can check? (I.e. to confirm that 2 different PWA sites on the same installation does not have the same queue name)

    Secondly, your suggestion of changing the SiteID – What would we do here?  Simply confirm that the SiteID is correct?

    Thanks,

    Nico Oosthuysen

  32. Hi Nico,

    Thanks for finding my error!  I should have said both are trying to write to the same CUBE name.  I will correct this.  You shouldn’t have duplicate SiteID’s but the easiest way to look at this is if you have the repository in SQL Server to open the tables and take a look.  See what cube names are given for the different PWA sites that you have.  It is possible that there is a bug that is causing some sort of clash.  You could also try setting cube build times far enough apart to avoid any clash of times.

  33. Hi Mvanwyk,

    Sorry for the delay – it would appear the repository isn’t being found.  I would take a look at the articles on http://technet2.microsoft.com/Office/en-us/library/ec990b7c-ec98-4d6d-b1a1-081a67fd66cc1033.mspx?mfr=true and specifically look at the article relating to the version of Analysis Services you are using and set you repository up in SQL Server.

    Brian.

  34. Chris says:

    Hi Brian,

    We have been working to get our Analysis services started for quite some time. We have encountered all the errors noted but now, I have never seen this one posted:  Error: disk not ready. Cannot access repository server. Any clues?

  35. Hi Chris,

    I’ve not seen that one, but appears to be an I/O problem getting to the repository.  I would suggest re-building the repository as a SQL Server database following the TechNet article if you haven’t already – or look for other errors in the event log that may indicate why disk I/O may be a problem. Also check the repository setting in Management Studio for Analysis Services in case they are pointing to a non-existent location.

    Brian.

  36. Hi Vincent,

    I’m guessing as my Spanish isn’t good – but it may be the path to the Analysis Services repository. Try using a repository in a SQL db rather than an mdb in the filesystem.  The documents on TechNet for using Project Server 2007 with SQL 2005 detail how to configure this.

    Brian.

  37. Rakesh Luhar says:

    I did all configuration according to guide. I am getting following error. Before this I was getting erro which say that your permission on AS not allow you to administrator.

    Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server. Error: Authentication failed.

  38. Hi Rakesh,

    FOr authentication errors I would check the event logs on all your servers, as there should be some other indication of this failure – hopefully detailing the account that couldn’t be authenticated.  Possibly you may also need to restart AS to get changes to security to work.

    Brian.

  39. Rakesh says:

    Thanks for reply Brain.

    Following is my setup.

    I have Two servers. One have Project server running and second server has SQL 2005 database and AS on that.

    I have used only one account <prsqlservice> for all places like WSS3.0 service account, SSP Pool account, and all other place where we need to use domain account.

    I have added this user on the server carrying SQL 2005 Database and AS. I give server role of sysadmin, also added in AS security properties. I am using SQL 2005 database as Repository.

    Now the Error of Authentication I was getting was b’coz I change the account running OLAP service to that account <prsqlservice> then local. As I change to Local that error stop coming and I am getting following error.

    Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server <Server Name>. Error: Your permissions on the server computer do not allow you to administer this Analysis server.

    After this my event log shows error of 7704 & 7682.

  40. Ginni says:

    Hi,

    I have followed all steps mentioned in the article below:

    http://technet.microsoft.com/en-us/library/cc197728.aspx

    still no luck,

    I am getting the following error:

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

    [3/12/2008 11:15 AM] Cube build request message has been added to the Project Server queue

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

    [3/12/2008 11:15 AM] Verifying and running pre-build server event handler

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

    [3/12/2008 11:15 AM] Cube build initialization started

    [3/12/2008 11:15 AM] OLAP database and cube structure was determined successfully

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

    [3/12/2008 11:15 AM] Cube build session started

    [3/12/2008 11:15 AM] Analysis Services session started

    [3/12/2008 11:15 AM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server DATIN06SQL01. Error: ActiveX component can’t create object

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

    [3/12/2008 11:15 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server DATIN06SQL01. Error: ActiveX component can’t create object

    Please suggest how to resolve it?

  41. Hi Ginni,

    This error can be seen when the components aren’t the right version – but if everything is up to date you can still see it – particularly if re-building cubes frequently (within 10-20 minutes of a previous build).  I’ve seen it intermitently on my server and put it down to some process still running that is blocking.  Usually trying again after a short wait will work for me.  I must try and track down a better answer than this…  Any ideas anyone?

    Best regards,

    Brian.

  42. Kimberlee says:

    Hi Brian,

    I’m getting the same error posted by Michael Santos but I did not see a response to his issue.  For me this is the very first time I am building the cube.  It is a new installation with SP1 applied.

    Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to process the Analysis Services database <NAME> on the <DB> server. Error: Errors in the OLAP storage engine: The linked measure group with the ID of ‘EPM Timesheet’, Name of ‘EPM Timesheet’ cannot be processed because it contains MG dimension with the ID of ‘Task Is Overallocated’, Name of ‘Task Is Overallocated’ with different granularity attribute than its source object.

  43. Hi Kimberlee,

    I don’t have an answer on this one yet.  Hopefully early next week I can get back to you.  It helps to know this is the first time you have tried to build a cube as it then would indicate some difference unrelated to any existing data – and perhaps a mis-match between the database and the binaries requesting the build.  I will keep digging.

    Best regards,

    Brian.

  44. VMAI says:

    Brian… I’m getting this error… I hope you can guide me to a solution…

    Error in the OLAP storage engine: The linked measure group with the ID of ‘Epm Timesheet’, name of ‘EPM Timesheet’ cannot be processed because it contains MG dimension with the ID of ‘Resource is active’, name of ‘resouce is active’ with different granularity attribute than its source object.

  45. Hi VMAI,

    We are still researching this issue – but current thoughts are suggesting mis-matched versions of the SQL feature pack – so I would ensure you have all the latest updates for SQL Server loaded on the db engine, AS and alos your Project Server machine which needs to talk correctly to AS.

    More as I find out more…

    Best regards,

    Brian.

  46. VMAI says:

    TKS Brian… I checked the versions of the SQL Feature pack and that was the issue… I got PS2007 and SQL 2005 both in spanish… and I had one of the feature pack items installed in english… I reinstalled the spanish version of the item as well as the MSXML 6 SP1 and now I have the cubes generating without errors…

    Thanks a lot… My head was about to roll because of this issue!!

  47. Excellent news VMAI.  Glad to hear this resolved things!

  48. PJ Mistry says:

    Hi Brian;

    we are getting an error message when building the OLAP cube.

    Failed to build the OLAP cubes. Error: Analysis Services session failed with

    the following error: Failed to process the Analysis Services database

    OLAPCube on the ukapp09 server. Error: Errors in the OLAP storage engine:

    The linked measure group with the ID of ‘EPM Timesheet’, Name of ‘EPM

    Timesheet’ cannot be processed because it contains MG dimension with the ID

    of ‘Task Is Overallocated’, Name of ‘Task Is Overallocated’ with different

    granularity attribute than its source object.

    Please let me know what the cause might. I have come accross this error

    before. Tried a few times.

    This issue is also experienced by others I see and you had been looking into

    this as well. Not sure what the outcome was.

    Thanks

    Regards

    PJ Mistry

  49. Hi PJ,

    This error appears to relate to mis-matched components – so make sure that all of the servers and components and parts of the feature pack (DSO, backwards compatibility etc.) are at the same release level.  This applies to the components on your application server as well as your Analysis Services and Database Engine server.  I’m not in the office right now but will try and do a full posting on this soon.

    Best regards,

    Brian.

  50. ladydemona says:

    Brian,

    Has there been a hotfix issued since September for the issue Dan had in this thread?  (Analysis Services session failed with the following error: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.)  

    Your work-around corrected the issue, but its not a permanent fix.  If you would like details surrounding our instance I can supply.  

    -Christina Odom

  51. Hi LadyDemona,

    There isn’t a hotfix for this yet, but we have identified how it can happen.  I’ll be doing a full post shortly but basically you can get into this bad state if you have two instances of PWA trying to build a cube at or around the same time.  One will work – the other will fail, and then the failing one will give this error as the repository details for the cube get corrupted.

    Best regards,

    Brian

  52. One of my customers had the same issue Michael Santos and Kimberlee had:

    "Error in the OLAP storage engine: The linked measure group with the ID of ‘Epm Timesheet’, name of ‘EPM Timesheet’ cannot be processed because it contains MG dimension with the ID of ‘Resource is active’, name of ‘resouce is active’ with different granularity attribute than its source object."

    The problem was that they had installed SQL Analysis Services after they applied SP2 to SQL server. This lead to a mismatch of versions between MS SQL Server 2005 and MS SQL Analysis Services 2005.

    Just as a little extra piece of information, the server was 64 bit, BUT I would expect the same issue on a 32 bit environment.

    I hope this helps Michael or Kimberlee.

    Regards,

    Virgilio Arciniegas

    virgilio.arciniegas@catapultsystems.com

    MCSE, MCDBA, MCITP EPM

  53. Ginni says:

    Hi Brian,

    Still no luck. I am getting errors 7704 and 7762. Have tried re-installing evrythig again on both the database server as well as the project server.Any help?

  54. Sadaf Shaikh says:

    Hi Brian,

    I’m facing the same issue as Michael Santos and Kimberlee, at the client I’ve deploying project server 2007 at.

    "Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to process the Analysis Services database OMV_EPM_OLAPDB on the somvpk001203 server. Error: Errors in the OLAP storage engine: The linked measure group with the ID of ‘EPM Timesheet’, Name of ‘EPM Timesheet’ cannot be processed because it contains MG dimension with the ID of ‘Task Is Overallocated’, Name of ‘Task Is Overallocated’ with different granularity attribute than its source object."

    I have a two server scenario, with SQL Server 2005 Standard Edition plus AS on one machine, and the Feature Pack I had downloaded sometime back, works well with installations based on SQL Server 2005 Enterprise Edition. Is this issue related to the standard edition ? That is , is there a separate feature pack download for different versions of SQL Server 2005 ?

  55. Sadaf Shaikh says:

    Hi Brian,

    Any way we can check a mis-match between the database and the binaries requesting the build on the Application Server ?

  56. Steve says:

    I am coming across the error id="17013" name="CBSAttemptToOverwrite" messages.  

    I can create a new cube and builds fine.  But my scheduled cube build at night fails and receive these error messages.  What would be preventing it to overwrite?  

  57. Johan says:

    Hi Brian,

    I have the same problem as Michael Santos, Kimberlee and Sadaf Shaikh. But I use SQL Server 2005 Enterprise edition, and with SP2 installed after Analysis Services was installed. The error message also pops up on the screen when I click properties on Analysis Services Repository in SQL Server Management Studio.

    Any input on this issue would be highly appreciated.

    Kind regards,

    Johan

  58. Hi Johan,

    The error is caused by mis-matched versions of components and here is a set of steps suggested by one of my colleagues for resolving.  This was back in May – so check for even more recent versions than the ones listed.

    Step #1: Installed newest Management Objects on SQL server

    On SQL Server computer, please download and install the latest Management Objects from the following link:

    http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/SQLServer2005_XMO.msi

    Step #2: Updated Native Client and BC Objects, and reinstalled Management Objects on Application Server

    On Project Server computer (Application Server), download and update Native Client from the following Link:

    http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/sqlncli.msi

    On Project Server computer (Application Server), download and update BC Objects from the following link:

    http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/SQLServer2005_BC.msi

    On Project Server computer (Application Server), download and install the latest Management Objects from the following link:

    http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/SQLServer2005_XMO.msi

  59. Mswt says:

    Regarding –

    "The best way is to go to the Shared Services Administration in SharePoint Central Administration then select the drop down for the SSP you want to identify the user for and select edit properties. The user shown under SSP Service Credentials will be the one running this SSP."

    I have the Network Service account running but want to change that to a domain user so i can test logging in to the Analysis server through the admin tool.  I have a build error saying i do not have permission to the analysis server.

    How do i change the SSP Service Credentials and still get PWA to run.  When i tried the PWA site went down with an "unexpected" sharepoint error.

    Anywhere else I need to update?

    Many thanks…

  60. Sorry for the delayed response Mswt.  That is the only place – but the domain account will need the right permissions.  See http://blogs.msdn.com/brismith/archive/2007/02/08/operating-system-and-sql-permissions-for-the-microsot-office-project-server-2007-service-account.aspx for details of permissions required.

    Best regards,

    Brian.

  61. Hi Steve,

    Sorry for the delayed response.  The CBSAttemptToOverwrite error indicates that the cube named in the repository does not appear to match up to the instance of Project Server that is trying to build it.  It can happen if two cubes are being built at the same time from different instances.  Is this your scenario?  Another workaround is to edit the repository to remove this cube name, which is the same as using a new cube name – but will maintain all the views built against the named cube.

    Best regards,

    Brian.

  62. Ravi Gokulgandhi says:

    I am getting this error while building cubes.  I am using Sql Server 2008 and have also installed feature pack as well as backward compatibility pack for sql server 2005. Any pointers.

    <— Log—->

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

    [8/24/2008 11:32 AM] Cube build request message has been added to the Project Server queue

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

    [8/24/2008 11:32 AM] Verifying and running pre-build server event handler

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

    [8/24/2008 11:32 AM] Cube build initialization started

    [8/24/2008 11:32 AM] OLAP database and cube structure was determined successfully

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

    [8/24/2008 11:32 AM] Cube build session started

    [8/24/2008 11:32 AM] Analysis Services session started

    [8/24/2008 11:33 AM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dev-1. Error: ActiveX component can’t create object

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

    [8/24/2008 11:33 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dev-1. Error: ActiveX component can’t create object

    <—End Log–>

  63. Hi Ravi,

    The "usual" reason for this error is incompatible versions of the various components.  Do you have SQL Server 2008 for your Analysis Services as well as your databases?  I will be moving some of my servers over to 2008 later this week so will test this scenario and check the component versions when I get it working.

    Best regards,

    Brian

  64. Scott Stumpf says:

    I am running into the same issue.  Even with all the SQL 2008 Feature Pack components installed, including SQL 2008 ADOMD.NET, we see the same error when trying to build the cube against SQL Server 2008 Analysis Services.  If I find a workaround, I will post it.

  65. Hi Scott – I am getting close on this one.  Try loading the 2005 stuff as per the previous docs and then add the SQL Server 2005 cumulative update 10.  KB956854.  I hope to do a full posting soon – just testing some things out…

    Best regards,

    Brian.

  66. Paul Mather says:

    Hi Brian,

    We have an issue where the scheduled cube does not work but when you build now it works fine. On further investigation it appears that none of the scheduled jobs appear to be working. The cube build timer job references an old project server instance ‘PWA’ and not the new instance ‘projectserver’. To try and resolve the issue we have deleted SSP and Web application.

    Re-created the web application and SSP and then created new PWA instance linking to existing databases and that has not re-created the timer jobs. Please can you let me know if you have any ideas what could cause this issue or if you can think of anything else that we can try?

    Kind Regards

    Paul Mather

  67. Matt Stevenson says:

    In addition to the above, in our customer’s 2 server PS2007 + SP1 on SQL2005 + SP2 build it was necessary to manually enter the following value:

    SQL Server Mgt Studio > Connect to Analysis Services > Right-click server > Properties > Show Advanced (All) Properties > DSO RemoteLocksDirectory > type in value of \<servername>MSOlapRepository$ > OK

    nb. Remember to re-start the Analysis Services service after this step and before trying to re-build your OLAP cube again.

    This tip was found on: http://social.msdn.microsoft.com/forums/en-US/sqlanalysisservices/thread/f62966c5-522e-47fb-ae7e-90a445a6e9d5/

    Regards: Matt Stevenson (matt@mstraining.net)

  68. Thanks for sharing Matt.  

    I must admit I prefer the option to use a repository in SQL Server – then none of this is necessary, and any issues are far easier to troubleshoot.

    Best regards,

    Brian.

  69. Matt Stevenson says:

    Hi Brian,

    In this instance, they are using an SQL Server database. It still required this setting before things worked…

    Matt

  70. Interesting Matt.  I’ve never needed to set that.  Does it actually stop working if you remove those settings?  Just a double check to make sure that some other change didn’t resolve the issue.  For instance the restart may have corrected a permissions issue.  Let me know how this goes.

    Thanks,

    Brian.

  71. PeteH says:

    Finally got it working! The following steps solved a continuous "Your permissions on the server computer do not allow you to administer this Analysis server." error:

    1. Setup DSO9 directory in Program FilesMicrosoft SQL ServerMSSQL.xOLAP

    2. Share the folder as MSOLAPRepository$

    3. Give your SSP account full control of this share

    4. Edit Program FilesMicrosoft SQL ServerMSSQL.xOLAPConfigMSMdsrv.ini – add the following in the DSO section near the end:

    <RemoteLocksDirectory>\SERVERNAMEMSOLAPRepository$</RemoteLocksDirectory>

    <LocksDirectory>C:Program FilesMicrosoft SQL ServerMSSQL.xOLAPDSO9</LocksDirectory>

    (where MSSQL.x is the directory that contains the OLAP folder)

    5. Restart Analysis Services.

    Good luck!

    Pete

  72. Thanks for sharing Pete.  I must admit I prefer the option of using a SQL repository – but know of others that have better success using the mdb with the steps you give above.

    Best regards,

    Brian.

  73. TomR says:

    OMG!  Thanks Pete.  I’ve been trying to get this to work for 4 months (on and off).

    I have read all of the technet tips, Brian’s blog, waiting on the components that would work without a workaround etc., but kept getting the same error as you.

    Your solution finally got rid of that error.

    To Brian’s comment about using the SQL repository, that is what I am using, but it wouldn’t work until I added the share and put the lock folder in MSAS settings.

    We have a small 20 person setup with a 2 server config (both running Win2k8).  A 64Bit SQL Server 2008 with a named instance supporting the second server.  This one is 32 bit and is hosting both Project Server and Team Foundation Server. I don’t know what makes this setup unique, but I’m glad someone finally had the same issue as I did and solved it.

    One other comment.  The build settings web interface in PS doesn’t allow you to type the Backslash "" to specify the named instance.  You have to paste it in from another program !#@$.

    Thanks,

    Tom

  74. Sara says:

    Hi Brian,

    I just finished reading through this blog and all the comments and wanted to touch base regarding the CBSAttemptToOverwrite error message.  You mentioned looking for ways to repro that error.  We just experienced this again and I believe I have one for you.  Our OLAP cube has been building successfully for months (every night).  However, yesterday I came in and it was still "processing" at 50%.  It started to build as scheduled at 1:00am.

    So that it would not tie up a queue thread and since all the reporting jobs were getting backed up I canceled the job within the queue.  All the Data Analysis views were visible, so I believe the cube actually built, it just didn’t finalize to 100% complete within the queue.  I couldn’t find anything in the ULS or Application logs, granted I may not have known really what to look for over that 8 hour time frame.  

    Today the OLAP cube build failed with the message about not being able to overwrite.  That is because I "touched" it by canceling it within the queue.  We had to use the workaround of renaming the cube in order for it to rebuild.  And of course we then had to rename all of our views to point to the newly created cube.  I would really like to understand why the cube hangs at 50%.  This was really strange for us as I stated before it had been working for quite some time.

    Have you ran across this before and do you have any insight you can share?  If we can determine why it hangs occasionally, we can prevent this scenario of receiving that failure.

    Thanks,

    Sara

  75. Hi Sara,

    Thanks for this feedback.  I haven’ come across the 50% complete issue – but I think you are on the right track that cancelling somehow didn’t then complete the update of the repository which led to the overwrite problems.  I will ask around to see if this is behavior we have seen elsewhere.

    Best regards,

    Brian.

  76. Fahiem Rahim says:

    Pete,

    Thank you so much for your steps. The 2 lines that go into the ini file have resolved my pains with Cube building. Thanks.

  77. Rosie says:

    I am trying to build a sample cube, but when I try to deploy, I get the following errors.  Any ideas as to what the problem is?  Thanks,

    Error 1 Internal error: The operation terminated unsuccessfully.

    Error 2 Internal error: The operation terminated unsuccessfully.

    Error 3 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: No process is on the other end of the pipe. ; 08S01.

    Error 4 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘Adventure Works DW’, Name of ‘Adventure Works DW’.

    Error 5 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘Customer’, Name of ‘Customer’ was being processed.

    Error 6 Errors in the OLAP storage engine: An error occurred while the ‘Customer Alternate Key’ attribute of the ‘Customer’ dimension from the ‘Analysis Services Tutorial’ database was being processed.

    Error 7 Server: The operation has been cancelled.

  78. Pankaj says:

    Standard Information:PSI Entry Point:

    Project User: APPSRV2010Pankaj

    Correlation Id: 4353f292-80e9-4243-8cf3-962432bbb9a0

    PWA Site URL: http://epm/PWA

    SSP Name: Project Web App Service

    PSError: CBSOlapDatabaseSetupFailure (17007)

    Project Server failed to generate an OLAP object. CBS queued message: Setting UID=6c05aa93-538b-4a95-96eb-07a19dfd6b8d ASServerName=EPMPOWERPIVOT ASDBName=OLAP ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=02/04/2011 00:00:00 ToDate=02/04/2011 00:00:00 HighPriority=True. Error: Failed to create the Olap database: OLAP. Error: PowerPivot database error: Cannot set StorageEngineMode property of database 'OLAP' to 'Traditional' because Analysis Services is in VertiPaq mode.

  79. Hi Pankaj,

    Not sure if that is a question or a statement – but what you appear to be trying to do is build a cube on an instance of Analysis Services set up for PowerPivot (the Vertipaq engine) and this is not supported.  You can just install another instance of AS and use the normal mode for your Project Server OLAP needs.

    Best regards,

    Brian.

  80. Andre Janveaux says:

    Hi Brian,

    I've been dealing with this issue for over a week now…I've read through all of your fixes above, as well as all the other posts, and I still can't get the cube to build properly.  I'm fairly new to SQL 2008 and Project Server 2007 but I'm pretty sure I've followed all of your actions above correctly.  Here are the errors I receive:

    From PWA:

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

    [5/13/2011 2:51 PM] Cube build request message has been added to the Project Server queue

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

    [5/13/2011 2:51 PM] Verifying and running pre-build server event handler

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

    [5/13/2011 2:51 PM] Cube build initialization started

    [5/13/2011 2:51 PM] OLAP database and cube structure was determined successfully

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

    [5/13/2011 2:51 PM] Cube build session started

    [5/13/2011 2:52 PM] Analysis Services session started

    [5/13/2011 2:52 PM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server can6800vm018. Error: ActiveX component can't create object

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

    [5/13/2011 2:52 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server can6800vm018. Error: ActiveX component can't create object

    From Windows App logs:

    Standard Information:PSI Entry Point:

    Project User: XRXNAMSPS_SrvFarm_Svc

    Correlation Id: 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    PWA Site URL: http://can6800vm018/PWA

    SSP Name: SharedServices1

    PSError: CBSASConnectionFailure (17003)

    Cube build failed to connect to the Analysis Services server. Verify the data source connection is valid. Error: Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=can6800vm018 ASDBName=can6800vm018Analysis ASExtraNetAddress=can6800vm018 RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=05/11/2011 16:12:12 ToDate=05/11/2011 16:12:12 HighPriority=True

    From ULS:

    PWA:http://can6800vm018/PWA, SSP:SharedServices1, User:XRXNAMSPS_SrvFarm_Svc, PSI:   [CBS] Status message: Cube build initialization started 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    05/13/2011 14:13:56.61 Microsoft.Office.Project.Server (0x0BE4) 0x1044 Project Server                 Project Server Analysis Cube Bu 8swo Medium   PWA:http://can6800vm018/PWA, SSP:SharedServices1, User:XRXNAMSPS_SrvFarm_Svc, PSI:   [CBS] Status message: OLAP database and cube structure was determined successfully 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    05/13/2011 14:13:56.70 Microsoft.Office.Project.Server (0x0BE4) 0x1044 Project Server                 Project Server Analysis Cube Bu 8swo Medium   PWA:http://can6800vm018/PWA, SSP:SharedServices1, User:XRXNAMSPS_SrvFarm_Svc, PSI:   [CBS] Status message: Cube build session started 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    05/13/2011 14:14:06.08 OWSTIMER.EXE (0x0AD8)                   0x0C28 Windows SharePoint Services   Topology                       0 Medium   Adding XRXNAmsps_shrdprvdr_svc to local group 2.

    05/13/2011 14:14:06.08 OWSTIMER.EXE (0x0AD8)                   0x0C28 Windows SharePoint Services   Topology                       0 Medium   Adding XRXNAmsps_shrdprvdr_svc to local group 0.

    05/13/2011 14:14:06.17 OWSTIMER.EXE (0x0AD8)                   0x0C28 Windows SharePoint Services   Topology                       0 Medium   Adding XRXNAmsps_shrdprvdr_svc to local group 2.

    05/13/2011 14:14:06.17 OWSTIMER.EXE (0x0AD8)                   0x0C28 Windows SharePoint Services   Topology                       0 Medium   Adding XRXNAmsps_shrdprvdr_svc to local group 0.

    05/13/2011 14:14:20.69 Microsoft.Office.Project.Server (0x0BE4) 0x1044 Project Server                 Project Server Analysis Cube Bu 8swn Medium   PWA:http://can6800vm018/PWA, SSP:SharedServices1, User:XRXNAMSPS_SrvFarm_Svc, PSI:   [CBS] ProjectServerOlapCubeGenerator status: Analysis Services session started 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    05/13/2011 14:14:20.69 Microsoft.Office.Project.Server (0x0BE4) 0x1044 Project Server                 Project Server Analysis Cube Bu 8swn Medium   PWA:http://can6800vm018/PWA, SSP:SharedServices1, User:XRXNAMSPS_SrvFarm_Svc, PSI:   [CBS] ProjectServerOlapCubeGenerator status: Verify DSO is installed' 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    05/13/2011 14:14:20.69 Microsoft.Office.Project.Server (0x0BE4) 0x1044 Project Server                 Project Server Analysis Cube Bu 8swn Medium   PWA:http://can6800vm018/PWA, SSP:SharedServices1, User:XRXNAMSPS_SrvFarm_Svc, PSI:   [CBS] ProjectServerOlapCubeGenerator status: Connect to Analysis Server 'can6800vm018' 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    05/13/2011 14:14:20.69 Microsoft.Office.Project.Server (0x0BE4) 0x1044 Project Server                 Project Server Analysis Cube Bu 8swn Medium   PWA:http://can6800vm018/PWA, SSP:SharedServices1, User:XRXNAMSPS_SrvFarm_Svc, PSI:   [CBS] ProjectServerOlapCubeGenerator status: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server can6800vm018. Error: ActiveX component can't create object 84b64eb8-bf47-4ca1-91dd-9bad8a629b16

    Which goes on and on…

    Also, I'm running Win2008.

    I'd greatly appreciate it if you could help a rookie out!  Thanks!

  81. Hi Andre, looks like everything is on the same server as your AS name = the url, so that should make things easier.  I'm guessing the right version of DSO isn't in place – or a reboot (or service restart) is needed to convince the Project Server process that the right one is there.  The 2005 xmo is the one you need – regardless of SQL Server version – http://www.microsoft.com/…/details.aspx

    Best regards,

    Brian.

  82. Andre Janveaux says:

    Success!  Pretty ridiculous that I had to rollback my DSO version in order for this to work?  I had installed everything from the 2008 feature pack since I have SQL 2008…don't think I would have ever thought of that and you've saved me plenty of time wandering around aimlessly.

    Thanks again Brian!

    Andre

  83. No problem Andre – the way I think about it is that our component is written to use a specific version – so even if thhe other end changes we still need the old one.  Agreed, it shouldn't be this hard – but thinking about it like that keeps me sane (just).

    Have a good weekend!

  84. Sachin says:

    Hi Brian,

    For last 2-3 weeks, we are facing below issue with cube build job once or twice a week.

    Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.

    To resolve this issue. each time I have to perform following steps. but it is not getting fix permanently.

    1) Deleted both the tables from OLAP Repository(In my case SQL Repository).

    2) Recreate both the tables.

    3) Restart Analysis Service.

    4) Delete the OLAPCube

    5) Rebuild the Cube.

    After getting error in cube build, each time we need to perform the above steps to make it successful.

    We have 2 env QA and Prod(PS-2007) on different machines for both App as well as Database server.

    Prod cube build starts at 11:00 PM and QA starts at 1:00 AM

    But unfortunately we are facing Issue with Prod env only, once or twice a week.

    So plese help me to find out the root cause of this issue, and let me know in case you have any questions to further investigate the Issue.

    Thanks

    Sachin Vashishth

  85. Saideep says:

    Hi Brian,

    I am getting the same error message as PJ was getting, in our project server 2007 environment.I am getting following error message

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

    [5/9/2012 5:04 AM] Cube build session started

    [5/9/2012 5:04 AM] Analysis Services session started

    [5/9/2012 5:42 AM] 1408 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'

    [5/9/2012 5:42 AM] Analysis Services session completed successfully

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

    [5/9/2012 5:42 AM] Verifying and running post-build server event handler

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

    [5/9/2012 5:42 AM] Process OLAP database session started

    [5/9/2012 5:42 AM] Analysis Services session started

    [5/9/2012 5:44 AM] Analysis Services session failed with the following error: Failed to process the Analysis Services database ProjectServer on the srv111 server. Error: Errors in the OLAP storage engine: The linked measure group with the ID of 'EPM Timesheet', Name of 'EPM Timesheet' cannot be processed because it contains MG dimension with the ID of 'Task Is Overallocated', Name of 'Task Is Overallocated' with different granularity attribute than its source object.

    I just compared my DSO objects in my app server with DB server and have the same version.

  86. Hi Saideep,

    It isn't about compatibility between the DSO versions between your two servers – but having the right version on the application server – so that our Project Server code can talk to it. Use the exact versions in our documnetation and all should be good – I think the link you need is technet.microsoft.com/…/cc197728(v=office.12).aspx then follow the path to the right artilce for your SQL Server version (but the XMO will always be the 2005 version).

    Best regards,

    Brian

  87. Saideep says:

    Hi Brian,

    Thanks a lot for the guidance. We installed the said patches from the link on our Application server and got our cubes building to success. We had that link even before we posted the query but we want to take an expert advice.

    The appl and DB server were sitting on old versions of DSO, updating just the Appl server with the latest DSOs did the trick.  

    Many Thanks

    Saideep