CTS+ transport gets stuck on "release started"

[tamasszirtes]

Hi,

I have implemented CTS+ for a portal system (close coupling via Transport Organizer). I can create a transport request, but when I release it, it stays on status "release started" for ever and "return code 9997" is displayed in the Transport Organizer.

It is running on EhP1.

The error I get in SLOG is the following:

HALT 20101207133853

ERROR: uncaught internal error:

ERROR: EXIT(16) -> process ID is: 9012

I would appreciate an advice, I went though already the usual notes.

Thanks,

Tamas

[tomas_black · Accepted solution]

Hello Tamas,

this error '9997' is seldom-seen, so you can start by checking and applying the following notes, to make sure your CTS+ environment is up-to-date:

#1172252: CTS+, 'attach file': Troubleshooting Guide;

#1003674: Enhancement for non-ABAP systems in CTS;

#1155884: CTS+, configuration 'close coupling': Troubleshooting guide;

#1139406: CTS+: cx_ai_system_fault when importing requests

#1426622: No deploy step termination in transport for return code 12;

If this does not help, we need to check the trace files generated for this error (which is not specific to the transport itself, as per [this link|http://help.sap.com/saphelp_sm40/helpdata/en/57/38e26c4eb711d182bf0000e829fbfe/content.htm]). So, it's also important to have tp and R3trans tools updated to the very last version available in SAP MarketPlace.

I hope this helps

Best regards,

Tomas Black

[tamasszirtes · Accepted solution]

Hi Tomas,

I went through your ideas, but the issue is still there. What we noticed is that transports in the web ui without attachements can be released. When they have attachments, they cannot be released. On the file system in the transport directory everything looks ok.

Do you have another idea?

Thanks,

Tamas

[Former Member · Accepted solution]

I think you should upfrade your tp version

please read Note 1449610 - tp terminates in function 'tp_search_buffer_entry'

[former_member273752 · Accepted solution]

Hey Tamas,

we are experiencing the same problem. Can you please let us know how this problem was solved in your case?

Thanks and Sincere Regards,

Sid

[tamasszirtes · Accepted solution]

Hi All,

The solution was indeed to upgrade our tp - as suggested by Oren Shem-Tov. Thanks, Oren!

Thanks,

Tamas

[former_member1351189]

Note#1449610 solved the issue

[stphane_ami]

Hi,

I've got the same problem, do you find a solution ?

Thx