CMS Application - Delivery - Add version on Documentation - V2

CMS Application - Delivery - Add version - Fatal Error - An error has occurred while reading the property file localpswds dat Access is denied

Mon, 01 Jan 0001 00:00:00 +0000

Description

In CAST MS, in the delivery tab, when adding a new version, the following fatal error occurs:

An error has occurred while reading the property file: \data{fcbcb54d-abbb-4bd0-b191-d2a2decbed22}\localpswds.dat

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step Scenario

Open CAST MS
Add a new version in CAST MS

Action Plan

The error message is displayed when the file localpswds.dat is not accessible. The file localpswds.dat contains the password used by some type of package that needs password to perform extraction (like SVN, TFS, PL/SQL, SQL Server, …)

CMS Application - Delivery - Add version - Fatal Error - Failed to create temporary file for jnidispatch library - FileNotFoundException

Mon, 01 Jan 0001 00:00:00 +0000

Description

When using CMS, you may get the error:

Failed to create temporary file for jnidispatch library: java.io.FileNotFoundException

as shown in the screenshot below. This has been seen during the accept delivery operation as well as the creating a new version operation in CMS.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

CMS Application - Delivery - Add version - Fatal Error - Failed to delete XXXXX - the directory may be locked by another application

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page provides solution to the error Failed to delete XXXXX - the directory may be locked by another application which is encountered during cleanup source code repositories while “Accept delivery and use it as current version”

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step Scenario

Try to Accept delivery in CMS, for 2nd or higher version

Action Plan

CMS Application - Delivery - Add version - Fatal Error - Invalid delivery dmtcoe

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page explains how to resolve the error message related to invalid delivery resources.

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 a new version
Or open the DMT

Action Plan

This issue occurs when the COE plugins are not installed in the delivery folder.

Add the missing COE plugins in the delivery folder as explained in the documentation : Installing a custom plugin for the DMT

Impact on Analysis Results and Dashboard

CMS Application - Delivery - Add version - Fatal Error - No connection to server

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page provides solution to the version delivery error “No connection to server”, when DMT is launched from start menu.

Also if you try to download JNLP, through AIC portal, then the following error is seen : Unable to launch delivery XXX is encountered.

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

CMS Application - Delivery - Add version - Fatal Error - The application XXX is not binded to the Source Delivery Server

Mon, 01 Jan 0001 00:00:00 +0000

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 / : The application ‘XXXX-XXXX’ is not binded to the Source Delivery 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:

CMS Application - Delivery - Add version - Fatal Error - The Program Delivery Manager Tool has not ended correctly- errorcode - 1000

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page outlines the error that is encountered when we try to accept the delivery or set it as current version.
When you accept the delivery, you might face one of the below mentioned error.

Error 1:

Error 2:

This issue can be countered as per the scenarios explained in the Action Plans.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step scenario

CMS Application - Delivery - Add version - Fatal Error - Content is not allowed in prolog

Mon, 01 Jan 0001 00:00:00 +0000

Description

When adding a new version, the fatal error - Content is not allowed in prolog - occurs in the add version log:

INF: 2023-09-18 13:24:30: Adding version ‘XXX’

INF: 2023-09-18 13:24:30: Running DMT command

Using arguments:

AddVersion

-application: XXX

-oneApplicationMode:

-logFilePath:

-storagePath:

-guid:

-name: XXX

-releaseDate: YYY

-activateDiscoverers: ZZZ

-copySources: false

Error: Internal error occurred.

The application is closing. Call CAST support now providing the log file at C:\Windows\Temp\DMT.log.txt