SCSM2012: Cube processing failing on two cubes - ConfigItemDimKey not found

Question

Hi
Two of our cubes (SystemCenterSoftwareUpdateCube and SystemCenterPowerManagementCube) has started to fail processing lately. In ServiceManager they the error is just "failed", but in SSAS there is a lot of errors.
Both cubes fails with the following error when SSAS processing them:
"Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'ConfigItemDim', Column: 'ConfigItemDimKey', Value: '7200'. The attribute is 'ConfigItemDimKey'. Errors in the OLAP storage engine: The attribute key was converted
to an unknown member because the attribute key was not found. Attribute ConfigItemDimKey of Dimension: ConfigItemDim from Database: DWASDataBase, Cube: SystemCenterSoftwareUpdateCube, Measure Group: ConfigItemDim, Partition: ConfigItemDim, Record: 7201. 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 'ConfigItemDim'
partition of the 'ConfigItemDim' measure group for the 'SystemCenterSoftwareUpdateCube' cube from the DWASDataBase database."
=> My question: is it possible to recreate this ConfigItemDimKey manually (and how), or delete those cube and create them from scratch (back to oob status) ?
Thanks.
/Peter

Answer 1

Hi Peter,
We recently had similar issues with our ChangeAndActivityManagementCube. After a conversation with a Microsoft supporter I was able to work around that problem and so far it hasn't appeared yet.
As you can read from the error message the issues appears when Analysis Services tries to process the ConfigItemDim measure group. During the processing it's looking up the corresponding dimension for attribute key. Now when the Measure Group
is getting processed before the corresponding dimension is processed, it's possible that the attribute key doesn't exist in the dimension table yet and then this error occurs.
What you have to do is the following:
1. Process the dimensions manually using PowerShell and the following code (change the server address and SQL instance and execute it on the AS server):
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices") > $NULL
$Server = New-Object Microsoft.AnalysisServices.Server
$Server.Connect("YOUR_DW_AS_SERVER\DW_AS_INSTANCE")
$Databases = $Server.Databases
$DWASDB = $Databases["DWASDatabase"]
$Dimensions = New-Object Microsoft.AnalysisServices.Dimension
$Dimensions = $DWASDB.Dimensions
foreach ($Dimension in $Dimensions){$Dimension.Process("ProcessFull")}
2. Then process the affected measure group manually using the SQL Management Studio. You have to connect to the AS Engine, expand the DWASDatabase DB -> Cubes -> Measure Groups -> right click the affected Measure Group and select process ->
leave the standard settings in the next window and press ok.
You have to repeated step 2 for each Masure Group mentioned in the event logs.
3. Now process the entire cube by right clicking the cube in SQL Management Studio and select Process. Now the processing should finish successfully.
Since then the data warehouse cube processing jobs were working fine again too in our installation.
Hope this helps.
Cheers
Alex