SSAS Cube - Throws "attribute key not found" when the key exists

Question

Hi,
I created a cube with 2 fact tables ( CabecNF and ItensNF ) and with some dimensions, in this case Cliente.
When I proccess the cube it throws this error:
Internal error: The operation terminated unsuccessfully.
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 'ITENSNF' partition of the 'ITENSNF' measure group for the 'SCA' cube from the SCA_Cube_ database.
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.
Server: The operation has been cancelled.
Errors in the OLAP storage engine: An error occurred while processing the 'CABECNF' partition of the 'CABECNF' measure group for the 'SCA' cube from the SCA_Cube_ database.
Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'dbo_CLIENTE', Column: 'CODIGO', Value: '6571'. The attribute is 'CLIENTEID'.
Errors in the OLAP storage engine: The attribute key was converted to an unknown member because the attribute key was not found. Attribute CLIENTEID of Dimension: CLIENTE from Database: SCA_Cube_, Cube: SCA, Measure Group: ITENSNF, Partition: ITENSNF, Record: 152957.
I understand that is not finding the ClienteID 6571. But I've checked on my database and he exists, and he has itens in the CabecNF wich has itens on ItensNF.
I've already customized the error configuration on the dimensions, but it didn't solve the problem.
What could be causing this behavior?
Thanks.
 

Answer 1

i did nt get what are trying say by this:
"First the Cliente dimension reported 500 rows skipped due to having the same name(even the name not being a key), so I changed the dimension and set the "name" property as not aggregable. Re-processed the dimension, and this time no skipped rows"
1.) were u able to do a full process of the dimension successfully?
if yes can you go and check the view or data source query that is making this dimension  have the value for the column 'CODIGO' 6571
Yes, the process of the dimension was successful. At first successful with warnings, and then successful without warnings.
But I found the problem: The Cliente dimension has relathionship with the Seguimento dimension, and the Cliente 6571 had NULL at that relationship. I fixed that and the cube was processed successfully.
It was a bit hard to find the problem because the error didn't mentioned anything about the Seguimento dimension.
Thanks for all your help guys!