cancel
Showing results for 
Search instead for 
Did you mean: 

Charm - Domain Link connections

ken_halvorsen2
Active Participant
0 Kudos

I have a very puzzling problem trying to setup Charm.

1st the SolMan is setup on a release 701 system while the Satellite systems (R/3 4.7) are on 620.

The original system's transport landscape is Dev - QA - Prd + Trn. There are 3 sandboxes (with a copy from Prd) on VMWare systems.

I'm trying to setup Charm and am having difficulty creating a Domain link between The SolMan and The Dev system.

I'm trying to create it from the SolMan system going to the Dev system. It appears to hang (on the SolMan system), eventually (5 - 6 minutes) giving an error "RFC system error in system/destination TMSADM DEV.EXTCOM, connection to partner 'server:sapgw00' broken / CPIC-CALL ThSAPCMRCV: cmRc=20 thRc=223#CPIC pr

But looking at the STMS from the Dev system, the SolMan does show up. With a blue arrow (waiting for domain link) status. After clicking on the Approve button, It appears to hang then comes withthe same error, but it appears to look normal.

The Link never does show up in the SolMan STMS landscape.

At first I thought it might be the TMSADM automatic password problem. (Capitals vrs lower case) but tested this against one of the Sandbox systems.

So I can create a Domain link from the SolMan (701) to a Sandbox (620) and everything works fine. I can also create a Domain link between the Dev system (620) and the same Sandbox (620) system. But can not create the Domain link between Dev and SolMan.

In the SolMan dev_rd trace record I found the message:

***Log QOI = NiIRead: recv (10053: WSAECONNABORTED: Software caused connection abort)

      • Error = NiIRead: SiRecv failed for hdl 31 / sock 769 (SI_ECONN_BROKEN/10053: ...

Error connection to partner 'hostname:sapgw00' broken

errno 10053

errorno text WSAECONNABORTED: Software caused connection abort

Anyone have any ideas of what I need to do to overcome this error?

I have even turned off the anti virus on both systems, just to check and get the same results.

Ken

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Dear All,

I am also facing an error while creating domain link. I am using solman 7.1 but I am unable to create domain link from any satelite system. please suggest.please find the screenshot of the error.

Thanks

Sajin TS

Former Member
0 Kudos

Dear All,

I am also facing an error while creating domain link. I am using solman 7.1 but I am unable to create domain link from any satelite system. please suggest.please find the screenshot of the error.

Thanks

Sajin TS

ken_halvorsen2
Active Participant
0 Kudos

Hi Sajin

My first guess is Password. Is the TMS system working fine before you tried tying in the SolMan? I seem to remember a problem with older kernels and that the passwords had to be capitalized. But if you had the TMS working before this, it's probably OK.

Next I'd try firewalls. Does there happen to be a firewall blocking communication?

I would also check the services file to make sure the dispatcher, gateway and message ports are open both ways.

Without more information I can't think of anything else right off.

Ken

Former Member
0 Kudos

Hi Ken,

Its really seems to be confusing but i am sure something is messy.

You can go like this way:

1) Check host name of each other(solman.dev) is maintained on both the systems.

2) Create a manual RFC from solman to dev and dev to solman test it!

3) In case 1 and 2 is successful , delete TMS RFcs and create same manually provide your user name and password (Both way you need to create solman to dev and dev to solman)

Revert after applying following these steps.

Regards,

Gagan Deep Kaushal

ken_halvorsen2
Active Participant
0 Kudos

Thanks Gagan

I thought we had overcome the problem, but NO!

1) Check host name of each other(solman.dev) is maintained on both the systems.

As I was checking this out, I noticed a problem while pinging the dev server from SolMan server. We got the network people involved and they disabled the IPV6 in Wondows 2008. Solving that I thought we had it so tried again, but my original problem has not been solved.

2) Create a manual RFC from solman to dev and dev to solman test it!

The RFC,s work both ways. We manually deleted them and recreated them, (Manually entering the TMSADM Password into the RFC each time). We also deleted them and used the STMS - Extras - generate RFC Destinations. Each time re-entering the TMSADM password into the RFCs. All rfc connections test fine.

3) In case 1 and 2 is successful , delete TMS RFcs and create same manually provide your user name and password (Both way you need to create solman to dev and dev to solman)

Recreated but the TMSADM@(sid).DOmain_(sid) & TMSSUP@(sid).Domain_(sid). Then retried creating a Domain link unsuccessfully.

It seems to hang at the time the following message is on the message bar. (sid): Adjust domain EXTDOM. The requesting system hangs, but the requested system has the request show up in STMS. Although it wont allow the approval.

Help?

ken_halvorsen2
Active Participant
0 Kudos

I should also add that we successfully add a Domain Link to a 3rd system from each of these. Meaning a domain link is created between Solman - 3rd & Dev & 3rd. Just not between Solman & Dev.

We've changed the passwords in all of the systems and RFC connections and tested to ensure the Authorization works (We did have to add S_A.SYSTEM profile to the TMSADM user to over come an RFC authorization issue.

Ken

ken_halvorsen2
Active Participant
0 Kudos

FYI, Yes, I believe we've fixed the problem.

The Network team had enabled JumboFrame to a higher MTU than 1500.

They reset it to the default 1500 and flushed the DNS cache. Then we were able to create the Domain link.

The 3rd system that both Solman and Dev could establish the link to did NOT have this feature enabled. But both Solman and Dev did.

We believe this caused our problem.

Ken