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.
Related
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
This is a legacy project in vb.net. When I run it in debug there are no errors but when I create a release version and run it in VS, I get a class not registered error when the code tries to instantiate a form. I am pretty sure the error has to do with a Crystal Reports dll, perhaps AxCrystal, but of course there is no useful information, like, which class.
Any suggestions, hints, anything are very welcome.
Try to register the class as it is described here:
A solution for this problem is to register the PrintContoll.dll
First the Crystal Reports 2010 SP1 Redistributable needs to be installed.
Then download the following file containing the PrintControll.dll:
ActiveXControls Crystal Reports 2011 SP1
Extract the folder ‘ActiveXControls’ to:
C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\Crystal Reports 2011\crystalreportviewers
I'm trying to migrate an script written in Visual Basic from 32-bit Windows Server 2008 to a 64-bit Windows Server 2012 R2. The script connects to SQL Servers, performs some queries and executes calls to a vendor/third-party API.
The dll file with the vendor's API code was not included in the new server installation, so I copied it from the old server. In order for me to be able to add the dll (via Add Reference option) to the project, I had to run the dll through Tlbimp.exe.
When I try to run the executable for my script on the new Windows server, I get the infamous error:
Unhandled Exception: System.Runtime.InteropServices.COMException:
Retrieving the COM class factory for component with CLSID {...} failed
due to the following error: 80040154 Class not registered (Exception
from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
I assume this is a complaint about the third party dll not being registered, so I have tried...
...setting the platform to x86
As per:
Retrieving the COM class factory for component with CLSID {XXXX} failed due to the following error: 80040154. In the MS Visual Basic 2010 Express IDE, I have set the platform to Active (x86) which is the only option I have.
...placing the dll in the System32 folder
...registering the dll
Using regsvr32.exe. But I gett he error:
The module "C:\Windows\SysWOW64\vendor.dll" was loaded but the
entry-point DllRegisterServer was not found...
Admittedly, I don't know the basics when it comes to programming for Windows and I feel like I may be missing something simple or fundamental here.
How do I get my VB application to run on the new server with the vendor API (dll)?
This was indeed a silly error on my part...
When attempting to register the dll, I tried to register the dll that was converted by Tlbimp.exe (the one that I could add as a reference to the project), instead of the original dll file that I copied from the old server.
The original dll file registers successfully and the executable can now run.
I'm moving a legacy application from a windows 2003 32 bit IIS 6 server to a windows 2008 r2 IIS 7.5 server.
Ultimately, I'm getting a Server.CreateObject(customobject) failed on the app.
Researching this, it seems that the object's DLL needs to be registered with the server.
I went back to the old server, found the dll by running regedit, it was located in C:\windows\system32 folder.
So I moved it over and am trying to register it using regsvr32.exe from the SysWOW64 directory. However, I'm getting two errors depending on what I do:
The command:
regsvr32.exe "I:\mypath\mymodule.dll"
generates
The module "I:\mypath\mymodule.dll" was loaded but the entry-point DllRegisterServer was not found.
Ok, so lets try the options:
regsvr32.exe /n /i "I:\mypath\mymodule.dll"
throws
The module "I:\mypath\mymodule.dll" was loaded but the entry-point DllInstall was not found.
I have no idea what else I can try, I don't think I have the source to the dll, any suggestions please?
I've figured it out,
I had to get .net fw 2.0 sp2 on there and use regasm.exe to register the dll.
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.