This page will help in troubleshooting the issue with duplicate versions of Delivery seen in Cast-MS.

Duplicate deliveries can come up in the delivery tab of an application for which a delivered version with a snapshot already exists due to various scenarios similar such as this specific one mentioned below:

• Open Cast-MS and in parallel open a command prompt and execute a CAST-MS-CLI.exe AutomateDelivery with all the appropriate parameters creating a new delivery from the same application. Once this finishes successfully, refresh your view in Cast-MS which will show you the new delivery.
  Now if you exit CMS, saving all. When you reopen CMS you will have your duplicate delivery 
  
  
  
  

This may also result in an error when trying to add a version as shown in the screenshot below:

Step by Step scenario

Since the issue is linked to concurent connection to CAST Management Studio, the step by step scenario can be as follows (other scenarios are possible as well):

1)Deliver V1 through DMT. 
2)In CMS,accept V1 and set it as current version. 
3)Run snapshot for V1. 
4)Leave CMS open. 
5)Open command prompt and run the following: 

CAST-MS-cli.exe AutomateDelivery -connectionProfile "!Name of the profile" -appli "Your Application Name" -version "V2" -fromVersion "V1" -date 20150718 

6)After completion of process, refresh the CMS and check V1 and V2 in delivery tab of CMS 
7)Click Save and close CMS 
8)Again open the CMS and check for duplicate deliveries of V2

Action Plan

To troubleshoot this issue, you need the following Relevant input

1. Remove the duplicate version with respect to their duplicated object_id from the Management base If the query does not return any duplicates then please go to point 2
2. Remove the duplicate version with respect o the duplicated version names
3. Remove any duplicated entries in the application's index.xml file

Relevant input

1. Provide us with the CAST Support Tool (CST) - alias Sherlock
    
2. Screenshot showing the duplicated versions in Cast-MS
   

Action 1

Remove the duplicate version with respect to their duplicated object_id from the Management base

DELETE FROM CMS_PORTF_Version v
WHERE v.Object_ID IN 
(
SELECT d1.Object_ID
--.*
FROM 
(
SELECT v1.* FROM cms_portf_version v1 JOIN cms_portf_version v2 
ON (v1.previousVersion = v2.previousVersion) AND (v1.Object_ID != v2.Object_ID)
) d1
JOIN 
(
SELECT v2.* 
FROM cms_portf_version v1 JOIN cms_portf_version v2 
ON (v1.previousVersion = v2.previousVersion) AND (v1.Object_ID != v2.Object_ID)
) d2
ON (d1.previousVersion = d2.previousVersion) AND (d1.Application_ID=d2.Application_ID) AND (d1.Object_ID < d2.Object_ID)
)

Workaround

Query 1:

delete from CMS_PORTF_Version where object_id not in
(select max(object_id) from CMS_PORTF_Version
group by object_name, application_id);

Query 2:

delete
from CMS_DynamicFields
where Entity_GUID = 'pmcdeliveryunit.ApplicationVersion'
and Object_ID not in (select Object_ID from CMS_PORTF_Version);

select <<MNGT>>.sys_set_option('Enable CMS Lock Management', 'yes')

select <<MNGT>>.sys_remove_option('Enable CMS Lock Management')

Ticket # 4693, 10180, 14642