It looks like the v1.3 version isn't signed. That is bad. I would recommend you use the product feedback like for it and report the issue. Just clicking on the docs page led me to here but I don't know if that is the correct place to report the problem.
MSFT Oracle Connector (SSIS) fails to install
- Host
- Windows 10
- Visual Studio 2022
SQL Server Integration Services
-
Mark Covian 21 Reputation points
2024-02-02T21:22:46.3433333+00:00 Michael, thanks for the assist. I've downloaded and installed multiple times to no avail.
The MicrosoftSSISOracleConnector-SQL19-x64.msi installed successfully. Do you know if other medium exists? -
Michael Taylor 51,346 Reputation points
2024-02-02T21:35:56.42+00:00 The given error seems to indicate a network related issue. Is there a chance your firewall is getting in the way? Check the Event Log to see if it is reporting any errors for setup.
Some additional troubleshooting thoughts:
- Did you restart SSIS after installing the SQL19 version?
- Are you targeting SQL 19 and 22? If not then you don't need both versions.
- Uninstall SQL19, restart SSIS and then install SQL22. If it works then try to install SQL19 again.
-
Mark Covian 21 Reputation points
2024-02-02T22:02:56.5233333+00:00 Laptop Event Log
- Beginning a Windows Installer transaction: c:\tmp\msft oracle\microsoftssisoracleconnector-sql22-x64.msi. Client Process Id: 22272.
- Product: SQL Server Integration Services Oracle Connector -- Error 1937. An error occurred during the installation of assembly 'Microsoft.SqlServer.IntegrationServices.OracleUI,fileVersion="16.0.5479.0",version="16.0.0.0000",culture="neutral",publicKeyToken="89845DCD8080CC91",processorArchitecture="MSIL"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, component: {FFBA850F-B6C2-4DCE-88C7-8FB2D8CB4E5A}
- Windows Installer installed the product. Product Name: SQL Server Integration Services Oracle Connector. Product Version: 16.0.5479.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
- Product: SQL Server Integration Services Oracle Connector -- Installation failed.
-
Michael Taylor 51,346 Reputation points
2024-02-02T22:23:50.04+00:00 Looks like it is having an issue registering the OracleUI in the GAC. Time to test this manully.
- Open the .msi file in a zip editor like 7-zip.
- Find the file `SSIS_Microsoft_SqlServer_IntegrationServices_OracleUI_dll_64 and extract it.
- Rename the file to
Microsoft.SqlServer.IntegrationServices.OracleUI.dll
- Use the Developer Command Prompt start menu icon (from VS) and start it as an administrator.
- Install the assembly into the GAC using
gacutil -i <path to dll>.
- If that works then the binary is fine. Try rerunning the installer.
-
Mark Covian 21 Reputation points
2024-02-02T22:57:53.6233333+00:00 -
Michael Taylor 51,346 Reputation points
2024-02-03T03:18:19.5366667+00:00 That binary definitely looks bad. MS usually provides the SHA hash for files so you can confirm they are correct but they didn't do that here. Can you please post the SHA hash for the msi file you downloaded? The instructions are here.
I'm assuming here that your machine isn't having a GAC issue as I wouldn't expect the other installer to succeed but just in case could you try downloading the _x86 version and try installing it as well.
-
Mark Covian 21 Reputation points
2024-02-05T15:09:33.3766667+00:00 Below are the PS Get-fileHash results from my target machine.
I've downloaded new SQL22 _x64 and _x86 msi to another host, copied them to my machine and both SQL22 installs threw exceptions on my host.
-
Michael Taylor 51,346 Reputation points
2024-02-05T16:22:01.1066667+00:00 Hmm, the checksum doesn't line up with what I see. Just out of curiosity, can you view the properties of the file and make sure it is blocked? That doesn't seem applicable here since it shouldn't even bother to install but.
Extract the _x64 DLL from the MSI. Rename it so it is a DLL. Then view the properties. You should have a Digital Signature tab. View the signature and ensure it is valid. Then view the certificate and make sure the chain is valid. This is where it seems that the GAC is having an issue.
While I've never seen the issue, I have found one case where someone ran into a similar problem and had to go into the registry and delete the
CSP
value fromHKLM\Software\Microsoft\StrongName
. I have no idea why this would work and I cannot answer how dangerous it is to remove so you might want to back up the key first. It seems like if this were the issue then none of the MS binaries would install, including the x86 version. -
Mark Covian 21 Reputation points
2024-02-05T17:57:40.9866667+00:00 Below is old MSFT Oracle Connect DLL from that I stached from 2022. It has a digital signature in the properties section.
This is the 2022 version, it does not have a digital signature in the properties section
-
Mark Covian 21 Reputation points
2024-02-05T18:05:20.8133333+00:00 This is the SQL2019 DLL it has a Digital Signature section. The SQL 2019 installed without issue.
-
Mark Covian 21 Reputation points
2024-02-05T18:07:43.7733333+00:00 The SQL22 *.DLL highlighted, do not have a digital signatures.
The SQL19 *.DLL highlighted, All have digital signatures, in the properties dialog.
-
Mark Covian 21 Reputation points
2024-02-05T18:32:57.1166667+00:00 Hello Yitzhak,
Current SSIS Solutions - Production
- 2019 and 2016
Planning to consolidate\upgrade all current SSIS to SQL 2022.
-
Michael Taylor 51,346 Reputation points
2024-02-05T19:14:35.4966667+00:00 The binary must be signed before it can be installed to the GAC. If there is no signature there then that is a problem. The version that ships as part of the MSI has a signature. I also notice that your DLL is actually smaller than the official size of 249KB. The version # (in Details) should be 16.0.1000.6.
I'm not sure where you're getting the download from so here is the official download link. This file has the signed binaries in it. Please download from here and verify the OracleUI.dll has the digital signature and correct version.
-
Mark Covian 21 Reputation points
2024-02-05T19:58:40.2833333+00:00 INSTALL SUCCESS - Yahoo
Your Link https://www.microsoft.com/en-us/download/details.aspx?id=104113I pulled from here, V1.3, the latest ? https://www.microsoft.com/en-us/download/details.aspx?id=105811
-
Deleted
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
-
Mark Covian 21 Reputation points
2024-02-05T20:23:10.04+00:00 Thank You Michael Taylor for your successful guidance. We have successfully over this obstacle! Be well and thank you again!
-
Mark Covian 21 Reputation points
2024-02-05T20:33:01.5733333+00:00 FYI, I've sent a message to MSFT regarding the MSFT ORA connector V1.3.
-
ZoeHui-MSFT 35,556 Reputation points
2024-02-06T01:54:30.6+00:00 Hi @Mark Covian, It seems that your issue has been resolved by experts. you could mark it as answer so other user with similar problem could see this easier. :)
-
Mark Covian 21 Reputation points
2024-02-06T14:21:55.8766667+00:00 Good Morning @ZoeHui-MSFT. I have obtained the latest MSFT ORA Connector V1.3 for SSIS from here: https://www.microsoft.com/en-us/download/details.aspx?id=105811
Inspection of the DLLs suggests the associated problem continues,
And when I attempt to upgrade my current bits I'm met with the nasty error dialog that has already cost me alot of time.
@ZoeHui-MSFT, if you have a connection to MSFT, could you advise them of the problem? Thanks - Mark
Sign in to comment
-
Michael Taylor 51,346 Reputation points
2024-02-05T20:10:38.2866667+00:00
5 additional answers
Sort by: Most helpful
-
Mark Covian 21 Reputation points
2024-02-12T15:45:44.48+00:00 Good morning Rock Soft, Using VS2022 and Microsoft Connector for Oracle V1.2 I have been able to modify and deploy multiple SSIS 2019 packages to a SSIS 2019 environment and execute all packages successfully. I am good for now and can move onto the remaining 2019 packages. Mark