Skip to Content
avatar image
Former Member

NW2004s MSCS cluster Logon trouble after failover to second node

I have completed the MSCS cluster install of NW2004S. I have the CI installed on node 1 with system number 00, and DI installed on node 2 with system number 01. When the SAP and DB cluster are assinged to node 1, I can logon via the SAP logon pad with the system number of 00. When I failover to node 2, I have to change the system number in the Logon pad to 01 to be able to sign on. Can someone tell me what I need to change to be able to logon with out making the system number change?

The application server is the cluster name of dpgtqclv. The error I receive is "partner not reached (host dpgtqclv.sap.littelfuse.com, service sapdp01 or spadp00) depending on which node the cluster is assigned to.

Thanks for your help.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Sep 10, 2008 at 08:59 PM

    I found the answer in SAP note 112266. The ABAP central instance (now without the message and enqueue servers) is generally installed locally on one of the cluster nodes with a second, identically configured dialog instance on the remaining cluster node. This means that my CI and DI have the same system number. Now when the cluster moves between nodes, that I can logon without changing the system number in the Logon Pad.

    Add comment
    10|10000 characters needed characters exceeded