Install and Trace fails

[BillAmes]

I am using the portable version 3.3.4 and when I try to run the install it stops after a few seconds, no install elements are displayed. I found if I extracted the msi file (run setup and copy the msi from the temp folder) and did the install on the msi file everything appeared to work and I was able to save and review the log.
Problem and workaround but would like not to have to do it the hard way.

[Steven]

BillAmes
Can you please give us a copy of that .msi (.exe) setup file to reproduce the issue?

[BillAmes]

It is the application used to run a mass spectrometer and is installed on a 32bit win 7 AOpen PC. It is a clean environment, I do the windows setup myself. So I don't think it would be a good idea but I can try things you might wish to try your self and let you know what happens. I did try another install to see what would happen, I tried it on WinTask:
http://www.wintask.com/index.php

and it also failed. It was then I got the msi file for my app and it worked.

[Steven]

BillAmes
Just have tested 'wintaskx64.exe' setup on a clean Windows 7 SP1 x64 machine.

Install Tracker worked fine (see attached log).

Screenshot

[BillAmes]

I just did an install of an older version of wintask (I have it in a zip file, about 24 meg, but it seems too big for an attachment) on a win 7 32 bit system using the portable version I mentioned. It failed. I can send you the zip file if you have a way...

[Steven]

You can use any free file sharing hosting or cloud storage (mega, dropbox, google drive)

[Aleksey]

Hello all, It seems that I have the same problem, Unistall tool does not trace any .exe installer.

Clean Windows XP 64, and Install and Trace reports that it does not found any installation.

Any ideas?

p.s. portable license, XP Professional 64 bit SP2

[Steven]

Aleksey
Can you try reboot, then try to install & trace this setup file?
http://www.crystalidea.com/downloads/anytoiso_setup.exe

A log file is appreciated.

[Aleksey]

No problem, take a look.

Uninstall is ran under Administrator account renamed to User with Group Policy console.

[Steven]

Aleksey
Your issue is different, please see this topic

[Steven]

BillAmes
'setup37.zip' works just fine in our environment. Please provide us with installation log created by Install Tracker.

[BillAmes]

Here it is...

[Steven]

BillAmes
Thanks for the log, the issue is now more clear

1. Were there any errors/messages produced by the installer ('setup37.exe') between 06:37:56 and 06:38:06 in the log?
2. Can you install 'setup37.exe' without Install Tracker?
3. As you can see our log differs, the .exe is creating .msi:

08:46:00 Starting Install Tracker service...
08:46:00 Service version is: 0x103
08:46:00 Starting setup37.exe...
08:46:00 Installation monitor is started
08:46:00 Create Folder C:\Users\me\AppData\Local\Temp\{C695184A-115F-4CDC-80B8-FF9897A4218C}
08:46:00 Create File C:\Users\me\AppData\Local\Temp\_MSI5166._IS
08:46:00 Create File C:\Users\me\AppData\Local\Temp\{C695184A-115F-4CDC-80B8-FF9897A4218C}\Setup.INI
08:46:00 Create File C:\Users\me\AppData\Local\Temp\{C695184A-115F-4CDC-80B8-FF9897A4218C}\_ISMSIDEL.INI
08:46:00 Create File C:\Users\me\AppData\Local\Temp\{C695184A-115F-4CDC-80B8-FF9897A4218C}\0x0409.ini
08:46:00 Create File C:\Users\me\AppData\Local\Temp\~4242.tmp
08:46:00 Create File C:\Users\me\AppData\Local\Temp\{C695184A-115F-4CDC-80B8-FF9897A4218C}\WinTask 3.7.msi
08:46:05 Process Created C:\Windows\SysWOW64\msiexec.exe
08:46:05 Create File C:\MSI656fa.tmp
08:46:05 Create File D:\MSI656fb.tmp
08:46:05 Create File G:\MSI656fc.tmp

4. What is your Windows version?

Thanks

[BillAmes]

Windows 7 Pro 32 bit

It installs fine by itself

When using the tracker I never see any GUI of the install program. No errors, nothing, just the log.

I can do other tests for you if you need something?

[Steven]

BillAmes
We have just tested this setup on Win 7 32-bit, it works fine:

12:04:25 Starting Install Tracker service...
12:04:27 Service version is: 0x103
12:04:27 Starting setup37.exe...
12:04:27 Installation monitor is started
12:04:27 Create Folder C:\Users\Admin\AppData\Local\Temp\{102640EC-EBB5-44F8-BA83-F66B47C12CBB}
12:04:28 Create File C:\Users\Admin\AppData\Local\Temp\_MSI5166._IS
12:04:28 Create File C:\Users\Admin\AppData\Local\Temp\{102640EC-EBB5-44F8-BA83-F66B47C12CBB}\Setup.INI
12:04:28 Create File C:\Users\Admin\AppData\Local\Temp\{102640EC-EBB5-44F8-BA83-F66B47C12CBB}\_ISMSIDEL.INI
12:04:28 Create File C:\Users\Admin\AppData\Local\Temp\{102640EC-EBB5-44F8-BA83-F66B47C12CBB}\0x0409.ini
12:04:28 Create File C:\Users\Admin\AppData\Local\Temp\~8B9D.tmp
12:04:28 Create File C:\Users\Admin\AppData\Local\Temp\{102640EC-EBB5-44F8-BA83-F66B47C12CBB}\WinTask 3.7.msi
12:04:45 Process Created C:\Windows\System32\msiexec.exe
12:04:50 Create File C:\Users\Admin\AppData\Local\Temp\CabE19D.tmp
12:04:50 Create File C:\Users\Admin\AppData\Local\Temp\TarE19E.tmp
12:04:51 Create Folder C:\MSI5e6dd.tmp

Actually this really sounds strange, we haven't had any report like this. It must be some system-specific issue.

Does it actually happen with any installation .exe? or only msi-based executables?

[BillAmes]

Well, I did try it with something and it worked so it probably is when it is msi based. You must have some an msi install you use for test? A test case? You are using the portable version right?

My log never sees
12:04:28 Create File C:\Users\Admin\AppData\Local\Temp\~8B9D.tmp

And the setup process is killed. Can you make a guess as to what is happening?

[Steven]

Yes, I've tried portable version.

You must have some an msi install you use for test?

Yes, we have bunch of different setups, everything works fine.

Can you make a guess as to what is happening?

No ideas at the moment why this installations fails (process is killed) when running under Install Tracker.

Can you try your portable version of Uninstall Tool (on a USB flash drive) on another PC to install WinTask?

[BillAmes]

Tried two other PCs, same results.

If you have a test install, small, send it to me and I can try it.

Perhaps your tool has options for single step or verbose logging or you made a recent change that broke something? Perhaps you have a previous version I could try? Perhaps you have a debug version that would show exceptions? Anything?

[Steven]

I have just tested on a clean Win 7 32-bit, please see the video:
https://www.dropbox.com/s/mpdblkqlolrs9 ... apture.avi

No log would help to locate the issue, for a unknown reason the WinTask installer process terminates without any error messages.

I do suppose it's some system specific related issue. What would help us to resolve it - a virtual machine with reproducible environment. I understand though it's hardly possible to create such an operation for a user. BTW converting real machine to Virtual (e.g. Vmware) is technically possible.

[BillAmes]

I did not see in your video the display of the OK dialog showing the InstallShield command line parameters?