TMSADM RFC is getting created with Wrong Password

[Former Member]

Hi All,

There is a Stange Problem We are facing while TMS configuration.

We are setting Up TMS as below

Dev -> QA -> Pre Prod -> Prod (With Domain Link)

For the TMSADM Password, We select the second Option ( New Password as per Note...)

TMSADM RFC is working fine from Dev to Prod System.

But it is failing from QA to Prod due to Wrong Password of TMSADM.

Since these RFCs are Autogenerated, they should be generated by Correct password which is not happening.

We Tried Deleting Entire TMS cofiguration along with TMSADM user and rebulding the same. We also tried executing TMS_UPDATE_PWD_OF_TMSADM but still QA to Prod fails.

is there any other place where TMSADM is stored and is not deleting even if we deleted user and TMS Configuration

We also checked SECSTORE but none of the trials solved the issue.

TMS RFC is working fine from Dev to Prod but same

TMS RFC is working fine from QA to Prod

System Details:

SAP_BW 730 patch 4

Did anybody faced such error?
Please Advice

Regards,

Pramod

[manumohandas82 · Accepted solution]

Hi Pramod ,

Also check on the following Note

1568362 - TMSADM password change

use the report TMS_UPDATE_PWD_OF_TMSADM

Thanks ,

Manu

[Former Member]

Hi All,

Thanks for all your suggestions. I have used all these reports already but it did not solved by issue.

Below are the course of activity I did now to solve the problem.

1. Deleted the Domain.pfl and tpparam file.

2. Deleted the RFC that was auto created and was failing.

3. Generated the RFC again from STMS

4. Execute the Report TMS_UPDATE_PWD_OF_TMSADM from Both the Domains (Dev and Prd)

5. RFC are now working fine.

After configuring routes, I see Duplicate copy of TRs coming to Production.

Checking on what the cause it, meanwhile if you faced similar issue , please assist.

Regards,

Pramod

[Former Member]

As a workaround try to change the password in RFC's for distributed system. We also faced this problem, and we manually entered passwords in the RFC's.

[Reagan]

Faced this issue few years ago and the issue was due to some password restrictions or policy enabled on the system. I had to change the password for the TSMADM user on client 000 to a complex one and it helped.

[manumohandas82]

Hi Pramod ,

You said you checked the transaction SECSTORE . Would you mind sending a sceenshot of the same on RFC

HAVE you checked for theUSER-ID tmsadm in 000 client ?

What do you get in the TMS Alerts in STMS ?

Thanks ,

Manu

[hariom_garg]

Hello,

please check if TMSADM user is locked or not or if STMS is setup with password option then reconfigure stms with correct password.

[Former Member]

Hi Hariom,

Thanks for the suggestion, Yes we have already checked that and TMSADM is not locked.

The RFC is working fine for Dev to Prod. It seems QA RFC is not taking the correct password for TMSADM User.

Regards,

Pramod

[hariom_garg]

hi,

could you please check with current user configuration.

[Sriram2009]

Hi Pramod

1.  Is the QAS system has refreshed from production?

2. Could you refer the SAP Notes

       1801805 - Addition of new destinations in TMS_UPDATE_PWD_OF_TMSADM

1691028 - Fix for TMS_UPDATE_PWD_OF_TMSADM

1414256 - Changing TMSADM password is too complex

BR

SS