6.2

Troubleshooting 7
In addition to reviewing the pre-migration and migration report and log files, use these troubleshooting tips
to help diagnose problems that you might encounter during or after the vRealize Automation migration
process.
This chapter includes the following topics:
n
Cleaning Up Migration Tables in Source 5.2 Database
n
Database Name Mismatch During Pre-Migration
n
User Principals Cannot be Migrated
n
Cannot Connect to Model Manager Web Service
n
Cannot Connect to Remote Server
n
Cannot Create Application Services Reservation
n
Model Manager Web Service is Offline
n
Pre-Migration Fails with a Load Balancer Timeout Error
n
Migration Fails when Port Number is Part of Database Server Address
n
Migration Fails with a Wait Operation Timeout Error
n
Migration Fails with a RepoUtil Assembly Timeout Error
n
Machines Not Visible on Items Page After Migration
n
Reservation Not Available After Migration
Cleaning Up Migration Tables in Source 5.2 Database
The source supported vCloud Automation Center 5.2 version database contains stale migration table data
that is blocking the administrator from successfully rerunning the vRealize Automation pre-migration or
migration task.
Problem
Stale migration tables in the source database can cause several problems. In some cases, pre-migration
or migration fails. In other cases, pre-migration and migration appear to be successful, but managed
machines are not visible in the catalog after migration is finished.
VMware, Inc.
54