Cascade Skyline - with Microsoft Logo and Project Support header - author Brian Smith

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2007 - Common installation problems

    • 148 Comments

    These are probably repeats for many of you reading - but based on personal experience there are still some people that haven't got these messages:-

    1. If you are going to run Microsoft Office SharePoint Server 2007 and Microsoft Office Project Server 2007 on the same farm then ALL servers need both sets of bits loaded - and preferably Office SharePoint Server loaded first.  Failure to do this will probably first be seen when provisioning fails for your PWA sites.  You don't have to run all the services on all the servers - but you just can't have a "Project Server" in a farm of SharePoint servers.
    2. If you do a one-click installation of Microsoft Office Project Server 2007 (either using the Basic option, or then Advanced and Stand-alone) and then can't find your databases then chances are they are in a SQL Server 2005 instance called <machinename>\OFFICESERVERS.  The one-click doesn't allow you to choose your database server - it creates a SQL Server 2005 Express Edition instance for you.  If this isn't what you want then best to uninstall and try again - this time using the Advanced, and then Complete - which does allow you to select your SQL Server.  This will still permit you to have everything on a single stand-alone server - but with the SQL Server of your choice.

    Technorati Tags: Project Server 2007

  • Brian Smith's Microsoft Project Support Blog

    My Queue is Stuck! - How to manage your queue service in Project Server 2007

    • 102 Comments

    The new world of Project Server 2007 and the architectural changes are catching a few of our customers out - and I thought I'd share a few tips and tricks for keeping the queue flowing - and some tips for getting things moving again if they appear to have stopped. 

    First I will point to a great TechNet article on the Queue and as you will all have read this then my explanations will make more sense :).

    Under Server Settings in Project Web Access the Manage Queue option allows you to see what is happening in the project and timesheet queues - if you don't have admin access then the Personal Settings will give you a glimpse of your queue jobs.  The latter option may not however give you the complete picture and allow you to see what might be ahead or you.  It is like being stuck on the highway and not being able to see around the corner to where the flashing lights are... 

    So lets start with some definitions:-

    Waiting to be processed - means exactly what it says.  Once I get to the front of the queue then I am ready to go.  But there may be other active jobs ahead that will stop my job starting even if I am first in line.  The queue is clever enough that it will hold jobs back if their processing would interfere with other running jobs.  An example might be a publish job that will need to wait for a cube build to finish.

    Processing - means that I made it to the front of the queue, was allocated a thread and am working away!  One thing I have noticed is that the % complete indicator doesn't always make you think that "processing" is happening - but generally it is.  Looking in the ULS logs, event logs or at general server activity (particularly the Microsoft.Office.Project.Server.Queuing.exe process should help if you have continued doubts that processing is moving along.

    Skipped for optimization - is the queue's way of telling you that it is not going to do the same thing twice.  Some queue jobs have a payload (such as saving a project) and others are merely instructions (such as publish a project).  If several of the same instruction are in the queue, then only one needs to be actioned.  An example might be working on a project and publishing a few times during a period of time.  If the queue was busy all of these jobs might be sitting waiting for a while - and then rather than doing each in turn it just needs to do one.  It is just an instruction to publish the content of the saved project.  This would not happen with a queue job that had a payload as each of these contains real data that needs to be applied - rather than just an instruction to do something with data somewhere else.

    Getting Queued - appears to be one of the more confusing messages.  I mentioned above that some jobs, such as save project from Project Professional, have a payload. This payload goes into the queue as a group of related messages, which then get processed once they reach the front of the queue.  Getting queued means that these messages are going into the queue.  It is possible that the Getting Queued message appears for some time because a very large project is coming in across a very slow link.  One other potential problem that can break things is if this flow in of messages does not complete.  Perhaps the Project Manager saving the project shuts down Project before it completes - or perhaps goes out of wireless range midway through the process.  Either way the Getting Queued could sit there for some time. To fix this up find the person who has this project in mid-save and get them to reconnect and complete the job.  As a last resort you can cancel the Getting Queued - but YOU WILL LOSE DATA!  Any changes the Project Manager made will not get saved.  To protect you from inadvertently canceling one of these jobs we add a check box under Advanced options labeled "Cancel jobs getting enqueued" which will need to be checked before these jobs can be canceled.

    Failed and Not Blocking correlation - is a failure that is isolated and not stopping any other jobs from processing.  The term correlation is used to group related queue jobs together.  There should be an associated error message and entries in the log to help explain the problem.

    Failed and Blocking correlation - means that something bad happened that is also blocking other things in the related group.  If a save fails then a publish could not continue would be one example.

    Success - is the one message we like to see!  It can also be useful to sometimes show the Success messages (by default they are not shown in the Manage Queue display) as it is a way of seeing if the queue is working at all.  Adding the completion state of Success through the options on the manage queue page is how this is done.

    Canceled - means what it says.  It could have been canceled by a user, but it is also possible for jobs to be canceled by the server.  One example would be a failure early on in a save from Project Professional.  A job would have been added to the queue for the save - but reconnection may lead to cancellation of this job and the addition of another save job - it really depends hoe far the save got before the problem.  I simulate bad things like this by pulling my network cable out just after hitting save - just to see what happens!

    I will follow up with another posting on the queue with some further tips on troubleshooting -but my parting gift is a guide to what the dialogs at the bottom of Project Professional 2007 mean during a save.

      • Blue progress bar - saving to local cache
      • Synchronizing data to server... - The data is going from the local cache to the PSI and being passed into the queue (Getting Queued)
      • Save job xx% complete.  Expected Wait Time 20s - The job is either Waiting to be processed or more likely Processing.  Once you see this then it is safe to close Project Professional - your saves are safely in the queue!

    Technorati Tags: Project Server 2007

  • Brian Smith's Microsoft Project Support Blog

    Common Error Messages when Building Cubes with Project Server 2007

    • 87 Comments

    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:DOMAIN\User, 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: DOMAIN\User

    ·         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:DOMAIN\User, 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: DOMAIN\User

    ·         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  

    ·         PWA:http://<server>/PWA, SSP:SharedServices1, User:DOMAIN\User, PSI:   [CBS] ProjectServerOlapCubeGenerator status: ProjectServerOlapCubeGenerator failed with exception: Microsoft.Office.Project.PI.CBSCommon.CBSProcessException: Failed to connect to the Analysis Services server <SERVER>. Error: Cannot connect to the repository.    Analysis server: <SERVER>    Error:  The Microsoft Jet database engine cannot open the file 'C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\DSO9\msmdrep.mdb'.  It is already opened exclusively by another user, or you need permission to view its data. ---> System.Runtime.InteropServices.COMException (0x80040033): Cannot connect to the repository.    Analysis server: <SERVER>    Error:  The Microsoft Jet database engine cannot open the file 'C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\DSO9\msmdrep.mdb'.  It is already opened exclusively by another user, or you need permission to view its data.     at Interop.Dso.ServerClass.Connect(String ServerName)     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.ConnectToAnalysisServer()     --- End of inner exception stack trace ---     at ProjectServerOlapCubeGenerator.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:38:50 PM

    ·         User:                     N/A

    ·         Computer:          <SERVER>

    ·         Description:

    ·         Standard Information:PSI Entry Point:

    ·         Project User: DOMAIN\User

    ·         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=<SERVER> 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.

    4.            This is probably going to be a fairly uncommon error.  In my case my repository copied from another server already had a cube referenced and I was trying to use the same cube name on this new server.  The error messages are slightly misleading as they tend to indicate the server name is already in use – rather than the cube name.

    ULS Logs

    ·         Microsoft.Office.Project.Server

    ·         0x1204

    ·         Project Server                

    ·         Project Server Analysis Cube Bu

    ·         8swn

    ·         Medium  

    ·         PWA:http://<server>/PWA, SSP:SharedServices1, User:DOMAIN\User, PSI:   [CBS] ProjectServerOlapCubeGenerator status: ProjectServerOlapCubeGenerator failed with exception: Microsoft.Office.Project.PI.CBSCommon.CBSProcessException: Cannot overwrite an Olap database created outside of Project Server or by another Project Server Site.     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.VerifySiteOwner(Server dsoAnalisysServer, Database oldOlapDatabase, Guid siteUid)     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.GenerateOlapDatabase()     at ProjectServerOlapCubeGenerator.CMain.Main(String[] args)

    ·         Critical

    ·         Standard Information:PSI Entry Point:   Project User: DOMAIN\User  Correlation Id: 87a08e57-822e-4ec9-9a47-671f14679d6e  PWA Site URL: http://<server>/PWA  SSP Name: SharedServices1  PSError: CBSAttemptToOverwrite (17013) The Analysis Services server name that has been selected is already being used by another Project site. Select a different name or remove the existing one and try again.

    Application Event Log

    ·         Event Type:        Error

    ·         Event Source:    Office SharePoint Server

    ·         Event Category:                Project Server Analysis Cube Building

    ·         Event ID:                              7685

    ·         Date:                     2/7/2007

    ·         Time:                     2:51:09 PM

    ·         User:                     N/A

    ·         Computer:          <SERVER>

    ·         Description:

    ·         Standard Information:PSI Entry Point:

    ·         Project User: DOMAIN\User

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

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

    ·         SSP Name: SharedServices1

    ·         PSError: CBSAttemptToOverwrite (17013)

    ·         The Analysis Services server name that has been selected is already being used by another Project site. Select a different name or remove the existing one and try again.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    5.            This final error occurs if the account running Analysis Services is not a datareader in the reporting database for Project Server.

    ULS Logs

    ·         Microsoft.Office.Project.Server

    ·         0x0D44

    ·         Project Server                 

    ·         Project Server Analysis Cube Bu

    ·         8swn

    ·         Medium  

    ·         PWA:http://<server>/PWA, SSP:SharedServices1, User:DOMAIN\User, PSI:   [CBS] ProjectServerOlapCubeGenerator status: ProjectServerOlapCubeGenerator failed with exception: Microsoft.Office.Project.PI.CBSCommon.CBSProcessException: Failed to process the Analysis Services database PSCubeTest on the <SERVER> server. Error: OLE DB error: OLE DB or ODBC error: Login failed for user '<SERVER>\ASAdmin'.; 42000. 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 'PSCubeTest', Name of 'Booking Type' was being processed.  ---> System.Exception: OLE ...DB error: OLE DB or ODBC error: Login failed for user '<SERVER>\ASAdmin'.; 42000. 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 'PSCubeTest', Name of 'Booking Type' was being processed.      at Interop.Dso._Database.Process(ProcessTypes ProcessOption)     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.ProcessOlapDatabase(Database olapDatabase)     --- End of inner exception stack trace ---     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.ProcessOlapDatabase(Database olapDatabase)     at ProjectServerOlapCubeGenerator.OlapDatabaseBuilder.ProcessOlapDatabase()     at ProjectServerOlapCubeGenerator.CMain.Main(String[] args)

    Application Event Log (3 errors)

    ·         Event Type:        Failure Audit

    ·         Event Source:    MSSQLSERVER

    ·         Event Category:                (4)

    ·         Event ID:              18456

    ·         Date:                     2/7/2007

    ·         Time:                     2:57:01 PM

    ·         User:                     <SERVER>\ASAdmin

    ·         Computer:          <SERVER>

    ·         Description:

    ·         Login failed for user '<SERVER>\ASAdmin'. [CLIENT: 157.59.123.99]For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

     

    ·         Event Type:        Error

    ·         Event Source:    MSSQLServerOLAPService

    ·         Event Category:                (289)

    ·         Event ID:              3

    ·         Date:                     2/7/2007

    ·         Time:                     2:57:01 PM

    ·         User:                     N/A

    ·         Computer:          <SERVER>

    ·         Description:

    ·         OLE DB error: OLE DB or ODBC error: Login failed for user '<SERVER>\ASAdmin'.; 42000.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    ·         Event Type:        Error

    ·         Event Source:    Office SharePoint Server

    ·         Event Category:                Project Server Analysis Cube Building

    ·         Event ID:              7691

    ·         Date:                     2/7/2007

    ·         Time:                     2:57:02 PM

    ·         User:                     N/A

    ·         Computer:          <SERVER>

    ·         Description:

    ·         Standard Information:PSI Entry Point:

    ·         Project User: DOMAIN\User

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

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

    ·         SSP Name: SharedServices1

    ·         PSError: CBSOlapProcessingFailure (17004)

    ·         Cube build failed during an OLAP Processing operation. CBS queued message: Setting UID=00007829-4392-48b3-b533-5a5a4797e3c9 ASServerName=<SERVER> ASDBName=PSCubeTest ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=02/07/2007 14:56:01 ToDate=02/07/2007 14:56:01 HighPriority=True. Error: Analysis Services session failed with the following error: Failed to process the Analysis Services database PSCubeTest on the <SERVER> server. Error: OLE DB error: OLE DB or ODBC error: Login failed for user '<SERVER>\ASAdmin'.; 42000.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 'PSCubeTest', Name of 'Booking Type' was being processed.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    Technorati Tags:

     

  • Brian Smith's Microsoft Project Support Blog

    Project Server, Office SharePoint Server and Workflow

    • 79 Comments

    Windows SharePoint Services 3.0 builds on top of Windows Workflow Foundation to enable workflow to be used on list items and documents.  So you can create your own business logic to work with the content in WSS to create your own applications.  Microsoft Office SharePoint Server (MOSS) takes this to the next level and has some out of the box workflows built in that you can associate with your lists.  If Project Server is installed with MOSS then a new feature of Project Server 2007 becomes available - an automated workflow approval process for proposals.

    This feature makes use of the new server side light weight projects, and there is a certain type - called a proposal.  The idea is that this proposal is a set of steps you need to follow to get a project accepted, and when you create the proposal it will also create a WSS Task in a list that has a workflow associated with it.  This task will be assigned to a user in the Proposal Reviewers security group within Project Server.  There is a special custom field associated with proposals called the state field.  Initially this is set to proposed - but it gets changed automatically based on the approval status of the WSS task - if the reviewer says it is OK and accepts it, then the state field gets changed to Approved.  This is a very simple example of how workflow can be used on the platform - your imagination can fill in the other extensions to this to make it work for your organizations.

    As I mentioned - MOSS comes with some pre-defined approvals - but this doesn't stop you adding your own approvals to WSS lists even if you don't have MOSS.  The easiest approach (which also works in MOSS) is to go to any list or library, then under Settings, Document Library Settings you will find Workflow Settings.  You can configure simple workflows against the list from there.  Using SharePoint Designer you can create quite complex workflows against WSS lists.  One thing to point out here is that you will not be able to connect to a Project Server 2007 PWA site using SharePoint Designer as it is blocked due to the risk of you breaking some of our functionality.  However you can connect to the Project Workspaces (often referred to as PWS sites) that you create for individual projects.  If SharePoint Designer doesn't do enough for you then you can also create workflows using Visual Studio 2005.  These can obviously be much more complex and if you wanted to integrate deeply with Project Server through events and the PSI then this is the tool for you.  Once you create workflows through Visual Studio you can then consume these either through SharePoint Designer or even have them appear in the workflows available through the workflow settings of the libraries.

    So if this has sparked your interest in workflow the next places to go are:-

    Windows Workflow Foundation - http://msdn2.microsoft.com/en-us/library/ms735967.aspx

    Workflow Development for Windows SharePoint Services - http://msdn2.microsoft.com/en-us/library/ms414613.aspx

    Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation) - http://www.microsoft.com/downloads/details.aspx?familyid=5D61409E-1FA3-48CF-8023-E8F38E709BA6&displaylang=en 

    and the general SharePoint blog also is a great place for all information on the MOSS platform - http://blogs.msdn.com/sharepoint/

    If you are considering MOSS then there are plenty of other benefits on top of Project Server.  One would be search - to enable all those Project Workspaces to be easily mined for information.  Another would be Excel Services which enables you to load, calculate, and display Excel workbooks on Office SharePoint Server 2007.  I know one of my colleagues is preparing a post on the use of Excel Services with Project Server to visualize data so I will not steal his thunder - but instead suggest you subscribe to Christophe's blog at http://blogs.msdn.com/chrisfie to make sure you do not miss it.

    Technorati Tags:

  • Brian Smith's Microsoft Project Support Blog

    Microsoft Office Project Server 2007 and SQL Server 2005 Analysis Services - Building Cubes

    • 57 Comments

    Following on from my permissions piece with Project Server I will extend this logic to the service accounts and permissions to get a successful cube build.  I'll start with an explanation of what goes on when building cubes which should help any troubleshooting you do.

    When you click on Build Cube then this kicks of a sequence of events starting with the save of any new or changed data in the cube settings - such as the server or cube name.  Next a job will be placed on the Project Server queue requesting a cube build.  This job will be picked off the queue and processed by the Microsoft.Office.Project.Server.Queuing.exe process, which will spawn the ProjectServerOLAPCubeGenerator.exe process. Both of these processes will be running under the identity of the admin account of the SSP - in my last posting this is the SSPAdmin.  So this user needs to be an admin within Analysis Services so it can communicate through DSO to Analysis Services.  This permission is added through a SQL Management Studio connection to Analysis Services by right-clicking the instance name and then selecting Properties, selecting the Security tab and then adding the user (a restart of the Analysis Services service at this point will also unsure the running instance is aware of the permission change) .  This process also needs to access the repository of meta data used to define the cubes.  This repository is detailed in KB 921116 (as are some other pre-requisites for multi server environments) and is in a share on the Analysis Services server called MSOLAPRepository$.  If you have a single server then the share will not be used - instead the direct directory location of C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\DSO9. (The X will be a number relating to the installation of analysis services).  Therefore SSPAdmin, or your equivalent service account will need read and write access to this directory - and if you are in a multi server environment then also read/write access via the share.

    The next activity in the cube building process is the Analysis Services executable - MSMDSRV.exe -  actually building the cube based on the instructions given by the ProjectServerOLAPCubeGenerator.exe process.  This executable runs under the identity of the account running the SQL Server Analysis Services (MSSQLSERVER) (or named instance) service.  I'll refer to this account as ASAdmin  So this account needs to be able to read the reporting database of the Project Server instance, which is in effect the staging tables for the cubes.  Adding a login to SQL Server for ASAdmin with datareader role on ProjectServer_Reporting (or whatever reporting database name you are using) achieves this.  That should be all you need to get a cube building.

    So basically the SSPAdmin needs to be an admin in Analysis Services with read/write access to the repository.  ASAdmin needs datareader access to the reporting database.

    Also remember - when building a cube your application server is talking to/from your SQL Server Analysis Services server - when viewing or building views in Project Web Access your client PC is talking directly to your Analysis Services server (and each client needs the ASOLEDB 9.0 components).  Make sure any firewalls allow for this traffic.

    The default instance of Analysis Services will normally be listening on port 2383.  If you have named instances then the SQL Browser service will need to be running on the server to tell give clients a port for the named instance.  The SQL Browser is normally on port 2382.

    Named instances of Analysis Services will have other dynamically allocated ports. These can be discovered by looking in the configuration file for SQL Server Browser.  Open the msmdredir.ini file located at %Program files%\Microsoft SQL Server\90\Shared\ASConfig and look at the <Instances> section in it.  On 64 bit machines this may be in the Program Files (x86) directory.
    Here is an example:-

    <Instances>
         <Instance>
             <Name>AS2005</Name>
             <Port>1259</Port>
         </Instance>
     </Instances>

    and would mean your AS2005 instance is listening on port 1259.

    For my next post, rather than cluttering this one, I will show a variety of the errors from both ULS logs and Event logs that can appear if the above settings are not in place.

    Technorati Tags:

Page 1 of 92 (460 items) 12345»