2373829 - Deployment error : Deployment of archive xxx for component xxx is rejected because it is already deployed

While deploying a higher SP release for a component already present on the system using the SUM tool, you see the following errors :

Log name : <path to SUM>/SUM/sdt/log/SUM/TroubleTicket_<xx>.txt

Validation of deployment queue completed with error: Validation finished with error. See log <path to SUM>/sdt/log/SUM/deploy_api.0.log for details.
For more information, see the log file <path to SUM>/sdt/log/SUM/SHOW-VALIDATION-RESULT_02.LOG.

Sep 22, 2016 4:40:15 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Validation of deployment queue completed with error: Validation finished with error. See log <path to SUM>/deploy_api.0.log for details.

The following example shows how to check the log files to confirm the issue.
Note : You may get this issue for any other component as well, and the same solution will apply.

In this example, we assume the case where you have VCMCR4E SP 06 installed on your system, and you are deploying a higher SP release, 07.
You should see errors similar to the following :

Log name : <path to SUM>/SUM/sdt/log/SUM/VALIDATION_RESULTS_<xx>.LOG

Sep 22, 2016 4:40:12 PM [Info  ]: Deployment of archive <path to SUM>/sdt/VCMCR4E07_0-10013150.SCA --> tc~vcm~sdk~app.sda for component sap.com/tc~vcm~sdk~app is rejected because it is already deployed
Sep 22, 2016 4:40:12 PM [Info  ]: Deployment of archive <path to SUM>/sdt/VCMCR4E07_0-10013150.SCA --> tc~vcm~report~crlib~app.sda for component sap.com/tc~vcm~report~crlib~app is rejected because it is already deployed

The CREATE-QUEUE log file should show that there is a higher SP being deployed :

Log name : <path to SUM>/SUM/sdt/log/SUM/CREATE-QUEUE_<xx>.LOG

<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Sep 22, 2016 4:40:00 PM [Info  ]: Target version 740 is higher or equal to 730, SP stack will be used to determine new active usages.
Sep 22, 2016 4:40:00 PM [Info  ]: Saving data model Jump.JSPM.DataModel.xml ...
Sep 22, 2016 4:40:00 PM [Info  ]: Data model Jump.JSPM.DataModel.xml saved.
Sep 22, 2016 4:40:00 PM [Info  ]: Saving data model JUP.J2EE.DataModel.xml ...
Sep 22, 2016 4:40:01 PM [Info  ]: Data model JUP.J2EE.DataModel.xml saved.
Sep 22, 2016 4:40:01 PM [Info  ]: sap.com/VCMCR4E: 2.10.6.0 -> 2.10.7.0 (<path to SUM>/sdt/VCMCR4E07_0-10013150.SCA)

The source and target versions for the component can also be checked in the following log files :

Log name : <path to SUM>/SUM/sdt/log/SUM/DEFINE-TARGET-SOURCE_<xx>.LOG

Sep 22, 2016 4:13:31 PM [Info  ]: File <path to SUM>/sdt/VCMCR4E07_0-10013150.SCA is a valid deployable file archive.
Sep 22, 2016 4:13:31 PM [Info  ]: Basic component properties of SDU file <path toSUM>/sdt/VCMCR4E07_0-10013150.SCA have been read. Component name is sap.com/VCMCR4E, version is 2.10, support package level is 7, patch level is 0, counter is 1000.2.10.7.0.20160513081227.
Sep 22, 2016 4:13:31 PM [Info  ]: Processing subcomponents of component sap.com/VCMCR4E.
Sep 22, 2016 4:13:31 PM [Info  ]: Basic component properties of SDU file DEPLOYARCHIVES/tc~vcm~report~crlib~app.sda have been read. Component name is sap.com/tc/vcm/report/crlib/app and version is 2.10.
Sep 22, 2016 4:13:31 PM [Info  ]: Basic component properties of SDU file DEPLOYARCHIVES/tc~vcm~sdk~app.sda have been read. Component name is sap.com/tc/vcm/sdk/app and version is 2.10.
Sep 22, 2016 4:13:31 PM [Info  ]: Subcomponents of component sap.com/VCMCR4E have been processed.
Sep 22, 2016 4:13:31 PM [Info  ]: File <path to SUM>/sdt/VCMCR4E07_0-10013150.SCA has been analyzed for deployment components.

Log name : <path to SUM>/SUM/sdt/log/SUM/DETECT-SOURCE-COMPONENTS_<xx>.LOG

Sep 22, 2016 4:14:52 PM [Info  ]: Found software component sap.com/VCMCR4E with version 2.10.6.0 with following development components:
Sep 22, 2016 4:14:52 PM [Info  ]: Found development component sap.com/tc/vcm/sdk/app with version 9569989.
Sep 22, 2016 4:14:52 PM [Info  ]: Found development component sap.com/tc/vcm/report/crlib/app with version 9569988.

When you check the SAP_MANIFEST.MF file for both the source and target SP levels, you should see the same keycounter value maintained.
You can obtain the SAP_MANIFEST.MF file as described below :

1. Download and extract the SCAs from the SAP Service Marketplace.
2. Extract the DEPLOYARCHIVES folder.
3. Extract the SDA for the component.
4. Open the SAP_MANIFEST.MF file present in the META-INF folder

For the above example, the Manifest file will look as follows :

File : SAP_MANIFEST.MF for SP 07 :

Manifest-Version: 1.0
Ext-SDM-SDA-Comp-Version: 1
softwaretype: J2EE
...
...
keycounter: 9569989
...
...
compress: true

File : SAP_MANIFEST.MF for SP 06 :

Manifest-Version: 1.0
Ext-SDM-SDA-Comp-Version: 1
softwaretype: J2EE
...
...
keycounter: 9569989
...
...
compress: true

Deployment of a higher SP level for a component which is already present in the system, using the SUM tool

Software Update Manager, deployment, fail, error, rejected, already deployed,  Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch., Contains Aborted deployment component:, Already deployed component has version , KBA , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem