Mike Mahoney said:
Mike Mahoney said:
Hello Mike,
Ok, I've made a lot of tests regarding this issue.
With the existing PWA site:
- With custom fields, project/assignment -> Cube Building Failed
- Remove everything (custom fields, projects/assignments) -> Cube
Building Failed
Creating a new PWA site:
- Empty site -> Cube Building Failed
- With one projects/assignments -> Cube Building Failed
Reinstalling from scratch the Project Server 2007 server but without
SP1, then creating a PWA site:
- Empty site -> Cube Building Succeed
- With custom fields, projects/assignments -> Cube Building Succeed
BUT - after installing WSS SP1 and Project Server 2007 SP1 -> Cube
Building Failed still with a "Errors in the OLAP storage engine"
One very interesting point is to compare the Dimension Usage for the
"MSP_Project_Timesheet" cube before and after the SP1. The cube
definition is completely changed (would say corrupted) and it does not
work anymore.
For me the only solution is to re-install without SP1 and wait for a
fix from Microsoft
Regards,
Dje- Hide quoted text -
- Show quoted text -
For me the only solution is to re-install without SP1 and wait for a
fix from Microsoft
Dje
I have upgraded several PS2007 systems to SP1 and have not hit this
problem, These systems are using SQL/AS 2005 SP1 and SP2 (and in one
case AS2000 SP4), without a problem (see SP2 note in Sindre's mail). A
final thought - I have noticed when deleting acubedatabase the
metadata in the repository relating to thatcubeis not removed, a
related issue is that if you configure a calculatedfieldit seems
impossible to remove it from thecubeeven after taking it out of your
config settings.
So you may have done this already, but try changing yourcubesettings
to a brand newcubedatabase name, and see if that builds cleanly.
regards
Mike
regards
Mike- Hide quoted text -
- Show quoted text -
milrock said:For me the only solution is to re-install without SP1 and wait for a
fix from Microsoft
Dje
I have upgraded several PS2007 systems to SP1 and have not hit this
problem, These systems are using SQL/AS 2005 SP1 and SP2 (and in one
case AS2000 SP4), without a problem (see SP2 note in Sindre's mail). A
final thought - I have noticed when deleting acubedatabase the
metadata in the repository relating to thatcubeis not removed, a
related issue is that if you configure a calculatedfieldit seems
impossible to remove it from thecubeeven after taking it out of your
config settings.
So you may have done this already, but try changing yourcubesettings
to a brand newcubedatabase name, and see if that builds cleanly.
regards
Mike
regards
Mike- Hide quoted text -
- Show quoted text -
Hi,
To get around this issue do the following:
1) Remove the custom fields from your cube configuration
2) Backup your custom fields by going to Server
Settings>Administrative Backup, select Enterprise Custom fields from
the drop-down and click backup.
3) Once the custom field backup has been completed, go to Server
Settings>Administrative Restore, select Enterprise Custom Fields and
select Restore. This will force a complete rebuild of the Reporting
Database. Depending on the number of projects/resource/custom fields,
etc, this may take an hour or possibly more.
4) If you have corrupt MDX expressions in the Reporting Database
(custom fields that no longer calculate correctly and are causing the
cube to fail) go to the SQL server, start SQL Mgmt Studio and connect
to Database Services. Go to System Databases and delete the OLAP
Objects database (as Analysis services data is generated from the
database any calculations/olap objects that you still have will be
regenerated, those that are corrupt will be removed.)
5) Add your custom fields back to the appropriate cubes by going to
Server Settings>Cube>Configuration
6) Save your settings and then rebuild the cube.
You should be good to go.
Let me know if you still have problems and I will try to assist.
Scot Milroy
Agora Consulting Partners
36 Toronto Street, Suite 960
Toronto, ON
milrock said:On Jan 24, 11:32 am, (e-mail address removed) wrote:
On Jan 22, 5:42 pm, (e-mail address removed) wrote:
Hello,
It seems we are running into the exact same problem (database isa SQL
cluster).
Problem is we are just installing Project Server 2007 + SP1 + some
customization (mainly addingcustomfileds)
So even with a brand new installation and an empty database we have
this error message :
===== Initiatingcubebuild process =====
[1/22/2008 6:22 PM]Cubebuild request message has been added to the
Project Server queue
===== Verifying and running pre-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running pre-build server event
handler
===== Determining database andcubestructure =====
[1/22/2008 6:23 PM]Cubebuild initialization started
[1/22/2008 6:23 PM] OLAP database andcubestructure was determined
successfully
===== Building database and cubes =====
[1/22/2008 6:23 PM]Cubebuild session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session completed successfully
===== Verifying and running post-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running post-build server event
handler
===== Processing OLAP database =====
[1/22/2008 6:23 PM] Process OLAP database session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session failed with the
following error: Failed to process the Analysis Services database
ProjectServer_OLAP on the 10.100.200.71 server. Error: Errors inthe
OLAP storage engine: The linked measure group with the ID of 'EPM
Timesheet', Name of 'EPMTimesheet' 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.
===== Process Completed =====
[1/22/2008 6:23 PM] Failed to build the OLAP cubes. Error: Analysis
Services session failed with the following error: Failed to process
the Analysis Services database ProjectServer_OLAP on the 10.100.200.71
server. Error: Errors in the OLAP storage engine: The linked measure
group with the ID of 'EPMTimesheet', Name of 'EPMTimesheet' 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.
Hope that Microsoft or someone will find a fix or a workaround.
We've already try renaming thecube, cleaning the repository db ....
nothing solve this issue.
Thank you
Dje
Dje
I have not seen this exact message, however it is possible to generate
a similar error ("Errors in the OLAP Storage Engine). You do this by
deleting a value in a lookup table which is in use on a published
plan.
In your system I would create another instance of PWA, publish a 1
task plan with an assignment, enough data to create acube. Do not
create anycustomfields or calendars (fiscal, time periods). The
cubeshould build successfully. If it doesn't there is something
fundamentally wrong with your installation. If it does then it points
to a problem with your data. Manuallly processing thecubein
Analysis Services will highlight the problem.
Mike
Hello Mike,
Ok, I've made a lot of tests regarding this issue.
With the existing PWA site:
- Withcustomfields, project/assignment ->CubeBuilding Failed
- Remove everything (customfields, projects/assignments) ->Cube
Building Failed
Creating a new PWA site:
- Empty site ->CubeBuilding Failed
- With one projects/assignments ->CubeBuilding Failed
Reinstalling from scratch the Project Server 2007 server but without
SP1, then creating a PWA site:
- Empty site ->CubeBuilding Succeed
- Withcustomfields, projects/assignments ->CubeBuilding Succeed
BUT - after installing WSS SP1 and Project Server 2007 SP1 ->Cube
Building Failed still with a "Errors in the OLAP storage engine"
One very interesting point is to compare the Dimension Usage for the
"MSP_Project_Timesheet"cubebefore and after the SP1. Thecube
definition is completely changed (would say corrupted) and it does not
work anymore.
For me the only solution is to re-install without SP1 and wait for a
fix from Microsoft
Regards,
Dje- Hide quoted text -
- Show quoted text -
Dje
I have upgraded several PS2007 systems to SP1 and have not hit this
problem, These systems are using SQL/AS 2005 SP1 and SP2 (and in one
case AS2000 SP4), without a problem (see SP2 note in Sindre's mail). A
final thought - I have noticed when deleting acubedatabase the
metadata in the repository relating to thatcubeis not removed, a
related issue is that if you configure a calculatedfieldit seems
impossible to remove it from thecubeeven after taking it out of your
config settings.
So you may have done this already, but try changing yourcubesettings
to a brand newcubedatabase name, and see if that builds cleanly.
regards
Mike
regards
Mike- Hide quoted text -
- Show quoted text -
To get around this issue do the following:
Hi Scot,
I have now tried backing up and restoring the custom fields, thus rebuilding
the Reporting database. I then deleted the AS OLAP database and the
repository, created a new repository in a SQL 2005 database, and rebuilt the
cube without custom fields. This resulted in the same error as before. Any
ideas?
Regards,
Sindre- Hide quoted text -
- Show quoted text -
Mike,Mike Mahoney said:milrock said:For me the only solution is to re-install without SP1 and wait for a
fix from Microsoft
Hi Scot,
I have now tried backing up and restoring the custom fields, thus rebuilding
the Reporting database. I then deleted the AS OLAP database and the
repository, created a new repository in a SQL 2005 database, and rebuilt the
cube without custom fields. This resulted in the same error as before. Any
ideas?
Regards,
Sindre- Hide quoted text -
- Show quoted text -
Sindre
Have you tried processing the cube database from within SQL Server
Management Studio? When it fails it often provides a more specific
error message identifying the problem data.
regards
Mike
Mike Mahoney said::
On Jan 24, 11:32 am, (e-mail address removed) wrote:
On Jan 22, 5:42 pm, (e-mail address removed) wrote:
Hello,
It seems we are running into the exact same problem (database is a SQL
cluster).
Problem is we are just installing Project Server 2007 + SP1 + some
customization (mainly addingcustomfileds)
So even with a brand new installation and an empty database we have
this error message :
===== Initiatingcubebuild process =====
[1/22/2008 6:22 PM]Cubebuild request message has been added to the
Project Server queue
===== Verifying and running pre-build server eventhandler =====
[1/22/2008 6:23 PM] Verifying and running pre-build server event
handler
===== Determining database andcubestructure =====
[1/22/2008 6:23 PM]Cubebuild initialization started
[1/22/2008 6:23 PM] OLAP database andcubestructure was determined
successfully
===== Building database and cubes =====
[1/22/2008 6:23 PM]Cubebuild session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session completed successfully
===== Verifying and running post-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running post-build server event
handler
===== Processing OLAP database =====
[1/22/2008 6:23 PM] Process OLAP database session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session failed with the
following error: Failed to process the Analysis Services database
ProjectServer_OLAP on the 10.100.200.71 server. Error: Errors in the
OLAP storage engine: The linked measure group with the ID of'EPM
Timesheet', Name of 'EPMTimesheet' cannot be processed because it
contains MG dimension with the ID of 'Task Is Overallocated', Name of
'Task Is Overallocated' with different granularity attributethan its
source object.
===== Process Completed =====
[1/22/2008 6:23 PM] Failed to build the OLAP cubes. Error: Analysis
Services session failed with the following error: Failed to process
the Analysis Services database ProjectServer_OLAP on the 10.100.200.71
server. Error: Errors in the OLAP storage engine: The linkedmeasure
group with the ID of 'EPMTimesheet', Name of 'EPMTimesheet' 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.
Hope that Microsoft or someone will find a fix or a workaround.
We've already try renaming thecube, cleaning the repository db ....
nothing solve this issue.
Thank you
Dje
Dje
I have not seen this exact message, however it is possible to generate
a similar error ("Errors in the OLAP Storage Engine). You do this by
deleting a value in a lookup table which is in use on a published
plan.
In your system I would create another instance of PWA, publisha 1
task plan with an assignment, enough data to create acube. Do not
create anycustomfields or calendars (fiscal, time periods). The
cubeshould build successfully. If it doesn't there is something
fundamentally wrong with your installation. If it does thenit points
to a problem with your data. Manuallly processing thecubein
Analysis Services will highlight the problem.
Mike
Hello Mike,
Ok, I've made a lot of tests regarding this issue.
With the existing PWA site:
- Withcustomfields, project/assignment ->CubeBuilding Failed
- Remove everything (customfields, projects/assignments) ->Cube
Building Failed
Creating a new PWA site:
- Empty site ->CubeBuilding Failed
- With one projects/assignments ->CubeBuilding Failed
Reinstalling from scratch the Project Server 2007 server but without
SP1, then creating a PWA site:
- Empty site ->CubeBuilding Succeed
- Withcustomfields, projects/assignments ->CubeBuilding Succeed
BUT - after installing WSS SP1 and Project Server 2007 SP1 ->Cube
Building Failed still with a "Errors in the OLAP storage engine"
One very interesting point is to compare the Dimension Usage forthe
"MSP_Project_Timesheet"cubebefore and after the SP1. Thecube
definition is completely changed (would say corrupted) and it does not
work anymore.
For me the only solution is to re-install without SP1 and wait for a
fix from Microsoft
Regards,
Dje- Hide quoted text -
- Show quoted text -
Dje
I have upgraded several PS2007 systems to SP1 and have not hit this
problem, These systems are using SQL/AS 2005 SP1 and SP2 (and in one
case AS2000 SP4), without a problem (see SP2 note in Sindre's mail). A
final thought - I have noticed when deleting acubedatabase the
metadata in the repository relating to thatcubeis not removed, a
related issue is that if you configure a calculatedfieldit seems
impossible to remove it from thecubeeven after taking it out of your
config settings.
So you may have done this already, but try changing yourcubesettings
to a brand newcubedatabase name, and see if that builds cleanly.
regards
Mike
regards
Mike- Hide quoted text -
- Show quoted text -
Hi,
To get around this issue do the following:
1) Remove the custom fields from your cube configuration
2) Backup your custom fields by going to Server
Settings>Administrative Backup, select Enterprise Custom fields from
the drop-down and click backup.
3) Once the custom field backup has been completed, go to Server
Settings>Administrative Restore, select Enterprise Custom Fields and
select Restore. This will force a complete rebuild of the Reporting
Database. Depending on the number of projects/resource/custom fields,
etc, this may take an hour or possibly more.
4) If you have corrupt MDX expressions in the Reporting Database
(custom fields that no longer calculate correctly and are causing the
cube to fail) go to the SQL server, start SQL Mgmt Studio and connect
to Database Services. Go to System Databases and delete the OLAP
Objects database (as Analysis services data is generated from the
database any calculations/olap objects that you still have will be
regenerated, those that are corrupt will be removed.)
5) Add your custom fields back to the appropriate cubes by going to
Server Settings>Cube>Configuration
6) Save your settings and then rebuild the cube.
You should be good to go.
Let me know if you still have problems and I will try to assist.
Scot Milroy
Agora Consulting Partners
36 Toronto Street, Suite 960
Toronto, ON
Hi Scot,
I have now tried backing up and restoring the custom fields, thus rebuilding
the Reporting database. I then deleted the AS OLAP database and the
repository, created a new repository in a SQL 2005 database, and rebuilt the
cube without custom fields. This resulted in the same error as before.Any
ideas?
Regards,
Sindre- Hide quoted text -
- Show quoted text -
Have you tried processing the cube database from within SQL Server
Management Studio? When it fails it often provides a more specific
error message identifying the problem data.
Mike
Mike,
I have tried processing the cubes from Management Studio, and I have been
able to narrow the problem down to one specific cube, MSP_Project_Timesheet.
As far as I know this is a consolidated cube consisting of three other cubes:
EPM Timesheet, Resource Timephased and Assignment Timephased. All these cubes
can be processed successfully on their own, but when the
MSP_Project_Timesheet cube is processed the EPM Timesheet measure group
fails. The error message is the same in Management Studio as in PWA.
-Sindre- Hide quoted text -
- Show quoted text -
Mike Mahoney said::
On Jan 24, 11:32 am, (e-mail address removed) wrote:
On Jan 22, 5:42 pm, (e-mail address removed) wrote:
Hello,
It seems we are running into the exact same problem (database is a SQL
cluster).
Problem is we are just installing Project Server 2007 + SP1 + some
customization (mainly addingcustomfileds)
So even with a brand new installation and an empty database we have
this error message :
===== Initiatingcubebuild process =====
[1/22/2008 6:22 PM]Cubebuild request message has been added to the
Project Server queue
===== Verifying and running pre-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running pre-build serverevent
handler
===== Determining database andcubestructure =====
[1/22/2008 6:23 PM]Cubebuild initialization started
[1/22/2008 6:23 PM] OLAP database andcubestructure was determined
successfully
===== Building database and cubes =====
[1/22/2008 6:23 PM]Cubebuild session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session completed successfully
===== Verifying and running post-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running post-build server event
handler
===== Processing OLAP database =====
[1/22/2008 6:23 PM] Process OLAP database session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session failed with the
following error: Failed to process the Analysis Services database
ProjectServer_OLAP on the 10.100.200.71 server. Error: Errors in the
OLAP storage engine: The linked measure group with the ID of 'EPM
Timesheet', Name of 'EPMTimesheet' 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.
===== Process Completed =====
[1/22/2008 6:23 PM] Failed to build the OLAP cubes. Error:Analysis
Services session failed with the following error: Failed to process
the Analysis Services database ProjectServer_OLAP on the 10.100.200.71
server. Error: Errors in the OLAP storage engine: The linked measure
group with the ID of 'EPMTimesheet', Name of 'EPMTimesheet' 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.
Hope that Microsoft or someone will find a fix or a workaround.
We've already try renaming thecube, cleaning the repository db ....
nothing solve this issue.
Thank you
Dje
Dje
I have not seen this exact message, however it is possible to generate
a similar error ("Errors in the OLAP Storage Engine). Youdo this by
deleting a value in a lookup table which is in use on a published
plan.
In your system I would create another instance of PWA, publish a 1
task plan with an assignment, enough data to create acube. Do not
create anycustomfields or calendars (fiscal, time periods). The
cubeshould build successfully. If it doesn't there is something
fundamentally wrong with your installation. If it does then it points
to a problem with your data. Manuallly processing thecubein
Analysis Services will highlight the problem.
Mike
Hello Mike,
Ok, I've made a lot of tests regarding this issue.
With the existing PWA site:
- Withcustomfields, project/assignment ->CubeBuilding Failed
- Remove everything (customfields, projects/assignments) ->Cube
Building Failed
Creating a new PWA site:
- Empty site ->CubeBuilding Failed
- With one projects/assignments ->CubeBuilding Failed
Reinstalling from scratch the Project Server 2007 server but without
SP1, then creating a PWA site:
- Empty site ->CubeBuilding Succeed
- Withcustomfields, projects/assignments ->CubeBuilding Succeed
BUT - after installing WSS SP1 and Project Server 2007 SP1 ->Cube
Building Failed still with a "Errors in the OLAP storage engine"
One very interesting point is to compare the Dimension Usage for the
"MSP_Project_Timesheet"cubebefore and after the SP1. Thecube
definition is completely changed (would say corrupted) and it does not
work anymore.
For me theonlysolution is to re-install without SP1 and wait for a
fix from Microsoft
Regards,
Dje- Hide quoted text -
- Show quoted text -
Dje
I have upgraded several PS2007 systems to SP1 and have not hit this
problem, These systems are using SQL/AS 2005 SP1 and SP2 (and inone
case AS2000 SP4), without a problem (see SP2 note in Sindre's mail). A
final thought - I have noticed when deleting acubedatabase the
metadata in the repository relating to thatcubeis not removed, a
related issue is that if you configure a calculatedfieldit seems
impossible to remove it from thecubeeven after taking it out of your
config settings.
So you may have done this already, but try changing yourcubesettings
to a brand newcubedatabase name, and see if that builds cleanly.
regards
Mike
regards
Mike- Hide quoted text -
- Show quoted text -
Hi,
To get around this issue do the following:
1) Remove the custom fields from your cube configuration
2) Backup your custom fields by going to Server
Settings>Administrative Backup, select Enterprise Custom fields from
the drop-down and click backup.
3) Once the custom field backup has been completed, go to Server
Settings>Administrative Restore, select Enterprise Custom Fields and
select Restore. This will force a complete rebuild of the Reporting
Database. Depending on the number of projects/resource/custom fields,
etc, this may take an hour or possibly more.
4) If you have corrupt MDX expressions in the Reporting Database
(custom fields that no longer calculate correctly and are causing the
cube to fail) go to the SQL server, start SQL Mgmt Studio and connect
to Database Services. Go to System Databases and delete the OLAP
Objects database (as Analysis services data is generated from the
database any calculations/olap objects that you still have will be
regenerated, those that are corrupt will be removed.)
5) Add your custom fields back to the appropriate cubes by going to
Server Settings>Cube>Configuration
6) Save your settings and then rebuild the cube.
You should be good to go.
Let me know if you still have problems and I will try to assist.
Scot Milroy
Agora Consulting Partners
36 Toronto Street, Suite 960
Toronto, ON
Hi Scot,
I have now tried backing up and restoring the custom fields, thus rebuilding
the Reporting database. I then deleted the AS OLAP database and the
repository, created a new repository in a SQL 2005 database, and rebuilt the
cube without custom fields. This resulted in the same error as before. Any
ideas?
Regards,
Sindre- Hide quoted text -
- Show quoted text -
Sindre
Have you tried processing the cube database from within SQL Server
Management Studio? When it fails it often provides a more specific
error message identifying the problem data.
regards
Mike
I have tried processing the cubes from Management Studio, and I have been
able to narrow the problem down to one specific cube, MSP_Project_Timesheet.
As far as I know this is a consolidated cube consisting of three other cubes:
EPMTimesheet, Resource Timephased and Assignment Timephased. All these cubes
can be processed successfully on their own, but when the
MSP_Project_Timesheet cube is processed the EPMTimesheetmeasure group
fails. The error message is the same in Management Studio as in PWA.
Hi Sindre
I suspect it is a corruption in the reporting database - maybe a
localisation issue - are you using english language version? Below for
comparison is contents of EPMTimesheetcube (sp1standard).
regards
EPMTimesheet
Measures
EPMTimesheet
Actual Overtime Work Billable
Actual Overtime Work Non Billable
Actual Work Billable
Actual Work Non Billable
Planned Work
Fiscal Time
Fiscal
...
read more »- Hide quoted text -
- Show quoted text -
milrock said:For me theonlysolution is to re-install without SP1 and wait for a
fix from Microsoft
Hi Sindre
I suspect it is a corruption in the reporting database - maybe a
localisation issue - are you using english language version? Below for
comparison is contents of EPMTimesheetcube (sp1standard).
regards
EPMTimesheet
Measures
EPMTimesheet
Actual Overtime Work Billable
Actual Overtime Work Non Billable
Actual Work Billable
Actual Work Non Billable
Planned Work
Fiscal Time
Fiscal
...
read more »- Hide quoted text -
- Show quoted text -
Sorry for the delay in getting back to you.
The corruption is normally around the OLAP Objects table. Did you go
into the systems database in SQL and delete the OLAP object table?
That is probably where your corruption lies. Let me know.
Gordon said:Hi All,
Was this issue resolved as I am having the exact same problem after
application of Project Server 2007 SP1
milrock said::
:
On Jan 24, 11:32 am, (e-mail address removed) wrote:
On Jan 22, 5:42 pm, (e-mail address removed) wrote:
Hello,
It seems we are running into the exact same problem (database is a SQL
cluster).
Problem is we are just installing Project Server 2007 + SP1 + some
customization (mainly addingcustomfileds)
So even with a brand new installation and an empty database we have
this error message :
===== Initiatingcubebuild process =====
[1/22/2008 6:22 PM]Cubebuild request message has been added to the
Project Server queue
===== Verifying and running pre-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running pre-build server event
handler
===== Determining database andcubestructure =====
[1/22/2008 6:23 PM]Cubebuild initialization started
[1/22/2008 6:23 PM] OLAP database andcubestructure was determined
successfully
===== Building database and cubes =====
[1/22/2008 6:23 PM]Cubebuild session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session completed successfully
===== Verifying and running post-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running post-build server event
handler
===== Processing OLAP database =====
[1/22/2008 6:23 PM] Process OLAP database session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session failed with the
following error: Failed to process the Analysis Services database
ProjectServer_OLAP on the 10.100.200.71 server. Error: Errors in the
OLAP storage engine: The linked measure group with the ID of 'EPM
Timesheet', Name of 'EPMTimesheet' 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.
===== Process Completed =====
[1/22/2008 6:23 PM] Failed to build the OLAP cubes. Error: Analysis
Services session failed with the following error: Failed to process
the Analysis Services database ProjectServer_OLAP on the 10.100.200.71
server. Error: Errors in the OLAP storage engine: The linked measure
group with the ID of 'EPMTimesheet', Name of 'EPMTimesheet' 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.
Hope that Microsoft or someone will find a fix or a workaround.
We've already try renaming thecube, cleaning the repository db ....
nothing solve this issue.
Thank you
Dje
Dje
I have not seen this exact message, however it is possible to generate
a similar error ("Errors in the OLAP Storage Engine). You do this by
deleting a value in a lookup table which is in use on a published
plan.
In your system I would create another instance of PWA, publish a 1
task plan with an assignment, enough data to create acube. Do not
create anycustomfields or calendars (fiscal, time periods). The
cubeshould build successfully. If it doesn't there is something
fundamentally wrong with your installation. If it does then it points
to a problem with your data. Manuallly processing thecubein
Analysis Services will highlight the problem.
Mike
Hello Mike,
Ok, I've made a lot of tests regarding this issue.
With the existing PWA site:
- Withcustomfields, project/assignment ->CubeBuilding Failed
- Remove everything (customfields, projects/assignments) ->Cube
Building Failed
Creating a new PWA site:
- Empty site ->CubeBuilding Failed
- With one projects/assignments ->CubeBuilding Failed
Reinstalling from scratch the Project Server 2007 server but without
SP1, then creating a PWA site:
- Empty site ->CubeBuilding Succeed
- Withcustomfields, projects/assignments ->CubeBuilding Succeed
BUT - after installing WSS SP1 and Project Server 2007 SP1 ->Cube
Building Failed still with a "Errors in the OLAP storage engine"
One very interesting point is to compare the Dimension Usage for the
"MSP_Project_Timesheet"cubebefore and after the SP1. Thecube
definition is completely changed (would say corrupted) and it does not
work anymore.
For me theonlysolution is to re-install without SP1 and wait for a
fix from Microsoft
Regards,
Dje- Hide quoted text -
- Show quoted text -
Dje
I have upgraded several PS2007 systems to SP1 and have not hit this
problem, These systems are using SQL/AS 2005 SP1 and SP2 (and in one
case AS2000 SP4), without a problem (see SP2 note in Sindre's mail). A
final thought - I have noticed when deleting acubedatabase the
metadata in the repository relating to thatcubeis not removed, a
related issue is that if you configure a calculatedfieldit seems
impossible to remove it from thecubeeven after taking it out of your
config settings.
So you may have done this already, but try changing yourcubesettings
to a brand newcubedatabase name, and see if that builds cleanly.
regards
Mike
regards
Mike- Hide quoted text -
- Show quoted text -
Hi,
To get around this issue do the following:
1) Remove the custom fields from your cube configuration
2) Backup your custom fields by going to Server
Settings>Administrative Backup, select Enterprise Custom fields from
the drop-down and click backup.
3) Once the custom field backup has been completed, go to Server
Settings>Administrative Restore, select Enterprise Custom Fields and
select Restore. This will force a complete rebuild of the Reporting
Database. Depending on the number of projects/resource/custom fields,
etc, this may take an hour or possibly more.
4) If you have corrupt MDX expressions in the Reporting Database
(custom fields that no longer calculate correctly and are causing the
cube to fail) go to the SQL server, start SQL Mgmt Studio and connect
to Database Services. Go to System Databases and delete the OLAP
Objects database (as Analysis services data is generated from the
database any calculations/olap objects that you still have will be
regenerated, those that are corrupt will be removed.)
5) Add your custom fields back to the appropriate cubes by going to
Server Settings>Cube>Configuration
6) Save your settings and then rebuild the cube.
You should be good to go.
Let me know if you still have problems and I will try to assist.
Scot Milroy
Agora Consulting Partners
36 Toronto Street, Suite 960
Toronto, ON
Hi Scot,
I have now tried backing up and restoring the custom fields, thus rebuilding
the Reporting database. I then deleted the AS OLAP database and the
repository, created a new repository in a SQL 2005 database, and rebuilt the
cube without custom fields. This resulted in the same error as before. Any
ideas?
Regards,
Sindre- Hide quoted text -
- Show quoted text -
Sindre
Have you tried processing the cube database from within SQL Server
Management Studio? When it fails it often provides a more specific
error message identifying the problem data.
regards
Mike
Mike,
I have tried processing the cubes from Management Studio, and I have been
able to narrow the problem down to one specific cube, MSP_Project_Timesheet.
As far as I know this is a consolidated cube consisting of three other cubes:
EPMTimesheet, Resource Timephased and Assignment Timephased. All these cubes
can be processed successfully on their own, but when the
MSP_Project_Timesheet cube is processed the EPMTimesheetmeasure group
fails. The error message is the same in Management Studio as in PWA.
-Sindre- Hide quoted text -
- Show quoted text -
Hi Sindre
I suspect it is a corruption in the reporting database - maybe a
localisation issue - are you using english language version? Below for
comparison is contents of EPMTimesheetcube (sp1standard).
regards
EPMTimesheet
Measures
EPMTimesheet
Actual Overtime Work Billable
Actual Overtime Work Non Billable
Actual Work Billable
Actual Work Non Billable
Planned Work
Fiscal Time
Fiscal
...
read more »- Hide quoted text -
- Show quoted text -
Sorry for the delay in getting back to you.
The corruption is normally around the OLAP Objects table. Did you go
into the systems database in SQL and delete the OLAP object table?
That is probably where your corruption lies. Let me know.
Hi!
We were able to solve this problem at our customer in the end. We used the
following process to solve the problem:
- Install SQL Server 2005 SP2 Cummulative Update 6. (This hotfix must be
requested from Microsoft.)
- Reinstall/Update SQL Server Native Client, SQL Server 2005 Backward
Compatibility Components and SQL Server 2005 Management Objects Collection,
all part of Feature Pack for SQL Server 2005 - february 2007, on the
application server.
- Delete OLAP Repository database.
- Delete Cube database.
- Create new OLAP Repository database (with new name), set user rights and
DSO connections.
- Delete all content in OLAP\Data folder, and in the specified locks
directory.
- Remove all custom fields from cube configuration.
- Back up and restore custom fields to rebuild Reporting database.
- Set up Cube database to be created with new name and run cube building.
If building succeeds:
- Add custom fields to cube configuration.
- Run cube building.
If building succeeds second time:
- Connect all existing Data Analysis views to new Cube database.
As you can see most of these steps were suggested earlier in this thread,
and it was the first two steps that did the trick. We don't know which oneof
them actually solved the problem, as they both were applied between the last
failed and first successful cube build. The SQL hotfix probably isn't common
in most PS2007 installations where the cube building works fine though, sowe
think the SQL feature pack update is most likely the solution.
Regards,
Sindre
Gordon said::
:
On Jan 24, 11:32 am, (e-mail address removed) wrote:
On Jan 22, 5:42 pm, (e-mail address removed) wrote:
Hello,
It seems we are running into the exact same problem (database is a SQL
cluster).
Problem is we are just installing Project Server 2007 + SP1 + some
customization (mainly addingcustomfileds)
So even with a brand new installation and an empty database we have
this error message :
===== Initiatingcubebuild process =====
[1/22/2008 6:22 PM]Cubebuild request message has been added to the
Project Server queue
===== Verifying and running pre-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running pre-build server event
handler
===== Determining database andcubestructure =====
[1/22/2008 6:23 PM]Cubebuild initialization started
[1/22/2008 6:23 PM] OLAP database andcubestructure was determined
successfully
===== Building database and cubes =====
[1/22/2008 6:23 PM]Cubebuild session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session completed successfully
===== Verifying and running post-build server event handler =====
[1/22/2008 6:23 PM] Verifying and running post-buildserver event
handler
===== Processing OLAP database =====
[1/22/2008 6:23 PM] Process OLAP database session started
[1/22/2008 6:23 PM] Analysis Services session started
[1/22/2008 6:23 PM] Analysis Services session failedwith the
following error: Failed to process the Analysis Services database
ProjectServer_OLAP on the 10.100.200.71 server. Error: Errors in the
OLAP storage engine: The linked measure group with the ID of 'EPM
Timesheet', Name of 'EPMTimesheet' 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.
===== Process Completed =====
[1/22/2008 6:23 PM] Failed to build the OLAP cubes. Error: Analysis
Services session failed with the following error: Failed to process
the Analysis Services database ProjectServer_OLAP onthe 10.100.200.71
server. Error: Errors in the OLAP storage engine: The linked measure
group with the ID of 'EPMTimesheet', Name of 'EPMTimesheet' cannot
be processed because it contains MG dimension with the ID of 'Task Is
Overallocated', Name of 'Task Is Overallocated' withdifferent
granularity attribute than its source object.
Hope that Microsoft or someone will find a fix or a workaround.
We've already try renaming thecube, cleaning the repository db ....
nothing solve this issue.
Thank you
Dje
Dje
I have not seen this exact message, however it is possible to generate
a similar error ("Errors in the OLAP Storage Engine). You do this by
deleting a value in a lookup table which is in use on a published
plan.
In your system I would create another instance of PWA,publish a 1
task plan with an assignment, enough data to create acube. Do not
create anycustomfields or calendars (fiscal, time periods). The
cubeshould build successfully. If it doesn't there is something
fundamentally wrong with your installation. If it does then it points
to a problem with your data. Manuallly processing thecubein
Analysis Services will highlight the problem.
Mike
Hello Mike,
Ok, I've made a lot of tests regarding this issue.
With the existing PWA site:
- Withcustomfields, project/assignment ->CubeBuilding Failed
- Remove everything (customfields, projects/assignments)->Cube
Building Failed
Creating a new PWA site:
- Empty site ->CubeBuilding Failed
- With one projects/assignments ->CubeBuilding Failed
Reinstalling from scratch the Project Server 2007 serverbut without
SP1, then creating a PWA site:
- Empty site ->CubeBuilding Succeed
- Withcustomfields, projects/assignments ->CubeBuilding Succeed
BUT - after installing WSS SP1 and Project Server 2007 SP1 ->Cube
Building Failed still with a "Errors in the OLAP storageengine"
One very interesting point is to compare the Dimension Usage for the
"MSP_Project_Timesheet"cubebefore and after the SP1. Thecube
definition is completely changed (would say corrupted) and it does not
work anymore.
For me theonlysolution is to re-install without SP1 and wait for a
fix from Microsoft
Regards,
Dje- Hide quoted text -
- Show quoted text -
Dje
I have upgraded several PS2007 systems to SP1 and have nothit this
problem, These systems are using SQL/AS 2005 SP1 and SP2 (and in one
case AS2000 SP4), without a problem (see SP2 note in Sindre's mail). A
final thought - I have noticed when deleting acubedatabasethe
metadata in the repository relating to thatcubeis not removed, a
related issue is that if you configure a calculatedfielditseems
impossible to remove it from thecubeeven after taking it out of your
config settings.
So you may have done this already, but try changing yourcubesettings
to a brand newcubedatabase name, and see if that builds cleanly.
regards
Mike
regards
Mike- Hide quoted text -
- Show quoted text -
Hi,
To get around this issue do the following:
1) Remove the custom fields from your cube configuration
2) Backup your custom fields by going to Server
Settings>Administrative Backup, select Enterprise Custom fields from
the drop-down and click backup.
3) Once the custom field backup has been completed, go to Server
Settings>Administrative Restore, select Enterprise Custom Fields and
select Restore. This will force a complete rebuild of theReporting
Database. Depending on the number of
...
read more »- Hide quoted text -
- Show quoted text -