cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

TMS Configuration

Former Member
0 Likes
5,107

Hi,

I´ve maked and upgrade of Netweaver 7.01 to Netweaver 7.3. After upgrade I cannot configure the TMS configuration.

I´ve deleted and reconfigure the TMS configuration several times but always I get the same error.

In the STMS screen appears that the TMS configuration is inconsistent.

If I go to the import queue I can see this:

I´ve executed the Check> Transport Tool and I get this error:

The error message og RFC Ping is the next:

If I go to redistribute the configuration over the system I get this error message:

What can I try to resolve this error?

Many thanks.

View Entire Topic
Former Member
0 Likes

Hi Sergio,

login to 000 client enter stms transaction then go to Extras menu---> click on Delete TMS Configuration.

Use /ndico tcode in stms screen to delete TMS.

it will delete TMS configuration.

Now again configure TMS. go to se06 click on perform post installation actions.

then enter stms and configure stms.

Thanks,

Venkat

Former Member
0 Likes

Thanks Venkat for your answer,

This steps I´ve done several times.

The transaction dico, doesn´t work. I´ve Netweaver 7.3.

I´ve deleted the TMS in the STMS transacction, after I´ve gone to SE06 and choose post installation actions, in this step I get a popup for introduce the password of TMSADM user. The system was and homogeneous system copy and after that I´ve done an upgrade to NW 7.3.

I´ve put the password for TMSADM user and I get the error of The distribution of configuration PCT it´s not possible.

The rfc TMSADM@SID.DOMAIN_SID TMSSUP@SID.DOMAIN_SID was deleted and created with the delete of TMS configuration, the TMSADM user is in the security tab, and test conection is correct.

What can I do?

Many thanks

Former Member
0 Likes

Hi Sergio,

ok do one thing.

delete TMS as i mensioned above in stms tcode and go to os level usr/sap/trans/bin-- delete domain config file and tp files.

then start again fresh. this should work.

Thanks,

Venkat

Former Member
0 Likes

The same problem.

I´ve deleted the TMS configuration and the files under usr/sap/trans/bin, after that I´ve repeated the different steps but I get the same and now only have one file under usr/sap/trans/bin.

What can I try now?

former_member189725
Active Contributor
0 Likes

Please check TMSADM is not locked in client 000. Provide SAP_ALL to the TMSADM temporarily . Set the password of TMSADM in 000.

Try configuring the STMS and also if required set the TMSADM password in TMSADM RFC .

You can use the standard new password.

Regards

Ratnajit

Former Member
0 Likes

Hello Ratnajit,I get the same error

In the TMS Alert viewer appears this messages

former_member189725
Active Contributor
0 Likes

Can you check if the /etc/hosts file are updated properly and also check if /usr/sap/trans has proper permission.

Check if user TMSADM in client 000 is not locked .

Regards

Ratnajit

Former Member
0 Likes

Hello Ratnajit,

In the file hosts appears the FQDN with the correct ip, and the the user sidadm and SAPServiceSID, can read and write in the path usr/sap/trans

The user TMSADM isn´t locked.

When I delete the TMS configuration and go to SE06 I´ve two optios Standard Installation and Database Copy or Database Migration.The system is and Homogeneous system copy with the backup/restore method.What option I´ve to select?

Many thanks

former_member189725
Active Contributor
0 Likes

You need to select database copy or migration.

Also provide full permission to directories under /usr/sap/trans

Regards

Ratnajit

Former Member
0 Likes

Ok, It´s the option that I´ve selected.

The path have the group SAP_LocalAdmin where the users sidadm and SAPServiceSID are included.

This is correct,no?

I´ve executed the commands R3trans.exe -d and tp.exe connect SIDDB and I get this output

Former Member
0 Likes

Hi,

From the logs, I could notice that there must be some problems in the secure storage. Could you please check that as well?

Orelse, please check the RFC of TMS (Authorisation test ) -> If you are getting name or password is incorrect - I would suspect that it must be a problem with the secure storage.

ALso ensure that the transcation secstore --> execute --> all should  state as green.

Regards

Vijay

former_member215961
Contributor
0 Likes

Hi Sergio,

Please follow the sap note:

Note 1532825 - Deleting SECSTORE entries during system export/system copy


Also check if you can import the profiles from active application server from RZ11.

This will solve your error.

Cheers

Former Member
0 Likes

Hello Vijay,

The authorization test is failed and I get the error No RFC authorization for function module RFCPING.

In the secstore the RFC is on green status.

former_member215961
Contributor
0 Likes

Hi Sergio,

Check if you can import the profiles from active application server from RZ11.

Then Delete the STMS configuration and recreate it again.

This will solve your error.

Cheers

Former Member
0 Likes

Hi Sergio,

As suspected, this must be a secstore problem..


Can you please go to the transcation SECSTORE --> and execute it ..

Please paste the output..

Former Member
0 Likes

The output of secstore is

The 1532825 - Deleting SECSTORE entries during system export/system copy was realized after the copy but I´ve problems during the TMS configuration.

Former Member
0 Likes

Hi Sargan,

I´ve followed this note after the system Copy.

And the profiles will be imported correctly.

former_member189725
Active Contributor
0 Likes

Please provide TMSADM user S_A.TMSADM authorization profile and check if that resolves the issue. If you still have authorization issue , temporarily assign SAP_ALL profile till the TMS configuration is completed.

Regards

Ratnajit

Former Member
0 Likes

The user TMSADM have the S_A.TMSADM authorization, and I´ve assigner the SAP_ALL, but I get the same error:

Errors during the distribution of tp configuration.

Former Member
0 Likes

Hi Sergio,

Might be a non sense suggestion , but let we try this one as well,

Can you reset the password of TMSADM ( Password must be in capital letter ) and update the same in RFC's. Then please do check the same of RFCPING status.

Note : I had similar kind of issue earlier - this did the trick indeed. So, I am just wanted you try this as well


Regards

Vijay