STMS Transport Error TMS_TP_SHOW_BUFFER RFC Error

[Former Member]

Hi guys

I have a problem with my solution manager STMS queue. Specifically it will not read the import buffer in the Production system from both the transport domain controller (SMD) and the Production (SMP) System.

See below for screenshot of the error when attempting to access SMP Transport Buffer:

If I attempt a command line "TP Connect SMP" I get the following

D:\usr\sap\trans\bin>tp connect SMP
initial value of NLS_LANG: '<NULL>'
This is tp version 372.05.49 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
Error in TPSETTINGS: transdir not set.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
  error in transportprofil (param missing, unknown,...)

Why it is trying to access E_TPSETTINGS I  don't know (Maybe that is default) - nor do I know where this is set. (Original setup was done by IBM and not touched for ages)

Below is the image containing the transport path diagram:

In this same "transport routes" section If I Click on Configuration then "Check" Then "Request Consistency" For both local and all systems it is fine.

Also doing the same check menu but transport routes it reports everything is fine.

All RFC Connections are fine:

Below is the Transport Tool Configuration Screenshots:

SMP:

SMD

I'm quite at a loss as to where to next for troubleshooting this as everything seems to be in place as it should be??

Cheers

[former_member189725 · Accepted solution]

Can you do a check of the transport directory from STMS for both SMP and SMD ?

STMS -->SYSTEM Overview ->SAP system --> CHECK --> transport directory .

Check if the buffers are accessible for SMP and SMD under /usr/sap/trans/buffer and have the right permission.

Regards

Ratnajit

[Former Member · Accepted solution]

Hi Ratnajit

It appears to definitely be folder permissions on the /usr/sap/trans/buffer folder, I added everyone to have full access and hello, it worked so next is narrowing down the user but that is alot easier than the previous pain