TeamWork 64-bit setup workarounds

To install 64-bit support, launch the 64-bit MSI package included on the distribution package. Following are limitations, prerequisites, and workarounds that apply to various scenarios:

• This setup does not install the AutoVue 2D Professional viewer since a 64-bit version is not available. The TeamWork 32-bit version, which does include AutoVue 2D Professional 32-bit, may be installed and run on 64-bit computers if the viewer is required. However, installing both versions can lead to occasional errors if installed on Windows 7 and should be avoided. In such configurations, we recommend installing the AutoVue Client/Server viewer instead as described in the BlueCielo TeamWork Administrator's Guide.
• Installing 32-bit TeamWork components on 64-bit client computers does not install 64-bit application links to support 64-bit authoring applications. To install the 64-bit application links, install them from the 64-bit Windows Installer Package and install the remaining client components from the 32-bit Windows Installer Package or Setup program.
• Before running the TeamWork 32-bit setup program (Setup.exe) on 64-bit computers running Windows XP or Windows Server 2003 or prior Windows versions, download and install Microsoft Core XML Services 6 64-bit (msxml6_x64.msi) from Microsoft if it is not installed already. This component is necessary for proper TeamWork operation or else errors will occur. Installing this component is not necessary on Windows Vista or Windows Server 2008 or higher because it is included with Windows.
• Attempting to install or upgrade a TeamWork application on any 64-bit Windows operating system can fail if a 32-bit version of Application Integration (AMHookTrayU.exe) is already running. The problem occurs when the Select Components page of the Setup program is shown and produces the error "Remote procedure call failed." This can occur when performing a custom installation of an additional product on an existing installation or when modifying an existing installation. This issue does not occur with the initial installation of BlueCielo products, when setup types other than Custom are selected, or with the Windows Installer Packages. To work around the problem, close Application Integration before running any BlueCielo setup programs (setup.exe) on 64-bit Windows computers.