Prev: Strange VB6 IDE crash
Next: Directory Comments
From: Steve on 14 May 2010 13:57
This might not be the correct place to ask this question as it really
is not VB specific (at least I do not think it is) but you guys here
have always been able to help me out either directly or by pointing me
to a more appropriate group...so here is the issue.

I have a large VB6 app here at the company I work for. This app uses
many COM+ components (some VB some .NET). To install these COM+
components on client machines we have simply exported the COM+
application to an MSI package. This was done several years ago and
has worked flawlessly since. Well they recently started upgrading the
machines to Windows 7 Professional. On virtually every (but not in
fact every one) machine one or more of the proxies will fail during
install. Which one fails seems to be random but the error returned is
always the same..."Error registering COM+ Application. Contact your
support personnel for more information.". In researching this problem
I found a M$ article (308940) that indicates the problem is either a
missing dependency or a permissions issue. I am fairly certain that
it is not a permissions issue as I am logged onto the machine as
Administrator when I run the MSIs. Also the fact that it works for
some and not for others on a particular machine also leads me to
believe that permissions are not the issue. That leaves me with
dependencies. The problem is I have no idea what may be missing.
Again the fact that any particular MSI may install on one box but not
another (ostensibly identical) box is very perplexing to me. Further
the entire thing including all of the MSI has never failed to install
on an XP box.

Can anybody help me...I realize that I haven't given much information
but it is all I have. I have never had to debug install problems and
do not even know where to begin to get any more information.

Thanks,
Steve
From: Paul Clement on 14 May 2010 14:16
On Fri, 14 May 2010 10:57:04 -0700 (PDT), Steve <sredmyer(a)rfcorp.com> wrote:

� This might not be the correct place to ask this question as it really
� is not VB specific (at least I do not think it is) but you guys here
� have always been able to help me out either directly or by pointing me
� to a more appropriate group...so here is the issue.
�
� I have a large VB6 app here at the company I work for. This app uses
� many COM+ components (some VB some .NET). To install these COM+
� components on client machines we have simply exported the COM+
� application to an MSI package. This was done several years ago and
� has worked flawlessly since. Well they recently started upgrading the
� machines to Windows 7 Professional. On virtually every (but not in
� fact every one) machine one or more of the proxies will fail during
� install. Which one fails seems to be random but the error returned is
� always the same..."Error registering COM+ Application. Contact your
� support personnel for more information.". In researching this problem
� I found a M$ article (308940) that indicates the problem is either a
� missing dependency or a permissions issue. I am fairly certain that
� it is not a permissions issue as I am logged onto the machine as
� Administrator when I run the MSIs. Also the fact that it works for
� some and not for others on a particular machine also leads me to
� believe that permissions are not the issue. That leaves me with
� dependencies. The problem is I have no idea what may be missing.
� Again the fact that any particular MSI may install on one box but not
� another (ostensibly identical) box is very perplexing to me. Further
� the entire thing including all of the MSI has never failed to install
� on an XP box.
�
� Can anybody help me...I realize that I haven't given much information
� but it is all I have. I have never had to debug install problems and
� do not even know where to begin to get any more information.
�
� Thanks,
� Steve

See if the following helps:

http://social.technet.microsoft.com/Forums/en/w7itproappcompat/thread/a2fc9171-4c0c-40d3-8b6f-1c5fd74a10ce

In addition, you may be logged on as an Admin but you should still be selecting the Run As an
Administrator option in order to elevate privileges.


Paul
~~~~
Microsoft MVP (Visual Basic)
 | 
Pages: 1
Prev: Strange VB6 IDE crash
Next: Directory Comments