Exception during start of deployment for deploy type 'SLP_CTS'

[fredericorocha]

Hello,

When we are trying to transport a MTAR (CAP app) from our Cloud Foundry sub-account dev/qua to the preprod sub-account we are getting the following error message:

"Exception during start of deployment for deploy type 'SLP_CTS': Error during deployment initialization: Not Found"

Any idea of what might be the issue?

Warm regards,

Frederico

[Harald_Stevens]

Hi Frederico,

this error points into the direction that the deploy service in the preprod system could not be reached. Could you please double-check the destination you are using in the definition of the preprod node. The 'Check Connection' should deliver the return code '200':

Kind regards
Harald

[Mujeeb]

Hi,

I am facing this error, what culd be the reason ??

https://deploy-service.cf.eu10-004.hana.ondemand.com/slprot/myorg/myspace/slp

Regards,

Mujeeb

[mirek2]

Hi Frederico,

I had the same issue. In my case it was wrong domain in deploy URL. I wanted to put to eu10 domain, but should be us10. From CI/CD pipeline the output is by service key, so no issue. Here URLs must be double checked.

So briefly:

The error was cause by URL in destination:

https://deploy-service.cfapps.eu10.hana.ondemand.com/slprot/<space-guid>/slp this,

I have put this (right real used:)):

https://deploy-service.cfapps.us10.hana.ondemand.com//slprot/<space-guid>/slp

Now CTMS import from queue is working perfect (MTAR app).

Best Regards,

Mirek

[mirek2]

In the post above URLs should be :

https://deploy-service.cfapps.eu10.hana.ondemand.com/slprot/my-space-guid/slp

https://deploy-service.cfapps.us10.hana.ondemand.com/slprot/my-space-guid/slp

so I used space guid, but can be also org according to SAP manual.
Editor wiped out the <> brackets:)

[manuel_jesus_gamero_parra]

Hi,

I am getting the same error. Any update in this issue?

Thanks,

Manuel.

[fredericorocha]

Hi Harold,

Thank you for your quick and prompt answer.

I tested the destinations and they seem to be OK:

• Node 1 destination:

• Node 2 destination:

Warm regards,

Frederico

[former_member787774]

Hello Frederico,

Did you solve this issue ? We have excatly the same behavior, could not find anything yet.

Regards,

Thomas