We added an dialog abap instance to a system consisting of 3 DI and one CI

[Former Member]

We added an dialog abap instance to a system consisting of 3 DI and one CI.

When trying to switch instance from new instance in sm51 to old instance while being logged to an new instance directly this is possible

However when trying to switch instance in sm51 to new instance while being logged to an old instance this is not possible.

What could be the reason?

[JPReyes · Accepted solution]

Most likely you have not maintained the services and host file to accomodate the new instance in all the rest of the landscape and viceversa.

Regards

Juan

[martin_E]

jan,

My first thought is whether the hostname of the new instance is availble to the old Dialog Instances (via the services file or DNS) ?

Failing that, can you answer these questions...

1) if you use SM51 to connect to an old instance from the new instance, can you then use SM51 to connect back to new instance ?

2) When you access the new system from SM51, how does the logon fail ?

• invalid user / password ?

• Load balancing failure ?

• Connectivity failure ?

You'll probably find the answer to your problem if you investigate down these three lines. However, a more arcane cause could be the network topology...

• Are the instances on the same IP subnet ?

• Are the instances on the same domain or subdomain ?

• Check that there's nothing strange going on with the IP subnet mask.

Good luck