Member Avatar for garbee

Hi

I am trying to share a drive on my home network. When I try to change the setting to share I get an error message..

"An error occoured while trying to share... . The serever service is not started."

I have never seen this message before. Please help :!:

  • 4 Contributors
  • 4 Replies
  • 190 Views
  • 5 Years Discussion Span
  • Latest Post Latest Post by mac_965

Dani AI

Generated

As reports, the problem is usually fixed by starting the Server service — that was the simplest outcome here. As and noted, that’s the right first step; when the service won’t start or keeps dying, the causes are usually deeper than the Services snap‑in and logs alone. The notes below outline practical next steps and common causes to try if someone reading this finds the Server service won’t stay up.

If the service refuses to start or fails after starting:

  • The Server service (LanmanServer) is implemented by srvsvc.dll and is a core SMB/file‑sharing component; a missing or corrupted DLL will block the service. Use DISM then SFC to repair system files before attempting file replacement. See Microsoft’s guidance for DISM/SFC. (Microsoft: Use the System File Checker tool).
  • Inspect the service configuration and dependencies with sc qc LanmanServer and sc query LanmanServer — that shows the binary, startup type and any dependent services (e.g., SamSs or kernel SMB drivers). The sc qc command is documented by Microsoft. (sc qc documentation).

Common, less-obvious causes:

  • An inaccessible volume referenced in the system PATH can prevent LanmanServer from starting (Microsoft KB explains the symptom and Event ID patterns). (KB: LanmanServer and inaccessible PATH volume).
  • Missing/removed dependencies (for example the Security Accounts Manager) or third‑party security/firewall drivers can also stop the service — repair or restore those components, or temporarily disable third‑party network filters while testing. Microsoft’s service guidance lists Server/SamSs roles and risks when they’re disabled. (Service security guidance).

Quick commands to try (run elevated):

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
sc qc LanmanServer
sc query LanmanServer

If those don’t help, collect the exact service error code or Event Log entry and consult Microsoft Support/forums with that detail. Note: keep SMB exposure limited to the LAN — don’t open file‑sharing ports to the Internet. This thread’s fix was valid for a one‑off; if it recurs, the steps above point to the usual root causes.

Recommended Answers

All 4 Replies

Member Avatar for bentkey

In order to serve anything to anybody, the server service must be running. It is set to run by default on all MS operating systems. If it's not running, then you must determine why it's not. Give us some more information. What operating system are you using? What have you installed or done lately that might have affected it? Have you scanned for viruses and such? If you're running Windows2000 or XP or NT, you can go to Control Panel, Administrative Tools and open Services. Scroll down to the Server service entry and click properties. In startup it should be set for automatic. If it's not, change it. Try clicking the start button to start the service manually and see if it starts or you get an error.

Member Avatar for kc0arf

Hello,

If the service starts up and then dies out, you might be able to look in the Event Viewer, and see if there are log entries associated with your problem. That may hint if something is out of whack or not.

Christian

Member Avatar for garbee

Thanks

My server service is now started. I turned it on through the administrative tools in the control panel. Again thank-you very much.

Member Avatar for mac_965

many thanks ......not my post but it helped me out ......thanks angain ...keep up the good work guys
Mac

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.