Data Sharing Service crashes on Windows Server 2016 - Event ID 7023

While troubleshooting an issue recently on a Windows Server 2016 system, I noticed errors on the System event log about the Data Sharing Service crashing.

The Data Sharing Service service terminated with the following error:  %%3239247874
The Data Sharing Service service terminated with the following error: %%3239247874

Searching online for more information about this service and why it might be failing, I came across a lot of people describing similar problems, but the only explanation and solution I found came from this December blog post by Microsoft Japan.    Google translate did a great job making the post understandable to me, but since the information doesn't seem to have been widely publicized I thought I'd share it here to help get the word out.

The Data Sharing Service fails due to a resource conflict with another service included in Server 2016, the User Access Logging Service.  Either one of these services alone will run without issue, but if one is already running and you try to start the other, it will fail.

According to an update to the blog post, Microsoft plans to resolve the issue in a future update to Server 2016, but in the mean time there is a simple workaround that will allow the Data Sharing Service and User Access Logging Service to live in harmony.  The internal resource conflict occurs because the two services are running in a shared process.  By configuring the services to each run in their own process, the conflict is avoided and both services can be running at the same time.  Run these two commands to change the configuration:
Sc config ualsvc type=own
Sc config dssvc type=own

Successful result of SC Commands

After changing the service configuration, you should now be able to start the Data Sharing Service successfully.  


  1. Thanks for sharing that such good information.

  2. I was getting error 2114 when starting the service LanManServer. (File Sharing)

    Then I run Procmon64 for debugging.

    I found an error "NOT FOUND" in registry key.


    This key was empty. I get full key from a running server. After import to registry. I could start service successfully.


Post a Comment

Popular posts from this blog

Windows 10 Credential Guard breaks WiFi

Mystery Solved: Bitlocker is enabled, but Intune shows the computer as non-compliant for Require Bitlocker