SSISMHash icon indicating copy to clipboard operation
SSISMHash copied to clipboard

Installation location of Multiple Hash transform non-default SQL Server install location

Open IamOzymandias opened this issue 7 years ago • 8 comments

I modified the location of my SQL Server 2017 installation directory (I made it the same folder, but on the D drive). The Multi-Hash installer installed to the C Drive. When I copied the DLLs to the corresponding folder on the D Drive, the transform appeared in VS 2017 as expected.

IamOzymandias avatar Aug 13 '18 20:08 IamOzymandias

That is not supposed to happen. The installer is supposed to detect where the installation of SQL Server has been done.

Can you please check the content of the following registry keys?

SOFTWARE\Microsoft\Microsoft SQL Server\140\SSIS\Setup\DTSPath Key (Default) SOFTWARE\Microsoft\Microsoft SQL Server\140\DTS\Setup Key SQLPath

The installer checks these registry locations, and gets the path from them. If neither exists, it defaults to [ProgramFiles64Folder]\Microsoft SQL Server\140\DTS, which appears to be what has happened.

keif888 avatar Aug 15 '18 12:08 keif888

Both keys's value is: D:\Program Files\Microsoft SQL Server\140\DTS\

IamOzymandias avatar Aug 15 '18 12:08 IamOzymandias

Is it possible for you to uninstall the component (and delete the files you manually copied), and re-install it with logging turned on in the installer, and upload that installation log file?

eg. (change the log location as appropriate)

msiexec /i "MultipleHashInstallerx64.msi" /L*V "D:\log\MultipleHashInstall.log"

If you can't upload the entire file, I am interested in the section that starts:

Action 22:50:27: AppSearch. Searching for installed applications

and finishes with (the time will be different)

Action ended 22:50:28: AppSearch. Return value 1.

This is where it logs what it finds in the registry.

keif888 avatar Aug 15 '18 12:08 keif888

I can do that later today or this evening.

IamOzymandias avatar Aug 15 '18 14:08 IamOzymandias

For what it's worth...but, this may be the designed behavior. I'll still upload the log info later..

My HKLM has these paths and keys. However, HKCU does not. For example, HKCU stopped at the following path, and there was no DTS version of that path.

\HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\140\SSIS

IamOzymandias avatar Aug 15 '18 18:08 IamOzymandias

I have built a clean server with SQL 2017 only installed onto D:. This has shown a defect in the installer, as it incorrectly identifies that SQL 2017 is not present. But, it did correctly identify the installation locations., as shown in a custom install. Could you please clarify what else is installed on your server? Is SSDT's installed, or another edition of SQL Server?

keif888 avatar Aug 17 '18 11:08 keif888

I suspect that you may have run into a known installer issue:

Known Installer Issue If you have relocated the installation location from C: to another drive, AND one or more of the following folders exists, then you MUST use a CUSTOM install, and change the installation locations to your relocated install. C:\Program Files\Microsoft SQL Server\nnn\DTS C:\Program Files (x86)\Microsoft SQL Server\nnn\DTS The symptom of this is that Multiple Hash will not show up in SSDT's.

I am testing a fix for this.

keif888 avatar Aug 17 '18 13:08 keif888

I have just released a new installer that corrects the issue where SSIS folders exist on C:, but are not the correct installation locations..
Release v1.7.4.0

Please try this installer, and confirm that it corrects the issue you encountered.

keif888 avatar Aug 18 '18 06:08 keif888