Cube Deploy Error

Hello, I'm trying to deploy a cube on Analysis Services and I'm getting the next error:

Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: DSAP PRODUCTO of Dimension: DSAP PRODUCTO from Database: SAPIN_BI, Cube: Sapin BI Dllo, Measure Group: DSAP COMBOS, Partition: DSAP COMBOS, Record: 1.

I'm sure the data is consistent and has integrity.... and I verified It ...

Could you please give me a clue ?

What do I have to post or which script do I have to send you ?

Thanks a lot !

jortiz wrote:

Hello, I'm trying to deploy a cube on Analysis Services and I'm getting the next error:

Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: DSAP PRODUCTO of Dimension: DSAP PRODUCTO from Database: SAPIN_BI, Cube: Sapin BI Dllo, Measure Group: DSAP COMBOS, Partition: DSAP COMBOS, Record: 1.

I'm sure the data is consistent and has integrity.... and I verified It ...

Could you please give me a clue ?

What do I have to post or which script do I have to send you ?

Thanks a lot !

Hello, Is there any service like a kind of remote desktop via Web, to show you the problem ?

|||

Assuming your cube is built on top of a SQL Server relational database, your best bet might be to use Profiler to capture the SQL queries being generated by SSAS as it processes your cube. Then look at the queries and try to determine what query is returning unexpected data. More than likely the problem lies in the design of the dimension usage within the cube. Perhaps one of the dimensions is related to one of the measure groups based on the wrong attribute or fact table column?

HTH,

Dave Fackler

|||

Dave Fackler wrote:

Assuming your cube is built on top of a SQL Server relational database, your best bet might be to use Profiler to capture the SQL queries being generated by SSAS as it processes your cube. Then look at the queries and try to determine what query is returning unexpected data. More than likely the problem lies in the design of the dimension usage within the cube. Perhaps one of the dimensions is related to one of the measure groups based on the wrong attribute or fact table column?

HTH,

Dave Fackler

Hi Dave, It doesn't matter which dimensions and fact table I use, I get a similar error like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_HSAP_REDENCIONES, Column: NMPRODUCTO_KEY, Value: 1. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: DSAP PRODUCTO of Dimension: DSAP PRODUCTO from Database: SAPIN_BI, Cube: Sapin BI Dllo, Measure Group: HSAP REDENCIONES, Partition: HSAP REDENCIONES, Record: 1. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'HSAP REDENCIONES' partition of the 'HSAP REDENCIONES' measure group for the 'Sapin BI Dllo' cube from the SAPIN_BI database.

|||

Based on the errror message, it would appear that your fact table has a column named NMPRODUCTO_KEY and a record was read from the fact table that has a value of 1 in that column. In addition, the measure group HSAP REDENCIONES would appear to be related to the DSAP PRODUCTO dimension using the NMPRODUCTO_KEY column to match the DSAP PRODUCTO attribute (which appears to be serving as the key attribute in the dimension). The question is: do any of the members in the DSAP PRODUCTO dimension have a key value of 1 for the DSAP PRODUCTO attribute? What column in the underlying dimension table is the DSAP PRODUCTO attribute based on?

Dave F.

|||

Sorry if I interfere. Have you added a new column to your fact table lately that was not in the processed cube initially?

If you use query binding for the partition(s) this new column will not appear automatically. You will have to add it yourself.

This looks like a problem that I had a few days ago.

Regards

Thomas Ivarsson

|||

Thomas Ivarsson wrote:

Sorry if I interfere. Have you added a new column to your fact table lately that was not in the processed cube initially?

If you use query binding for the partition(s) this new column will not appear automatically. You will have to add it yourself.

This looks like a problem that I had a few days ago.

Regards

Thomas Ivarsson

Thank you so much for your answers !!

|||

What solution did work?

Regards

Thomas Ivarsson