1. Skip to Menu
  2. Skip to Content
  3. Skip to Footer>

Expert Sessions!

CTS+ Error Scenario # 3

Monday, 18 June 2018 11:10

Symptom : While importing a transport request using CTS+, below mentioned error is thrown (java.lang.IllegalStateException

Reason : Deployment process failed due to unknown state, above error may be thrown with various reasons, in our case there was a space shortage in the drive where the JSPM inbox was configured.

 

Solution : Free up the space by deleting unwanted files in the drive where JSPM inbox is configured (or) configure a different JSPM inbox directory.

 

 

 

{fcomment} {flike}

Share

CTS+ Error Scenario # 3

CTS+ Error Scenarios # 1

Monday, 18 June 2018 11:10

java.rmi.RemoteException

 

When you perform imports using CTS+, you might face many number of issues as the nature of CTS+ setup requires multiple components involvement (i.e. Domain Controller, NWDI, Development, Quality, Production, SDM, Java Engine, etc.,), in this series, we will be discussing about various issues that may occur in CTS+ environment and the steps to be taken to resolve them.

 

 

 

Read more...

CTS+ Error Scenario # 2

Monday, 18 June 2018 11:10

java.rmi.RemoteException:Another Session = [Local port:0, Host:xxxxx, Port:5xx18, SessionID:3] is still valid – cannot create a new one

When deploying the changes using CTS+ there are chances that you encounter the below issue,

 

Steps to Analyse such issues:

 

  • By looking at the error message it is very clear that, there is already a deployment which is already  running or terminated abnormally.
  • Normally if the deployment is running for a longer time say more than 3-4 hours, though the deployment is successful (you can check this using the SDM logs) but this is not getting notified to the transport management system (ABAP System – Solution Manager in this case)
  • If you try to restart the target system / NWDI system / Solution manager system this will not solve this issue.
  • To resolve this issues, you can need to identify where the DeployProxy webservice is running, this is where you would have configured your CTSDEPLOY RFC connection from your ABAP stack.
  • Restart the system where the DeployProxy service is running.

 

 

 

 

 

Restart the transport after the above steps, this should resolve the issue.

 

{fcomment} {flike}

Share

CTS+ Error Scenario # 2

AS Java