I am trying to deliver an SSIS package to SQL Server 2005 Enterprise Edition running on Windows Server 2003 R2 (64bit).
The package itself is quite simple, just a basic read/write of a MySQL table (testing the integration).
I am able to build and deploy the package on my development machine, and I'm able to debug & build the package on the server that will eventually host it (using the local install of BIDS), but for some reason the deployment wizard fails when I attempt to execute the build package from Windows.
The error message that I get is:
TITLE: Package Installation Wizard
------------------------------
Unexpected error occurred.
------------------------------
ADDITIONAL INFORMATION:
Retrieving the COM class factory for component with
CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due
to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
------------------------------
Retrieving the COM class factory for component with
CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due
to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
The install seems to have the DLLs in the right place... Has anybody else come across this particular problem? Any tips would be appreciated. I've looked up the error in various places, but cant' seem to find any other cases quite the same as mine.
Many thanks,
Stuart
Upgrading the install to SQL Server 2005 SP2 solved this issue.
Related
I am getting an error trying to install Onyx Obsidian on my pc. Every time I try I get the error:
Error 1720. There is a problem with this Windows Installer Package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action LoadDefaultShowFile64 script error -2147467259. Microsoft SQL Server Native Client 11.0: SQL Server Network Interfaces: The specified LocalDB instance does not exist. [x89C50107]. Line 24, Column 2.
Can anyone help, I have been trying since December to get this working.
I am trying to install SSM 18.8 release. I get at then end of the installation process a fatal error 0x80070643. There's also another detail shown and I presume that is causing the error.
"Microsoft SQL Server 2012 Native Client : There's a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. "
The same error detail was shown while installing the 16.5.3 release as well as when installing Microsoft SQL Server 2012 Native Client.
I am trying to convent a Ms Access Database to MS SQL 2012, using Microsoft SQL Server Migration Assistant for Access version 6.0
but each time i try to convert it an error pops up. any ideas how i can solve the problem i reinstall the program Microsoft SQL Server Migration Assistant for Access , and it worked just ones and after that i have the same error.
any help will be most appreciated
Access Object Collector error: Database
Retrieving the COM class factory for component with CLSID {CD7791B9-43FD-42C5-AE42-8DD2811F0419} failed due to the following
error: 80040154 Class not registered (Exception from HRESULT:
0x80040154 (REGDB_E_CLASSNOTREG)). This error may be a result of
running SSMA as 64-bit application while having only 32-bit
connectivity components installed or vice versa. You can run 32-bit
SSMA application if you have 32-bit connectivity components or 64-bit
SSMA application if you have 64-bit connectivity components, shortcut
to both 32-bit and 64-bit SSMA can be found under the Programs menu.
You can also consider updating your connectivity components from
http://go.microsoft.com/fwlink/?LinkId=197502.
An error occurred while loading database content.
Just to complete the other side of the story...
If you have a 64-bit setup, you might have to go the other direction
and install the 64-bit MSAccess 2010 engine.
I'm running Access 2013, and I believe it is 64-bit.
But the SMAA tool threw the 80040154 error.
I think SMAA can't or doesn't use the 64-bit connectivity drivers that come with 64-bit Access 2013.
So using the 32-bit SMAA didn't help.
Installing the 64-bit 2010 engine did.
I got it as a free standalone download here:
https://www.microsoft.com/en-us/download/details.aspx?id=13255
After the quick install of this, I simply started
SMAA 64-bit again,
and the wizard was successful the first time.
thanks to :
https://social.technet.microsoft.com/Forums/itmanagement/en-US/0249eebf-14bd-45f6-9bca-3b42395a3d13/ssma-60-error-retrieving-the-com-class-factory-for-component-failed-due-to-the-following-error?forum=sqlservermigration
I remember this error. I had to find the EXE for 32-bit SSMA even though I was running 64-bit windows. The default installed location was:
C:\Microsoft SQL Server Migration Assistant for Access\bin
And the filename was:
SSMAforAccess32.exe
[SOLVED]
I encountered the same error while using SSMA v7.7.0 for migrating from MS-Access 2016 DB to SQL Server 2017. Fortunately, I got it fixed by installing Microsoft Access Database Engine 2016 Redistributable
with regards to installing the runtime environment of Access to get around the 80040154 error from SSMA: With Access 2016, I found that the runtime environment would not install because I already had Access installed. I needed to deinstall Access, then install the runtime only version. Then, SSMA would run without the 80040154 error. Total pain tho.
If you're trying to read/write data from/to MS Access database file via .NET application, try to switch the project to x86 architecture. It helps in my case
I am using SQL Server Data Tools 2012 version and Project Deployment Model.
I am getting below error while changing Protection level stage of the Deployment on Client's Testing Environment.
The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails.
I have created Project parameters to provide Sharepoint Site Connection String and SQL Server Database Connection String.
( Overview of the SSIS Package : Extracting data from SharePointLists and then importing in SQL Tables.)
When I searched for this error, found many ways to set the package configurations for Package Deployment Model.
What is that thing which I am missing here in the configuration of Package, so that it is not able to encrypt decrypt the mentioned UserID and Password details ?
I have gone through many forums to get clear idea on this, but could not find any solution yet.
Is it something to do with the Integration Services Version and Deployment Utility version same on the Client environment as well ? Where exactly I should check the installed versions of them ?
The ProtectionLevel is set to : DontSaveSensitive
Please help.
Thank you,
Mittal.
The prob for me was the version of sql targeting. The sql target was 2016 while i was trying to deploy to sql server 2012. so just changed the targeting from VS project properties and it worked.
I faced this issue where i was getting 'changing protection level failure. Earlier I got package version issue when I run the package from catalog. Thats because i used latest sql server data tools in my development environment and version in dev environment was 8 but in server it requires 6. But even after deploying from server with sql 2012 version, the problem persists. Later I changed the target versions in the project properties as suggested by patricgh and it worked fine.
My case is slightly different but, in the similar lines.
Local SQL server version: SQL Server 2016
Server SQL server version: SQL Server 2012
If I open the ISPAC file on my local, the package gets converted to Version 8. But on the server, its version 6. So, if you try to deploy the version 8 package on SQL server 2012, you will get the following error.
Deployment failed on Changing Protection Level stage with XML Error
To resolve this, Open the ISPAC file on the server and build it. Then deploy the package on the server. It should get deployed successfully. Hope this helps.
I converted an old dts package into SSIS package and trying to run it Windows 2008 server. This SSIS package runs an Win32 exe file which is using Interop.SQLXMLBULKLOADLib.dll and trying to load some XML data into database. But i get following error when this exe gets executed.
COM Exception: Retrieving the COM class factory for component with CLSID {8270CB2F-B0E6-4C37-8A40-D70778F47894} failed due to the following error: 80040154.
I'm trying to run the .exe file in Windows 2000 compatability mode. Please let me know if you have any suggestions.
Thanks
That CLSID belongs to SQLXML 3.0. You can download 3.0 sp3 here. FYI 0x80040154 = REGDB_E_CLASSNOTREG.
As far as I can tell SQLXML 4 does not implement the same CLSID, so I think you'll actually have to install 3 even if you have 4 installed already.