The RiskFabric cube processing step (16) of the nightly RiskFabric Processing job fails and the following error is captured in the SQL Server Agent log:
<Error ErrorCode="3239313412" Description="Errors in the metadata manager. Either the database with the ID of 'RiskFabric' does not exist in the server with the ID of '<hostname>', or the user does not have permissions to access the object."
If you connect to the Analysis Services (SSAS) server hosting the RiskFabric cube using SQL Server Management Studio (SSMS), the RiskFabric database and cube are missing from Object Explorer. If you attempt to edit the SSAS server's properties, SSMS displays an error similar to the following:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Cannot show requested dialog.
------------------------------
ADDITIONAL INFORMATION:
File system error: The following file is corrupted: Physical file:\\?\<path>\Program Files\Microsoft SQL Server\MSAS<n>.MSSQLSERVER\OLAP\Data\RiskFabric.0.db\Action Plan Assigned To Portal User.0.dim\216.Action Plan Assigned To Portal User Locked Out.(All).sstore. Logical file .
Errors in the metadata manager. An error occurred when loading the 'Action Plan Assigned To Portal User' dimension, from the file, '\\?\<path>\Program Files\Microsoft SQL Server\MSAS<n>.MSSQLSERVER\OLAP\Data\RiskFabric.0.db\Action Plan Assigned To Portal User.216.dim.xml'.
Errors in the metadata manager. An error occurred when loading the 'Risk Fabric' cube, from the file, '\\?\<path>\Program Files\Microsoft SQL Server\MSAS<n>.MSSQLSERVER\OLAP\Data\RiskFabric.0.db\Risk Fabric.19703.cub.xml'.
(Microsoft.AnalysisServices.Core)
------------------------------
BUTTONS:
OK
------------------------------
The files referenced in the error message are extant on the file system; however, if you attempt to delete or move them, you may see an error indicating one or more filenames are too long.
The RiskFabric cube must be re-installed from an XMLA script. If you don't have access to an Information Centric Analytics (ICA) environment with a working cube, contact Broadcom for assistance with obtaining a script.
If you have a working development, UAT, or QA environment running the same version of ICA as is deployed in your production environment, follow this procedure to generate the script:
To restore the cube from the XMLA script, follow this procedure:
After restoring the cube, you must update the cube's data source connection string and impersonation identity. To update the connection string, follow this procedure:
To update the impersonation identity, follow this procedure:
After restoring the cube, you must run the nightly RiskFabric Processing job. Follow this procedure: