Cube building errors in Project Server 2007 farm

[dineshks]

In my project server farm setup(DB & App server seperate) I have several PWA instances.
I have setup cube building service for each PWA sites. I am using SQL 2005 database as OLAP repository. I am able to successfully build cubes for each PWA sites (with different cube names for each PWA site) initially with schedule setup for building daily at 11PM. But next day I am seeing following error:
__________
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.
___________________________________

If I change the cube name & manually build it builds. But the scheduled build fails with same error later. Not sure whether it's due to the fact that all other cubes are also scheduled to build at same time!

[ssanderlin]

Originally Posted by dineshks

In my project server farm setup(DB & App server seperate) I have several PWA instances.
I have setup cube building service for each PWA sites. I am using SQL 2005 database as OLAP repository. I am able to successfully build cubes for each PWA sites (with different cube names for each PWA site) initially with schedule setup for building daily at 11PM. But next day I am seeing following error:
__________
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.
___________________________________

If I change the cube name & manually build it builds. But the scheduled build fails with same error later. Not sure whether it's due to the fact that all other cubes are also scheduled to build at same time!

Are you using the same OLAP Repository for multiple instances?

[dineshks]

Yes, I am using the same repository.

[ssanderlin]

Originally Posted by dineshks

Yes, I am using the same repository.

According to Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service article:

Organizations may have multiple Project Web Access instances on the farm. The information described in this article applies to each instance.

Because of this, and the problem you're having, I'm inclined to believe that using a single OLAP Repository for multiple Project instances is not supported. Nothing definitive, of course, but I would consider it as a possibility.

[dineshks]

Originally Posted by ssanderlin

According to Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service article:


Because of this, and the problem you're having, I'm inclined to believe that using a single OLAP Repository for multiple Project instances is not supported. Nothing definitive, of course, but I would consider it as a possibility.

____________________
We can configure only One repository for Analysis services for a setup(with one DB server). Only parameter I can supply while setting up cube build is cube name. I am giving different cube name for each instance. Still the build fails. When I contacted support person, I was told I need to schedule the build for each cube at different intervals(shouldn't overlap). I wonder why it need to be so. My be analysis server doesn't accept more connections at a time?
If this is the limitation, then I can schedule for maximum 47 instances with unique build time (since schedule allows only 30 min interval gaps)

[ssanderlin]

Originally Posted by dineshks

____________________
We can configure only One repository for Analysis services for a setup(with one DB server). Only parameter I can supply while setting up cube build is cube name. I am giving different cube name for each instance. Still the build fails. When I contacted support person, I was told I need to schedule the build for each cube at different intervals(shouldn't overlap). I wonder why it need to be so. My be analysis server doesn't accept more connections at a time?
If this is the limitation, then I can schedule for maximum 47 instances with unique build time (since schedule allows only 30 min interval gaps)

I assumed that you had set up seperate AS instances for each PS instance to minimize the impact between the instances. I should have asked

I would venture to guess that the reason you have trouble with the overlap is that the Project Server writes some sort of locking record to the repository. AS should take more than one connection at a time -- I have a feeling it has to do with the way the Repository is designed.