Software Deployment

Why not call the msiexec command directly instead through cmd?

Actually.. it is and will be. This is a call inside a .net app. Process object's parameters are set as such to wait for exit in the .net code.

Sorry, are you launching the cmd or msiexec in "your" .net app?
Could you post the code that executes either one of them?

was calling msiexec.exe initially

basically something like this

Process RunInstall = new Process();
RunInstall.StartInfo.FileName = "msiexec.exe";
RunInstall.StartInfo.Arguments = @"/i mymsi.msi /lv* C:\mylog.log /qn";
RunInstall.Start();
RunInstall.WaitForExit();

I may have missed couple lines.. going off memory, too many windows open.

Process runs quickly and RunInstall.ExitCode is = 1620, which is an error indicating the package is not accessible. If you view the log file, it doesn't tell you much except that a 1620 occurred.

I am old school and create a batch file to accomplish this.

@echo off
start /wait APP.msi /qn

good call mjschutt.. I'll just do that

Sound like the current directory isn't set correctly.

Try setting the WorkingDirectory property to the folder where the msi resides in, ex.:
RunInstall.StartInfo.WorkingDirectory = @"C:\bla\bla\";

Hey AngelD - I figured out what was causing the 1620 error. The MSI was on a network share that I was copying to the target machine.. somehow it was getting corrupted during the file copy. I did get it to exit with 0, however, it still does not run synchronously. I had to use start.exe with the /wait switch.