Client B is not known to the message server A

[KMK]

Hi,

We have refreshed our server (let's say server A) by data from server B.

After running sm21 on A, we get the msg "Client B is not known to the message server A". It seems somewhere in the configuration of A, the client B has been left and it is not recognized by msg server A.

I checked all profile parameters, sm51, rz04 for operation modes but don't find any traces from client B.

Can anyone help  to let me know where else in configurations I can look for client B ?

Many thanks,

Kamand

[Former Member · Accepted solution]

Hi Kamand,

What is vaue of client A? Is it a 3 digit number ?? If not then doesn't make sense to hide its value as "A".

However I think it  is more like some hostname or IP. If that is the case then try to figure what does this point to ??

In any case please answer my question.

Regards.

Ruchit Khushu

[KMK · Accepted solution]

The <SID> is a 3-char name.

[JPReyes · Accepted solution]

I agree with Ruchit can you post the error in detail?... no point in guessing

Regards, Juan

[KMK · Accepted solution]

Sure, here is the error:

[Thr 01] *** ERROR => MsSClientHandle: C0 (NewServer_BAS_00) send inv_name OldServer_PRD_00 [msxxserv_mt. 4698]

[Thr 01] ***LOG Q0U=> MsSClientHandle, inv_name (OldServer_PRD_00) [msxxserv_mt. 4706]

[Former Member · Accepted solution]

Hi,

Please check OSS note 430896.

Regards.

Ruchit.

[JPReyes · Accepted solution]

You could also check, RZ03, RZ04, RZ12 and SMLG,  for references to old instances.

Regards, Juan

[benoit-schmid · Accepted solution]

Hello Juan,

There is a zombie in rz12:

parallel_generators    OldServer_PRD_00

What should I do with it?

Are there any related action to performs, after deleting this bad rz12 guy?

I have done several refreshes in the past.

But I never had to perform this.

How has this situation occurred?

Thanks in advance for your answers.

[JPReyes · Accepted solution]

Just delete the assigment on the old server and assign the "parallel_generators" to the new server. The Old server will simply disappear, it might ask you to remote logon to the old host, simply ignore that.

No additional actions required

Regards, Juan

[benoit-schmid · Accepted solution]

Hello,

It is done.

Would you know why I did not have to do so in the past refresh?

Thanks in advance for your answer.

[Former Member · Accepted solution]

Hello Benoit,

RZ12 and other txns that Juan has mentioned are pretty regular fare post system refreshes.

So in theory you should do it everytime.

Btw is the error gone now ?? Or still showing up.

Regards.

Ruchit Khushu

[JPReyes · Accepted solution]

I always do it as part of the refresh, so most likely was there but you never noticed

Did that solve the problem in SM21?

Regards, Juan

[KMK · Accepted solution]

Thank you to all. We can  check sm21 tomorrow morning as the error happens following a midnight job. If the error doesn't appear anymore, I will let you know and will close the thread.

Best,

Kamand

[Former Member · Accepted solution]

Well if the job/program using parallel processing then most likely your issue is resolved. Else probably not.

Regards.

Ruchit Khushu

[KMK · Accepted solution]

Hi Juan,

I had to remove the instance left from the old server. By removing the assignment, it came back in RZ12 the day after.

Thank you for your help, the problem is finally solved !

Regards,

Kamand

[JPReyes]

Did you perform you post cloning/refresh activities, like changing the Logical system, fixing TMS, etc....?

Did you check SCC4?

Regards, Juan

[KMK]

yes, we configured logical system names via BDLS.

TMS is rebuilt from scratch.

The output of scc4 is correct.