OLAP Cube Storage Error

[john]

Hi Everybody,

Has anyone come across the below?

iled to build the OLAP cubes. Error: Analysis Services session failed with
the following error: Failed to process the Analysis Services database ISC
Production AS Repository on the dabwinpro01 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.

Thanks for your help.

 

[Sander]

Hi,

I have seen something like this once, but not on the field that you mention
here. It means that it cannot convert the value to the format it needs to
store it in the OLAP database. I have only seen this on number fields, which
is easier to understand when decimal settings are not in line. But for your
field, which is a boolean, I cannot understand how it mismatches on data type.
You could try to manually process the olap cube on the sql server. Then see
if you get more information on the error.
Processing the cube manually, you need to logon to the sql server and start
sql management studio and connect to 'analysis services' (and NOt database
services). Expand the server node until you see your cube name appear. Right
click on the name and select 'process'. In next dialog, klick ok to start
processing.

hope you get some more info what is wrong with this.

Sander

 

[ghostme]

Are you building the cube remotely? That is do you have sql server on a
separate computer

 

[john]

Thanks guys for your responses. I am in a 2 server environment - app & db -
schedule the cube to build.

I can process 13 of the 14 cubes, with it blowing up on
MSP_Project_Timesheet. There is the same as in PWA.

Any other suggestions?

Thanks
John

 

[Sander]

Found something on Brian smith blo
http://blogs.msdn.com/brismith/arch...ror-messages-when-building-cubes.aspx#8342614

Some people have had same error and was caused by mismatched versions of SQL
feature pack. So suggestion is to have SQL sp level and language the same
level as the feature pack components on the web server.

hope this helps.

Sander

 

[ghostme]

Hi,

To add to what Sander's wrote, I suggest you take the following steps

1. Install SQL Server client tools on the application server(Project Server
2007 machine)

2. Install the Sql server Management Object component(SQLServer2005_XMO.msi)

3. Now if your Sql server 2005 installation on the sql server machine has
been patch with SP1 or SP2, make sure you apply the same level of patch on
the application server(Project Server 2007 end).

4.Try building your cubes.

Please let have your feed back on this
Cheers

 

[john]

Hi Guys,

No luck wih your suggestions. I have found some others experiencing the
same issue, but with no resolutuion.

Any other suggestions?

Thank you,
John

 

[Mike Mahoney]

Hi Guys,

No luck wih your suggestions.  I have found some others experiencing the
same issue, but with no resolutuion.  

Any other suggestions?

Thank you,
John












- Show quoted text -

John

Try removing custom configuration items from the cube definitions
(enterprise codes and calculated fields) then build cubes. If this is
successful review projects to see if any have corrupt enterprise
values.

regards

Mike

 

[ghostme]

Hi John,

Have you deleted the existing cube database in analysis service. This is the
database that was partially created when the cube building process failed.
Just log in to Analysis and delete the database

 

[john]

Hi Guys,

I re-installed the SQL Components on the App and DB servers, I think for the
fifth time, and it now builds all three instance when they are scheduled.
Thank you for you guidance.

John