Skip to Content
author's profile photo Former Member
Former Member

JSPM in high availability

Dear Friends,

I have installed PI 7.1 in High availability using Microsoft windows MNS based cluster. It was with initial patch level 04 of Netweaver 710.

I have installed SCS, ASCS, Enque Replication Services etc in cluster mode. I have installed primary application server on Node 2 and Additional Application server on Node 1.

Now I installed SP07 using JSPM from my Primary Application server i.e. Node 1. It went successfully and my support Pack level was upgraded to Sp07. But now when I open Java stack in Node 1, It shows only home page using url -

After that if I open any link e.g. UME or NWA, it does not open and throughs following error :


Service cannot be reached

What has happened?

URL call was terminated because the corresponding service is not available.


The termination occurred in system PIP with error code 404 and for the reason Not found.

The selected virtual host was 0 .

What can I do?

Please select a valid URL.

If it is a valid URL, check whether service /wsnavigator is active in transaction SICF.

If you do not yet have a user ID, contact your system administrator.


HTTP 404 - Not found

Your SAP Internet Communication Framework Team


Java is started properly on both the nodes without any error. While it is working fine on Node 2 i.e.

Please suggest ! Do we need to do so special step for installing patch through JSM in High availability setup?

Jitendra Tayal

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2009 at 03:45 PM

    Hi Jitendra,

    While doing a patch upgrade with JSPM in HA scenario, you need to switch off the automatic switchover option because, once the components are deployed, the J2ee gets restarted. If the automatic failover is active, the service gets switched over to the other node.

    In this case, shutdown all the instances and stop the cluster.

    Restart the systems. Start the cluster in the original servers.

    Restart JSPM.

    It should work fine then.

    Let me know if it is helpful.

    Best Regards


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.