/bundles/itninjaweb/img/Breadcrumb_cap_w.png
hi guys

i`ve extraced a *.exe to a *.msi ( i have extraced it this way> start installer and copy the msi from %temp% to a new location) in the %temp% i found the *.msi and a few *.ini files.

So when i try to install the Msi file , the installer say that one *.dll could not be registered. so when i try to install the *.exe it works.

why does the extraced msi do not work ??

please help me , thanks martin
0 Comments   [ - ] Hide Comments

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

Answers

0
Normally, it's due to a missing dependency which, presumably, the EXE installs before running the MSI.

Use ProcMon. It will show you what's happening.
Answered 07/09/2008 by: VBScab
Red Belt

Please log in to comment
0
i have tried procmon but i found nothing......

is there another way to extract the msi from the exe ??
Answered 07/09/2008 by: 3dmartist
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: 3dmartist
i have tried procmon but i found nothing......
Then, with respect, you're not using it correctly. I suspect you have one too many processes or paths excluded from its view.

ORIGINAL: 3dmartist
is there another way to extract the msi from the exe ??
None that I can think of...
Answered 07/09/2008 by: VBScab
Red Belt

Please log in to comment
0
the msi register the dll correctly but the msi only say that the dll could not be registered. so the application work, but when i try the deploy the software unattand with our deployment tool , the msi will do a rollback because of the "wrong" errormessage.

so back to roots > i will try the procmon again

regards martin
Answered 07/09/2008 by: 3dmartist
Senior Yellow Belt

Please log in to comment