cancel
Showing results for 
Search instead for 
Did you mean: 

We couldn't release any transport request!

Former Member
0 Kudos

Hi experts,

We could't release any transport request on DEV from today.

We could do it until yesterday.

We have never changed any settings.

Except release, we can use SAP system, and

we can import released transport request to QAS .

Also I could tp addtobuffer on DEV.

[Operation]

SE10 -> select transport request -> click [release] button

and, we can see the error message as below.

    • Error Message *****************************************************

Test call of transport control program (tp) ended with return code

****************************************************************************

[Transport Log]

We can see the log as below.

*********************************************************************************************

ERROR: No connect due to DbSl Load Lib Failure

ERROR: environment variable dbms_type is not set.

ERROR: Connect to RDV failed (20090220140504).

ERROR: Connect to RDV failed (20090220140740), failed to read table SVERS.

*********************************************************************************************

[Our Action]

1. Change Environment variable & Restart SAP (note 351586)

2. replace tp & saptrans

3. change parameter (note 175627)

4. add full control to everyone on sap/trans

5. see note 534765,98678,128126,592514,799058,879941,508140,610640

Thank you in advance.

BR,

Toshi

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

It looks like tp can't connect to your DB because it can't find the database library files. Have you logged in with the sidadm account to see if any of the environment variables have been changed (or removed)?

J. Haynes

Former Member
0 Kudos

Hai,

Run R3trans -d and check the log file (Trans.log), also paste the same here.

Check the TP_DOMAIN.pfl file for this entry, DBMS_TYPE= your DB type. for ex., ora,mss,etc.,

Regards,

Yoganand.V

Former Member
0 Kudos

Hi,

Thank you for your reply.

I did r3trans -d, and the result is as belllow.

-


F:\usr\sap\RDV\SYS\exe\run>r3trans -d

This is r3trans version 6.13 (release 640 - 07.01.08 - 14:25:00).

unicode enabled version

2EETW000 sap_dext called with msgnr "2":

2EETW000 -


db call info -


2EETW000 function: db_ntab

2EETW000 fcode: NT_RDTDESCR

2EETW000 tabname: TADIR

2EETW000 len (char): 5

2EETW000 key: TADIR

2EETW000 retcode: 2

r3trans finished (0012).

-


Also I checked TP_DOMAIN.pfl, but it seems that there is no problem.

But I found doubtful point.

It is environmental variable, and now it is differnt from last friday.

Example, last friday , there was variable as bellow,

but today I couldn't find them

In the meantime , I will deal with them.

-


dbms_type=MSS

MSSQL_DBNAME=RDV

MSSQL_SCHEMA=rdv

MSSQL_SERVER=<hostname>\RDV

-


Toshi

Former Member
0 Kudos

Hi,

I added environment variable in system environment variable,

and issue was solved at this moment.

But I couldn't understand ,

As I confirm that last frinday they were set correctly,

today they became clear!

Therefore I doubt that there is something wrong wiht H/W etc.

Anyway the issue was solved,

I close this thread.

Thank you for your kindness help.

Toshi