on 02-27-2015 7:35 PM
Hello All,
During enchanced retrofit configuration I am getting into "No export system error" after activating change request management. Everything looks good before activating change request management.
Any idea why this no eport system error occurs?
Regards,
Dheeraj
Hi,
You need to check your logical components in LMDB, quality and test systems should be maintained as target system. You can maintain the system roles there. Development systems will be defined as source system etc.
Recommendation: Before activating charm, run the consistency check on your project.
This should resolve your issue.
Regards
Rishav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Murali,
Looks like you are right, I had some issue distributing configuration of the transport routes in of the system. It throws an error TMSADM login failed.
As Rishi said I have checked the project before activating charm, everything looks good. Once I activate charm I get this export error.
Regards,
Raj
Connection test of TMSADM@<solman SID>.DOMAIN_<solman SID> and TMSADM@<Solman.SID>.EXTDOM RFC are working fine.
Authorization test is failing for both.
Even TMSSUP@<solman SID>.DOMAIN_<solman SID> RFC connection test is working fine but authorization test is failing. Do I need to delete all RFC in managed systems and create / generate new RFC's?
Also, I have one more question. Below is the configuration of transport routes in our landscape. Do I need to include transport group in logical components too?
Transport Routes:
DEV1 - 010 ---> Transport Group ---> QAS1 - 010 ---> VDE(virtual system) - 010 ---> P10 - 010
DEV2 - 010 ---> QAS2 - 010 (Virtual System)
Logical Components:
Logical Component | Dev System | QAS system | PRD system | Retrofit System |
---|---|---|---|---|
Maintenance | DEV1 010 | QAS1 010 | P10 010 | DEV2 010 |
Implementation | DEV2 010 | QAS2 010 |
Please correct me if I am missing something.
Regards,
Raj
Hi,
Check your trusted RFCs, You need to remove the maintained user in trusted rfc at client level.
If trusted RFCs are failing than only TMSSUP rfcs will be called. Maintain the current user settings in trusted RFCs also check the trusted rfc radio button in logon and security. Also make sure you have sufficient authorizations in managed system setup.
Please paste the logical component settings with system role here.
Regards
Rishav
Hi,
System roles looks fine, however can you make the evaluation as target system and then try.
Run the trace on your ID (in managed system), once you are configuring the retrofit, Please can you paste the consistency checks screen shots here. (mainly transport route checks).
Please check for SLG1 logs also. On which version of Solman are you in.
Can you give a look at
1756014 | Harmonizing RFC communication infrastructure for ChaRM Check |
Regards
Rishav
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.