...why you're not re-packaging the application? It seems to me that, after 3 days (this is essentially the same question that you asked the other day), you could have done that and moved on to the next challenge.

Hi EdT
In command line i used the full path its working fine now.  Sorry for small misatkes. 
Sorry for troubling you.

Thanks very much.

...is that you seem to post at the first hurdle. You will find your career path severely limited unless you begin to undertake basic troubleshooting before running up the white flag.

- Hopefully, you're testing this stuff on VMs/VPCs so you have nothing to lose by simply trying things. If 'x' doesn't work, go back to a snapshot and try 'y'.
- Log EVERYTHING.
- Learn how to use proper tools, like ProcMon.
- Test, test, test, test. Then test again.
- Search here, AppDeploy,InstallSite.ORG  and the vendor's site F I R S T, before posting. Someone, somewhere will almost certainly have come across the same - or similar - situation.
- Think laterally. Don't dismiss what you find in a search just because the post you found doesn't explicitly mention the application version you're dealing with or the file/registry key/value which is causing your problem. Think around what you find.
- Avoid running vendor set-ups via MSI unless you really, REALLY have to. I have yet to encounter an app which couldn't be re-packaged. Apart from anything else, until you do that, you have no idea what it's going to do to your workstations. One day, that app you pushed out to 100s of workstations will break those workstations and you'll need to know why. If you don't know what's inside the package, how will you fix it and, just as importantly, explain to senior management why no-one can do any work for the next 'x' hours while you do?

Hi
The above discussion i have gone through the log file which umeshbg was posted.

QUOTE: If i run the script choosing destination folder as D:\GMSTemp\CCAP2p0_Installable the setup.exe will run. If i choose the different folder say D:\GMSTemp or some other folder, MSI script will execute without any error but the setup.exe will not run.
I copied the Test.msi script to different machine there also MSI script will run without executing setup.exe. The script is
Execute a Program From Destination [INSTALLDIR]\CCAP2p0_Installable\setup.exe Default Directory XYZ (INSTALLCCAP)

The solution from EdT is Quote:ALWAYS specify a full path to every file you reference in a command line

From log file INSTALLDIR is D:\Umesh\Project
the full path of a file is D:\Umesh\Project\CCAP2p0_Installable\setup.exe

As he questioned if he going to run the Test.MSI file on different machine. The path  D:\Umesh\Project may not be available on that machine. 

My question is if path D:\Umesh\Project is not available on different machine how the setup.exe will run?

HI
The default directory  INSTALLDIR is D:Umesh\Project

As i understood that : if you running MSi script in a different machine while installation it will ask for the destination folder path there you can choose the path where MSI script is running for example your MSI script is in the path D:\First\New\Test.msi
The default directory is here INSTALLDIR is D:\First\New
The setup.exe path will be D:\First\New\CCAP2p0_Installable\setup.exe.

Please correct if i am wrong?

Thanks

...where possible. In this case, prefix your EXE name with '[INSTALLDIR]'. The engine will resolve that property to the path that the user chooses to install to. Of course, it's a nonsense to have that choice, because the user isn't installing anything at that point. I would probably use [%TEMP] instead, i.e. the user's temporary folder.

Having said that, I would have avoided wasting days and days on pointless dead-ends and captured the thing to an MSI in the first place. Hang on, let me check...did I say that already? Hang on.........................oh yes, I did. Only three times so far, though. This is the fourth. And I'm willing to bet a sizeable sum that you STILL won't take that course. Bannatynning...

HI VBScab
i will try to specify the correct path with the above post if anything wrong please correct me.

Quote ramyahg : The default directory is here INSTALLDIR is D:\First\New
The setup.exe path will be D:\First\New\CCAP2p0_Installable\setup.exe.

The default directory is here INSTALLDIR is D:\First\New
 Execute a Program From Destination [%TEMP%]\CCAP2p0_Installable\setup.exe.

The umeshbg post i understood that his question is, the msi script created if he gives msi script to the client, can the client able to run a script without any error?