Running VB6 App causes MS Office Install 
Author Message
 Running VB6 App causes MS Office Install

I have a VB6 application that I am supporting that has references to MS Word
& MS Excel.  Recently, users are complaining that each time they try to run
the application, a dialogue appears attempting to to install MS Office.  This
fails as they users do not have necessary permissions to install software.

Could someone give me some advice on best way to solve this problem

tia



Fri, 18 Feb 2011 22:35:00 GMT  
 Running VB6 App causes MS Office Install


Quote:
> I have a VB6 application that I am supporting that has references to MS
Word
> & MS Excel.  Recently, users are complaining that each time they try to
run
> the application, a dialogue appears attempting to to install MS Office.
This
> fails as they users do not have necessary permissions to install software.

> Could someone give me some advice on best way to solve this problem

> tia

The normal soluction is to switch the computer to admin, allow the install
to occur and then switch back to normal user.


Fri, 18 Feb 2011 23:08:00 GMT  
 Running VB6 App causes MS Office Install

Quote:
> The normal soluction is to switch the computer to admin, allow the install
> to occur and then switch back to normal user.

If it were only one machine then this would be fine.  unfortunately this is
going to happen on 50 machines.  Is their a way to manage this for multiple
machines?

Also, why is this happening?  Im guesing that the office install must have
changed in someway (my app has not changed).  Is there anything I can do in
my vb app that would avoid this problem - The app does need to use Word &
Excel



Fri, 18 Feb 2011 23:27:00 GMT  
 Running VB6 App causes MS Office Install
Hi Terry,

Are you using a msi installer, and/or distributing any office or shared dlls
?  If the dlls are part of office and you require office best not to
distribute them.  I'd hazard a guess office installer is detecting a
modified entry for shared components.


Quote:
>> The normal soluction is to switch the computer to admin, allow the
>> install
>> to occur and then switch back to normal user.

> If it were only one machine then this would be fine.  unfortunately this
> is
> going to happen on 50 machines.  Is their a way to manage this for
> multiple
> machines?

> Also, why is this happening?  Im guesing that the office install must have
> changed in someway (my app has not changed).  Is there anything I can do
> in
> my vb app that would avoid this problem - The app does need to use Word &
> Excel



Fri, 18 Feb 2011 23:45:59 GMT  
 Running VB6 App causes MS Office Install


Quote:
>> The normal soluction is to switch the computer to admin, allow the
>> install
>> to occur and then switch back to normal user.

> If it were only one machine then this would be fine.  unfortunately this
> is
> going to happen on 50 machines.  Is their a way to manage this for
> multiple
> machines?

> Also, why is this happening?  Im guesing that the office install must have
> changed in someway (my app has not changed).  Is there anything I can do
> in
> my vb app that would avoid this problem - The app does need to use Word &
> Excel

Common problem.  For whatever reason (usually involves shared components),
Office "thinks" its installation is broken..and perhaps it is.  Perhaps you
installed a shared component that is older than included with Office.
Anyway, Office is merely trying to fix the problem.  The only way to really
get rid of it is to let Office do what it wants.  You might want to take a
closer look at your installation.  You say your app references both Word and
Excel.  You're not including the type libraries in your installation, are
you? If so, that'd almost definitely cause Word/Excel to "fix" things.

--
Mike
Microsoft MVP Visual Basic



Sat, 19 Feb 2011 01:48:05 GMT  
 Running VB6 App causes MS Office Install

Quote:

>> The normal soluction is to switch the computer to admin, allow the
>> install to occur and then switch back to normal user.

> If it were only one machine then this would be fine.  unfortunately
> this is going to happen on 50 machines.  Is their a way to manage
> this for multiple machines?

It should be done at the time your app is installed, which presumably also
requires Admin permission. Install your app, then run Word and Excel to allow
them to update, before returning the machine to the user.

It is not you, it is the Microsoft way. I have no idea why they made their
Office install work that way (esp 2003), but they did.



Sat, 19 Feb 2011 02:33:22 GMT  
 Running VB6 App causes MS Office Install


Quote:
> I have a VB6 application that I am supporting that has references to MS
Word
> & MS Excel.  Recently, users are complaining that each time they try to
run
> the application, a dialogue appears attempting to to install MS Office.
This
> fails as they users do not have necessary permissions to install software.

> Could someone give me some advice on best way to solve this problem

> tia

"Well the best way to solve the problem" depends on your domain and how much
pull you have with system admin. <g>

[Note: what follows is a general over-view. Details will vary depending on
your version/s of Office, and how it is configured - running from the net,
local copy, etc.]

There are many things that might cause this problem, but in your case it is
almost certainly caused by the difference in Accounts. Most Office products
have to be installed twice. One time by the Admin and a second by the User.
The latter is mostly to setup 'StartUp' folders and Registry entries for
that User.

This can been done during the intial install. For example, if you usually
install by an Admin going to each machine after the Admin finishes he could
have the User login and finish the install. This can also be done with Admin
scripts.

But since this wasn't done, going back and repairing it will take a little
time. Suggestion pick one User box and throughly investigation the problem
for that machine. By first showing the error - take a snapshot of the
Registry and Folders, then install Office using the User account. For clues
of what you are looking for take a look at the following article. While not
dealing exactly with your situation, it provides good information for what
is going on.

You might try the Office Cleanup utility. This is useful for getting every
machine on the same page.
"Description of the Windows Installer CleanUp Utility"
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

If you identify the exact missing Registry Entries, which can usually be
done with a little investigation (unfortunately only after you learn what
you are looking for <g>), you can create a simple reg file and modify the
boxes. Sometimes all that is needed is to insure each Users has the
necessary folders on their machine. Content doesn't matter.
Example: Create an empty folder: "C:\Program Files\Microsoft
Office\OFFICExx\XLSTART"
This often shuts up Excel complaints...
Sometimes just running Office Apps on the Box will install the missing
folders or Registrations - again depends on versions and User permissions.

How to configure Office applications to run under a specific user account
http://support.microsoft.com/kb/288367

Once you have repaired the problem. Especially if you had to visit all 50
boxes, get with your Admin ppl and work out the correct way to manage Office
installs for multiple users in the future so this doesn't happen again. The
Admin might even consider doing a complete remote reinstall of Office taking
User accounts in to account to help you out. <g>

[Don't forget to test MSAccess, or any other office product you are
automating while you're at it, or you may have to revist the boxes again.
Ha.]

-ralph



Sat, 19 Feb 2011 03:21:07 GMT  
 Running VB6 App causes MS Office Install


Wanted to add:

If you give us a simple description of how YOUR Office is configured, what
version, user's permissions, and how YOUR shop goes about installing
applications, ... . We may hopefully be able to provide a more exact and
simple method for fixing YOUR current problem.

-ralph



Sat, 19 Feb 2011 03:40:17 GMT  
 Running VB6 App causes MS Office Install


Quote:

> For clues
> of what you are looking for take a look at the following article. While
not
> dealing exactly with your situation, it provides good information for what
> is going on.

I included the URL at the bottom:
Quote:

> How to configure Office applications to run under a specific user account
> http://support.microsoft.com/kb/288367



Sat, 19 Feb 2011 04:37:46 GMT  
 Running VB6 App causes MS Office Install
Thanks for all replies.  I am out of office for a couple of days and will
check out some of your suggestions when I return.  My guess is that the
install package does include some office type libraries
Quote:

> I have a VB6 application that I am supporting that has references to MS Word
> & MS Excel.  Recently, users are complaining that each time they try to run
> the application, a dialogue appears attempting to to install MS Office.  This
> fails as they users do not have necessary permissions to install software.

> Could someone give me some advice on best way to solve this problem

> tia



Sat, 19 Feb 2011 04:44:01 GMT  
 Running VB6 App causes MS Office Install


Quote:
> Thanks for all replies.  I am out of office for a couple of days and will
> check out some of your suggestions when I return.  My guess is that the
> install package does include some office type libraries

If you mean Office "Type Libraries", Type Libraries should never be a part
of any install package. (Unless you are installing a developer utility).

If you mean "Office-type" libraries, then again there should be no reason to
include these as part of a package. And yes this could cause problems.

Your original post suggested that you were using automation and only
recently have some users been reporting problems. This to me implied that
the original install worked without problems and users were able to use the
application after install - in that case the problem is with User Accounts
not components.

-ralph



Sat, 19 Feb 2011 06:18:33 GMT  
 Running VB6 App causes MS Office Install

Quote:

>I have a VB6 application that I am supporting that has references to MS
>Word
> & MS Excel.  Recently, users are complaining that each time they try to
> run
> the application, a dialogue appears attempting to to install MS Office.
> This
> fails as they users do not have necessary permissions to install software.
> Could someone give me some advice on best way to solve this problem

Office will do this if you use a component that is part of a section of
office that was not installed. It is msi behavior or more commonly known as
"Install on First Use". When you use this component the Windows installer
will attempt to install that part of office that uses that component. It is
rather annoying but that the way M$ made it... The only way to do something
about this is to eithe install that part of office or disable the part of
the Windows Installer (registry entry) that makes this happen.

--
Randem Systems, Inc.
Your Installation Specialist
Makers of InnoScript for Inno Setup.
It creates the script for you from a vbp, vbg, vbproj or setup.lst file.
http://www.innoscript.com/innoscript.html
http://www.randem.com/installerproblems.html


Quote:
>I have a VB6 application that I am supporting that has references to MS
>Word
> & MS Excel.  Recently, users are complaining that each time they try to
> run
> the application, a dialogue appears attempting to to install MS Office.
> This
> fails as they users do not have necessary permissions to install software.

> Could someone give me some advice on best way to solve this problem

> tia



Sat, 19 Feb 2011 11:06:41 GMT  
 Running VB6 App causes MS Office Install
Here is the contect of my Setup.lst file.  Are you able to identify any files
that would cause this behaviour?

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=Tranzacct280.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]


AM,22288,4.71.1460.1

AM,17920,2.40.4275.1

AM,147728,2.40.4275.1

AM,164112,5.0.4275.1

AM,598288,2.40.4275.1

AM,1386496,6.0.97.82

[IconGroups]
Group0=Tranzacct
PrivateGroup0=-1
Parent0=$(Programs)

[Tranzacct]
Icon1="Tranzacct280.exe"
Title1=Tranzacct
StartIn1=$(AppPath)

[Setup]
Title=Tranzacct
DefaultDir=$(ProgramFiles)\Tranzacct
AppExe=Tranzacct280.exe
AppToUninstall=Tranzacct280.exe

[Setup1 Files]


1:00:00 AM,119808,6.1.97.82

AM,131856,6.1.97.82

6:43:19 PM,166600,6.0.84.18

1:00:00 AM,137000,6.0.81.69

1:00:00 AM,609824,6.0.81.5

1:00:00 AM,662288,6.1.97.82

1:00:00 AM,1081616,6.1.97.82

1:00:00 AM,260880,6.1.97.82

1:00:00 AM,152848,6.1.97.82

9:25:50 PM,1321744,6.0.3890.0

2:36:36 AM,92160,3.0.1325.0

2:36:36 AM,91648,3.0.1325.0

2:36:42 AM,437760,3.0.1325.0

6:00:00 AM,235520,1.2.814.0


AM,241693,4.0.8618.0

AM,552989,4.0.8015.0

AM,315423,4.0.6508.0

AM,421919,4.0.7328.0

AM,831519,4.0.6508.0

AM,614429,4.0.8905.0



AM,151583,4.0.8905.0


AM,1507356,4.0.8618.0

AM,561179,3.60.8618.0

11:15:20 AM,1704,0.0.0.0


1:00:00 AM,397824,6.1.97.82

; The following lines may be deleted in order to obtain extra
; space for customizing this file on a full installation diskette.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX



Sat, 19 Feb 2011 16:32:13 GMT  
 Running VB6 App causes MS Office Install
Mike

could I ask you to have a look at my reply to Ralph.  Do you see any files
in my Setup.lst  that would cause this behaviour.

Also, it there a was to retrospectively break the link between my installed
app and any changes to office shared components?



Sat, 19 Feb 2011 16:35:06 GMT  
 Running VB6 App causes MS Office Install


Quote:
> Here is the contect of my Setup.lst file.  Are you able to identify any
files
> that would cause this behaviour?

Still need to know the version of Office you are using and the target/s
platform for your install.

Comments following mild editing...

Remove the following ...


(Can't remember if these are required by Setup or not. But you will find out
quickly enough - if you remove anything required, P&D will immediately
squawk.)

































(Never include a type library with an install.)


You need the executable, of course

I believe I correctly identified the MS files, however, if you are including
any Dlls with a similar name, I may have missed one. So, obviously if any of
the above are your own Dlls, then they must be included.

Most of these files are Office components, Ole 'system' files, Data Access
libraries, VB Runtime, and 3rd party and MS Controls. These items best
managed on the Platform level. Simply because each version has its own
version of these components already included or provide a separate MS
install - targeted to specific platforms.

But again we really don't know anything about YOUR problem domain. Are you
really using DAO and ADO and SOAP and special formatting in your program?

Just delete these files, perform an install on a sample target, test your
program, and report back. With specific error messages if any, and the
specific version of Office and the target platform.

-ralph



Sun, 20 Feb 2011 02:44:21 GMT  
 
 [ 15 post ] 

 Relevant Pages 

1. CAB questions: 1) run app after install 2) installed multiple apps

2. Custom ActiveX controls cause MS-Office 2000 forms to crash

3. How to determine the version of MS-Office installed on the machine

4. Problem with installing MS Office 2000 Developer V1.5

5. Problem installing new vbnet app on a computer with vb6 app

6. How can I find out what version of MS OFfice is installed

7. installing VB6 apps breaks VB? - VB5 apps

8. install vb.net cause vb6 program--error--30468!

9. installing Office 2000 kills Access 97 run-time applications

10. Runtime error 429 with VB6 pgm using DAO when Office 2000 installed

11. Problems with Ms Office VB Help app ?

12. App starts MS Office installer as Guest

 

 
Powered by phpBB® Forum Software