During a TrueSight Server Automation (TSSA) upgrade using the Unified Product Installer (UPI), the upgrade fails with:
Failed to migrate deployment configuration to latest version



Below are the three commonly observed scenarios.

SCENARIO #1 - Deployment Options Migration Failure
'bsainstallupgrade.log' contains messages such as:
(Mar 21 2021 03:39:11.239 PM +1000),SEVERE,com.bmc.install.product.bladelogic.upgrade.mig.DeploymentOptionsMigratorRunner,
  THROWABLE EVENT {Description=[Options migration failed for host [jobserver01].]},
  Throwable=[java.lang.NullPointerException
 com.bmc.install.product.bladelogic.upgrade.mig.DeploymentOptionsMigrator.createNewValueForSpecificCase(DeploymentOptionsMigrator.java:317)
...
(Mar 21 2021 03:39:11.309 PM +1000),SEVERE,com.bmc.install.product.bladelogic.upgrade.BlUpgStatelessConfigurationCreator,
  LOG EVENT {Description=[Pre Upgrade execution could not be completed Successfully. Pre Upgrade Execution Summary:
Configuration Collection: STATUS_SUCCESSFUL
Configuration Migration: STATUS_NOT_ATTEMPTED
Options Migration: STATUS_NOT_ATTEMPTED
Application Server Stop Execution: STATUS_NOT_ATTEMPTED
Database Migration: STATUS_NOT_ATTEMPTED
Persisting Configuration into Database: STATUS_NOT_ATTEMPTED
]}
...
(Mar 21 2021 03:39:11.756 PM +1000),INFO,com.bmc.install.product.bladelogic.task.upgrade.BlUpgCollectPersistConfigErrorsTask,   LOG EVENT {Description=[Validation error],Detail=[Failed to migrate deployment configuration to latest version.<br><b>Remediation steps:</b><br>1. Please refer to the installation log file bsainstallupgrade.log located in the host computer's temporary directory to understand the cause for the deployment migration failure.<br>2. If you are not able to determine the problem from the installation log file, please contact BMC support.
CONFIGURATOR_EXECUTION_FAILED]}

SCENARIO #2 - Database Migration Failure
(Mar 19 2024 12:47:03.487 PM +0800),SEVERE,com.bmc.install.product.bladelogic.upgrade.BlUpgStatelessConfigurationCreator,
  LOG EVENT {Description=[Pre Upgrade execution could not be completed Successfully. Pre Upgrade Execution Summary:
Configuration Collection: STATUS_NOT_ATTEMPTED
Configuration Migration: STATUS_NOT_ATTEMPTED
Options Migration: STATUS_NOT_ATTEMPTED
Application Server Stop Execution: STATUS_NOT_ATTEMPTED
Database Migration: STATUS_FAILED
Persisting Configuration into Database: STATUS_NOT_ATTEMPTED
]}
(Mar 19 2024 12:47:03.487 PM +0800),SEVERE,com.bmc.install.product.bladelogic.task.upgrade.BlUpgPersistConfigurationIntoDatabaseTask,
  THROWABLE EVENT {Description=[Database migration failed.],Detail=[Database migration failed.]}
...

SCENARIO #3 - SQL Server Permission Failure
Error similar to the following appear in the 'bsainstallupgrade.log' during upgrade execution:
The SELECT permission was denied on the object 'sysjobs', database 'msdb', schema 'dbo'

SCENARIO #1 - Deployment Migration Failure

1. Validate appserver-options.properties
- Check the file:
<appserver_install_dir>/NSH/br/deployments/<DeploymentName>/options/appserver-options.properties
- Compare it with the same file from a working Application Server.
- If differences exist, copy the correct version to the problematic server and re-run the upgrade.

2. Check for invalid deployment folders
In:
<appserver_install_dir>/NSH/br/deployments/
Look for unexpected or backup folders such as:
_util
_postmig
Any duplicate deployment folders

Action:
Move these folders out of the directory (after taking a backup) and re-run the UPI upgrade.

Reference Documentation
About Application Server deployments and profiles
Troubleshooting UPI Upgrade issues

SCENARIO #2 & #3 — Database Migration or Permission Failure
If the TSSA database is hosted on Microsoft SQL Server, ensure:

Required SQL Server Roles
The TSSA DB user must have:
- sysadmin (recommended for upgrade)
(If sysadmin is selected, dbcreator is not required.)
- db_owner on the TSSA database
- Sufficient disk space
- Autogrowth enabled on DB files

Steps to Validate SQL Permissions
1. Open SQL Server Management Studio
2. Navigate to:
Database → Security → Logins
3. Open the TSSA DB user properties
4. Under Server Roles, verify:
- sysadmin (preferred)
- OR public + dbcreator
5. Under User Mapping, ensure:
- The TSSA database is mapped
- db_owner is selected

Re-run the upgrade afterwards.

If using Oracle Database
Refer to the Oracle DB permission requirements documented in:
List of required database permissions

Ensure the following are correctly configured:
- Tablespace autogrowth
- Correct grants to the TSSA schema
- Permissions required for schema migration

If the UPI Still Fails
Open a BMC Support case and provide:
- Source → Target TSSA versions
- The 'appserver-options.properties' file from impacted & working servers:
<appserver_install_dir>/NSH/br/deployments/<DeploymentName>/options/appserver-options.properties
- 'bsainstallupgrade.log' from the failing upgrade
- 'blmigration.log' (for Scenario #2)
- Database details (SQL/Oracle, permissions, screenshot of user roles)