Software Deployment

Have you tried to see whether the stub allows an administrative install (as in 'setup /a')?

Yes,
We tried that, but it started installation directly. It did not take /a parameter

search for "msidata1.cab " during installation, it might be extracted somewhere and once the installation is completed it might get deleted

If we analyze setup.exe installation, we get only 1 msi extracted, but in installer folder we get 3 msi files
We tried that, but it started installation directly. It did not take /a parameter

Did you try setup.exe /a, or msiexec [Sage Serveur.msi] /a, or both?

To mekaywe: We tried that as well but we did not find it at the time of install.
To pjgeutjens: We tried both. As I said for setrup.exe it failed. But for msi which we got in c:\pogram files\installshield information, it worked. so we have admin install for 1 msi. As I said before it is not complete one.
there are some assemblies and merge modules are installing extra, and we can see 3 msi files extra in c:\windows\installer, but we are not able to make them work, as they are giving us error saying msidata1.cab missing.

did you search for MSIs in %appdata%, %temp% and app related folders ? any luck ?

In appdata we did not check. Will check and get back to you..

have admin install for 1 msi. As I said before it is not complete one.

Have you checked that 1 msi's CA's for nested MSI installs or similar actions?

no luck.

check the Uninstall string for those MSIs and check the value of registry key " InstallSource "
During the installation go to that location and you should be able to find your MSIs there

We checked nested scenario as well, but no any clue.

getting close to where I don't know how to help you further without actually getting my hands on the setup. But it looks to me like either there's something still hiding in the MSI's binary tables, OR the setup actually does a number of non-msi related operations that don't show up.

Last ditch option is to look at the small MSI's in the Windows\Installer folder (which would indeed be stripped of files), look at their product codes and do a lookup of these in the registry (HKCR\Installer). Hope there's more info in the LastUsedSource and other reg keys there.

PJ

Yes.. PJ.... that might give a fruitful solution

I am getting uninstall hives for all 4 msi applications, and I am able to trigger it's uninstallation as well. There is no any uninstallstring. For all msi's it is showing same install location.


Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A8F803B0-CFC6-4EF7-A1F1-CD4479855F26}]
"ModifyPath"="\"C:\\Program Files\\InstallShield Installation Information\\{A8F803B0-CFC6-4EF7-A1F1-CD4479855F26}\\setup.exe\" -runfromtemp -l0x040c"
"NoRepair"=dword:00000001
"UninstallString"="\"C:\\Program Files\\InstallShield Installation Information\\{A8F803B0-CFC6-4EF7-A1F1-CD4479855F26}\\setup.exe\" -runfromtemp -l0x040c -removeonly"
"LogFile"="C:\\Program Files\\InstallShield Installation Information\\{A8F803B0-CFC6-4EF7-A1F1-CD4479855F26}\\setup.ilg"
"InstallLocation"="C:\\Program Files\\ntmaes"
"ProductGuid"="{A8F803B0-CFC6-4EF7-A1F1-CD4479855F26}"
"InstallSource"="C:\\Documents and Settings\\local_administrator\\Desktop\\ntmaes\\"
"DisplayName"="Sage Serveur"
"Publisher"="Sage"
"URLInfoAbout"="http://www.sage.fr"
"HelpLink"="http://www.sage.fr"
"URLUpdateInfo"="www.sage.fr"
"DisplayIcon"="C:\\Program Files\\InstallShield Installation Information\\{A8F803B0-CFC6-4EF7-A1F1-CD4479855F26}\\cbinstuninst.ico"
"InstallDate"="20100507"
"Language"=dword:0000040c
"DisplayVersion"="16.02"
"Version"=dword:10020000
"MajorVersion"=dword:00000010
"MinorVersion"=dword:00000002
"LogMode"=dword:00000001


Throw the EXE on to something like senduit.com, if you can (there tends to be a size limit on these sites): perhaps someone else can open it and see what's what.

ORIGINAL: Packagingteam

Yes,
We tried that, but it started installation directly. It did not take /a parameter


If you're refering to the MSI's here, try /a <msi> PATH=<extraction path> /qb
I've found out that sometimes an administrative install that failed before will work afterall.

No Luck.
What can be the harm, if we capture assemblies?

Great news!!!

We got all msi files: Process as follows.
we tried to take admin image of cache copies. It threw an error message for cab file, but at the same time, it created admin image msi. (msi with admin flags). We copied that msi to another location, and tried to install that msi seprately. Now it threw an error message for files\folders. We provided all the files and folders to it, and then it started working. Now we can merge loose folders in a cab file. Which is our standard.

Thanks to everyone for their inputs.

Even we are doing the same application and facing the same problem. We tried the solution that Packagingteam has suggested at the end. But the issue is still there. Is there any other way to go about with this application?

Why not just create a response file for the installshield based setup and use that to get a silent setup?

Actually we cannot do that. It is not according to our standards.

But the issue is still there.What issue would that be?

Then try
setup.exe /extract_all:"C:\path where to extract the files"

@VBScab - The issue that Packagingteam mentioned in the first post.
@AngelD - Will try your suggestion and let you know. Thanks.

setup.exe /extract_all:"C:\path where to extract the files"
This doesnt seem to be working. The msi and files are getting extracted to "C:\Program Files\InstallShield Installation Information"

@VBScab - The issue that Packagingteam mentioned in the first post. I asked because, as far as my reading goes, the issue is resolved (post #19).

I tried the same solution. But it dint work for me.

Hi Richa,
Solution is simple.
Install your source. Obviously you will not get msi files in temp. Identify your msi files from c:\windows\installer
Copy thse msi and paste it in the c:\
now, You will have to take an admin image for these msi files.
msiexec /a c:\sage_sample.msi targetdir=c:\admin
you will get all loose files and folders, with admin image msi.

Hi PackagingTeam,

I tried the exact same solution that you had mentioned above. After taking the admin image and trying to install the msi's, i got an error saying that a file was missing. Now earlier, i had taken a capture of this setup to provide all the files. But the files shown in the error where not captured in the setup. So we couldnt provide the files. Just wanted to know how did u provide the mssing files?

Which sage package are you doing? there are so many...sage gestion, compatibilite,immobilisatin,moyens, or server client
See in such type of issues, you just have to search for that file on the machine where source is installed. Then copy that file and paste in appropriate admin image folders

It wouldn't be too hard to check the MSI and/or CAB for the file. If all else fails, you could do a dummy install and copy the file into the correct location in the AIP.

Hi Richa,
Like Ian suggest in an earlier post: Can you please upload this app to senduit?
With that, we could get a look on this beast and give you instructions how to proceed.

BTW: Never seen a setup with an MSI inside, which could not be extracted...
A solution which works all the time: Check the log files. The path to the installation source is ALWAYS in there.
Regards, Nick

Hi Richa,
just tried to download the package. It's already expired. Please reupload it.
Make it last 2 days. Do have heavy workload right now, so i can't always check for it.
Regards, Nick

Hi Richa,
i just got short look at the client only installation.
By analyzing the log files, one can see, that the "Sage Serveur.msi" is installed 3 times,
but with different product and package codes to make it possible to install 3 instances.
You can see the differences by producing transforms from the 3 installed MSI's against Serveur.msi.
One of them will trow a 2223 error, which means, there are no differences to the original.
So, you will end up with 2 Transforms.
The files, BTW are stored in an embedded CAB, you can extract it with msidb from the SDK.
Make sure, that there are no changes done outside of the MSI's.
To do so, make a check against the original with this method: http://www.appdeploy.com/messageboards/fb.asp?m=59499
Regards, Nick

The name of the application is SageServer-16.01.
I tried to copy the files captured during setup capture. Let me try if i can provied the source files to it and i will get back to you.

Hello nheim,

BTW: Never seen a setup with an MSI inside, which could not be extracted...
A solution which works all the time: Check the log files. The path to the installation source is ALWAYS in there.

I have all the msi's available with me. The installation is the only problem. I have also checked the log files for the same.

I have uploaded the setup of this application. The link for the same is http://senduit.com/7668f4

Hi Nick,

Please find the updated package at the following link:
http://senduit.com/ff8024

Thanks for your help

Thanks a lot for the suggestion Nick. Will try this out and let you know.