Problems and Solutions

AdminStudio 2021 | 21.0 | Automated Application Converter

The following chart lists some typical problems that you might encounter when using the Automated Application Converter and some suggested solutions.

Solutions to Common Problems

Problem

Possible Causes

Solution

Cannot connect to a virtual machine

Virtual machine has not been prepared.

Verify that the Virtual Machine Preparation Setup (VMCfg.exe) was run on the virtual machine to enable automatic login. See Running the Virtual Machine Preparation Setup for instructions.

Tip:A quick way to determine if the Virtual Machine Preparation Tool has been run on a virtual image is the presence of the GuestAgent.exe file on the root of the C: drive.

Specified Guest Username or Guest Password property is not specified correctly.

When you add a virtual machine to the Automated Application Converter, you specify the User name and Password on the User Credentials panel. If you entered an incorrect value or if one of these values has changed, you will be unable to connect to the virtual machine. Open the Machines tab and verify that the values in the Guest Username and Guest Password properties for the virtual machine are correct.

Note:When using a domain account, do not include the domain name in the Guest Username property.

Cannot connect to a Windows 7 or Windows Server 2008 virtual machine

User Account Control (UAC) settings on a Windows 7 or Windows Server 2008 virtual machine could be causing problems during auto-login.

Make sure that you run the Virtual Machine Preparation Setup on the virtual machine to disable UAC. See Running the Virtual Machine Preparation Setup.

Unable to add packages from an AdminStudio Application Catalog

User does not have required login and/or view permissions on the Application Catalog.

Try to manually view packages in an AdminStudio Application Catalog to see if you have the required view permissions.

Use AdminStudio Application Catalog to view the packages in the Application Catalog.

Also, if using an AdminStudio Application Catalog with the Software Repository, make sure you have view permission to the Software Repository location of that Application Catalog.

Cannot connect to an AdminStudio Application Catalog

There are connection issues between domains due to user name.

Try to manually connect to the Application Catalog to make sure that you are using the correct credentials or that there are no other networking issues.

Unable to publish packages to an AdminStudio Application Catalog

User does not have required permission to import/publish packages.

Try to manually publish and/or import a package to an AdminStudio Application Catalog to see if you have the required permissions:

Use AdminStudio Application Catalog Import Wizard to manually import a package into the Application Catalog. This enables you to determine if you have import permission.

Also, if using an AdminStudio Application Catalog with the Software Repository, make sure you have write permission to the Software Repository location of that Application Catalog.

Cannot connect to a Microsoft Hyper-V Server

DCOM configuration settings need to be adjusted.

Adjust the DCOM settings, as described in this MSDN article, Connecting to WMI on a Remote Computer:

http://msdn.microsoft.com/en-us/library/aa389290%28VS.85%29.aspx 

Copy errors are generated during package conversion

User does not have permission to the Output Path location specified in the Automated Application Converter.

To make sure that you have permission to the Automated Application Converter output directory, perform the following steps:

To specify Output Path directory:

1. Open the Automated Application Converter.
2. Select Options on the Tools menu. The Project Options dialog box opens.
3. Locate the Output Path setting under Conversion Options. By default, the path is C:\Users\[UserName]\Documents\AutoRepack.
4. Browse to that location using Windows Explorer to and attempt to copy a file to that location.
5. If you are unable to copy a file to that location, change the Output Path to a location that you do have write permission on.

Package status changes to soft or hard timeout

The installation is requesting user input.

In order for the Automated Application Converter to perform automated repackaging, packages must support silent installation mode and the silent installation mode command line parameters must be specified in the Command Line property for each package.

To resolve this problem, open the Packages tab and make sure that the package’s Command Line property contains the command line parameters to run the installation silently.

Note:The Automated Application Converter automatically populates the Command Line property for Windows Installer (.msi) packages that you add to the project. However, for non-MSI packages, you must manually enter the Command Line property.

If the Command Line property is specified, but you are still receiving a timeout error, you may want to try to manually run the installation using the command line parameters to make sure that the installation is not requesting any user input.

App-V application does not launch

VM does not have App-V client installed

If you are able to connect to the virtual machine, but the App-V package will not launch, make sure that the App‑V client is installed on the virtual machine.

Also, make sure that App-V file streaming is enabled on the virtual machine.

Note:When you select Launch Package for Testing, you are prompted to Install the Microsoft App-V Client on the Select Virtual Machine panel. See Testing Packages.

Cannot build a ThinApp package

ThinApp application is not installed.

To create a ThinApp application, you are required to have ThinApp installed on the same machine as the Automated Application Converter.

Cannot connect to Hyper-V server

Hyper-V configuration tools are not installed.

Make sure that the Hyper-V configuration tools are installed on the Hyper-V Server’s Hyper-V Microsoft Management Console.

Virtualization Readiness status of a package is “Unknown” ()

Location of source files is no longer accessible.

When you originally added the package to your Automated Application Converter project, you were able to access the source files, but now the source files are either no longer there or you no longer have permission to access them.

Repackaging is taking a long time

It is taking a long time to copy the files required for repackaging to the virtual machine and back to the host machine.

Try to copy the files manually from the host machine to the virtual machine to attempt to identify the cause of the delay.

For VMware, try switching the Network connection setting between Bridged and NAT on the virtual machine to see if it helps to improve the copy speed.

The package’s Compressed property setting is incorrect.

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.

Cannot connect to a VMware virtual machine

The latest version of the VMware vSphere API is not installed on the same machine as the Automated Application Converter.

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.

You are using VMware Workstation 7.01, but the wrapper‑config.txt file does not identify Workstation 7.0.1

If running VMware Workstation 7.0.1, verify that the vSphere wrapper‑config.txt contains the following line that identifies a Workstation 7.0.1. For example:

# Workstation 7.0.1

ws 9vmdb 7.0.1 Workstation-7.0.0

player 9 vmdb 3.0.1 workstation-7.0.0

You are attempting to connect to a VMware ESX and a VMware Workstation image at the same time.

When performing repackaging on a VMware virtual machine using the Automated Application Converter, you should connect to either a VMware ESX/ESXi image or a VMware Workstation image, but not both at the same time.

vSphere API is not working properly on virtual machine.

If the vSphere API is not working, verify that vmrun.exe works. You can enter vmrun.exe /? to get the parameters for this tool. For example, to power up a virtual image on a VMware ESX server, use this command:

C:\Program Files (x86)\VMware\VMware vSphere>vmrun -h https://172.17.1.221/sdk -T esx -u root -p hostpassword -gu UserName -gp guestpassword start "[QA_ISO] Windows 7 Ultimate - 32-bit/Windows 7 Ultimate - 32-bit.vmx"