Windows file server 2019 - Server service not starting - missing dependencies

Milty 1 Reputation point
2021-01-22T19:56:51.733+00:00

Very odd issue - I rebooted a Windows 2019 file server (data drives accessed via iscsi - iscsi is not running locally but via VM host iscsi to SAN). The reboot was required following the install of a Datto backup agent.
End users could not access the data drives - shares.
After a bit of troubleshooting found EV called out the Server service - I attempted to start it but received - rpc service too busy to start - I checked the dependencies for the service on another 2019 server and SMB 2 xxx Driver was not listed. I was able to start the smb driver via a command prompt. I uninstalled the Datto agent. I disabled AV as a precaution - installed Windows updates - uninstalled and installed Windows server feature - file and storage - checked the NIC card for file and print services - rebooted server - server service not started - did not find many relevant hits via Google. After a couple of hours decided to power off this VM and build a new 2019 VM server.
In my spare time I will power on the failing 2019 VM server and continue troubleshooting - seeking advice on next steps.
Thanks,

Milty

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,501 questions
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP
    2021-01-22T20:02:57.347+00:00

    I'd check the event logs for clues but if you think it happened after installing Datto backup agent I'd suggest reaching out to vendor for trouble shooting.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  2. Milty 1 Reputation point
    2021-01-22T20:14:18.087+00:00

    I checked with Datto and the software does not use/affect the server service. I have other 2019 servers running the Datto agent without issue. I think the reboot of the server was the factor that presented the "Server service" issue. The event logs following the reboot time did call out the Server service not starting but no causing factors.

    Thanks,

    Milty

    0 comments No comments

  3. Dave Patrick 426.2K Reputation points MVP
    2021-01-22T20:20:47.077+00:00

    Sounds good, I'd suggest starting a case here with product support.
    https://support.serviceshub.microsoft.com/supportforbusiness

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  4. Milty 1 Reputation point
    2021-01-25T15:28:26.903+00:00

    DSPatrick,

    I am looking to the forum for advice, past experience, support on this issue but not fee based.

    Thanks,

    Milty

    0 comments No comments

  5. Dave Patrick 426.2K Reputation points MVP
    2021-01-25T15:33:00.257+00:00

    Simplest solution may be to stand up a new one, patch fully, migrate the roles or applications over to new one and move on.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments