This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 5%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
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?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
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:
Laptop Event Log
Looks like it is having an issue registering the OracleUI in the GAC. Time to test this manully.
Microsoft.SqlServer.IntegrationServices.OracleUI.dllgacutil -i <path to dll>.
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.
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.
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 from HKLM\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.
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
This is the SQL2019 DLL it has a Digital Signature section. The SQL 2019 installed without issue.
The SQL22 *.DLL highlighted, do not have a digital signatures.
The SQL19 *.DLL highlighted, All have digital signatures, in the properties dialog.
Hello Yitzhak,
Current SSIS Solutions - Production
Planning to consolidate\upgrade all current SSIS to SQL 2022.
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.
Your Link
https://www.microsoft.com/en-us/download/details.aspx?id=104113
I pulled from here, V1.3, the latest ?
https://www.microsoft.com/en-us/download/details.aspx?id=105811
Thank You Michael Taylor for your successful guidance. We have successfully over this obstacle!
Be well and thank you again!
FYI, I've sent a message to MSFT regarding the MSFT ORA connector V1.3.
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. :)
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
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.
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