In native HANA development scenarios, migration of HANA Content across systems in your landscape (Development  > Quality > Production) is made simple by the use of Application Life cycle Management tools provided by SAP. There are excellent blogs on SCN that help us understand how to configure and use ALM. SAP NOTE 2159899 does give excellent inputs with respect to various system parameters required to smooth functioning of a ALM.

My attempt here is to share some of the leanings we recently had with respects to a few issues we faced using ALM.  Some of the issues we faced are:


1. Symptom:  Warning appears while attaching a change to a transport.

Warning in Change.png

Root Cause: This is because you have objects in the change that belong to Packages that are not assigned to any Delivery Units. If you proceed without heeding the warning, these objects will not be imported into your target system.

Resolution: Before attaching this change to a transport, assign these packages to a Delivery unit for which the transport route is set up. You can then proceed with attaching the The warning would then disappear.


2. Symptom: A blank popup appears without displaying the list of changes. You will notice an error as shown in the picture below.

– The message reads: “An Internal Error occurred.

– Transport Tab is not a valid tab in the current configuration.Error with Change to TR.png

Root Cause: Looking at the XS Server trace files shows that there is a ‘time out error’ with service ”.

The XSEngine.trc will contain something like this:

[7543]{7543}[-1/-1] 2016-08-xx 13:47:57.991438 i TraceContext    TraceContext.cpp(00923) : UserName=xxxx.ApplicationUserName=xxxx.ApplicationName=sap.hana.xs.lm, ApplicationSource=/sap/hana/xs/lm/core/ChangeMgmt.xsjs?

[7543]{7543}[-1/-1] 2016-08-xx 13:47:57.991435 e xsa:sap.hana.xs. SandBox.cpp(01472) : The execution of the script has exceeded the maximum request runtime.

[7543]{7543}[-1/-1] 2016-08-xx 13:47:57.991775 e XSHttpNetIO      XSHttpConnectionContext.cpp(00067) : exception  1: no.2110005  (Basis/IO/Stream/impl/NetworkChannel.cpp:1423)

    Error during stream send: NetworkChannel::send. Socket state not valid, rc=$sysrc$: $sysmsg$

$NetworkChannel$=

Resolution: We overcame this by increasing the timeout on the server xsengine.ini>max_request_timeout to a suitable value.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply