Solved

Problem registering ocx files with Installshield 2008 express

Posted on 2010-08-31
19
1,303 Views
Last Modified: 2013-11-14
I've was using Installshield 20008 express with Vista for quite some time without any problems, the package would install successfully on the target machine under XP, Vista and Win7.

I have since purchased a new laptop with windows 7 to develop on.

I am now having issues using IS2008 Express and the same IS project as I used on Vista where it won't register ocx files on the target machine when they install. The install runs smoothly, but as soon as the user attempts to run the app - ocx not registered or outdated message.

The user can then manually register the ocx files using regsvr32.

Is there something in IS2008 Express that I have to change to be able to compile IS projects successfully under win7 ? There are no errors or warnings when compiling the projects.

The registration option for all ocx files are set to 'Extract COM Information' same as they were when running under Vista. I did try changing all these to Self-Register which seemed to do the trick for a select few ocx files, but others will still not register.  

I'm at a loss as to why this problem would start to occur with target machine installs when the only thing that has changed was going from Vista to Win7 on the development machine.

Attached are three install logs, one for when the files are set to 'Extract COM information', one when they are set to 'Self-Register' and another log for a prior install compiled on the old vista machine that was successully installed on all target machines.

I've looked over these files and can't really see anything wrong, although I'm not to familiar with install logs so could easily have missed something.

Any help would be much appreciated !
Log-Files.zip
0
Comment
Question by:peters4286
19 Comments
 

Expert Comment

by:StevenRichardson
ID: 33573033
After briefly read your issue, and not being particulary clued up on this sort of stuff my suggestions;
On windows 7 I've noticed one of the big changes is permissions to users.
When installing the program are you running as administrator?
When running the program the first time, you may also need to run it as administrator?
0
 

Author Comment

by:peters4286
ID: 33573192
Just to clarify -

The package installed perfectly on XP, Vista and Win7.

I updated my development machine that I create the install with using Installshield 2008 express from Vista to Win7, and created a new compile of the package using the same saved Installshield project.

The created package now doesn't register the ocx files when installing on Win7 machines.
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 33607943
suggestions:
1. Run ICE validation on the package., and take care of the warnings, if any.
2. make a note of some piece of the registration that is created when you manually run regsvr32 (some specific value in the registry), and after the installation try to find that piece in the log, and in the registry, so you will know if Installer is even trying to create it, and if it does, then where.

<rant>Most likely this is the result of another ton of UAC-related complications made in Windows 7, in addition to Vista, which, imho, safely put that area out of comprehension, and make the results practically unpredictable - all to supposedly protect the users from something.</rant>
0
 

Author Comment

by:peters4286
ID: 33614177
Thanks Vadim, I will try those steps.

What I really don't understand is why this is now happening when all that has changed is the machine I compile the installshield project on.  It used to be Vista and is now Win 7.  The actual project and its files haven't changed, nor have the target machines that I am installing on.
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 33614733
See <rant> above. Up to Vista, permissions were fairly straightforward - you define what is allowed to each user, and it works. UAC added second level, so admin already was not quite admin until he confirmed that he is admin, and any user could become an admin upon confirmation. Then Windows 7 further complicated all this. In Installer all these issues find their culmination. Even before Vista, installation was being run by machine service, and it impersonated the user when necessary, which created a whole number of scenarios. Installer was fairly well doing all that, not without some bugs, but tolerable (note that besides the simple installation, there are many other scenarios: advertising, managed installation assigned or published by. But then the number of scenarios was multiplied by UAC, and then further by Win7, so by now, I guess, the number of people who can coherently predict the outcome of UAC-complicated installation is very limited.
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 33614746
(the above comment is result or hitting "enter" key prematurely)

See <rant> above. Up to Vista, permissions were fairly straightforward - you define what is allowed to each user, and it works. UAC added second level, so admin already was not quite admin until he confirmed that he is admin, and any user could become an admin upon confirmation. Then Windows 7 further complicated all this. In Installer all these issues find their culmination. Even before Vista, installation was being run by machine service, and it impersonated the user when necessary, which created a whole number of scenarios. Installer was fairly well doing all that, not without some bugs, but tolerable (note that besides the simple installation, there are many other scenarios: advertising, managed installation assigned or published by group policy, terminal session, and more; each can be per machine or per user). But then the number of scenarios was multiplied by UAC, and then further by Win7, so by now, I guess, the number of people who can coherently predict the outcome of UAC-complicated installation is very limited. Remarkably, despite all these gargantuan efforts, supposedly aimed at protecting the user, I haven't heard that the number of viruses or hackers underwent any noticeable change.

So in a nutshell, what did work before does not work now because now it's better protected.
0
 

Author Comment

by:peters4286
ID: 33624219
Thanks again Vadim,

I think your missing the main issue about the development machine that creates the installation file with installshield being the one that has changed OS.

The machines that the compiled package installs onto was working perfectly whether they were XP, Vista or Win7.

Since updating the "development" machine to win 7 and compiling the installation project again - those target machines that the package installs onto whether XP, Vista or Win7, now have the problem of not registering the components.

The log files attached to my first post are both from installing onto win7 machines, the successfull one using an install created with a vista machine, the unsuccessfull one was using the same installshield project to create the install but from a win7 machine.
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 33628634
Not quite missing - the term "unpredictable" covers it all :-)

The right approach I guess is to compare the installation built under win7 vs. installation built under vista or xp. Something must be different. Also compare the log files.

But both installations must be made from the same project. From what I see in the logs you uploaded, it does not seem to be the case: starting from "ProcessComponents. Updating component registration", the product code appears to be different (the guid after 1: in each line), also file SYNCOR11.DLL is absent in "prior success" but present in "extract com"... so , are you really sure it was the same source you built both from?
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 33628675
typo: in fact syncor11.dll is present in "prior success" but absent in "extract com".
0
 

Author Comment

by:peters4286
ID: 33632466
Thanks again for your help vadim.

As I said I really don't know what I'm looking for in the logs, which is why I uploaded them hoping an expert could help me out :)

The product code is changed each build so the installation overwrites previous versions which is what I want.  As for SYNCOR11.DLL, I must have accidentally added that at some stage (Its a soundmax driver dll, which has nothing to do with my app) and once I saw it I removed it.  

But I assure you the installs were built using the same project.

The deadline for a resolution to this issue is fast approaching, and I am considering purchasing Installshield 2011 express and creating a new installation using that.  Do you think that would solve my problem ?  Also do you have any other suggestions for better install packages ?
0
 

Author Comment

by:peters4286
ID: 33632533
update: I downloaded and installed Installshield 2011 premier trial, and had the same issue using my existing 2008 express project.

So there has to be something in the project that is causing this.  I will try making a new project with 2011 trial and see how I go
0
 
LVL 40

Assisted Solution

by:Vadim Rapp
Vadim Rapp earned 500 total points
ID: 33632625
>  I will try making a new project with 2011 trial and see how I go

yes, this is probably the best thing to do. It looks like this project underwent quite a few of changes and developed some deeply entrenched conflict. Most likely fresh new one will work.

If it does not:

Let's make assumption that source of the problem is not in the win7 as o/s for the development machine, but in something else - most likely some other changes you made in the installation. So let's forget about comparing the logs and concentrate on "extract com". So, (1) which specific dll fails to register? (2) how do you know it fails to register? specifically, what registry entries are missing after the installation that are created by running regsvr32.exe ?

> the deadline for a resolution to this issue is fast approaching,

If in the end you can't resolve it, I can take a look at your project and see if I can fix it.
0
 

Author Comment

by:peters4286
ID: 33632747
Also anothe thing I have just been made aware of - to get the installation to work, a tester ran command prompt as administrator (win7) and manuall registered all of the ocx files using regsvr32.

The program then ran successfully.

This doesnt explain why the install still fails under XP though !
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 33632764
I bet if you run ice validation, you will find things to fix.
0
 

Accepted Solution

by:
peters4286 earned 0 total points
ID: 34688647
Couldn't spend any longer on the issue so I ended up purchasing Installshield 2011 and re-created installation.  Working !
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 34689006
ID:33632625:
vadimrapp1: It looks like this project underwent quite a few of changes and developed some deeply entrenched conflict. Most likely fresh new one will work.
(after trial of non-express on the same project already failed, according to the previous author's comment)

ID:34688647
Author: I ended up purchasing Installshield 2011 and re-created installation.  Working !


Conclusion: accept http:#33632625
0
 

Expert Comment

by:_alias99
ID: 34811331
All,
 
Following an 'Objection' by vadimrapp1 (at http://www.experts-exchange.com/Q_26767938.html) to the intended closure of this question, it has been reviewed by at least one Moderator and is being closed as recommended by accepting the Author's answer and awarding full points to an Expert comment as an 'assisted answer'.
 
Thank you,
 
_alias99
Community Support Moderator
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Among others, I monitor the Windows Installer zone and Installer zone. I find that many of the questions could be answered much more quickly if a Windows Installer verbose log were submitted with the question.   However, I do not always have t…
I have been scripting applications way too long and can never remember how to create an ISS file.  So I decided to write this article to act as my own knowledge base for future reference, and hope you will also benefit. An ISS file is a response …
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now