I am doing a repackaging for one an application. I created MST (wise package studio) for the given MSI. The application installs and launches fine if I install using the MSI & MST through the command line.(normal as well as silent mode)
According to the process in our organisation this MSI and MST will be installed through the VBScript.(silent mode)
The installation with VBScript goes on fine but when I launch the shortcut an error comes up saying that "This application has failed to start because esc11.dll was not found. Re-installing the application may fix the problem". This dll will be in the application folder.

Help me out from this issue

Thanks in Advance
0 Comments   [ + ] Show 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.

Answers

0
It is not possible to get an error messsage, for application functionality, because of "Installation vbscript". Test your package properly.
Answered 10/20/2009 by: abking99
Second Degree Blue Belt

Please log in to comment
0
I checked but I don't find much defect in it.....!!!!
Answered 10/20/2009 by: apppackaging
Senior Yellow Belt

Please log in to comment
0
I will not believe on you, as you are saying application is giving problem, as you are installing your msi and mst through vbscript. Are you doing any additional custommisation, through script, and its not working? below is the code for calling msi and mst, just change msi and mst name. try it...
for e.g.

Set WshShell = wscript.CreateObject("WScript.Shell")
ScriptName = WScript.ScriptFullName
FilePath = Left(ScriptName, InstrRev(ScriptName, "\"))
Applesafari = chr(34) & Filepath & "Safari.msi" & chr(34) & " TRANSFORMS" & "=" & chr(34) & Filepath & "Apple Inc Safari 4.31.9.1.mst" & chr(34) & " /QB!"
wshshell.run Applesafari,1,true
Answered 10/20/2009 by: abking99
Second Degree Blue Belt

Please log in to comment
0
Firstly, does the package work if installed outside of the script, i.e. from a "long hand" command line?
This dll will be in the application folder. Do you mean that the MSI is designed to deliver it to the same folder as the EXE? If so, is it in fact present after the installation? To my mind, it can't be, in which case, your package is at fault. As usual, a verbose log will tell you if the component containing the file was installed or not.
Answered 10/20/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity