SSAS DSV in dimension pane is empty or you receive error: Error HRESULT E_FAIL has been returned from a call to a COM component
Issue: When you open a dimension (*.dim) file in a Visual Studio 2012 project, you either receive the following error, the dimension opens with a blank data source view (DSV) pane, or the dimension opens with no DSV pane at all. This is highly problematic when you need to add new attributes to the dimension.
COM Error Example. Click <OK> and the dimension will open with either no DSV pane, or an empty DSV pane.
Empty DSV pane example:
Internet Solution: You may have already read elsewhere on the Internet that this issue can be caused by the developer’s Control Panel --> Clock, Language & Region --> Language not being set to English (United States) and/or Control Panel --> Clock, Language & Region --> Region --> Home Location not being set to United States.
As this behavior only manifested itself for us in two of twenty dimensions and our Language and Regions were already set to United States, we pursued other alternatives. There are two relatively simple fixes, providing your dimension sources from a single table.
Alternative Solution #1 (preferred):
As show here -->
4. Now open the XML for the offending dimension and find the same section.
5. Copy and paste the XML from the working dimension.
6. Update the LogicalObject property which should contain the table name or named query used by the offending dimension.
7. Save the dimension file to disc, then reopen it in Solution Explorer as usual. Your DSV pane should now contain the solution DSV object you specified in LogicalObject.
Alternative Solution #2
We also found a workable solution to be right mouse clicking in the empty dimension's DSV pane and selecting Show All Tables. This is not the preferred solution because if you have many tables in your solution’s DSV, you have to wade through them all to find the one table you want for your dimension. This solution also did not work when the Error HRESULT E_FAIL has been returned from a call to a COM component error resulted in no DSV pane at all.
Side Note: If this error is happening when you try to open the solution’s DSV, it can be caused by the DSV having been created in Visual Studio 2014 while the developer is trying to open the DSV in Visual Studio 2012. (You can read a very good MSDN blog post on how to fix this particular issue here -->
|Microsoft Business Intelligence||
SQL Server Analysis Services