,
This tutorial contains instructions to resolve the following error in Server 2016: «The Data Sharing Service service terminated with the following error: %%3239247874» – Event ID 7023.
The Event ID 7023 which appears after every reboot, is a known issue in Server 2016 and occurs because the following two (2) services are trying to start under the same svchost process.
-
- Data Sharing Service
- User Access Logging Service
How to FIX Event ID 7023 in Server 2016: Data Sharing Service service terminated with error %%3239247874.
To resolve the error event 7023 in Server 2016, you have to configure the Data Sharing Service (DsSvc) and the User Access Logging Service (UALSVC), to start to their own svchost process. To do that:
1. Open command prompt as administrator. To do that:
1. In the Search box type: cmd or command prompt
2. Right click on the command prompt (result) and select Run as Administrator.
2. At the command prompt window, type the following two commands in order (press Enter after typing each command:
- Sc config ualsvc type= own
- Sc config dssvc type= own
3. Close Command Prompt and reboot the server, or start the Data Sharing Service manually.
That’s all folks! Did it work for you?
Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.
If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free:
- Author
- Recent Posts
Konstantinos is the founder and administrator of Wintips.org. Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).
Konstantinos Tsoukalas
Konstantinos is the founder and administrator of Wintips.org. Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).
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 |
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
After changing the service configuration, you should now be able to start the Data Sharing Service successfully.
Popular posts from this blog
Mystery Solved: Bitlocker is enabled, but Intune shows the computer as non-compliant for Require Bitlocker
For some time, I have struggled to understand why Intune reports some computers as non-compliant with the «Require Bitlocker» setting, even though Bitlocker is enabled and working on the computer. In my searches for an explanation, I found the same question asked by many others, but never an answer. Until today. I accidentally stumbled across this article from Microsoft’s Rob Lane , which explains how the Require Bitlocker setting is evaluated and why it might seem to incorrectly report a non-compliant state. I encourage you to check out that article for full details. I’ll just summarize here the part that suddenly made this bitlocker compliance issue make sense to me. The «Require Bitlocker» setting in Intune relies on the Device Health Attestation (DHA) service in Windows 10 to report the state of Bitlocker encryption on the computer. If Bitlocker protection is disabled or suspended, DHA will report that the computer is non-compliant with this …
Windows 10 Credential Guard breaks WiFi
Recently, I ran into an issue with computers running windows 10 that would not connect to our WPA2-Enterprise encrypted wifi network. When it failed to connect, there was no indication of why, only the message «Can’t connect to this network.» The computers were able to connect to unencrypted networks and networks using a Pre-shared key for WPA encryption without issue. Checking the event logs on the RADIUS server to see why the comptuer failed to connect, there was no log entry for a connection attempt from the affected system. The WLAN-Auto-Config log on the client listed a couple of errors, including Event ID 11006 and 12013, but other than showing that the failure reason was «Explicit EAP failure received», they didn’t give much to go on: Log Name: Microsoft-Windows-WLAN-AutoConfig/Operational Source: Microsoft-Windows-WLAN-AutoConfig Date: 8/15/2016 1:11:20 PM Event ID: …
среда, 23 августа 2017 г.
Windows Server 2016 Error. Source: Service Control Manager ID: 7023. Data Sharing Service
Ошибка:
Log Name: System
Source: Service Control Manager
Date: 23.08.2017 13:37:01
Event ID: 7023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: exch0.int.firma.ru
Description:
The Data Sharing Service service terminated with the following error:
%%3239247874
Лечение:
cmd (run as admin)
Sc config ualsvc type=own
Sc config dssvc type=own
Источник
http://www.neighborgeek.net/2017/05/server-2016-data-sharing-service.html
1 комментарий:
Every reboot you will see this error 3 times popping up … ?
Service Control Manager Event ID 7023
Message :
Data Sharing Service
%%3239247874
SOLUTION :
1. Run this command :
– sc config DsSvc type=own
2. Next start the service Data Sharing Service and check it runs OK
No errors in the Event Log anymore
Enjoy !
This entry was posted on Wednesday, November 8th, 2017 at 9:11 pm and is filed under Server, Windows. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Provide feedback
Saved searches
Use saved searches to filter your results more quickly
Sign up
Appearance settings