Question Re: STMS error in Technology Q&A

STMS error

Former Member — Tue, 06 Mar 2007 08:20:15 GMT

We have migrated the DEV and QAS system to a new i5 machine from old 720 with V4R4. The new i5 is in V5R4.

We are recreating the STMS for new DEV and QAS. Found out that the STMS is not working eventhough the QFileSRV can link to the correct system.

At OS level I found that the error was E-TPPARAM could npt be opened. TP internal error 0212.

At SAP side, the error is "TMS_MGR_READ_TRANSPORT_QUEUE" -> Transport control program tp could not be started. RFC System Failure TP608.

This error happens even when I try to view the DEV system transport buffer.

The SAP version is 4.0B.

Please advice is anyone has any experince handling this error before.

Thanks

Yuva

Re: STMS error

Former Member — Tue, 06 Mar 2007 12:44:46 GMT

Hello Yuva,

Could it be an authorization issue? I would logon as DEVOFR and DEV<instance> and navigate to the transport host ("qsh" then "cd"), then try to edit/create files.

Best regards,

Victor

Re: STMS error

Former Member — Tue, 06 Mar 2007 20:06:19 GMT

When I did AL11 from SAP, I can view the TPPARAM file without any problem. I've also checked the authority side for the file TPPARAM. It seems to be fine. In fact for testing purposes, I've allowed the PUBLIC access with full capability. The problem still occurs.

I cannot think of anything else at the moment.

Please let me know if you have any sugesstions.

Thanks

Yuva

Re: STMS error

Former Member — Tue, 06 Mar 2007 20:26:00 GMT

Hi Yuva,

are you able to run the following with sidofr ?

cd '/usr/sap/trans/bin'

tp 'connect sid'

(for all sids?)

If not, what is the error ?

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Re: STMS error

Former Member — Tue, 06 Mar 2007 21:50:07 GMT

Hi Volker,

I have performed the TP Connect. Only D01 (Development SID) was successful when I login in Development system with D01OFR. The rest has errors as below:

<b>A) Doing the TP Connect from Development system (Domain Control)</b>

i) D01 = Development SID

tp 'connect D01'

Was successful.

ii) T01 = Test system SID

tp 'connect T01'

Error Message:

This is R340BOPT/TPOS4DB4 version 252.08.36 (release 40B) for DB2/400 databas

ERROR: Connect to T01 failed (20070306132201).

Connect to T01 failed (20070306132201).

TRACE-INFO: 1: [/build/bas/40B/gen/opt/dbssldb4.c,5083] Socket error no. 342

50:.Generic error (SQL0901)

TRACE-INFO: 2:

0.000000

TRACE-INFO: 3: [/build/bas/40B/gen/opt/dbssldb4.c,13422] DB connect failed

TRACE-INFO: 4:

0.000000

TRACE-INFO: 5: [developertrace,0] Tue Mar 6 13:22:01 2007

0.000000

TRACE-INFO: 6: [ ,515] ***LOG BY2=>sql error -901 performing CON

0.000000

TRACE-INFO: 7: [ ,515] ***LOG BY0=>

0.000000

TRACE-INFO: 8: [/build/bas/40B/gen/opt/tpfsacc.c,501] tplock: check con

sistency of semaphore...

TRACE-INFO: 9:

0.000000

TRACE-INFO: 10: [/build/bas/40B/gen/opt/tpfsacc.c,502] /usr/sap/trans/tmp/SL

OG0710.T01.LOC

TRACE-INFO: 11:

0.000000

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0232

tp finished with return code: 232

meaning:

connect failed

<b>B) Doing the TP Connect from T01</b>

i) TP Connect to D01

tp 'connect D01'

This is R340BOPT/TPOS4DB4 version 252.08.36 (release 40B) for DB2/400 databas

/usr/sap/trans/tmp/SLOG0710.D01.LOC: Permission denied.

PANIC --> exiting

/usr/sap/trans/tmp/SLOG0710.D01.LOC: Permission denied.

PANIC --> exiting

/usr/sap/trans/tmp/SLOG0710.D01.LOC is already in use (1), I'm waiting 5 sec

(20070306133412).

/usr/sap/trans/tmp/SLOG0710.D01.LOC: Permission denied.

PANIC --> exiting

Press ENTER to end terminal session.

ii) TP Connect to T01

tp 'connect T01'

This is R340BOPT/TPOS4DB4 version 252.08.36 (release 40B) for DB2/400 databas

E-TPPARAM could not be opened.

EXIT

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0212

tp finished with return code: 212

meaning:

could not access file as supposed

Press ENTER to end terminal session.

Kindly advice.

Thanks

Yuva

Re: STMS error

Former Member — Tue, 06 Mar 2007 23:44:17 GMT

Hi Volker,

Managed to Fix the problem. It was due to DNS setting and the host name.

Thanks for the help.

Best Regards

Yuva