AppZero Troubleshooting Guide About This Document

AppZero Troubleshooting Guide About This Document
AppZero Troubleshooting Guide
AppZero Troubleshooting Guide
About This Document
This document provides information about known issues and possible solutions concerning managing AppZero software and VAAs.
The intended audience is administrators and those responsible for managing AppZero software and managing VAAs.
Copyright © 2007­15 AppZero Software Corp. All rights reserved.
Notice: All information contained herein is the property of AppZero Software Corp. No part of this document (whether in hardcopy or electronic form)
may be reproduced or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written
consent of AppZero Software Corp. This document is protected by copyright and distributed under a license restricting its duplication, distribution and
use. No part of this guide may be reproduced, adapted, or translated in any form by any means without the prior written consent of AppZero. Please
consult the license under which this document was acquired in order to review all of the applicable restrictions.
AppZero and the AppZero logo are trademarks or registered trademarks of AppZero Software, and may be registered in certain jurisdictions. Other
AppZero graphics and logos are trademarks or trade dress of AppZero. Red Hat and all Red Hat­based trademarks and logos are trademarks or registered
trademarks of Red Hat, Inc. in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the U.S. and other countries.
UNIX is a registered trademark of The Open Group. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries. Other company, product, and service names may be trademarks, registered trademarks, or service marks of their
respective owners.
This publication and the information contained herein are subject to change without notice and are provided pursuant to the terms of the software license
agreement to which it relates. All works provided by AppZero herein are provided on an ”as is” basis and there are no warranties, representations or
conditions, express or implied, written or oral, arising by statute, operation of law, course of dealing, usage of trade or otherwise, regarding them by
AppZero (including its affiliates, licensors, suppliers, subcontractors and distributors). AppZero including its affiliates, licensors, suppliers, subcontractors
and distributors disclaim any implied warranties or conditions of quality, merchantability, durability, fitness for a particular purpose and non­infringement.
AppZero Software Corp
1 Hines Road, Suite 105
Ottawa, ON K2K 3C7
300 Brickstone Square, Suite 201
Andover, MA 01810
[email protected]
About AppZero
AppZero™ creates, controls, and maintains Virtual Application Appliances (VAAs). VAAs decouple an application from the operating system and its
underlying infrastructure. The result is a single file that encapsulates an application with its dependencies, including executable libraries, files/registry,
configuration settings, and services. The VAA can be freely moved and managed without reconfiguring either the application or the operating system.
Isolated from the underlying infrastructure, VAAs can be easily moved among servers (physical or virtual) on­premise or in the cloud. This isolation
makes it easy for both legacy and new applications to move as needed from machine to machine, regardless of infrastructure changes, cloud provider, and
differing virtual and physical machine configurations, including hypervisor technology.
CLI options appear in Courier font.
CLI commands appear in Courier font bold.
AppZero Troubleshooting Guide
This symbol indicates a menu item. For example, ”Choose Tools>Options” means choose the Options item from
the Tools menu.
Bold font indicates a graphical user interface element. For example, ”Run Setup for AppZero, and then click Next.”
Other AppZero Resources
The resources in the following table can help you learn more about AppZero.
For information about
Important and late breaking information
AppZero Release Notes
AppZero Support
AppZero Support
Other services and products
If you have comments about AppZero products or AppZero user documentation, please contact us:
AppZero Support
For AppZero customer support, email [email protected] and see
Test Scripts and Errors
After you install AppZero software, AppZero recommends that you run batch test scripts (RunVAATest.bat) on the destination machine to determine
whether endpoint protection or other issues exist on the destination machine that would possibly interfere with application migration. The scripts are
located in the \EXTRAS\BasicVAATest folder in the AppZero installation folder.
For information about how to run the test scripts, see Running Test Scripts After Installation.
Test Script Errors
The following errors may be reported after you run RunVAATest.bat:
Fatal Error: Creation of VAA
appzcreate.exe could not create a
Fatal Error: Docking of VAA
appzdock.exe could not DOCK the VAA
Fatal Error: Undocking of VAA
appzundock.exe could not UNDOCK the
Fatal Error: Deletion of VAA
AppZero Troubleshooting Guide
appzdel.exe could not DELETE the VAA
Fatal Error: Registry and file
operations failed
Please check your endpoint protection or contact
AppZero Support Endpoint Protection or Antivirus
software is installed.
This will prevent AppZero Migrations
from succeeding.
Activity Log File
An activity log file will be generated in the following folder:
The log file name format is:
[email protected]
For example:
Tue03­10­[email protected]­53­21.06.WIN2K8R2­DEST.AppZero.20150310.activity.log
If you encounter issues, contact [email protected] or go to Please provide the test output and the activity log file.
Precheck Report
The Precheck Report lists the results of running appzprecheck. For more information about each section of the report, see Are You Ready to Migrate an
Application? in the AppZero Migration Guide.
Problems identified in the report may prevent the successful migration of applications. This topic provides information about what to do if there are
problems in the Precheck Report.
Port Status
This section of the report indicates the status of port 445 on the destination and the source machine, and port 80 for IIS application migration. The status
of the port or ports must be Open end to end across the network (if you are not migrating IIS applications then port 80 can be closed).
If a required port is not open, you must open the port. For information about how to open a port, see for example: How can I open or forward a port on
my router?
Destination and Source Machine Settings
Domain Match
This section indicates whether the domain names match across the destination and source machines.
Check the domain name on the source machine. If the application that you want to migrate has users that authenticate through the domain, then add the
destination machine to this domain. For information about how to add a machine to a domain, see­
OS Viable
This section indicates whether the operating system version of the destination machine is equal to or greater than the source operating system version.
If the versions of the operating systems are not viable, contact your system administrator.
Computer Name Compatible
This section indicates whether:
the host name of the remote machine is longer than 15 characters
the host name of the destination machine is shorter than 15 characters
If one or both of the above checks are true, this will cause issues with the Config­on­the­Fly process. The hostname can be more than 15 characters.
However, the netBIOS name is limited to 15 characters or less, which is why the hostname and the netBIOS values are different if the name is longer than
15 characters.
AppZero Troubleshooting Guide
Computer Name Compatible: No
*Remote Hostname: thisisareallyreallylongname
*Local Hostname: BW2K12R2
*Local NetBIOS Name: BW2K12R2
*The remote machine's hostname is longer than 15 characters and the local machine's hostname is
shorter than 15 characters. This may impact COTF functionality.
System Type Match
The operating systems of the destination and source machines must both be server operating systems.
If the operating systems do not match (for example, one is a server and the other is a desktop system), contact your system administrator.
System Root Drive Match
This section indicates whether the system root drives match on the destination and source machines, and identifies the drive letter on each machine.
If the system root drives do not match, contact your system administrator.
System Localization Match
This section indicates whether the locale of the destination and source machines match. A locale mismatch (for example, the source machine locale is
Danish and the destination machine locale is English_Australian) may cause issues.
This check is for the DEFAULT user profile only.
System Localization Match: No
*Remote Machine Locale: 00000409
*Local Machine Locale: 00001009
*There may be an issue with locale mismatch. For reference of the locale IDs Please visit:­ca/goglobal/bb895996.aspx
.NET Framework Viable
Verify whether .NET Framework version 4.0 or greater is installed on the source machine. If so, you must install .NET Framework 4.0 or 4.5 on the
destination machine before you perform a migration. On Windows Server 2012 R2, it is not possible to install version 4.0: you must install version 4.5.
To download .NET Framework 4, go to:­ca/download/details.aspx?id=17718
Web Deploy
This section indicates whether Microsoft Web Deploy is installed on the destination and source machines. If Web Deploy is required to migrate an IIS
application, AppZero will install it on the destination machine.
SID Accounts
This section indicates whether the user is logged in to the remote machine as a member of the Administrators Group. A user may proceed with a migration
For Windows Server 2003 source machines, they are members of the Administrators Group
For Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 , they are members of the Administrators
Group AND if User Account Control (UAC) is enabled, the LocalAccountTokenFilterPolicy registry key is set to allow the user to be
For assistance with setting administrator credentials, contact your system administrator.
COM+ Enabled
This section identifies whether COM+ is enabled on the destination and source machine.
IIS URL Rewrite Module
This section indicates whether the IIS Rewrite Module is installed on the destination and source machines. If the IIS Rewrite Module is required to
migrate an IIS application, AppZero will install it on the destination machine.
This section indicates whether antivirus software is detected on the destination machine.
Do not install and run antivirus software or "endpoint security" agents on the destination machine. These agents can be installed and run on the source
AppZero Troubleshooting Guide
machine without affecting AppZero software or application migration. Antivirus software or "endpoint security" agents interfere with AppZero software
on the destination machine. Note that many of these agents have self­restart logic and similar safeguards and that temporarily disabling them is not
sufficient. Do not install such software on the destination machine until after the migration, including Dissolve, is complete. After you have run Dissolve
successfully on the final destination machine, you can install antivirus software.
If antivirus software is detected on the destination machine, contact your system administrator.
This section also indicates whether antivirus software is detected on the source machine (for troubleshooting purposes only).
Source Machine Settings Only
Remote Administrative Shares Enabled
This section identifies whether remote administrative shares (such as c$, d$ etc.) are enabled in the registry. Admin shares must be enabled to copy data
over the network.
If these are disabled, contact your system administrator.
Remote Access
This section identifies whether remote access is enabled.
Cached Logins
Automatic services that authenticate with a domain controller may not start on reboot because the number of cached logins set for the source machine is
not sufficient or if cached logins is disabled (set to 0). To change the number of cached logins, see Automatic services that authenticate with a domain
controller do not start in the AppZero Troubleshooting Guide.
This section specifies the number of cached logins on source machine.
.NET Framework 1.1 Installed
This section identifies whether .NET Framework 1.1 is installed on the source machine. If your application requires .NET Framework, you must install
.NET Framework 1.1 on the destination machine.
A .NET Framework 1.1 installer is located in the C:\Program Files\AppZero\EXTRAS directory.
Destination Machine Settings Only
LAN Manager Authentication Level
This section indicates whether the LAN Manager Authentication Level on the destination machine is valid.
The destination machine may require that the "LAN Manager authentication level" setting be set to "Send LM & NTLM responses". This setting may be
required if :
a machine has been removed from the domain, OR
Active Directory is unavailable, AND
the source machine is Windows Servier 2000 and 2003
You can test whether this prerequisite applies to your situation. From the destination machine, try to access the UNC path to the source machine (i.e., \\
<sourcemachine>\c$). You will be prompted for credentials to connect to the source machine. If authentication is successful and you can see the C:
drive of the source machine, then AppZero Tether connection will succeed and you may ignore this prerequisite.
Change the setting as follows:
1. At the Start menu, type secpol.msc in the search line and press Enter. The Local Security Policy editor opens.
AppZero Troubleshooting Guide
2. Double­click Local Policies.
3. Click Security Options.
4. Double­click Network Security: LAN Manager authentication level.
5. Select Send LM & NTLM responses, and then click OK.
6. Close the Local Security Policy editor.
Shortnames on C
This section indicates whether shortnames on the C:/ drive are enabled on the destination machine. Shortnames must be enabled. You cannot create a
VAA on a drive where shortnames have been disabled (where the NtfsDisable8dot3NameCreation setting is set to 1).
To enable short names:
1. Click Start>Run, type regedit, and then click OK.
2. Locate and then select the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\File System
3. Right­click the setting NtfsDisable8dot3NameCreation and select Modify.
4. In the Value field, type one of the following:
0: NTFS creates short file names. This setting enables applications that cannot process long file names and computers that use different
code pages to find the files.
2: NTFS sets the 8.3 naming convention creation on a per volume basis.
3: NTFS disables 8dot3 name creation on all volumes except the system volume.
5. Click OK.
Note that this will give short names to files and directories created after the command is run and then rebooted. Files and directories that exist before you
run the command and reboot will not have short names. PACE ­ Application Discovery
Message: A migration of this product may be problematic
When you execute the appzpace /W command, the following message may be displayed:
A migration of this product may be problematic.
For example:
C:\Program Files\AppZero>appzpace.exe /C administrator password /
W "MySQL Server 5.5"
APPZERO (R) Product and Component Enumerator Version 5.4 x64
Copyright (C) AppZero Software Corp.
Initializing connection to remote host...
Product information retrieved.
Initializing connection to remote host...
Initializing connection to remote host...
The following installation information was found:
Install location: C:\Program Files\MySQL\MySQL Server 5.5\
AppZero Troubleshooting Guide
Uninstall string: MsiExec.exe /I{A1A64967­AEA8­4792­8461­A28473356E6C}
The following services were identified as product components:
A migration of this product may be problematic.
The following imports have been identified as COM­related:
+ C:\Program Files\MySQL\MySQL Server 5.5\bin\MySQLInstanceConfig.exe
­+ C:\WINDOWS\system32\ole32.dll v5.2.3790.4926
N/A OleGetClipboard
N/A CreateDataAdviseHolder
N/A CoCreateInstance
N/A CoGetClassObject
The product contains the following driver files:
C:\Program Files\MySQL\MySQL Server 5.5\share\czech\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\danish\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\dutch\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\english\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\estonian\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\french\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\german\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\greek\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\hungarian\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\italian\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\japanese\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\korean\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\norwegian\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\norwegian­ny\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\polish\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\portuguese\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\romanian\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\russian\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\serbian\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\slovak\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\spanish\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\swedish\errmsg.sys
C:\Program Files\MySQL\MySQL Server 5.5\share\ukrainian\errmsg.sys
This message may occur because the product was found to contain COM­related files and driver files. COM may complicate a migration
because the components could be DCOM. AppZero does not support the migration of drivers. Drivers should be pre­installed on the
destination machine.
VAA Services
Automatic services that authenticate with a domain controller do not
Automatic services that authenticate with a domain controller may not start on reboot because the number of cached logins set for the destination machine
is not sufficient or if cached logins is disabled (set to 0).
The Precheck Report will indicate the number of remote cached logins. For example:
Remote Cached Logins: 1
*Value too small. Automatic services may not start.
Remote Cached Logins: ­1
*Error accessing the number of cached logins. Automatic services may not start.
To resolve this issue, change the cached logins value on the destination machine as follows:
1. Click the Start button and type RegEdit to run Registry Editor.
2. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\
3. Select Edit>New>String Value. Create a registry value named CachedLogonsCount. Skip this step if CachedLogonsCount is already defined.
4. Increase the value to greater than 0 and up to 50. If group policies override this value, contact your system administrator.
If a user's login information is cached, they may be able to log in without domain validation and thus access network resources even if the Active
Directory (AD) domain controller is unavailable to authenticate a user account.
AppZero Troubleshooting Guide
Failure when starting main Cyborg service
When attempting to start the main service Cyborg, exception c00000fd may occur. AppZero is unable to retrieve a local copy of Cyborg, or any of the
other suites that succeeded it: Accero, SumtotalSystems excelHR.
Some software (such as Cyborg) requires that Data Execution Prevention (DEP) be disabled for services and executables to run.
If DEP is not disabled by default on a particular operating system, you can disable DEP on a system­wide basis as follows:
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Log into the destination machine as Administrator.
Open Windows Explorer.
Click Tools>Folder Options>View.
Uncheck Hide Protected Operating System Files (Recommended) and Hide Extensions for Known File Types.
Click Apply, then click OK.
Browse to C:\.
Right­click the boot.ini file, then select Properties.
Uncheck the Read­Only attribute, and then click OK.
Right­click the boot.ini file, then select Edit. If Edit is not listed, select Open With>Notepad.
To disable DEP, change /NoExecute= to: /NoExecute=AlwaysOff.
Click File>Save.
Right­click the boot.ini file, then select Properties.
Select the Read­Only attribute, and then click OK.
Restart the machine.
To resolve this issue on a selective basis, turn off DEP as follows:
1. 2. 3. 4. 5. Click Start>Control Panel>System and Security>System>Advanced>Advanced System Settings.
In the System Properties window, click Settings in the Performance area.
Click the Data Execution Prevention tab.
Enable Turn on DEP for essential Windows programs and services only.
Click OK.
Related to: Issue 9874
Cannot retrieve remote services
Remote services will not be retrieved if communication with the source machine is interrupted during the tethering process. This may occur for a number
of reasons; for example, if the firewall on the source machine is enabled while tethering is in progress.
If remote services are not retrieved, try any of the following to resolve the issue:
disable the firewall on the source machine, as applicable
make sure that the Remote Registry service is enabled on the source machine
make sure that the user credentials you specify to connect to the source machine are correct
check the Tether log for more information
Once you have identified the issue, connect to the source machine again.
For information about prerequisites for application migration, see the AppZero Application Migration Guide.
Related to: Issue 8507
Tethered service doesn't start
The system default service time out value is 30000 ms (30 seconds). A service being tethered may take more than 30 seconds to start due to large amount
of copying, which will cause the Windows Services Control Manager to time out and stop the service process.
A solution may be to increase the system default service time out:
1. Create a dword key value:
2. Set its data to a larger value (in ms). For example, 180000, which equals 3 minutes.
3. Restart the machine to make the new setting take effect.
AppZero Troubleshooting Guide
PostgreSQL service fails to start
The PostgreSQL service may fail to start when tethering from Microsoft Windows Server 2003 to Microsoft Windows Server 2008 R2 or Windows Server
Resolve this issue as follows:
1. Remove the leading '#' from (last) line:
"#host all all ::1/128 md5"
of the file \Program Files\PostgreSQL\9.0\data\pg_hba.conf
2. This can be accomplished with a Config­on­the­fly script:
<?xml version="1.0" encoding="utf­8" ?>
<AppZero feature="config­on­the­fly" version="3.0">
<TARGET folder="C:\Program Files\PostgreSQL\9.0\data" entries="pg_hba.conf">
<ACTION type="replace">
<SEARCH>^#host all all ::1/128 md5</SEARCH>
<REPLACE>host all all ::1/128 md5</REPLACE>
VAA service won't install on dock
A VAA service may fail to install when you dock a VAA for one of several reasons. For example:
A required port is in use by an application
The user password specified for the source machine does not meet policy requirements on the destination machine
If this issue occurs or other issues related to starting VAA services occur, use the Windows Event Viewer to view event details and troubleshoot problems
and errors with Windows and other applications.
1. Click Start>Control Panel>Administrative Tools.
2. Double­click Event Viewer.
3. Click the type of event you want to view, for example AppZero events.
4. View the list of events.
5. To view event details for a particular event or error, double­click an event.
Services won't start for migrated SQL Server 2005 VAA
This error occurs if a SQL Server 2005 VAA is migrated from Windows Server 2003 to Windows Server 2008.
To resolve this issue:
1. Click Start>Run.
2. Type:
Regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msftesql\DependOnService
3. Click OK or press Enter.
4. Edit the key by removing: NTLMSSP
5. Restart your machine.
6. Open the appliance folder, and then double­click the cservices file.
7. In the <dependencies> tag, remove dependencies on NTLMSSP.
8. Save the cservices file.
Service won't start, missing drive
AppZero Troubleshooting Guide
A service may fail to start if the service resides on a drive on the source machine (for example, drive F:) and the destination machine doesn't have this
drive (for example, it has only drive C: and E:).
To resolve this issue, add the required drive (in this example, drive F:) to the destination machine and start the service.
Application Migration
TetherProxy does not start after rebooting the destination server
TetherProxy may fail to start automatically after you reboot the destination server because of your network Group Policy.
To resolve this issue, try changing the settings of the AppZero.Controller service as follows:
1. Click Start>Administrative Tools>Services. The Services window opens.
2. Locate AppZero.Controller, then right­click the service and select Properties.
3. In Startup Type, select Automatic (Delayed Start).
4. Click OK, and close the Services window.
Connectivity issues, can't establish Tether connection
When trying to tether to the remote machine, you may receive the following error:
Error, could not validate tether credentials because no network settings configured
The following events are generated in the log:
cfmu_get_remote_system_root failed, error(5)
AppZero Troubleshooting Guide
cfmu_get_remote_system_root failed, error(93)
You verified that ports are open between the source and destination machines and that they can connect through the C$ admin share.
Appzprecheck reports the following:
Ports both open, Failed to validate connection.
This issue can be caused by a security script that is applying specific permissions to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg. These permissions supersede the
settings in the local security policy.
To resolve this issue, try adding "Administrators" to the permissions and then restart.
For more information, see the following:
Related to: Issue 12138
Tether Agent or tetherproxy.exe crashes
If Tether Agent or tetherproxy.exe should crash, Windows Server 2008 and later will notify you of the event via a message:
1. Select "Close the program". A crash dump will be generated in the folder <AppZero Installation Path>\CrashDumps (for example,
C:\Program Files\AppZero\CrashDumps) on the destination machine, with the name <Program Name>.exe.<Process
ID>.dmp (for example, tetherproxy.exe.3004.dmp). If Tether Agent crashes, the crash dump will be generated on the source machine.
2. Please send the dump file to AppZero for investigation and resolution.
Source name is truncated
Due to a Windows limitation, if the source name is over 15 characters long, the source name will appear truncated when you query a network in Tether
Console and will be truncated in the COTF field in the Tether Console and the Administrative Console. As a result, rehosting will fail.
If the source name is greater than 15 characters, resolve this issue as follows: manually change the source name parameter in the COTF field of the Tether
Console or the Administrative Console to the full name of the server. For example:
Change "C:\appliances\<VAA>\scripts\StandardCOTF.xml" "BTQ2R3Y2X86­MYSO"
to: "C:\appliances\<VAA>\scripts\StandardCOTF.xml" "BTQ2R3Y2X86­MYSOURCE"
Related to: Issue 9697
Tether Agent error occurs when starting a service
The following error may be generated in the Tether Log when attempting to start a VAA service when Tether Agent is enabled:
[ERROR]t1012:TetherManager::dstInit: ctu_start_remote_agent() failed. err
[ERROR]t1012:tp_start: tetherManager­>dstInit(C:\appliances\<VAAname>) failed
This error occurs because only one VAA at a time can tether using Tether Agent to the same source machine. Multiple tethers via Tether Agent at the
same time to the same source machine are not possible.
To resolve this issue:
1. On the source server, stop the appzagent.exe process associated with the previous VAA.
2. Dock the second VAA.
3. Start VAA services.
Related to: Issue 10960
During tether, services are running but application returns error
"Invalid license data. Reinstall is required."
During the tether process, all services are started and running but the application returns the error: "Invalid license data. Re­install is required".
The error occurs because the licensing for the application is linked to a specific computer and AppZero migrations do not move the license.
Resolve the issue by uninstalling the application using Add/Remove Programs. The example below uses Microsoft SQL Express 2012. In this case, a
Microsoft Management Studio component is returning the error.
1. Click Start>Add/Remove Programs, and then uninstall Visual Studio 2010 (Isolated) edition.
AppZero Troubleshooting Guide
2. In Add/Remove Programs, select SQL 2012.
3. Click Uninstall/Change, then select Repair.
4. Select Repair Shared Features Only and complete the wizard.
This will re­install the Visual Studio 2010 (Isolated) files.
Related to: Issue 10147
Remote DCOM Broken AppID Link
When migrating an application with DCOM information, a "Broken AppID Link" may be displayed in the AppID Name column on the Remote DCOM
tab of the AppZero Tether Console. This indicates that an AppID key was referenced by the CLSID key, but the AppID key itself could not be found.
There are a number of possible reasons why an AppID key might be missing from the registry of the source machine. The issue is not related to AppZero
support of DCOM information and the application may be migrated successfully despite the message in the AppID Name column.
Related to: Issue 9117.
Migration of SQL Management Studio Help does not work
In previous releases of AppZero, migration of the SQL Management Studio Help login screen was not fully supported.
The SQL Management Studio Help now works when the proper DCOM components are selected. This is true for Windows Server 2008 R2 and for up­
level scenarios.
Resolve this issue as follows:
If you are tethering by template: after VAA creation is complete, tether the VAA to the original source so that the listed DCOM components can be
tethered from the source.
For SQL DCOM components: in the Remote DCOM tab, sort by CLSID or AppID, and then select DCOM components that contain or start with
SQL, DTS, Vs, MSMDPP, and Microsoft Document Explorer.
Related to: Issue 8415
Enabling or disabling tether memory
You can enable or disable Tether memory. Tether memory means that the application does not go to the source machine for any item within a folder/key
that has already been copied over. This improves tether performance by reducing the need for merged views of folders/keys. Tether memory is enabled by
default (set to 0).
You can disable Tether memory if you want the application to always catch newly added items on the source machine. Keep in mind the following:
performance will be affected
Tether will not copy a file from the source machine if the file already exists in the VAA from a previous Tether session, even if the file on the
source is newer than the file in the VAA
You can enable or disable Tether memory by setting a registry key value.
Enable or disable Tether memory as follows:
1. Undock the VAA.
2. Under HKEY_LOCAL_MACHINE\SOFTWARE\AppZero Settings\Controller, create a REG_DWORD key value
3. Set the DisableTetherMemory data to 1 to disable Tether memory or to 0 to enable it.
Related to: Issue 8471
Can't tether to source machine due to a firewall
Make sure that port 445 is open to allow tethering. You may then start the Remote Registry Service on the source machine to allow remote registry access.
You can run the following command on the source machine to verify which ports are listening:
netstat –an
Tethering freezes when starting BES services
tetherproxy.exe may freeze when you try to start BES services. If you attempt to undock the VAA, tetherproxy.exe may crash. This is a Trusted Installer
AppZero Troubleshooting Guide
Resolve the issue as follows:
1. Download Process Explorer if the utility is not already installed on your machine:­ca/sysinternals/bb896653.aspx
2. Run Process Explorer (procexp.exe).
3. In Process Explorer, select the cinit that is not associated with a service, and then terminate the cinit process.
4. When Trusted Installer starts again, start the BES services again.
Error messages appear for Tether and Dissolve
After dissolving a VAA or tethering a VAA, error messages may appear even though the dissolve operation or tethering operation succeeded and the
application ran successfully.
For example, the appzdissolve report may contain the following error message:
Windows sxs not added to host:
The manifest file contains one or more syntax errors
The AppZero error log or Tether log file may contain error messages as well. For example, the Tether log may contain the following errors:
2012­12­12 12:50:29:266 [ERRO]t1376:TetherManager::installComponent:
(594) : InstallAssembly
ww_90f767f7\amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1801_x­ww_90f767f7.manifest: return
2012­12­12 12:51:12:733 [ERRO]t1376:TetherManager::installComponent:
(594) : InstallAssembly
return code=800736b3
You can safely disregard these error messages if the application is running correctly.
Tether credentials or password fail
Tether Credentials Fail
Tether credentials may fail when attempting to tether from a Windows XP source machine for a few reasons. To resolve this issue, try the following:
1. On the source machine, click Start>Control Panel>Folders Options.
2. Click the View tab.
3. In the Advanced Settings area, scroll to the bottom of the list and de­select Use Simple File Sharing.
4. Click OK.
Password Fails
If you specify a password on the command line and the password fails even though you are certain that it is correct, verify that any quotation marks or
other special characters within the password are properly escaped. This is often achieved using the backslash character (\). If the password contains
spaces, make sure that it is surrounded by non­escaped quotation marks.
For example:
my password becomes "my password"
pass"word becomes pass\"word
my pass"word becomes "my pass\"word"
For more information about escape characters, see:
AppZero Troubleshooting Guide­esc.html
IIS Application Migration
Migrating an IIS Application with an Encrypted web.config File
An application can have its web.config file encrypted for security purposes. It can hide sensitive information such as impersonation details or
connection strings to a database. Only a computer with the proper key can decrypt this information. When migrating this kind of application to a new
destination, there are two ways of ensuring that the application runs successfully on the destination machine. This topic uses MS Petshop 4.0 as an
example of how to migrate an encrypted web.config file.
Information about the Example Application
MS Petshop 4.0 is a simple Microsoft application that offers a catalog of pets that you can purchase using an account. The application uses a SQL Express
database to query the catalog and the user accounts. The information used to connect to the database is encrypted so that the hostname, username, and
password are not shown in plain text in the web.config file.
In the web.config file, the attribute "connectionStrings" has an encrypted cipher value noted here as [SOMEVALUE]:
<connectionStrings configProtectionProvider="PetShopProvider">
<EncryptedData Type=""
<EncryptionMethod Algorithm="­cbc" />
<KeyInfo xmlns="">
<EncryptedKey xmlns="">
<EncryptionMethod Algorithm="­1_5" />
<KeyInfo xmlns="">
<KeyName>Rsa Key</KeyName>
If you were to migrate this application the same way you would any other IIS migration, the following configuration error would occur when you load the
"Description: An error occurred during the processing of a configuration file required to service this
Please review the specific error details below and modify your configuration file appropriately.
Failed to decrypt using provider 'RsaProtectedConfigurationProvider'. Error message from the provider:
Bad Data."
Options for Migrating the Application
There are two ways to migrate this kind of application. Each method offers advantages and disadvantages.
Decrypt the configuration on the source machine and encrypt it again on the destination machine after migration. This is the easiest way to migrate
your application but it can be problematic if you do not want to leave your configuration files unencrypted for the duration of the migration process.
Export the key used to encrypt the configuration to the destination machine. This is the safest way to migrate your application to ensure that
sensitive information is not migrated.
AppZero does not recommend that you use Method 1 if leaving your configuration files unencrypted for the duration of the migration process poses a risk
to your files.
Method 2 will work only if you know the key that was used to encrypt it AND that the key was made to be exported at the time of creation.
If you do not know which key was used or whether the key can be migrated, you will need to follow Method 1 to decrypt the configuration on the source
machine, follow the steps outlined in Method 2 to create the key container, encrypt the configuration again and finally, import the key to the destination
AppZero Troubleshooting Guide
Method 1: Migrating a Decrypted Configuration
Follow these instructions to decrypt the web.config file on the source machine and to encrypt it again on the destination machine.
Refer to the AppZero Application Migration Guide for information about how to migrate the IIS web server.
1. On the source machine, open a command prompt and run as Administrator if you are not logged in as the built­in Administrator.
2. Navigate to the appropriate framework version directory. For our application, this is:
3. Run the decryption argument for the aspnet_regiis command:
aspnet_regiis ­pdf [section] [web.config path]
You will be encrypting the connectionStrings section to the database:
aspnet_regiis ­pdf "connectionStrings" "C:\Program Files\Microsoft\.NET Pet Shop 4.0\Web"
You should get a message that the decryption was successful. If you navigate to the web.config file again you will see the correct connection strings
with the database details.
4. Make sure that your application works on the source machine.
5. Begin the migration process. See To Migrate an IIS Application Using the AppZero Tether Console.
6. Exercise the application and make sure that it functions correctly.
7. Within the context of the VAA, run the AppZero Command Prompt with the following command:
aspnet_regiis ­pef [section] [web.config path]
For example:
aspnet_regiis ­pef "connectionStrings" "C:\Program Files\Microsoft\.NET Pet Shop 4.0\Web"
8. The web.config file is now encrypted again under the new web server. Restart IIS and make sure that the application functions correctly.
Method 2: Migrating an Encrypted Configuration
This section describes how to:
create a custom RSA key container
encrypt the web.config file with the custom RSA key container
export the key
migrate the application and
import the key to the destination machine
If you know which key was used to originally encrypt the web.config file and that it can be exported, skip to Step 8. Otherwise, you will decrypt the
configuration on the source machine and encrypt it using the new key.
1. Follow steps 1 to 5 in "Method 1: Migrating a Decrypted Configuration" to decrypt the configuration. The source for the following steps can be
found here:­us/library/2w117ede%28v=vs.140%29.aspx. The steps are also listed here with examples for the Pet
Shop application.
2. Create a custom RSA key container configured to ensure that the key can be exported:
aspnet_regiis ­pc "PetShopKey" ­exp
3. Grant ASP.NET identity access to the new RSA container:
aspnet_regiis ­pa "PetShopKey" "NT AUTHORITY\NETWORK SERVICE"
4. Add the configuration provider to the web.config file to allow the encryption tool to use the proper key. To do this, open the web.config file and
add the following section to it under the <configuration> </configuration> attribute. AppZero recommends that you put this at the top
of the configuration:
<add name="PetShopProvider"
type="System.Configuration.RsaProtectedConfigurationProvider, System.Configuration,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
useMachineContainer="true" />
Make sure that the <add name= is filled appropriately and keyContainerName is set to the proper key.
AppZero Troubleshooting Guide
5. Encrypt the configuration file again using the new key by running the following command:
aspnet_regiis ­pef "connectionStrings" "C:\Program Files\Microsoft\.NET Pet Shop 4.0\Web" ­prov
6. Export the RSA key container so that you can import it on the destination machine. To export the key, run the command:
aspnet_regiis ­px "PetShopKey" "C:\keys.xml" ­pri
where C:\keys.xml can be to any location on the system.
7. Begin the migration process. See To Migrate an IIS Application Using the AppZero Tether Console.
8. Copy the keys.xml file created in Step 8 to the destination machine. Make sure that you remove the keys.xml file from the source machine.
9. Run the AppZero Command Prompt from within the context of the VAA and run the following commands within the context of the VAA.
10. Navigate to the C:\Windows\Microsoft.NET\Framework\v2.0.50727 directory and run the following command:
aspnet_regiis ­pi "PetShopKey" "C:\keys.xml"
where "C:\keys.xml" is the location where you copied the key to.
11. Give the key access:
aspnet_regiis ­pa "PetShopKey" "NT AUTHORITY\NETWORK SERVICE"
The "NT AUTHORITY\NETWORK SERVICE" in this case is determined by the Application Pool identity that your application is running on. To double
check this, open InetMgr and click on Applications Pools. This should tell you which pool is running which application and the identity associated with it.
12. Begin exercising your application. You should be able to navigate as expected. However, if you also migrated the SQL database to the destination
machine, follow the next several steps to make sure that the new values are set correctly.
13. In the Pet Shop migration, the SQL database was also migrated, which means that any details pertaining to the source server needs to be configured.
To do this, run the command in Step 3 of Method 1 to decrypt the web.config file so you can run COTF on it.
14. After decryption is successful, open the file to see the connection strings. If you see an Access Denied error, right­click the web.config file and
check that the user on the destination has the proper ACL to read the file.
15. Run COTF on the VAA. See Config­on­the­Fly. When you open the web.config file, you should see the correct web server name for the
16. Run the encryption tool again to encrypt all sensitive information. To do this, perform Step 7 of Method 1 within the context of the VAA.
You should now have a fully functional application with an encrypted web.config file that connects to the database of the destination machine.
"Unable to validate data" error occurs when migrating an IIS
When migrating an IIS application, the following error may occur when you browse to the application:
Unable to validate data
This issue is likely due to having United States Federal Information Processing Standard (FIPS) compliant algorithms enabled in your policies. For more
information, see:
To fix this issue, see:­US/clr/thread/7a62c936­b3cc­4493­a3cd­cc5fd18b6b2a/
32­bit web application fails to run
If a 32­bit web application fails to run, you may need to select "Enable 32 bit applications" in the IIS Manager in order for the application to work.
To enable 32­bit applications in IIS7 Manager
1. In IIS Manager, right­click the Application Pool and select Advanced Settings or select Advanced Settings from the Actions pane after you select
the Application pool.
2. Change Enable 32­bit Applications to True (if you want the application pool to spawn in 32­bit mode).
3. Click OK.
To enable 32­bit applications via a command prompt
AppZero Troubleshooting Guide
1. Open a command prompt and navigate to the directory systemdrive\Inetpub\AdminScripts.
2. Type: cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true
Web Deploy fails due to Admin password string termination characters
Administrator passwords that include special characters (for example, quotes (")) are not supported in AppZero migrations.
For example, Web Deploy will fail if the BUILTIN\administrator password is similar to:
Check the AppZero migration.log file for more details about the password failure:
Cannot Dock VAA that Uses a Non Exportable Certificate When Using
Web Deploy
If you are migrating an IIS application using a non exportable certificate and using Web Deploy, an error will occur in both Tether Console and the
Administrative Console. When you try to dock the VAA, the status of the VAA will remain "Undocked". The following error will be displayed in the
migration log file:
A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT:
This is a Microsoft Web Deploy issue.
Resolve the issue in one of two ways:
Remove the Certificate
1. Remove the certificate that is not exportable.
2. Reimport the certificate to replace the certificate.
3. Make sure that "Mark exportable" is set to true. You require access to the original certificate to do this.
Execute appzmigrate without Using Web Deploy
1. Open the migration.config file in the VAA\scripts folder.
2. Remove the webDeploy node from the migration.config file:
<webDeploy bypassAgentService="false">
<stagedMigration pkgSource="scripts" />
3. Save the migration.config file.
Related to: Issue 11746
Page Not Found error
A Page Not Found error may occur if you migrate a web site that has:
custom bindings, and
HTTPS/SSL encryption using certificates
The error may occur after you perform an IIS migration and then browse to specific sites.
Resolve this issue as follows. Instructions are for Windows Server 2012.
1. Open InetMgr.exe in the context of the VAA.
2. In IIS Manager, select the web site.
3. In the Actions pane on the right, go to Edit Site|Bindings. The Site Bindings window opens.
4. In the Type menu, select HTTPS and then click Edit...
5. Make sure that the IP Address is correct.
6. Make sure that the SSL Certificate is correct. If the SSL certificate is not correct, you will need to generate a new one.
7. Click OK.
AppZero Troubleshooting Guide
Related to: Issue 11340
Troubleshooting IIS using the migration log
You can show more debug information in the migration.config file in the VAA\scripts folder by setting the tag debugLogs to true.
For example:
<?xml version="1.0" encoding="UTF­8"?>
<migrationManager debugLogs="true" >
ASP.NET 1.1 compatibility issue on Windows 2008 R2 and higher
If you are migrating an application that uses ASP.NET 1.1, a compatibility issue may occur if you run the application on ASP.NET 2.0 on a destination
machine with Windows 2008 R2 or higher.
To resolve this issue, you can try installing ASP.NET 1.1 on the destination manually. AppZero cannot guarantee that this workaround will succeed.
1. Download an install package for the installation of ASP.NET 1.1 at the following address:­ca/download/details.aspx?id=26
2. Download SP1 at the following address:­us/download/details.aspx?id=33
3. Download the SP1 hotfix at the following address:­ca/download/details.aspx?id=2551
A compatibility warning occurs when you download this package.
4. After the installation is complete, open IIS Manager. You will see a new application pool called ASP.NET 1.1.
5. Change the website or application to use this application pool.
Note that an error will occur if you try to access the ASP.NET settings. However, a website should still work.
Related to: Issue 11053
IIS Migration fails due to DependencyCheckFailOnError during Web
Deploy sync
The following error may occur and IIS application migration may fail if your web site or application has an invalid application pool:
Error: The AppPoolNotFound dependency check found the AppPool 'Classic .NET AppPool' to be in use by
the source data but not defined in source data or on the destination computer. Applications referencing
this application pool will have configuration issues.
Error: The synchronization was stopped by the 'DependencyCheckFailOnError' rule because one or more
dependency checks were triggered at the 'Error
Resolve the issue in one of the following ways:
add the missing application pool to the source server configuration, or
modify the web site or application so that it uses an existing application pool
Related to: Issue 9272
HTTP Error 401.1 ­ Unauthorized
When you use the fully qualified domain name (FQDN) or a custom host header to browse a local web site that is hosted on a computer that is running
Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:
HTTP 401.1 0 Unauthorized Logon Failed
This issue occurs when the web site uses Integrated Authentication and has a name that is mapped to the local loopback address. Authentication fails if the
FQDN or the custom host header that you use does not match the local computer name. You only receive this error message if you try to browse the web
site directly on the server. If you browse the web site from a client computer, the web site works as expected.
AppZero Troubleshooting Guide
To resolve this issue, perform one of the workarounds documented here:
Related to: Issue 10617
Web Deployment Agent Service does not start
The Web Deploy Agent may fail to start. You can resolve the issue a number of ways.
Services Time­Out
The Web Deploy Agent may fail to start on a source machine because of a services time­out issue. When a service starts, the service communicates the
time­out period for the service to the Service Control Manager. If the Service Control Manager does not receive a "service started" notice from the service
within this time­out period, the Service Control Manager terminates the process that hosts the service. Services that depend on the Windows Trace Session
Manager service may require more than 60 seconds to start.
To resolve this issue, increase the ServicesPipeTimeout registry value to provide all dependent services enough time to start:
Increase the value to at least 120 seconds:
"ServicesPipeTimeout"=dword:120000 (decimal)
Start or Restart the Service
If the Web Deployment Agent Service (MsDepSvc) does not start, you can try starting or restarting it:
1. Click Start>Services.
2. In the Services window, go to "Web Deployment Agent Service".
3. Right­click the service and select Start or Restart.
Bypass the Web Deployment Agent Service on the Destination Machine
If the service still doesn't start, you can bypass the Web Deployment Agent Service on the destination machine as follows.
DCOM must be enabled on the source machine to bypass the Web Deployment Agent Service.
If DCOM is functional on the source machine
1. Edit c:\appliances\myVAA\scripts\migration.config. Find the following line: <webDeploy bypassAgentService="false" />.
2. Replace "false" with "true".
3. Save the file.
4. Execute appzmigrate.exe.
If DCOM is not functional
1. Edit c:\appliances\myVAA\scripts\migration.config. Find the following line: <webDeploy
bypassAgentService="false" />.
2. Replace "false" with "manual".
3. Save the file.
4. Run the following command on the source:
msdeploy.exe ­verb:sync ­source:metakey=lm/w3svc ­dest:package=c:\,encryptPassword=
[password] ­disableLink:contentExtension
5. Copy c:\ from the source to c:\appliances\myVAA\scripts\ on the destination.
6. Execute appzmigrate.exe.
To Verify the Installation of Web Deploy
To perform a complete test, execute the following commands on the destination machine:
AppZero Troubleshooting Guide
cd C:\Program Files\IIS\Microsoft Web Deploy V3\
msdeploy ­verb:sync ­
source:metakey=lm/w3svc,computername=COMPUTERNAME,userName='USERNAME',password='PASSWORD' ­
dest:metakey=lm/w3svc ­disableLink:contentExtension ­whatif
COMPUTERNAME is the source IP address or hostname
userName is the account with administrator privileges
password is the password for the account
If there are no errors, Web Deploy 3.5 is successfully installed. Note:
Nothing will be modified on either the destination or source machines (due to using the ­whatif flag).
Related to: Issue 11172
Cannot connect to the remote computer
The remote server returns an error:
(404) Not Found. Could not connect to the remote computer ("hostname")
This error occurs if Web Deploy is not installed on the remote computer.
To resolve this issue:
install Web Deploy on the remote computer
make sure that the required process "Web Deployment Agent Service" is started.
You must perform a Complete Install of Web Deploy.
You can install Web Deploy from the following address:­ca/download/details.aspx?id=30436
If Web Deploy is installed but the service cannot be started, use the following alternative method:
On the source machine:
msdeploy ­verb:sync ­source:metakey=lm/w3svc ­dest:package=c:\tmp\,encryptPassword=
[password] ­disableLink:contentExtension
On the destination machine:
copy c:\tmp\ from the source to the destination machine in c:\tmp\
msdeploy ­verb:sync ­source:package=c:\tmp\,encryptPassword=[password] ­
For more information, see:
Versions of .NET Framework do not match
An error occurs if the versions of the .NET Framework Configuration Provider (rootWebConfig32) are different on the source and destination machines.
To resolve this issue, install the missing .NET Framework on the destination machine (if a .NET Framework is missing).
Otherwise, do as follows::
1. On the source machine, go to the following file:
%programfiles%\IIS\Microsoft Web Deploy V3\msdeploy.exe.config
2. In the supportedRuntime version element, change the order of the version of .Net that is specified first. This will indicate the version of .Net that will be
3. On the destination machine, go to the following file and do the same:
AppZero Troubleshooting Guide
%programfiles%\IIS\microsoft web deploy\msdepsvc.exe.config
4. If you modify the file in step 3, you must restart the Web Deployment Agent Service (net stop msdepsvc and net start msdepsvc).
For more information, see:
Error: Appliance doesn't exist or wrong directory
The following error may occur if the appliance does not exist or you specify the wrong directory for the appliance:
System.IO.DirectoryNotFoundException: Could not find a part of the path
To resolve this issue, create the appliance or make sure that the appliance path is correct.
Error: Host not found
The following error may occur if the network name cannot be found:
AppZero.Migrate.CommandException: net use \\hostname\c$ password /user:username has failed! Exit code was: 2
Standard error was: System error 67 has occurred.
The network name cannot be found.
To resolve this issue, specify the IP address of the host instead of the hostname.
Error: Incorrect password
The following error may occur if you specified the incorrect network password:
AppZero.Migrate.CommandException: net use \\hostname\c$ password /user:username has failed! Exit code was: 2
Standard error was: System error 86 has occurred.
The specified network password is not correct.
To resolve this issue, enter the correct password.
Error: Process cannot access a file
The following error occurs:
System.IO.IOException: The process cannot access the file
'C:\Windows\system32\inetsrv\config\\applicationHost.config' because it is being used by another
The error occurs because IIS is using that file. To resolve this issue, run the iisreset command line utility. For more information, see:­bac4­4e1f­bcb6­c52d49c9d7f4.mspx?mfr=true
Error: Server timeout
A request may time out if the tethering process takes a long time. The follow error may occur:
Server Error in '/applicationName' Application.
Request timed out.
To resolve this issue, refresh the web page.
Error when launching SqlWb.exe for SQL Server
This error occurs if the VAA service msftesql fails to start. To resolve this issue, log out of Microsoft Windows and log in again. After you log in
again, the SQL Server VAA will launch correctly.
Related to: Issue 7901
AppZero Troubleshooting Guide
Alfresco VAA fails to run
The alfrescoTomcat­Apache Tomcat 6.0.26 Server service may fail to start when tethered from Windows Server 2003 x86 to Windows Server 2008 R2
x64 due to a Java Virtual Machine memory option setting.
To resolve this issue:
1. Create a new empty VAA.
2. Enable and configure Tether, using the cotf_tomcat6.xml file configuration on the fly file (see below).
3. Dock the VAA.
4. Start VAA services.
cotf_tomcat6.xml file:
<?xml version="1.0" encoding="utf­8"?>
<AppZero feature="config­on­the­fly" version="3.0">
<TARGET folder="\REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun
2.0\alfrescoTomcat\Parameters\Java" entries="*">
<ACTION type="replace">
<ACTION type="replace">
Application fails to run, side­by­side configuration is incorrect
On Windows Server 2008 and later systems, this error may occur if a component is not installed in the first 10 minutes of a Tether copy operation and this
component is required by the application. In this case, the Tether log file may also indicate a missing component.
To resolve this issue:
1. In the Administrative Console, select the VAA and then click Undock.
2. Click Dock.
3. Start all required services.
All components should now be installed.
VAA application doesn't run properly, missing reparse point
This problem may occur if a VAA containing reparse points or symbolic links was created, and then compressed and moved.
To resolve this issue, expand the VAA and then re­create the reparse point in the VAA context.
Copied VAA doesn't run
You must use the appzcreate /C command to copy a VAA to ensure that the VAA copy includes all the information required for it to run
VAA application crashes
If an APPCRASH error occurs, try performing a Microsoft Windows update and then run the VAA again. If the application crashes again after the update,
AppZero Troubleshooting Guide
contact AppZero for assistance.
VAA created from system drive C can't run on destination machine
A VAA created from system drive C can't run on a destination machine with system drive E. AppZero supports the deployment of VAAs where the source
and destination machines have different system drives. However, the destination machine must have a local drive assigned the same drive letter as the
source machine's system drive.
You can use the appzvdrive command to map the system drive from the source machine to a system drive on the destination machine.
For example:
Source machine
Local Drives: C:
System Drive: C:
Destination machine
Local Drives: E:
System Drive: E:
>appzvdrive E:\appliances\<VAA> move c e
As a workaround, you can remap the virtual drive cstore_C to cstore_E by issuing the following command:
>appzvdrive E:\appliances\navicat9 move c e
If the VAA still does not run, the reason could be hardcoded drive references in config files or the registry.
Error "Failed to load dll"
A "Failed to load dll" error occurs when the CPROP_USE_VSXS flag is enabled for some applications. The Virtual SxS feature does not load side­by­side
assemblies embedded in an executable’s manifest. Do not enable Virtual SxS for applications that have embedded manifests.
To view the manifest, use a tool such as ManifestViewer:­view­1­0.aspx
Environment variable doesn't show up
When you use the appzenvedit command to set environment variables in a VAA that is running, the new variable will appear the next time that you
run the VAA.
Undocking an IBM WAS VAA fails
An IBM WebSphere Application Server VAA may fail to undock in the Administrative Console. The service IBMWAS80Service requires more time to
stop than the AppZero undock function allows for.
To resolve this issue, stop the service (and any other IBM WAS services) using the AppZero CLI appzstop command. The VAA will undock
successfully when all services are stopped.
Namespace exclusion filter doesn't work
AppZero Troubleshooting Guide
A namespace exclusion filter must be contiguous with the other filters of the same namespace entity; otherwise, the exclusion filter will not take effect.
For example, in the FileRead namespace array below, the "self: ­\ktest" exclusion filter will not take effect because it is not close to the other two "self"
File Read:
Namespace Drive Filter
I can't delete a VAA
If you cannot delete a VAA folder even after you have rebooted the computer:
1. Check to see if cinit.exe and crun.exe are running in the Windows Task Manager.
2. End those processes and then delete everything in the VAA folder that you can.
3. Restart the computer.
4. Delete the folder.
VAA that is moved loses its share permissions
A VAA that has a folder with sharing enabled may lose its share permissions when you move the VAA to the destination machine. Also, if you delete
share permissions on the underlying operating system on the destination machine, these share permissions are not maintained in the VAA context.
To resolve this issue, recreate the share permissions in the VAA context on the destination machine.
Compressed VAA is larger than the expanded VAA
Compressed VAAs may be larger than expanded VAAs when installer .exe or MSO Cache files are included in the VAA. You should delete installer files
from the VAA file system during the creation process.
Migration of Crystal Reports Server XI R2 fails when using SQL Server
Migration of Crystal Reports Server XI R2 may fail if you migrate to a destination server running Windows Server 2008 or greater, and if the application
is used in combination with SQL Server Database.
The Crystal Reports Server application deploys a service called "BOBJCentralMS Central Management Server (CMS)". After you migrate Crystal Reports
Server to a new operating system, such as Windows Server 2008 or greater, and if the application is used in combination with a SQL Server database, the
service will start and then shut down shortly after starting.
The ODBC database subsystem (odbcdatabasesubsystem.dll) used by this application is not compatible with newer operating systems. Therefore, the
application cannot connect to the database and fails.
AppZero Troubleshooting Guide
The problem does not occur if you use a MySQL database.
Oracle 11g and "Configuration Error" related to Oracle.DataAccess
In some cases, Oracle assemblies responsible for communication between an IIS application and an Oracle database may not be migrated properly.
When you try to migrate and exercise an IIS application that uses an Oracle backend, a "Configuration Error" may be displayed:
Parser Error Message: Could not load file or assembly "Oracle.DataAccess, Version=,
Culture=neutral, PublicKeyToken=[HASH]" or one of its dependencies. The system cannot find the file
Source File: C:\inetpub\wwwroot\[sitepath]\web.config
This can occur if the requested assembly does not exist on either the source or the destination machine, but a policy does exist on the source machine that
would allow another assembly to fulfill the request. For example, the source may possess a "" but not a "". A policy may permit
"" to be loaded in place of "". However, neither the assembly nor the policy are successfully migrated into the VAA.
To resolve the issue, try the following:
1. If the source machine is 32 bit, make sure that the VAA is docked, and then run Internet Information Services (IIS) Manager within the VAA
2. Stop the server by right­clicking it in the Connections pane on the left and selecting Stop.
3. If you click on the Application Pools branch, the migrated application pools should be visible. Identify the application pool corresponding to the
application that is currently experiencing the issue, and then right­click the application and select Stop to stop it.
4. Open Advanced Settings for the application. Under the (General) heading, an option called Enable 32­Bit Applications should be visible. If this
is set to False, set it to True.
5. Restart the application pool and restart the server.
6. Test to determine whether the problem persists.
If this does not apply or does not resolve the issue, you may have to register the assemblies by running a Microsoft utility called gacutil within the VAA
context. The utility is available as part of the Windows SDK. You may need to obtain the appropriate Windows SDK installer from MSDN.
1. Install gacutil.
2. Open the AppZero Command Prompt for the VAA, and navigate to the relevant Publisher Policy folder of the Oracle product. By default, the path
will resemble the following:
c:\app\name\product\version\client\ODP.NET\Publisher Policy\2.x\
3. Register the DLLs contained within this directory using the command gacutil /i. For example:
D:\Oracle\product\11.1.0\client_1\ODP.NET\bin\2.x>"C:\Program Files (x86)\Microsoft
SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\gacutil" /i Oracle.DataAccess.dll
Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.33440
Copyright (c) Microsoft Corporation. All rights reserved.
Assembly successfully added to the cache
4. Repeat this command for each DLL present in the folder. You may need to restart the IIS server for the change to take effect.
Compatibility warning occurs when running the SQL Rehost script
If you are migrating Microsoft SQL Server 2008, SQL Server 2008 R2, or SQL Server 2005 Enterprise Edition or Standard Edition less than version SP4
on Windows Server 2012 R2, Windows may display a compatibility error when you try to execute the SQL rehosting script.
Select Run the Program without getting help and proceed with rehosting anyway; the rehosting script will execute successfully despite the error
Related to: Issue 12067
Java environment variable not recognized when Eclipse is untethered
A Java error may occur when you try to run Eclipse after you disable Tether.
To resolve this issue:
1. Identify the location of javaw.exe on the source machine.
2. Using the Administrative Console or the CLI, re­enable the tether connection for the VAA.
AppZero Troubleshooting Guide
3. In a command prompt window, run javaw.exe.
The Eclipse VAA should run correctly after you un­tether it from the source machine.
To resolve this issue using the CLI:
1. In a command prompt window, type:
appzpedit <appliance> CPROP_USE_TETHER Y
2. When prompted, enter the source machine name and Administrator credentials.
3. Open a command prompt in the VAA context:
appzcmd <appliance>
4. In the command prompt window, type the following:
The missing files with be migrated into the VAA.
Related to: Issue 10503
Crystal Reports 9 does not launch after undock/dock
The following error may occur when you try to run a Crystal Reports 9 VAA after you undock and then dock the VAA:
Crystal Reports: Application Error
Couldn't load keycode.dll
To resolve this issue, run the following in a command prompt window:
cd \windows\syswow64
regsvr32.exe "C:\appliances\ERP2\cstore_C\Program Files\Common Files\Crystal
Related to: Issue 10093
PointBase Examples Server doesn't launch for Oracle Weblogic VAA
To start the PointBase Examples Server, issue the appzrun command as follows from the command line:
appzrun c:\appliances\weblogic c:\bea\wlserver_10.3\common\bin\consolew.exe /k
If a warning is displayed that java.dll and j2RE are not found, Oracle Weblogic will search the default location and Oracle Weblogic will launch.
Ensure that the JAVA_HOME and JDK_HOME environment variables are already defined before you create the VAA.
Google Earth error
An error is displayed when a non­admin user tries to run a Google Earth VAA, due to a firewall access issue.
To avoid this problem, the admin user should open the ports on the firewall before the non­admin user runs the Google Earth VAA.
Class Not Registered Error while testing dissolved application
A Class Not Registered Error may occur during user acceptance testing of a dissolved application. This error may occur because the application was not
exercised sufficiently before it was dissolved on the destination machine.
Resolve this issue as follows:
1. Identify the steps or actions that caused the error.
2. Double­click the Tether Console desktop shortcut. Tether Console opens.
AppZero Troubleshooting Guide
3. Create a new VAA. In the VAA Name field, enter the full path and name of the VAA you want to create.
4. In the Source Name field, specify the IP address or name of the source machine you want to connect to.
5. In the Administrator Password field, type the password of the local administrator account on the source machine you specified in step 4.
6. Click the Start Tether button.
7. Click the Launch Application button to open the AppZero command prompt window.
8. Launch the application in the context of the VAA by entering the launch string in the AppZero command prompt window.
9. Perform the steps or actions that caused the error, as identified in step 1.
10. When Tether Monitor activity stops, click the Finish Tether button.
11. Dissolve the VAA.
12. Restart your machine.
13. Verify that the steps or actions no longer result in an error.
Services do not start and do not display correctly after Dissolve
If you Dissolve a VAA application and then do not restart the destination machine, VAA services may not start; additionally, the service description may
display incorrectly in the Service Control Manager.
To resolve this issue, restart the destination machine after you dissolve the VAA, as per application migration best practices. Services should start
correctly and the service Description should be correct after the restart.
Other Issues
Error with a shared folder
You can store VAAs in any folder on any drive (local or remote). Remote drives can be in the form of a mapped network drive or a UNC (Universal
Naming Convention) path.
If a UNC share requires credentials to gain access, you may experience an error if you add the UNC location to your VAA location list in the
Administrative Console. In this instance, you must access the share using Windows Explorer before you add it to the VAA location list.
IP Address of destination isn't available from VAA or AppZero
Suggested methods for retrieving the destination computer’s IP address in scripts are as follows:
VbScript: (http://mobile.experts­
strcomputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery _
("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")
for each objitem in colitems
strIPAddress = Join(objitem.IPAddress, ",")
IP = stripaddress
wscript.echo ip
Or as a batch script:
FOR /F "tokens=2 delims=:" %%a in (%temp%\TEMPIP.txt) do set IP=%%a
del %temp%\TEMPIP.txt
set IP=%IP:~1%
echo %IP% >%temp%\ip.txt
AppZero Troubleshooting Guide
echo The current IP address is "%IP%"
Browser may crash when starting the browser in the VAA context
Your web browser may crash when you attempt to start the browser in the VAA context via Windows command line start functionality; for example, via
>start http://<localhost:name>.
To resolve this issue, start the web browser from the underlying operating system.
Script executes from the installation directory
Scripts (for instance, AfterDock.cmd) execute from the AppZero installation path (for example, C:\Progam Files\AppZero). You may wish
scripts to execute from the directory in which they exist, such as the VAA’s Scripts directory.
To resolve this issue, define a script’s Home directory. Add the following to the first line of the .cmd file:
cd /d %~dp0
This will change the Home directory to the directory in which the batch file is located.
Can't install AppZero ­ invalid license error
Installing AppZero on the destination machine fails with the following error:
The license entered is not valid for this operating system. Please re­enter a valid license or contact
AppZero for more information.
This error may occur if the Windows AppInit_DLLs functionality is enabled on the destination machine. AppInit_DLLs is a mechanism that allows
all DLLs that are specified by a registry value to be loaded by each Microsoft Windows­based application that is running in the current log in session. The
AppInit_DLLs value is found in the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows
The value AppInit_DLLs (REG_SZ) specifies the list of DLLs to load.
A program specified by this value will be loaded along with AppZero and may interfere with AppZero software and application migrations.
If this error occurs during AppZero installation and the Windows AppInit_DLLs functionality is enabled, disable AppInit_DLLs and then try
installing AppZero again.
For more information about AppInit_DLLs, see:­us/library/windows/desktop/dd744762%28v=vs.85%29.aspx
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF