CMS Application - Delivery - Add version - Fatal Error - The application XXX is not binded to the Source Delivery Server
Description
To add the next version of the application,
- Clicked on ‘Add verison’ in the ‘Delivery’ tab
- Gave ‘Name’ as v2
- Clicked on ‘Finish’ in the ‘Add version’ screen
the below error is encountered.
Source Server /
com.castsoftware.mda.validations.ValidationException:Source Server /XXXX-XXXX:
The application ‘XXXX-XXXX’ is not binded to the Source Delivery Server.
Referring to the CAST-MS log file we find the below detailed error corresponding to the GUI:
Error stack trace:
Generate Delivery Configuration for TKB_APP The program jars/MIGR_CMS2DMT.jar has not ended correctly.
Source Server /
com.castsoftware.mda.validations.ValidationException:Source Server /XXXX-XXXX:
The application ‘XXXX-XXXX’ is not binded to the Source Delivery Server.
Observed in CAST AIP
| Release | Yes/No |
|---|---|
| 8.3.x | ✅ |
Observed on RDBMS
This section is not applicable for this page(DMT)
| RDBMS | Yes/No |
|---|---|
| CSS | NA |
Step by Step Scenario
Add the next version of the application,
- Clicked on ‘Add verison’ in the ‘Delivery’ tab
- Gave ‘Name’ as v2
- Clicked on ‘Finish’ in the ‘Add version’ screen
Action Plan
- Open CAST Management Studio
- Check in the preferences the Delivery folder path
- Go the delivery folder
- Open the index file listing all the application and the Management ID.
- Check if the application name is listed in the Index.xml file.
- If it is not listed, that means it has been removed either from AIC Portal or manually.
- If it is listed check if the Management ID is in sync with the Management Database site id of the application:
To get the Management site id, run the following query
set search_path=<management_database>; select * from sys_site;
2. If the ID are not in sync, this is expected behaviour
3. Replace in the index.xml file the Management database id.
**Impact on Analysis Results and Dashboard**
NA
**Notes/comments**
Reference: Webcall-29464
**Related Pages**