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

disp+work unable to access saploc

Hi Experts,

I am faced with a strange issue wherein my dispatcher of SAP R/3 4.7 installed on windows 2003 server is dying down and getting stopped. When I click on the Developer traces in MMC, the message appears

cannot open file \\<hostname>\saploc\<SID>\DVEBMGS<Inst Nr>\work\dev_disp. The system cannot open the file specified.

However, the developer traces of message server can be accessed in saploc. The problem is only faced by disp+work. I recreated the saploc and sapmnt shares, re-registered the services via sapstartsrv.exe but to no resolution.

Please help with this issue.

Regards,

Sourabh Majumdar

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Posted on Nov 27, 2013 at 06:51 AM

    Hi Sourabh

    Off the top of my head if you copy and past \\<hostname>\saploc\<SID>\DVEBMGS<Inst Nr>\work into

    SART -> RUN does it open

    Second i would check the user in the services that is used to startsap if that user has the correct permission in the file system.

    Best Regards

    Marius

    Add a comment
    10|10000 characters needed characters exceeded

    • dev_disp was the file i was talking about,

      is the services running for SAP ?

      if so please stop then and start them again and see if they start correctly, reason for this is that i have had problems in the past where windows corrupts the sapstartsrv.exe and i had to replace the file and then sap started

      can you please upload the dev_ms

  • Posted on Nov 27, 2013 at 07:58 AM

    hi Sourbah,

    Please have look at this SAP Note and thread.

    Note 82751 - Problems with SAP Services & SAP Service Manager

    http://scn.sap.com/thread/1064315

    Please also share the dev_w0.

    Regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Please try the following

      Scenario 3: SAP does not start at all: no message server and no dispatcher

      Symptoms

      The message server and the dispatcher do not start at all in the SAP MMC.

      The following error when trying to view the developer traces within the SAP MMC: The network path was not found.

      No new developer traces written to disk (under the “work” directory.)

      Problem Analysis

      The network shares “saploc” and “sapmnt” do not exist. That explains the “network path not found” message when attempting to view the developer traces within the SAP MMC.

      Solution

      Re-create the “saploc” and “sapmnt” network shares. Both need to be created on the \usr\sap directory.

      source : http://sapbasisnotes.blogspot.de/2009/05/sap-startup-problems-in-windows.html

  • Posted on Dec 02, 2013 at 05:34 PM

    Hi,

    I don´t know if you solve this but have you tried to use the "effective permissions" in that windows folder so you can confirm that SAPServiceSID and SIDADM are able to create a file? or have you tried login in like SIDADM and SAPServiceSID and try to create a test file?

    Regards,

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2013 at 03:56 PM

    Please be aware that OLD SAPMMC versions (your's is probably an old one) MMC does only talk COM protocol to the SAPStart service.

    In this versions the SAPMMC does get the name of the developer trace file to open from the services and will then open the file by itself. It then will use above mentioned path to access the file.

    Newer SAPMMC versions are using the soap protocol to comunicate with sapstartsrv. The new versions get the content of the developer trace file using the tcp soap connection of the service.

    So I assume that your post has probably the wrong title and SAPMMC is not able to read dev_disp because it is not able to access the share for any reason.

    Whether the new or the old version is running can be verified by running tcpview.exe from www.sysinternals.com. If the mmc.exe has connections to sapstartsrv.exe using port number 5 13, then it is a new one, if not it is an old one.

    regards

    Peter

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 03, 2013 at 04:35 PM

    Sourabh,

    Just curious as to what prompted the original SAP restart?

    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.