cancel
Showing results for 
Search instead for 
Did you mean: 

Transport error 'USER_TMSADM_DENIED'

Former Member
0 Kudos

Short Text

Transport error 'USER_TMSADM_DENIED'

Long Text

Hi,

After a system copy I've been trying to re-establish the transport

system but transports from the refreshed QA system aren't working. When

I run a connection test from the Prod system it gives me the error

message:

'error occured in tms communication of C10'

When I click on that I see the error message 'USER_TMSADM_DENIED'.

I tried resetting the tmsadm user in client 000 for both QA and PROD

but it didn't solve the problem.

We need to be able to move key transports into production asap.

Accepted Solutions (0)

Answers (5)

Answers (5)

0 Kudos

At the same issue it was the SAP-Note 1414256 (1414256 - Changing TMSADM password is too complex) very helpful for me.


Particularly the report TMS_UPDATE_PWD_OF_TMSADM should be started in client 000 and the uniform password should be arranged.

Former Member
0 Kudos

Hi,

Exactly had the same issue, may it's too long for this post to be updated.

I can able to ping with the ipaddress from dev to qas not with the host name.

Added entry of FQDN in host file and it worked for me

Regards,

Rathish

Former Member
0 Kudos

Hi,

After a night on the phone with sap the problem is now resovled. How you may ask?

We changed so much I'm really not sure but here are some tips:

check the tmsadm user on all systems

check the tms* rfcs with both a regular test and an authorization check

ensure the tmsadm user is set to 'system'

Thanks for your help.

Jeff

Former Member
0 Kudos

Hi,

I encountered the same problem after a system copy.

somehow the domain controller generates RFC's with incorrect TMSADM passwords

the TMSADM user got locked everytime in every system in the landscape.

I ended up generating a new password on the domain controller.

alligned this troughout the domain and made sure ive set the password in all TMSADM rfc's too.

As previously said for a regular 3 system landscape this took about 10 to 15 minutes.

9 X RFC

3 x user

After this i could distribute the domain configuration and the TMS is consistent again.

and my TMSADM user doesnt get locked anymore.

if anyone has a hint on why this happens or a more friendly way of solving such issue please reply

Former Member
0 Kudos

HI,

First, you have to delete TP_DOMAIN.PFL from all boxes and also related TMS config files.

Second, you have to login to DEV>stms>you have configure again freshly from DOmain controller to all boxes.

Finally check the tp connect <SID>. if it should work fine, it means,then you dont have any problems.

Regards,

Srini Nookala

former_member192350
Active Participant
0 Kudos

The fastest way is probably to just re-initialize TMS. Log in to each system (DEV, QA, PRD) in client 000 and delete the TMS configuration (tcode STMS, under the Extras menu I believe). Then log in to the domain controller (normally DEV), and create the TMS config, go to each of the other systems and add them, approving on DEV to activate the config, and push it all back out again. It takes about 10 minutes to reinitialize it for a standard 3-system landscape. If you've got 40 clients and a complex set of transport routes, it will take much longer.

Rich