Use these checks when a migration fails, items are skipped, or the target catalog does not behave as expected.
Connection to Source or Target Fails #
- Confirm the SQL Server instance name and that the server is reachable from the computer running the wizard.
- Test the connection using SQL Server Management Studio from the same computer.
- For SQL Server SSIS Catalog operations, confirm that the running Windows user has the
ssis_adminrole on both source and target SSISDB. - For Azure SSIS IR endpoints, verify the Azure SQL Server hostname and SQL authentication credentials.
Target SSISDB Is Missing or Was Restored from a Backup #
Ensure that an SSIS Catalog already exists on the target. If it does not, create it under Integration Services Catalogs before migration. Restoring an existing SSISDB on the target may lead to unexpected migration or post-migration errors.
Catalog Inspection Reports Issues #
Run the catalog inspection operation before migration and review all warnings and errors it reports. Resolve source configuration problems where possible, then run the inspection again before migrating.
Items Differ Between Source and Target #
Use the source/target comparison view to identify missing or changed items. Green items indicate content present in the source but absent from the target; red items indicate differences; items shown in their original color are identified as unmodified/identical by the comparison. Select only the required items and review the migration summary before proceeding.
Environment Variables or Parameter Values Are Incorrect #
- Review key-value replacement rules and the selected replacement scope.
- Use Suggest to obtain recommendations, then inspect the affected mappings through the Ref column.
- Check whether Overwrite environment variable values is enabled. This setting recreates target variables based on the source and can replace target-specific values.
- For configuration-only migrations, confirm that the project already exists on the target. If it does not, the wizard also migrates the project definition.
SCMW Export or Import Fails #
- Confirm that the selected file path is correct and the file is accessible to the account running the wizard.
- For cross-network transfers, export on a computer with source access, securely transfer the SCMW file, and import it on a computer with target access.
- Remember that SCMW files are not encrypted. Handle files containing sensitive values according to your security policy.
Migration Results Show Warnings or Errors #
After the wizard finishes, inspect the Result column. Successful items are marked Passed. Warnings and errors are available in the tooltip beside the relevant folder or item. Record the affected item and message, correct the underlying issue, and rerun the migration for the required items.
Command-Line Migration Fails #
- Check the executable path and verify that parameter values are correctly quoted.
- Confirm that required parameters for the selected source and target types are present.
- Set
lfdto a known writable directory if you need logs in a specific location. - Review the process exit code:
0indicates success and-1indicates failure.
Script Task Compatibility #
The wizard does not modify the .ispac build during migration. Compatibility of .NET script tasks depends on the source and target SSIS versions. Test the migrated project in the target environment; contact support if you need help validating a specific project.
Contact Support #
If the issue persists, email support@azureops.org with the source/target types, product version, affected catalog item, exact error message, and relevant logs. Do not send passwords or unredacted sensitive values.