InstallUtilLib.dll: Unknown error in CorBindToRuntimeHost

  • Thread starter Thread starter Ryan Stevens
  • Start date Start date
R

Ryan Stevens

After creating a merge module using VS.Net 2003 and adding it to a setup,
again created with VS.NET 2003, i got this error when running the
setup."InstallUtilLib.dll: Unknown
error in CorBindToRuntimeHost " on a Windows 2000 adv server machine with
both frameworks 1.0 and 1.1 installed.

My project uses the installer classes to perform various CAs during install
(i.e. install a service)

Anybody have an idea whats wrong?
 
Well posting an identical message separately to different groups is wrong ;-)

In your final MSI file, LaunchConditions, try setting the .NET SupportedRuntimes
value to both of them, 1.1.4322;1.0.3705 , semi-colon delimited.
 
Wouldnt this mean that my install would only work if both versions of .NET
were installed? Which is not what I what in the long term. Anyhow as I
explained on my test machine I currently do have both runtime versions.

Phil Wilson said:
Well posting an identical message separately to different groups is wrong ;-)

In your final MSI file, LaunchConditions, try setting the .NET SupportedRuntimes
value to both of them, 1.1.4322;1.0.3705 , semi-colon delimited.
--
Phil Wilson [MVP Windows Installer]
----
Ryan Stevens said:
After creating a merge module using VS.Net 2003 and adding it to a setup,
again created with VS.NET 2003, i got this error when running the
setup."InstallUtilLib.dll: Unknown
error in CorBindToRuntimeHost " on a Windows 2000 adv server machine with
both frameworks 1.0 and 1.1 installed.

My project uses the installer classes to perform various CAs during install
(i.e. install a service)

Anybody have an idea whats wrong?
Click to expand...
Click to expand...
 
No, it means that your install can work on either of those runtimes.

This is a description of the problem when InstallShield users encounter it:
http://support.installshield.com/kb/view.asp?articleid=q108690

--
Phil Wilson
[MVP Windows Installer]
Ryan Stevens said:
Wouldnt this mean that my install would only work if both versions of .NET
were installed? Which is not what I what in the long term. Anyhow as I
explained on my test machine I currently do have both runtime versions.

Phil Wilson said:
Well posting an identical message separately to different groups is
Click to expand...
wrong
;-)

In your final MSI file, LaunchConditions, try setting the .NET SupportedRuntimes
value to both of them, 1.1.4322;1.0.3705 , semi-colon delimited.
--
Phil Wilson [MVP Windows Installer]
----
Ryan Stevens said:
After creating a merge module using VS.Net 2003 and adding it to a setup,
again created with VS.NET 2003, i got this error when running the
setup."InstallUtilLib.dll: Unknown
error in CorBindToRuntimeHost " on a Windows 2000 adv server machine with
both frameworks 1.0 and 1.1 installed.

My project uses the installer classes to perform various CAs during install
(i.e. install a service)

Anybody have an idea whats wrong?
Click to expand...
Click to expand...
Click to expand...
 
Because you added only a merge module, Visual Studio didn't create any .NET
support code. I made your example work by doing this:
1. Add the assembly lib.dll directly to the application folder of the setup
project and build it. This causes VS 2003 to generate a LaunchCondition and
other support code for the .NET framework.
2. Delete the assembly from the application folder! This gives you your
original project, but now it has the .NET framework supporting code in the
setup.
--
Phil Wilson
[MVP Windows Installer]
Ryan Stevens said:
Here is a very simple example solution demo'ing the problem.


Ryan Stevens said:
Wouldnt this mean that my install would only work if both versions of ..NET
were installed? Which is not what I what in the long term. Anyhow as I
explained on my test machine I currently do have both runtime versions.

Phil Wilson said:
Well posting an identical message separately to different groups is
Click to expand...
wrong
;-)

In your final MSI file, LaunchConditions, try setting the .NET SupportedRuntimes
value to both of them, 1.1.4322;1.0.3705 , semi-colon delimited.
--
Phil Wilson [MVP Windows Installer]
----
After creating a merge module using VS.Net 2003 and adding it to a setup,
again created with VS.NET 2003, i got this error when running the
setup."InstallUtilLib.dll: Unknown
error in CorBindToRuntimeHost " on a Windows 2000 adv server machine with
both frameworks 1.0 and 1.1 installed.

My project uses the installer classes to perform various CAs during install
(i.e. install a service)

Anybody have an idea whats wrong?
Click to expand...
Click to expand...
Click to expand...
 
Hi Phil and Ryan,
I went through your post. My problem goes like this
I am using InstallShield Developer 7.04 Windows Installer and Visual
Studio Dot Net 2003 (.net framework 1.1). I am using merge modules and
..net custom actions built with the installer class set to true.
I am facing the runtime error Unknown . CorBindUnkownHost Error 1001.
The solution for this is documented by InstallShield team in this
knowledge base article(Link: http://tinyurl.com/3cyks)
But having a tough time to get that thing working. So Phil, it seems
you have told Ryan about some alternate solution. Could you please be
more clear on this. Your help is highly needed and appreciated. I have
not got any help from InstallShield though I have posted them many a
times about it. This is urgent need from the customers, so the
slightest help will be nice.

Thanks & Regards
Sujit
 
Ryan's problem was a VS problem - VS wasn't adding the .NET runtime calls
because it didn't think it needed to (it didn't know that the content of the
merge module was an assembly). After looking at the InstallShield problem, it
doesn't seem to be the same issue. I suggest asking in the InstallShield
community perhaps, to see if anyone has been able to use that IS kb article
successfully.
 
Back
Top