drmor4
asked on
The version number wont update after creating an msi single file in Installaware group policy wizard
We have been successfully able to update the version number in our application when deploying an exe file in Installaware, however we are now required to deploy an msi. We create the msi via the group policy wizard and it compiles without issue however when installed the application version number does not update.
Are we simply missing a step? Any thoughts would be greatly appreciated.
Are we simply missing a step? Any thoughts would be greatly appreciated.
ASKER
Hi, thanks for your assistance. I have attached 2 log files that i could locate.
MSIfbfe9.LOG
MSIef2cb.LOG
MSIfbfe9.LOG
MSIef2cb.LOG
OK,
It looks like you are doing this:
TheTimetablerV8.msi = runs => TheTimetablerV8.exe = which extracts and runs => TheTimetablerV8.msi
I would suggest two approaches:
1) Don't generate an MSI to run and EXE which then runs an MSI
1.a) run the EXE manually until you see the feature selection dialog.
1.b) grab the folder (entire folder) C:\Users\PAUL~1.THO\AppDat
1.c) use the MSI in that folder to schedule the GPO - make sure you replicate the folder first.
2) If you can't do #1, then DON'T use the MSI name TheTimetablerV8.msi in the Installaware Group Policy wizard as it is also the name of the embedded .MSI
I have low confidence that #2 will fix your problem
It looks like you are doing this:
TheTimetablerV8.msi = runs => TheTimetablerV8.exe = which extracts and runs => TheTimetablerV8.msi
I would suggest two approaches:
1) Don't generate an MSI to run and EXE which then runs an MSI
1.a) run the EXE manually until you see the feature selection dialog.
1.b) grab the folder (entire folder) C:\Users\PAUL~1.THO\AppDat
1.c) use the MSI in that folder to schedule the GPO - make sure you replicate the folder first.
2) If you can't do #1, then DON'T use the MSI name TheTimetablerV8.msi in the Installaware Group Policy wizard as it is also the name of the embedded .MSI
I have low confidence that #2 will fix your problem
ASKER
Hi,
Thanks for the ideas. We tried both but ran into the same issue, we were able to successfully locate the msi by following the above instructions. We copied the file to our ftp site ran the update and still the version number did not update from the previous version. Symptoms are that a command line prompt appears briefly.
The msi file is only 377 kb in size?
Any other thoughts?
Thanks for the ideas. We tried both but ran into the same issue, we were able to successfully locate the msi by following the above instructions. We copied the file to our ftp site ran the update and still the version number did not update from the previous version. Symptoms are that a command line prompt appears briefly.
The msi file is only 377 kb in size?
Any other thoughts?
You may be trying a major upgrade when you need a minor upgrade.
Do this please:
*) Open a command line
*) Change to the folder containing the msi.
*) Run "msiexec /i thetimetablerv8.msi"
If you are trying to install a minor upgrade by double clicking or with the above command line, you will receive the message that the software is already installed. If you receive that message, then use this command:
"msiexec /fvomus thetimetablerv8.msi"
Once you figure out the correct command line, add "/qn" to make it silent for production rollout.
Do this please:
*) Open a command line
*) Change to the folder containing the msi.
*) Run "msiexec /i thetimetablerv8.msi"
If you are trying to install a minor upgrade by double clicking or with the above command line, you will receive the message that the software is already installed. If you receive that message, then use this command:
"msiexec /fvomus thetimetablerv8.msi"
Once you figure out the correct command line, add "/qn" to make it silent for production rollout.
ASKER
So if we determine that the second command line is correct does the msi code in installaware need to be changed? Could you please point us to the steps that need to be taken from here?
To accomplish an upgrade, you will need to use the "Upgrades" tab of the GPO software installation object you are creating for the new version to identify the previous version package and whether you wish to upgrade over the old package or uninstall the previous version package before install.
ASKER
I added the the command: msiexec /fvomus /qn thetimetablerv8.msi into the group policy wizard command line parameters is this correct?
We currently use the web updates feature. Each time we update the software we increment the version number by 1. So currently the exe upgrades from the previous version.
I am unable to locate an upgrades tab, the other alternative is to create a patch?
We currently use the web updates feature. Each time we update the software we increment the version number by 1. So currently the exe upgrades from the previous version.
I am unable to locate an upgrades tab, the other alternative is to create a patch?
No I mean when the package is actually deployed within Group Policy software distribution in active directory.
Perhaps I am misunderstanding here. Isn't the purpose of the Installaware group policy wizard to create a .MSI to wrap a setup.exe?
But now you have the .MSI that was inside the setup.exe - so you don't even need the group policy wizard, correct?
When your customers need to run the package via group policy software distribution, they would need to use the "Upgrades" tab in Group Policy Management console.
If they are running an msiexec.exe command line - they would need to use the /fvomus command line.
Perhaps I am misunderstanding here. Isn't the purpose of the Installaware group policy wizard to create a .MSI to wrap a setup.exe?
But now you have the .MSI that was inside the setup.exe - so you don't even need the group policy wizard, correct?
When your customers need to run the package via group policy software distribution, they would need to use the "Upgrades" tab in Group Policy Management console.
If they are running an msiexec.exe command line - they would need to use the /fvomus command line.
ASKER
Previously we have used the package installshield and compiled an exe and msi file each time an update was released. These files were then made available on our website for clients to download and install. The reason we require an msi is because some of our clients have issues downloading and installing exe's.
Essentially from our point of view we want the msi to behave the same way as the exe. EG the client runs an update and the msi is downloaded and installed the same way the exe would be. We do no neccasarily need it to be deployed by group policy (the client can deploy it in this fashion if the possess the know how), we have just used the group policy wizard in installaware to package the file.
I hope this clarifies things
Essentially from our point of view we want the msi to behave the same way as the exe. EG the client runs an update and the msi is downloaded and installed the same way the exe would be. We do no neccasarily need it to be deployed by group policy (the client can deploy it in this fashion if the possess the know how), we have just used the group policy wizard in installaware to package the file.
I hope this clarifies things
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
Unfortunately we keep hitting a brick wall. We have been in contact with Installaware support and have been very unimpressed with the level of support we have recieved. Please see below the chain of emails, they are quite vague and really havent assisted us at all. They believe there should not be an issue attempting what we are doing, however havnt given us any specific instructions to assist.
We have reached as stage where we really have to get this resolved and we would potentially like to engage your services, would you be interested? My personal email is paul.t@timetabling.com.au please contact me if you are interested doing this.
Installaware support
When you unable updates, InstallAware adds a script called "update" to your project. You need to play around with the installer to tweak it to enter the update mode even though it was ran normally (by altering the MSIcode using the Include Script command for example).
Otherwise, you could also use debug assertions like writing to a text file (with the Write to Text File command).
Please let me know.
Timetabling Solutions
We can debug the installer, but only for installing which goes through fine. Can't seem to find a way to debug the Update process (eg clicking update from the program files entry)? Any suggestions?
We've tried renaming the msi update to a different name from the exe. It still fails the same way, eg finds and displays the update to download/install. Completes the download, then a flash of the command prompt and then nothing.
Installaware Support
Are you able to debug your installer? When you add the update functionality, an update script is added to your project.
Could you step through that script and see where it failes?
Timetabling Solutions
Unfortunately no error message. After clicking the Update item in the All programs list, the update dialog correctly displays indicating the version number update is available. Click Download, the green progress bar runs through and gets to the end, holds for a few seconds, then there is a flash of the command prompt dialog (which doesn't occur with the exe) then it closes. The update dialog doesn't move onto Installing. The program isn't updated. However, if you click the Update item in the All programs list again, you get the message "All updates have been installed" etc. The version date in Program files hasn't changed.
Interestingly if we uninstall our program, we can successfully install using the msi, but we encounter the same issue when attempting to apply an update.
Installaware Support
What makes you say that the download is successful? What error are you receiving exatly?
Unfortunately we keep hitting a brick wall. We have been in contact with Installaware support and have been very unimpressed with the level of support we have recieved. Please see below the chain of emails, they are quite vague and really havent assisted us at all. They believe there should not be an issue attempting what we are doing, however havnt given us any specific instructions to assist.
We have reached as stage where we really have to get this resolved and we would potentially like to engage your services, would you be interested? My personal email is paul.t@timetabling.com.au please contact me if you are interested doing this.
Installaware support
When you unable updates, InstallAware adds a script called "update" to your project. You need to play around with the installer to tweak it to enter the update mode even though it was ran normally (by altering the MSIcode using the Include Script command for example).
Otherwise, you could also use debug assertions like writing to a text file (with the Write to Text File command).
Please let me know.
Timetabling Solutions
We can debug the installer, but only for installing which goes through fine. Can't seem to find a way to debug the Update process (eg clicking update from the program files entry)? Any suggestions?
We've tried renaming the msi update to a different name from the exe. It still fails the same way, eg finds and displays the update to download/install. Completes the download, then a flash of the command prompt and then nothing.
Installaware Support
Are you able to debug your installer? When you add the update functionality, an update script is added to your project.
Could you step through that script and see where it failes?
Timetabling Solutions
Unfortunately no error message. After clicking the Update item in the All programs list, the update dialog correctly displays indicating the version number update is available. Click Download, the green progress bar runs through and gets to the end, holds for a few seconds, then there is a flash of the command prompt dialog (which doesn't occur with the exe) then it closes. The update dialog doesn't move onto Installing. The program isn't updated. However, if you click the Update item in the All programs list again, you get the message "All updates have been installed" etc. The version date in Program files hasn't changed.
Interestingly if we uninstall our program, we can successfully install using the msi, but we encounter the same issue when attempting to apply an update.
Installaware Support
What makes you say that the download is successful? What error are you receiving exatly?
Paul,
I am too busy right now to engage in any projects.
I have a follow up question. When you said "...when installed the application version number does not update..."
Do you mean:
(a) the version number visible in Add/Remove Programs
(b) the version number of one of the EXEs or DLLs
If you mean (b), could you tell me which file?
I will take another look at the log once I have this information.
D.
I am too busy right now to engage in any projects.
I have a follow up question. When you said "...when installed the application version number does not update..."
Do you mean:
(a) the version number visible in Add/Remove Programs
(b) the version number of one of the EXEs or DLLs
If you mean (b), could you tell me which file?
I will take another look at the log once I have this information.
D.
ASKER
In our software application he have a help tab with an About the software section this lists the version number and we find it has not updated from the previous version when an msi file is applied. The file version is present in the Properties | Details of the exe but not present in the msi. Other symptoms include that we cannot apply any further updates without completely uninstalling after attempting to run the msi via automatic updates.
We have also attempted to apply a patch which again installed without issue for the exe, but we encountered issues when trying for an msi.
We have also attempted to apply a patch which again installed without issue for the exe, but we encountered issues when trying for an msi.
Ok, I understand from your last post that you want to leverage the InstallAware auto-updates feature (auto-updates is not a feature of MSI) - that wasn't clear to me. I am not familiar enough with the product to know how it is supposed to work and what it's requirements are in order to have it work well over the long run - I would escalate with the original company - ask to talk to a support supervisor.
If you wish to submit a verbose log of the MSI execution, please use the attached files. Find the most recent log in %TEMP%\MSI?????.LOG and attach it to this thread for analysis.
MSI-Verbose-Logging-ON.reg
MSI-Verbose-Logging-OFF.reg