Skip to Content

Sapjup cannot find correct shares on Windows 2008 R2 cluster

Hello Guru's,

I have succesfully installed CRM 5 Abap+Java on Windows 2008 R2 based hardware. This is a HA setup.

I am now in the process of upgrading to CRM 7.01. Unfortunately, the java upgrade program SAPjup runs into an error (share
Host_A\sapmnt does not exist) I cannot solve up to now.

This is my setup:

I have two application servers: Host_A and Host_B. Both servers form a Microsoft Failover Cluster. The shared disk for the abap and java central services is the F:\ drive, the cluster name is Cluster_X.

The Central Instance is installed on the local disk G:\ of Host_A; The Dialog instance on local disk G:\ of Host_B.

As instructed in the manual, I have moved the SAP cluster to Host_A and started the the upgrade process on G:\ drive of the same host.

During the phase PREPARE/INIT/INPUT_SAPSERVICESID_PWD_HA, the SAPjup program is trying to map the
Host_A\sapmnt share to a drive letter ('net use' command). This step results in an error.

I can explain this error since the proper share in my opinion should be
Cluster_X\sapmnt instead of

In Windows 2003 this was not a problem, because
Cluster_X\sapmnt and
Host_A\sapmnt can both be accessed and refers to the same disk location when the cluster group is active on Host_A. However, in Windows 2008 R2 this is not the case anymore and
Host_A\sapmnt is not a valid share.

Has any one of you run into this same problem or have suggestions how to solve?

Rob Veenman

SAP Technology.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 18, 2012 at 04:20 PM


    Please check this below SAP note.

    Also provide latest upgrade log files.

    1172679 Troubleshouting MSCS Issues

    Attach the log files or errors from it.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 08, 2012 at 01:30 PM

    I owe you an answer for the issue we had.

    I opened a message with SAP, and got acklowledge that this is indeed a bug in SAPJup. SAP is working on a solution.

    The work around (which was succesful) was as follows:

    1. I moved the SAP Cluster group to Host_B (the DI host).

    2. I created g:\sapmnt on Host_A and copied content from the shared drive

    to this local drive.

    3. I shared diretory g:\sapmnt with share name sapmnt on Host_A and gave

    SAP_<SID>_GlobalAdmin Read/write access.

    Now SAPJup can continue. At the next interrup, you can remove the local directory g:\sapmnt and move the cluster disk back to Host_A.

    I will give an update and close this thread as soon as I get a definitive solution from SAP AG for this issue.

    Rob Veenman

    SAP Technical Consultant.

    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.