- 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.
Requires Free Membership to View
When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.
Hannah Smalltree, Editorial Director
TROUBLESHOOTING SAP STARTUP PROBLEMS
Home: Introduction
Scenario 1: Dispatcher does not start due to a port conflict
Scenario 2: Dispatcher dies due to a database connection problem
Scenario 3: SAP does not start at all: no message server and no dispatcher
Scenario 4: Users get 'No logon possible' messages when they attempt to log in
Scenario 5: The message server starts but the dispatcher doesn't
Scenario 6: Work processes die soon after they start
Review: Conclusion and more resources
This was first published in July 2005