Error HRESULT E_FAIL has been returned from a call to a COM component

I got this error because i originally made the file in vs2014, and then used it in vs2012. this caused the error.

Fix

"View code" on the Data Source View file

Replace "000a” with “0008” to work with vs2012. 000a works with 2014, and 0008 with vs2012.




https://blogs.msdn.microsoft.com/sqlblog/2015/06/10/ssas-dsv-com-error-from-ssdt-ssas-design-data-source-view/

Check and install Integration services

To check if your machine/server has sql integration services installed:

Start > Settings > Control Panel > Administrative Tools > Services

Then look for 'SQL Server Integration Services'

To install it:

http://stackoverflow.com/questions/14551255/how-do-i-enable-integration-services-ssis-in-sql-server-2008

23down vote

Here are the screenshots of installation steps taken using SQL Server 2008 R2 installer. The steps listed below should give you an idea to install necessary components of SQL Server 2008. On the SQL Server installation media, right-click on Setup.exe and select Run as administrator. On SQL Server Installation Center, click Installation and then click New installation or add features to an existing installation. Click OK on Setup Support Rules step of SQL Server 2008 R2 Setup. If there are warnings or failures on Setup Support Rules, take necessary actions to fix them. Click Install on Setup Support Files step of SQL Server 2008 R2 Setup. Click Next > on Setup Support Rules step of SQL Server 2008 R2 Setup. If there are warnings or failures on Setup Support Rules, take necessary actions to fix them. On the Installation Type step of SQL Server 2008 R2 Setup, select either New installation or add shared features or select Add features to an existing instance of SQL Server 2008 R2 and pick an appropriate instance name. Click Next > Enter the product key on Product Key step of SQL Server 2008 R2 Setup and click Next > Check I accept license terms, if you choose to accept the terms and conditions and click Next >on License Terms step of SQL Server 2008 R2 Setup. Select SQL Server Feature Installation on Setup Role step of SQL Server 2008 R2 Setup, clickNext > On Feature Selection step of SQL Server 2008 R2 Setup, you need to decide what you would like to install. If you need only the Business Intelligence Development Studio for SSIS packages development, then install only the Business Intelligence Development Studio. If you need the Integration Services to deploy and run the SSIS packages, choose Integration Services. NOTE: I would recommend reading Licensing requirements on MSDN or Microsoft website before you choose this option. Below screenshot shows BIDS installation for SSIS packages development and other client only components. Read the details and click Next > on Installation Rules step of SQL Server 2008 R2 Setup. Read the details and click*Next >* on Disk Space Requirements step of SQL Server 2008 R2 Setup. Read the details and click Next > on Error Reporting step of SQL Server 2008 R2 Setup. Click Next > on Installation Configuration Rules step of SQL Server 2008 R2 Setup. If there are warnings or failures on Installation Configuration Rules, take necessary actions to fix them. Verify the components and click Install on Ready to Install step of SQL Server 2008 R2 Setup. Once the install is complete, the status wizard will appear. Click Close if everything is successful else take necessary action if the install fails. Hope that helps.

Stop validating excel source SSIS

Sorry to be vague, but this is too long to copy/paste

"SSIS package taking forever to load when you open it?"

This describes these 3 options which affect loading speed + the validation

• DelayValidation property
• ValidateExternalMetadata property
• “Work Offine” option

You can also "DelayValidation" to in several other places too per connection/task

http://stackoverflow.com/questions/6942985/disabling-ssis-package-validation-when-loading-a-package-in-the-vs-designer

Running SSIS Packages in 32-bit Microsoft.ACE.OLEDB.12.0 is not registered

Issue: 

Source: Package Connection manager “Excel Connection Manager” Description: The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode

Missing Components

X86 DTExec.exe not installed

I embrace a minimalist’s approach to software installation on all my servers. This means that often my servers will only have the database engine installed and possibly a few other features (such as Integration Services) as needed by the system. In most situations, there is no need for developer tools on a production server, therefore, BIDS and other components are omitted.

When installing components in this way it is easy to overlook DTExec.exe. This application is required to execute SSIS packages and only the 64-bit version will be installed if you omit some of the optional features. In order to prevent the SQL Agent error given as an example above, you will need to install either the Business Intelligence Development Studio (2008), SQL Server Data Tools (2012), or Client Tools (MSDN). I prefer to install the Client Tools when dealing with production servers.

Once installed, the 32-bit version of DTExec.exe will be available and your SQL Agent job will be able to execute in 32-bit mode. See below, Execution Properties – SQL Agent “Use 32-bit” check box, for more details on how to execute an SSIS package in 32-bit via SQL Agent job.

ACE OLEDB Provider not installed

While this is not technically a platform issue, as is the subject of this post, it does cause the same symptoms and thus is worth lumping in with this list of solutions. When attempting to interact with Microsoft Office files, such as Excel or Access, you need to have the right provider installed. Normally MS Office is installed as 32-bit even though the 64-bit version is available. Either way, if your server does not have Office installed you will not have the right providers necessary to execute your SSIS package.

Sticking to the minimalist’s mentality, I would never want to install a suite of tools like MS Office on my servers unless there was no other option. In this case, the option is to install the providers directly. The providers have a smaller footprint on your server and there are no licensing issues.

Typically you would use either the Jet 4.0 provider or the ACE OLEDB provider to interact with MS Office files. You might remember that in our example errors the system complained about the Microsoft.ACE.OLEDB.12.0 not being registered and the class not being found. The Jet provider is deprecated and not recommended for use.

Download site for the Microsoft Access Database Engine 2010 redistributable.

Execution Properties

SQL Agent “Use 32-bit” check box

In addition, to having the necessary components installed 64-bit installations of SQL Server must be told to use the 32-bit version of DTExec.exe when running a SQL Agent job. To set this option you must open the job and edit the job step for your SSIS package.

Then navigate to the Execution Options tab and select the Use 32 bit runtime check box.

Visual studio 64-bit runtime mode

Just like the SQL Agent job, your Visual Studio will likely need to be set to run as 32-bit also. In order to do this you need to open the project properties by right clicking on the project in the solution explorer and selecting properties or going to the menu bar and clicking Project and then <project_name> Properties. Once here you need to set Run64BitRuntime to FALSE.

http://www.sqlhammer.com/running-ssis-packages-in-32-bit/

Date and Value Filter

To get the correct filters shown in reporting services powerview, make sure the attribute of the dimension has a ValueColumn set with a dataType that is matches the type of filter.e.g. a date value

or you can change the dataType directly on the keycolumn if the type is wrong (e.g. wChar and should have been date)

https://www.mssqltips.com/sqlservertip/3271/sql-server-analysis-server-ssas-keycolumn-vs-namecolumn-vs-valuecolumn/

SSAS Cube Measures are empty

To correct Calculations:

In cube Calculations tab, , make sure you are on script view (as opposed to form view). Write the word CALCULATE in the script area. Click back to the Browser tab to verify that you now have measure data.


http://stackoverflow.com/questions/14451640/automatic-procesing-of-cube-after-every-1-hour