[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.setup

InstallUtilLib.DLL: Unknown Error?

Rob R. Ainscough

7/4/2006 5:07:00 PM

I'm yet another developer with the useless Installation error message, event
viewer is just as useless MsiInstaller error 1001 and shows
InstallUtilLib.DLL: Unknown Error, (NULL), (NULL), (NULL) -- oh that is so
helpful M$, how could I not know what this means...(yes, google searches has
not reveal any solutions, I've tried them all).

Trying to install a Windows Service using VS 2005, it will NOT install on
any client PC, but will install and work just fine on my development PC
(using either the Setup.EXE from Release dir or via the VS IDE right click
Install from the setup project.

Soon to be ex-developer because my company is about to go under because we
fell for the VS 2005 development platform as being ready for prime time --
hope this makes M$ developers, project managers, and QA folks for Windows
Installer and VS 2005 feel good -- I guess they have less competition now --
well ya got my $7500 over the past 3 years waiting for VS 2003 successor --
are you happy?

WTF is going on with M$? I'm just over it, every freakin' day I'm wasting
hours research problems with VS 2005. Any time I try to put a
"professional" complete package together with VS 2005, it just doesn't work.
I realize that some key people from the VS 2005 dev team were terminated
(yes every developer does need some "inside" contacts), but how does that
help me here and now?

1. Meaningful error message - how can I proceed without them, needle in a
hay stack
2. Don't "release" dev tools that are clearly BETA
3. Firing VS 2005 team members doesn't help me here and now
6 Answers

Rob R. Ainscough

7/5/2006 4:08:00 AM

0

I found a solution, but I have not found the reason for the problem.

I uninstalled .NET framework 2.0 on the client PC (my test PC) and let my
installer re-install it, this has cured the current issue on my test
machine. Why did this happen and how did this happen I will probably never
know -- the error message provided by the Install (MSIEXEC) is pathetic at
best. I'm going to do more testing because I'd like to duplicate this
problem since I've already raised a bug on M$ feedback. I know M$ don't
give a rats ass, but I hope that this might help others that have struggled
with this turd of a development platform called VS 2005.

Rob.

"Rob R. Ainscough" <robains@pacbell.net> wrote in message
news:O1s6xw4nGHA.3700@TK2MSFTNGP03.phx.gbl...
> I'm yet another developer with the useless Installation error message,
> event viewer is just as useless MsiInstaller error 1001 and shows
> InstallUtilLib.DLL: Unknown Error, (NULL), (NULL), (NULL) -- oh that is so
> helpful M$, how could I not know what this means...(yes, google searches
> has not reveal any solutions, I've tried them all).
>
> Trying to install a Windows Service using VS 2005, it will NOT install on
> any client PC, but will install and work just fine on my development PC
> (using either the Setup.EXE from Release dir or via the VS IDE right click
> Install from the setup project.
>
> Soon to be ex-developer because my company is about to go under because we
> fell for the VS 2005 development platform as being ready for prime time --
> hope this makes M$ developers, project managers, and QA folks for Windows
> Installer and VS 2005 feel good -- I guess they have less competition
> now -- well ya got my $7500 over the past 3 years waiting for VS 2003
> successor -- are you happy?
>
> WTF is going on with M$? I'm just over it, every freakin' day I'm wasting
> hours research problems with VS 2005. Any time I try to put a
> "professional" complete package together with VS 2005, it just doesn't
> work. I realize that some key people from the VS 2005 dev team were
> terminated (yes every developer does need some "inside" contacts), but how
> does that help me here and now?
>
> 1. Meaningful error message - how can I proceed without them, needle in a
> hay stack
> 2. Don't "release" dev tools that are clearly BETA
> 3. Firing VS 2005 team members doesn't help me here and now
>
>
>


Phil Wilson

7/5/2006 5:50:00 PM

0

For some reason that I am unaware of, Visual Studio decided to install
services in a rather convoluted way. There's a call from the msiexec process
to InstallUtilLib.dll passing a bunch of parameters, and then calls on .NET
Installer classes that locate your assembly, find its Installer classes,
instantiate them, call methods that install the service etc. As you can
probably imagine, this is rather complicated and sometimes fragile. However
Windows Installer has bult-in support for installing services (the
ServiceInstall and ServiceControl tables) that people used for years before
..NET came along, so why Visual Studio invented installer classes to install
services is a mystery to me.

Many installation developers who have been building setups for a while
consider managed custom actions a bad thing:

http://www.installsite.org/pages/en/msifaq/...

I wonder if this is the first time you've built an MSI-based setup. There
seem to be a lot of Visual Studio developers doing this since VS
setup&deployment projects came along and, although the lack of
InstallUtilLib diagnostics is a pain, it's not the only (and probably not
even the best) tool for building MSI-based setups.
http://www.installsite.org/pages/en/msi/aut...
--
Phil Wilson [MVP Windows Installer]
----
"Rob R. Ainscough" <robains@pacbell.net> wrote in message
news:%23LMpEi%23nGHA.2264@TK2MSFTNGP04.phx.gbl...
>I found a solution, but I have not found the reason for the problem.
>
> I uninstalled .NET framework 2.0 on the client PC (my test PC) and let my
> installer re-install it, this has cured the current issue on my test
> machine. Why did this happen and how did this happen I will probably
> never know -- the error message provided by the Install (MSIEXEC) is
> pathetic at best. I'm going to do more testing because I'd like to
> duplicate this problem since I've already raised a bug on M$ feedback. I
> know M$ don't give a rats ass, but I hope that this might help others that
> have struggled with this turd of a development platform called VS 2005.
>
> Rob.
>
> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
> news:O1s6xw4nGHA.3700@TK2MSFTNGP03.phx.gbl...
>> I'm yet another developer with the useless Installation error message,
>> event viewer is just as useless MsiInstaller error 1001 and shows
>> InstallUtilLib.DLL: Unknown Error, (NULL), (NULL), (NULL) -- oh that is
>> so helpful M$, how could I not know what this means...(yes, google
>> searches has not reveal any solutions, I've tried them all).
>>
>> Trying to install a Windows Service using VS 2005, it will NOT install on
>> any client PC, but will install and work just fine on my development PC
>> (using either the Setup.EXE from Release dir or via the VS IDE right
>> click Install from the setup project.
>>
>> Soon to be ex-developer because my company is about to go under because
>> we fell for the VS 2005 development platform as being ready for prime
>> time -- hope this makes M$ developers, project managers, and QA folks
>> for Windows Installer and VS 2005 feel good -- I guess they have less
>> competition now -- well ya got my $7500 over the past 3 years waiting
>> for VS 2003 successor -- are you happy?
>>
>> WTF is going on with M$? I'm just over it, every freakin' day I'm
>> wasting hours research problems with VS 2005. Any time I try to put a
>> "professional" complete package together with VS 2005, it just doesn't
>> work. I realize that some key people from the VS 2005 dev team were
>> terminated (yes every developer does need some "inside" contacts), but
>> how does that help me here and now?
>>
>> 1. Meaningful error message - how can I proceed without them, needle in
>> a hay stack
>> 2. Don't "release" dev tools that are clearly BETA
>> 3. Firing VS 2005 team members doesn't help me here and now
>>
>>
>>
>
>


Rob R. Ainscough

7/5/2006 8:41:00 PM

0

Hi Phil,

The clue that lead me to think there was more wrong with .NET framework
installation was when I tried to uninstall another .NET 2.0 project that had
installed just fine a few days ago -- my attempt to remove via Control Panel
resulted in the same InstallUtilLib.dll error. The only activity that
happened between these states was the uninstall and re-install of .NET 1.1.
This seems to have created some problems for .NET 2.0 installer. Fragile is
very true. However, I've looked into other tools such as InstallShield and
have found that many folks are experiencing the same or similiar problems
with InstallUtilLib.dll for their .NET 2.0 projects being distributed via
the InstallShield projects.

I'm not a dedicated "Installation Developer" -- I'm really the ONLY
developer that works on ALL our .NET projects (web, click once, windows
services, windows forms, etc.).

I've built many MSI setups before.



"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:uQTLltFoGHA.4432@TK2MSFTNGP05.phx.gbl...
> For some reason that I am unaware of, Visual Studio decided to install
> services in a rather convoluted way. There's a call from the msiexec
> process to InstallUtilLib.dll passing a bunch of parameters, and then
> calls on .NET Installer classes that locate your assembly, find its
> Installer classes, instantiate them, call methods that install the service
> etc. As you can probably imagine, this is rather complicated and sometimes
> fragile. However Windows Installer has bult-in support for installing
> services (the ServiceInstall and ServiceControl tables) that people used
> for years before .NET came along, so why Visual Studio invented installer
> classes to install services is a mystery to me.
>
> Many installation developers who have been building setups for a while
> consider managed custom actions a bad thing:
>
> http://www.installsite.org/pages/en/msifaq/...
>
> I wonder if this is the first time you've built an MSI-based setup. There
> seem to be a lot of Visual Studio developers doing this since VS
> setup&deployment projects came along and, although the lack of
> InstallUtilLib diagnostics is a pain, it's not the only (and probably not
> even the best) tool for building MSI-based setups.
> http://www.installsite.org/pages/en/msi/aut...
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
> news:%23LMpEi%23nGHA.2264@TK2MSFTNGP04.phx.gbl...
>>I found a solution, but I have not found the reason for the problem.
>>
>> I uninstalled .NET framework 2.0 on the client PC (my test PC) and let my
>> installer re-install it, this has cured the current issue on my test
>> machine. Why did this happen and how did this happen I will probably
>> never know -- the error message provided by the Install (MSIEXEC) is
>> pathetic at best. I'm going to do more testing because I'd like to
>> duplicate this problem since I've already raised a bug on M$ feedback. I
>> know M$ don't give a rats ass, but I hope that this might help others
>> that have struggled with this turd of a development platform called VS
>> 2005.
>>
>> Rob.
>>
>> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
>> news:O1s6xw4nGHA.3700@TK2MSFTNGP03.phx.gbl...
>>> I'm yet another developer with the useless Installation error message,
>>> event viewer is just as useless MsiInstaller error 1001 and shows
>>> InstallUtilLib.DLL: Unknown Error, (NULL), (NULL), (NULL) -- oh that is
>>> so helpful M$, how could I not know what this means...(yes, google
>>> searches has not reveal any solutions, I've tried them all).
>>>
>>> Trying to install a Windows Service using VS 2005, it will NOT install
>>> on any client PC, but will install and work just fine on my development
>>> PC (using either the Setup.EXE from Release dir or via the VS IDE right
>>> click Install from the setup project.
>>>
>>> Soon to be ex-developer because my company is about to go under because
>>> we fell for the VS 2005 development platform as being ready for prime
>>> time -- hope this makes M$ developers, project managers, and QA folks
>>> for Windows Installer and VS 2005 feel good -- I guess they have less
>>> competition now -- well ya got my $7500 over the past 3 years waiting
>>> for VS 2003 successor -- are you happy?
>>>
>>> WTF is going on with M$? I'm just over it, every freakin' day I'm
>>> wasting hours research problems with VS 2005. Any time I try to put a
>>> "professional" complete package together with VS 2005, it just doesn't
>>> work. I realize that some key people from the VS 2005 dev team were
>>> terminated (yes every developer does need some "inside" contacts), but
>>> how does that help me here and now?
>>>
>>> 1. Meaningful error message - how can I proceed without them, needle in
>>> a hay stack
>>> 2. Don't "release" dev tools that are clearly BETA
>>> 3. Firing VS 2005 team members doesn't help me here and now
>>>
>>>
>>>
>>
>>
>
>


Phil Wilson

7/6/2006 3:35:00 PM

0

It won't matter what tool you buiild an MSI file with if something has
broken the InstallUtilLib internals. However you don't need InstallUtilLib
to install services, and tools from InstallShield, Wise, Wix etc let you
install services using the standard MSI Service table instead of using
InstallUtilLib. All I can do is point out that managed custom actions can be
fragile, and if you're willing to use another tool to do things like install
services, and write custom actions that call a C++ Dll you can completely
avoid the fragility of calling managed custom actions.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.ht...

"Rob R. Ainscough" <robains@pacbell.net> wrote in message
news:u3JwONHoGHA.1248@TK2MSFTNGP05.phx.gbl...
> Hi Phil,
>
> The clue that lead me to think there was more wrong with .NET framework
> installation was when I tried to uninstall another .NET 2.0 project that
> had installed just fine a few days ago -- my attempt to remove via Control
> Panel resulted in the same InstallUtilLib.dll error. The only activity
> that happened between these states was the uninstall and re-install of
> .NET 1.1. This seems to have created some problems for .NET 2.0 installer.
> Fragile is very true. However, I've looked into other tools such as
> InstallShield and have found that many folks are experiencing the same or
> similiar problems with InstallUtilLib.dll for their .NET 2.0 projects
> being distributed via the InstallShield projects.
>
> I'm not a dedicated "Installation Developer" -- I'm really the ONLY
> developer that works on ALL our .NET projects (web, click once, windows
> services, windows forms, etc.).
>
> I've built many MSI setups before.
>
>
>
> "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
> news:uQTLltFoGHA.4432@TK2MSFTNGP05.phx.gbl...
>> For some reason that I am unaware of, Visual Studio decided to install
>> services in a rather convoluted way. There's a call from the msiexec
>> process to InstallUtilLib.dll passing a bunch of parameters, and then
>> calls on .NET Installer classes that locate your assembly, find its
>> Installer classes, instantiate them, call methods that install the
>> service etc. As you can probably imagine, this is rather complicated and
>> sometimes fragile. However Windows Installer has bult-in support for
>> installing services (the ServiceInstall and ServiceControl tables) that
>> people used for years before .NET came along, so why Visual Studio
>> invented installer classes to install services is a mystery to me.
>>
>> Many installation developers who have been building setups for a while
>> consider managed custom actions a bad thing:
>>
>> http://www.installsite.org/pages/en/msifaq/...
>>
>> I wonder if this is the first time you've built an MSI-based setup. There
>> seem to be a lot of Visual Studio developers doing this since VS
>> setup&deployment projects came along and, although the lack of
>> InstallUtilLib diagnostics is a pain, it's not the only (and probably not
>> even the best) tool for building MSI-based setups.
>> http://www.installsite.org/pages/en/msi/aut...
>> --
>> Phil Wilson [MVP Windows Installer]
>> ----
>> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
>> news:%23LMpEi%23nGHA.2264@TK2MSFTNGP04.phx.gbl...
>>>I found a solution, but I have not found the reason for the problem.
>>>
>>> I uninstalled .NET framework 2.0 on the client PC (my test PC) and let
>>> my installer re-install it, this has cured the current issue on my test
>>> machine. Why did this happen and how did this happen I will probably
>>> never know -- the error message provided by the Install (MSIEXEC) is
>>> pathetic at best. I'm going to do more testing because I'd like to
>>> duplicate this problem since I've already raised a bug on M$ feedback.
>>> I know M$ don't give a rats ass, but I hope that this might help others
>>> that have struggled with this turd of a development platform called VS
>>> 2005.
>>>
>>> Rob.
>>>
>>> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
>>> news:O1s6xw4nGHA.3700@TK2MSFTNGP03.phx.gbl...
>>>> I'm yet another developer with the useless Installation error message,
>>>> event viewer is just as useless MsiInstaller error 1001 and shows
>>>> InstallUtilLib.DLL: Unknown Error, (NULL), (NULL), (NULL) -- oh that is
>>>> so helpful M$, how could I not know what this means...(yes, google
>>>> searches has not reveal any solutions, I've tried them all).
>>>>
>>>> Trying to install a Windows Service using VS 2005, it will NOT install
>>>> on any client PC, but will install and work just fine on my development
>>>> PC (using either the Setup.EXE from Release dir or via the VS IDE right
>>>> click Install from the setup project.
>>>>
>>>> Soon to be ex-developer because my company is about to go under because
>>>> we fell for the VS 2005 development platform as being ready for prime
>>>> time -- hope this makes M$ developers, project managers, and QA folks
>>>> for Windows Installer and VS 2005 feel good -- I guess they have less
>>>> competition now -- well ya got my $7500 over the past 3 years waiting
>>>> for VS 2003 successor -- are you happy?
>>>>
>>>> WTF is going on with M$? I'm just over it, every freakin' day I'm
>>>> wasting hours research problems with VS 2005. Any time I try to put a
>>>> "professional" complete package together with VS 2005, it just doesn't
>>>> work. I realize that some key people from the VS 2005 dev team were
>>>> terminated (yes every developer does need some "inside" contacts), but
>>>> how does that help me here and now?
>>>>
>>>> 1. Meaningful error message - how can I proceed without them, needle
>>>> in a hay stack
>>>> 2. Don't "release" dev tools that are clearly BETA
>>>> 3. Firing VS 2005 team members doesn't help me here and now
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


Rob R. Ainscough

7/6/2006 5:32:00 PM

0

Understand Phil, but I'm trying to stay within the context of VS 2005 and
get things done the VS 2005 way (and I'm staying 100% managed). The concept
is good, just the implementation is bad, in some cases really bad. That
aside, poor error messages that provide no insight is a significant problem
with VS 2005, MSI, or just about anything under the M$ umbrella. NULL NULL
NULL -- at the very least they could provide the parameter list or what was
expected or some clues, NULL can be a clue, but by itself in this context it
is completely useless.

I've coded several Windows Services now, and my best diagnostics for when
problems occur is my extra effort I've put into trapping errors --
especially with multi-threaded processing, sometimes the only way to
identify a problem is proper error handling. M$ apparently teach this
concept put do not implement it which should concern anyone developing on an
M$ platform -- "just enough to meet a deadline" isn't a professional
approach and certainly not what I would expect from M$.


"Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message
news:%23MUn0FRoGHA.3348@TK2MSFTNGP03.phx.gbl...
> It won't matter what tool you buiild an MSI file with if something has
> broken the InstallUtilLib internals. However you don't need InstallUtilLib
> to install services, and tools from InstallShield, Wise, Wix etc let you
> install services using the standard MSI Service table instead of using
> InstallUtilLib. All I can do is point out that managed custom actions can
> be fragile, and if you're willing to use another tool to do things like
> install services, and write custom actions that call a C++ Dll you can
> completely avoid the fragility of calling managed custom actions.
> --
> Phil Wilson
> [Microsoft MVP-Windows Installer]
> Definitive Guide to Windows Installer
> http://apress.com/book/bookDisplay.ht...
>
> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
> news:u3JwONHoGHA.1248@TK2MSFTNGP05.phx.gbl...
>> Hi Phil,
>>
>> The clue that lead me to think there was more wrong with .NET framework
>> installation was when I tried to uninstall another .NET 2.0 project that
>> had installed just fine a few days ago -- my attempt to remove via
>> Control Panel resulted in the same InstallUtilLib.dll error. The only
>> activity that happened between these states was the uninstall and
>> re-install of .NET 1.1. This seems to have created some problems for .NET
>> 2.0 installer. Fragile is very true. However, I've looked into other
>> tools such as InstallShield and have found that many folks are
>> experiencing the same or similiar problems with InstallUtilLib.dll for
>> their .NET 2.0 projects being distributed via the InstallShield projects.
>>
>> I'm not a dedicated "Installation Developer" -- I'm really the ONLY
>> developer that works on ALL our .NET projects (web, click once, windows
>> services, windows forms, etc.).
>>
>> I've built many MSI setups before.
>>
>>
>>
>> "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
>> news:uQTLltFoGHA.4432@TK2MSFTNGP05.phx.gbl...
>>> For some reason that I am unaware of, Visual Studio decided to install
>>> services in a rather convoluted way. There's a call from the msiexec
>>> process to InstallUtilLib.dll passing a bunch of parameters, and then
>>> calls on .NET Installer classes that locate your assembly, find its
>>> Installer classes, instantiate them, call methods that install the
>>> service etc. As you can probably imagine, this is rather complicated and
>>> sometimes fragile. However Windows Installer has bult-in support for
>>> installing services (the ServiceInstall and ServiceControl tables) that
>>> people used for years before .NET came along, so why Visual Studio
>>> invented installer classes to install services is a mystery to me.
>>>
>>> Many installation developers who have been building setups for a while
>>> consider managed custom actions a bad thing:
>>>
>>> http://www.installsite.org/pages/en/msifaq/...
>>>
>>> I wonder if this is the first time you've built an MSI-based setup.
>>> There seem to be a lot of Visual Studio developers doing this since VS
>>> setup&deployment projects came along and, although the lack of
>>> InstallUtilLib diagnostics is a pain, it's not the only (and probably
>>> not even the best) tool for building MSI-based setups.
>>> http://www.installsite.org/pages/en/msi/aut...
>>> --
>>> Phil Wilson [MVP Windows Installer]
>>> ----
>>> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
>>> news:%23LMpEi%23nGHA.2264@TK2MSFTNGP04.phx.gbl...
>>>>I found a solution, but I have not found the reason for the problem.
>>>>
>>>> I uninstalled .NET framework 2.0 on the client PC (my test PC) and let
>>>> my installer re-install it, this has cured the current issue on my test
>>>> machine. Why did this happen and how did this happen I will probably
>>>> never know -- the error message provided by the Install (MSIEXEC) is
>>>> pathetic at best. I'm going to do more testing because I'd like to
>>>> duplicate this problem since I've already raised a bug on M$ feedback.
>>>> I know M$ don't give a rats ass, but I hope that this might help others
>>>> that have struggled with this turd of a development platform called VS
>>>> 2005.
>>>>
>>>> Rob.
>>>>
>>>> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
>>>> news:O1s6xw4nGHA.3700@TK2MSFTNGP03.phx.gbl...
>>>>> I'm yet another developer with the useless Installation error message,
>>>>> event viewer is just as useless MsiInstaller error 1001 and shows
>>>>> InstallUtilLib.DLL: Unknown Error, (NULL), (NULL), (NULL) -- oh that
>>>>> is so helpful M$, how could I not know what this means...(yes, google
>>>>> searches has not reveal any solutions, I've tried them all).
>>>>>
>>>>> Trying to install a Windows Service using VS 2005, it will NOT install
>>>>> on any client PC, but will install and work just fine on my
>>>>> development PC (using either the Setup.EXE from Release dir or via the
>>>>> VS IDE right click Install from the setup project.
>>>>>
>>>>> Soon to be ex-developer because my company is about to go under
>>>>> because we fell for the VS 2005 development platform as being ready
>>>>> for prime time -- hope this makes M$ developers, project managers,
>>>>> and QA folks for Windows Installer and VS 2005 feel good -- I guess
>>>>> they have less competition now -- well ya got my $7500 over the past
>>>>> 3 years waiting for VS 2003 successor -- are you happy?
>>>>>
>>>>> WTF is going on with M$? I'm just over it, every freakin' day I'm
>>>>> wasting hours research problems with VS 2005. Any time I try to put a
>>>>> "professional" complete package together with VS 2005, it just doesn't
>>>>> work. I realize that some key people from the VS 2005 dev team were
>>>>> terminated (yes every developer does need some "inside" contacts), but
>>>>> how does that help me here and now?
>>>>>
>>>>> 1. Meaningful error message - how can I proceed without them, needle
>>>>> in a hay stack
>>>>> 2. Don't "release" dev tools that are clearly BETA
>>>>> 3. Firing VS 2005 team members doesn't help me here and now
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


rivo2162

10/16/2006 4:02:00 PM

0

I got this message "installutillib.dll: unknown error" when I tried to install this software "ID Vault" into my system. Can someone tell me what is wrong here? Thanks in advance.
---
Posted via DotNetSlackers.com