Error at SSIS execution (SSAS Cube)

John Michailidis 21 Reputation points


I have the following layout.

1) SSAS Cube successfully deployed on server
2) SSIS Project which takes data from an Oracle source and process a dimension of the cube.

The component inside the dataflow which I am using is Dimension Processing (Destination) with Process (Add) Incremental.

When I execute the package from Visual Studio it runs with success.

But, when I deploy the project in the server I am getting the following:

Process Add <DimensionName>:Warning: The registry key "SOFTWARE\Classes\CLSID{0535BEA2-954F-48C4-BB17-9C1C74F8B92F}\DTSInfo" cannot be opened.

Process Add<DimensionName>:Error: Failed to create COM Component Categories Manager due to error 0x80040154 "Class not registered".

The software versions we are using are:

1) SQL Server 2017 -14.0.17289.0
2) SSAS Multidimensional (Compatibility Level 1100)

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
11,570 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,319 questions
SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,208 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Olaf Helper 36,001 Reputation points

    If it runs in Visual Studio but not as job, then it could be a 32/64 bit issue; VS is 32 bit, SQL 64 bit. For a test set in the job step => Execution option the checkbox "Use 32 bit enviroment", may it works then.

  2. Lukas Yu -MSFT 5,806 Reputation points

    I thinks this error involves no influence from SSAS side, it should be , as Olaf said, a 32/64 bit issue.

    In 64 bit windows machines the COM components need to register itself in HKEY_CLASSES_ROOT\CLSID (64 bit component) OR HKEY_CLASSES_ROOT\Wow6432Node\CLSID (32 bit component) . If your application is a 32 bit application running on 64-bit machine the COM library would typically look for the GUID under Wow64 node and if your application is a 64 bit application, the COM library would try to load from HKEY_CLASSES_ROOT\CLSID. Make sure you are targeting the correct platform and ensure you have installed the correct version of library(32/64 bit).

    0 comments No comments