hi all,

i have a strange behavior and i would appreciate it if someone could give me some clues as to how to fix this.

here's the situation;

the target machine is winxp with sp2.

i have built, with WFWI, a msi file that when i try it, sometimes it installs perfectly, sometimes msiexec.exe just stays in memory and nothing gets installed.

my machine is re-imaged, it works, re-imaged again, it fails.

when it's ok, eventlog shows successfull, when it fails, nothing gets written there.

what could be the changing factor? how can i troubleshoot this?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


This content is currently hidden from public view.
Reason: Hidden by Admin
For more information, visit our FAQ's.

check your application shortcut target exe and arguments... whether it tries to invoke other applications...
Answered 12/20/2011 by: mahendraKumar
Senior Yellow Belt

Please log in to comment
The application shortcut points to the correct executable in the correct folder. What I was trying to explain is when I double-click the executable "c:\program files\program one\app1.exe" it actually launches the executable "c:\program files\program two\app2.exe." Now, if that's not strange, I don't know what is! I've never before encountered this behavior so I don't know where to go from here. The two executables are separate and not at all related (two entirely different products), so I can't understand how this could happen. Thanks.
Answered 12/21/2011 by: stmasi
Senior Yellow Belt

Please log in to comment
ok ... dont launch the exe from the shortcut created ... launch it directly from the pfiles by double clicking it ...

open task manager to find what is the exe launched ... if the exe name that you have launched is found in the taskmanger then the exe might be internally code to launch the other application.. you have to ask your vendor ...(you may also kill the process of your application exe check if application B gets closed....)

also you can use promon ,filemon to dig into the issue more....

if you want to find whether application exe A and B are dependent ... use dependency walker to find out the relations...

i hope this tips may help....
Answered 12/21/2011 by: mahendraKumar
Senior Yellow Belt

Please log in to comment