cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Automated Application Converter

Getting this error:

Error 4314 controlling virtual machine: Failed to copy repackaged output from virtual machine: 040461c8

I've also noticed that it never really repackages the install. The repackage process runs for maybe a second. During the process it also sits at "Logging in interactively..." for about 3-5 minutes before continuing.

2011-09-30 19:32:16Repackaging is required for unspecified reasons.
2011-09-30 19:32:18Processing package Manufacturer Product Version
2011-09-30 19:32:18VirtualMachine: Getting Snapshot....
2011-09-30 19:32:18VirtualMachine: Reverting Snapshot....
2011-09-30 19:32:19VirtualMachine: Starting up image....
2011-09-30 19:32:28VirtualMachine: Waiting for image to finish booting....
2011-09-30 19:32:46VirtualMachine: Logging in...
2011-09-30 19:33:05VirtualMachine: Logging in interactively...
2011-09-30 19:37:07VirtualMachine: Logging in...
2011-09-30 19:37:07VirtualMachine: Executing: C:\GuestAgent.exe
2011-09-30 19:37:37Preparing repackager for VM use...
2011-09-30 19:37:37Command returned 5:
2011-09-30 19:37:37Copying Repackager to VM...
2011-09-30 19:37:37Copying folder to VM: C:\Program Files (x86)\AdminStudio\10.0\Repackager -> C:\Repackager
2011-09-30 19:37:40Preparing package for VM installation...
2011-09-30 19:37:40Command returned 5:
2011-09-30 19:37:40Copying package to VM...
2011-09-30 19:37:42Repackaging package on the VM with Installation Monitoring...
2011-09-30 19:37:42Launching [20 40]: c:\windows\system32\cmd.exe /c C:\Repackager\repack.exe -nr -mm -sb -o "C:\AutoRepack\Manufacturer Product Version" -app "\"C:\AppSetup\Manufacturer Product Version.EXE\";/s" -pp "Product" -pc "Version" -pv "6.0"
2011-09-30 19:37:42Command returned 3: Failed to launch process c:\windows\system32\cmd.exe
2011-09-30 19:37:42Retrieving repackaged output from the VM...



Any help appreciated.
(1) Reply
In our environment we use C:\WINXP rather than C:\Windows. Adding C:\Windows\system32\cmd.exe on the VM corrects this issue.