The installer for MultipleHash has a "bad" assumption built into it that the location that BIDS and Integration Services will look for it's files is the default install location.
As evidenced by your development database server, this isn't the location in your case, hence the manual copy of the file requirement. A reboot shouldn't have been required, and the DLL should already have been in the GAC, installed directly, rather
than from the file path by the installer.
In a 64 bit environment, where the default installation location hasn't been done, there are two registry keys that BIDS uses to locate where to look.
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\DTS Pipeline Components
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\AssemblyFolders\DTS Pipeline Components
Can you please check on your machine if these are not set to the following values?
- c:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents
- c:\Program Files (x86)\Microsoft SQL Server\90\DTS\PipelineComponents
And if not, then please copy the MultipleHash2005.dll to those locations, and see if it will then show up in the Choose Toolbox Items dialogue box.
I will roll my test machine back, and re-install with non-default path's and see if I can replicate the issue that way.
ps. I recommend using v1.3, as it doesn't have a potentially nasty issue with nulls and empty strings. It was released last night.
nb. There will be a v1.3.1 when I work out how to do a lookup of a registry key to use as the file location in the installer.