First Things to Check

AdminStudio 2021 | 21.0 | Automated Application Converter

If you encounter a problem when performing package conversion, first scan this table to review of list of the most likely causes for conversion failure.

Most Likely Causes of Errors

Cause of Error

Resolution

Did not run the Virtual Machine Preparation Tool

On each virtual machine that you are going to use to perform automated repackaging, you need to run the Virtual Machine Preparation Tool, an application that will enable automatic login. See Preparing Your Virtual Machines for Use With the Automated Application Converter.

Important:If you do not run the Virtual Machine Preparation Tool on the virtual machines you want to use, the Automated Application Converter will be unable to connect to them.

Did not install VMware vSphere API

If you are using VMware virtualization technology (VMware ESX or ESXi Server or a local VMware Workstation 6.5 or later), you need to have the VMware vSphere API installed on the same machine as the Automated Application Converter. See VMware vSphere API Requirement on the AdminStudio Machine.

Snapshot does not exist on the virtual image

After you run the Virtual Machine Preparation Tool on a virtual machine, you need to shut it down and create a snapshot. This enables the Automated Application Converter to revert the virtual image to a clean state after each repackaging run. See Taking a Snapshot.

Important:If a snapshot does not exist on the virtual machine, not only will repackaging on that virtual machine fail, but you will also be unable to use that virtual machine to perform testing (as described in Testing Packages).

Name of Snapshot on virtual image is not identified properly

If your virtualization technology supports named snapshots, you should name the snapshot AutoRepack_Base, which is the default name that the Automated Application Converter will be looking for.

If you assign a snapshot name other than AutoRepack_Base, after you add the virtual machine to the Automated Application Converter, you need to specify that snapshot name in the Snapshot Name property in the Properties window of the Machines tab for that machine. See Editing Virtual Machine Properties on the Machines Tab.

Important:If the snapshot on the virtual machine is not identified properly in the Automated Application Converter, not only will repackaging on that virtual machine fail, but you will also be unable to use that virtual machine to perform testing (as described in Testing Packages).

ThinApp client is not installed

If you choose to build ThinApp applications, AdminStudio will convert the package installation into a format compatible with ThinApp. However, the ThinApp build process requires the availability of certain ThinApp tools. As a prerequisite to building a ThinApp application from AdminStudio, you must have installed ThinApp and accepted any and all license agreements. For more information, see ThinApp on the VMware website.

Password of the virtual image has changed

When you add a virtual image to a project, you are prompted for the user name and password to logon to that machine. If you entered an incorrect password or if the password has recently changed, you need to edit that machine’s Guest Password property on the Machines tab. See Editing Virtual Machine Properties on the Machines Tab.

Virtual machine is corrupted, or cannot be launched

If the Automated Application Converter is attempting to connect to a virtual machine that is corrupt or cannot be launched, conversion will fail. To make sure that your virtual machines are in proper working order, attempt to launch them manually (outside of the Automated Application Converter) using the configuration tool of the virtual technology.

Virtual machine does not have network connectivity

In order for the Automated Application Converter to use a virtual machine, the virtual machine must have connectivity to your network. From the host machine, try to manually browse to the C drive of the virtual machine by entering the following address:

\\virtual_machine_name\C$

Repackaging is taking a very long period of time

If the repackaging of a package is taking a very long period of time, you may want to verify that the value for that package’s Compressed property is correct.

If a package is in a directory that contains many other applications, and its Compressed property is set to True, the Automated Application Converter knows that only that one file needs to be copied to the virtual machine for repackaging. However, if the Compressed property set is set to False, there is no way to determine which of the files in that directory belong to the package, so all of the files in the directory must be copied to the virtual machine before repackaging can start. See Editing Package Properties on the Packages Tab.

Tip:It is recommended that each package be placed in its own directory to avoid problems such as this one.