Debugging silent install
hello,
i have an setup.exe associated with .MSI file and i tried to do install
with this command line :
setup.exe /S /v"/l* c:\temp\install.txt ADDLOCAL=ALL TRANSFORMS=\"c:\temp\test.mst\""
but it seems some custom action or properties not appear in the log file
because .MSI needs to write data into one MSSQL base and it is missing.
In the MSI file ( install EXE sequence ), i didn't see one custom action
to do that.
If somebody have an idea in which part i can try :
- properties ?
- features ?
- install UI sequence ?
Thanks for helps.
i have an setup.exe associated with .MSI file and i tried to do install
with this command line :
setup.exe /S /v"/l* c:\temp\install.txt ADDLOCAL=ALL TRANSFORMS=\"c:\temp\test.mst\""
but it seems some custom action or properties not appear in the log file
because .MSI needs to write data into one MSSQL base and it is missing.
In the MSI file ( install EXE sequence ), i didn't see one custom action
to do that.
If somebody have an idea in which part i can try :
- properties ?
- features ?
- install UI sequence ?
Thanks for helps.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
One, abandon using the set-up stub and use the MSI directly. Two, check your command line: I think you have an error in the value you're passing with the TRANSFORMS property, specifically, the leading backslash.
As for the Custom Action, does it exist in the transform?
As for the Custom Action, does it exist in the transform?
Posted by:
philippe_tang_10
14 years ago
Hello, i found the solution by editing the script file : setup.inx
it contains the fileds recognized by the file : setup.exe
and i tried the syntax :
setup.exe adminname=xxxx adminpwd=xxxx /S /v"/l* c:\temp\install.txt ADDLOCAL=ALL TRANSFORMS=\"c:\temp\test.mst\""
and it works correctly.
it contains the fileds recognized by the file : setup.exe
and i tried the syntax :
setup.exe adminname=xxxx adminpwd=xxxx /S /v"/l* c:\temp\install.txt ADDLOCAL=ALL TRANSFORMS=\"c:\temp\test.mst\""
and it works correctly.
Posted by:
anonymous_9363
14 years ago
It might help to know what application this is connected with! :-)
Rather than tell us here, why not create a 'Package KB' for the application? Once it's appeared (entries are moderated), you can use the link at the top of this page to link the thread to the 'Package KB' entry.
Rather than tell us here, why not create a 'Package KB' for the application? Once it's appeared (entries are moderated), you can use the link at the top of this page to link the thread to the 'Package KB' entry.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.