MSIEXEC errors while using ADR-package
I have created a MSI using the AppDeply Repackager 1.1 application. As mentioned in the instructions i have used a clean XP install.
While double clicking on the produced MSI file the application is installed as expected and this is good, however while using MSIEXE.EXE i experience an error:
Does anyone have the same experience and what is the solution?
Thanks in advance!
While double clicking on the produced MSI file the application is installed as expected and this is good, however while using MSIEXE.EXE i experience an error:
Does anyone have the same experience and what is the solution?
Thanks in advance!
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
dunnpy
15 years ago
Berry,
Please post the command line you're using with msiexec.
If it works by double clicking then your command line must be duff.
Thanks,
Dunnpy
Please post the command line you're using with msiexec.
If it works by double clicking then your command line must be duff.
Thanks,
Dunnpy
Posted by:
Berry
15 years ago
[font="courier new"]msiexec -i AppName.msi
The idea is that we deploy those MSI's based on a GPO. But the manual installation with msiexec fails...
The idea is that we deploy those MSI's based on a GPO. But the manual installation with msiexec fails...
Posted by:
dunnpy
15 years ago
Berry,
The error message you get is the same as if you've specified an MSI file that can't be found i.e.the wrong path specified.
Are you running the command line in a batch file? Is it on a UNC path?
Try specifying the absolute path to the MSI file in your command line, and create a log file ' /l*v c:\mylog.log' that will also give you some indication of what the problem is.
Also it's also normal to use ' /i ' rather than ' -i'
Hope this helps,
Dunnpy
The error message you get is the same as if you've specified an MSI file that can't be found i.e.the wrong path specified.
Are you running the command line in a batch file? Is it on a UNC path?
Try specifying the absolute path to the MSI file in your command line, and create a log file ' /l*v c:\mylog.log' that will also give you some indication of what the problem is.
Also it's also normal to use ' /i ' rather than ' -i'
Hope this helps,
Dunnpy
Posted by:
Ram
15 years ago
Hi Berry,
This might also happen if you are trying to run the MSI straight from server location. Try mapping your drive to that location where your MSI is located and I think it will be OK
Regards,
Ram.
This might also happen if you are trying to run the MSI straight from server location. Try mapping your drive to that location where your MSI is located and I think it will be OK
Regards,
Ram.
Posted by:
Berry
15 years ago
This worked out fine... we will stick to mapped drives instead of UNC paths.
Thanks for the quick replies!
Thanks for the quick replies!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.