0xc1130002 ошибка кино и тв

• Remove From My Forums

All replies

• Hi,

  According to my research, the Data Sharing Service provides data brokering between applications and it is running as LocalSystem in a shared process of svchost.exe. Other services might run in the same process. If Data Sharing Service fails to load or initialize,
  Windows start up proceeds. Make sure that the DsSvc.dll file exists in the %WinDir%System32 folder.

  Please check if the below link helps:

  Event ID 7023 — Service Stop Operations

  https://technet.microsoft.com/en-us/library/cc756318(v=ws.10).aspx

  Best Regards,

  Alvin Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

  • Proposed as answer by

    Friday, March 24, 2017 9:01 AM

• Hi,

  Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

  Best Regards,

  Alvin Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• I am getting the same error message on startup with Windows Server 2016 1607 Build 14393.693 (a Hyper-V Server under Windows 10 1607 Build 14393.969 used for development with Visual Studio 2017 and IIS).  %WINDIR%System32dssvc.dll exists.  It
  is «polluting» my event log with errors (3 times):

  The description for Event ID 7023 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
  computer.

  If the event originated on another computer, the display information had to be saved with the event.

  The following information was included with the event: 

  Data Sharing Service
  %%3239247874

  The locale specific resource for the desired message is not present

  I would like to eliminate this error but want to follow best practices on doing so.   This same error message appears if I manually try to start the Windows Service
  Data Sharing Service.  Its startup mode is «Manual (Trigger Start)».  It is logging on as Local System.  I have seen a couple of posts to this with information such as its purpose is «Provides data brokering between
  applications.».  This information is available in the Description of the Windows service.  What appears to be absent is how to eliminate.  Having Server Manager, on startup, show a slew of errors causes us to ignore errors, which is a poor
  habit.

• +1 on this. SFC /scannow turns up nothin’.

  I have spent the past few days wrestling with WS16 with what feels to be a corrupted install for both my local host machine (Hyper-V for VS2017 development, exactly as RaceH20) and also for a WS16Essentials installed as a guest.  Both have had numerous
  DCOM issues where the Network Service/System do not have permissions to services they supposedly own.  Looking into the ACLs, there are orphaned entries from what seems to be former accounts by the same name.

  This is especially troubling as these installs are only a few weeks old.

• Yeah, pretty annoying.

  Get this error on multiple WS 2016 installations, even on clean installs without Domain/GPO.

  Every time the DsSvc starts, the SCM 7023 is reported, with the above mentioned Data Sharing Service 3239247874 Error. When started manually the DsSvc fails to start with the message: 0xc1130002: 0xc113002

  €: If started via cmd, it says «File not Found»

  Since the service fails to start, I consider to set it to «disabled». It seems like a new service introduced in WS2016. Since most services are related to the -oh so great- MS Store, and the stupid MS Apps, I believe this service is pretty unnecessary. 

  Any other thoughts on this?

  €2:

  So, if you run it as its own process, it starts fine.

  run in cmd: sc config DsSvc type= own

  • Edited by
    Alexander Schnitter
    Tuesday, May 9, 2017 1:22 PM
  • Proposed as answer by
    LukaszH
    Thursday, December 28, 2017 9:04 AM

• Yeah that’s great info Alexander.   Thanks for sharing.  I just now got it as well with a new update.  However, that was previous to the install.  I will keep an eye on it and update here if it still occurs.

  The update was released 2 days ago it seems:

  https://support.microsoft.com/en-us/help/4019472/windows-10-update-kb4019472

  Not sure if it has anything to do with this.  What I have done is:

  • Install «clean» (as you note above it is nothing but) from MSDN ISO (date 1/17/17).
  • Get all updates (several rounds)
  • Mount ISO, select «Download updates»
  • Install again, keeping nothing

  This seems to be better for me, but again still getting some errors.  Since I am doing some «real life» work currently I was able to keep this install with an uptime of 2 days, with 0 errors.  The party seems to happen upon reboots, which
  have also been good.  But for some reason this one poked its head up again.

• +1 for me too, exactly the same symptoms as RaceH20. Mine is on a VMWARE ESXi5.5 host and also W2016.

  I am running Exchange server on this platform and don’t especially want to disable the service, as this server is part of a DAG cluster so does need to share data, and with such scant details from MS about what this service does I would rather not disable
  it.

• Ran sc config DsSvc type= own. This fixed my issue with this service not starting properly.
  

• Please do not confuse my «works at MS» status as meaning anything even approaching that I have a clue about what’s actually going on with this…

  I see the same thing having upgraded a VM from Server 2012 R2 to Server 2016.

  DSSVC does seem to be new with Win10 and Server2016. At least it doesn’t show on another very similar VM that I haven’t yet upgraded. And it does show on a Win10 machine. However, on Win10 (according to sc query dssvc) it’s of type «30  WIN32»
  and on Server2016 it’s of type «20  WIN32_SHARE_PROCESS». Hmm.

  I tried sc config dssvc type= (all of the options) & sc query dssvc on Server16 looking for an option that would cause the type to match the 30  WIN32 from Win10. Nothing matched.

   type= own does seem to leave the service able to run, but it results in type: 10  WIN32_OWN_PROCESS. So. Not quite as tidy as one might hope.

• I wonder if option 30 WIN32 is actually 10 <logical OR> 20, sort of ‘both’ WIN32_SHARE_PROCESS and WIN32_OWN_PROCESS. I tried setting type= own and type=share at the same time and consecutively. No love. Also guessed that maybe «type= adapt»
  meant this, but it gave errors. Still mystified. Although I just typed «sc config dssvc type= own» on my two DCs and will probably move on to worry about other things …

• I’m getting the same on one of my own WS 2016 test boxes…

  Seemed to happen right after some Windows Update services became active:

  The Windows Update service entered the running state.
  The Update Orchestrator Service for Windows Update service entered the running state.
  The Windows Insider Service service entered the running state.
  The Data Sharing Service service entered the stopped state.

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

  (in this sequence in the span of about 2 seconds)

  «Data Sharing» makes me think it’s either related to MS telemetry features, or it’s part of the peer-2-peer «delivery optimization» windows update sharing thing.  In which case, I don’t care if it fails.  If it’s purpose is
  to share between local apps, like patching common libraries and components, that sounds more important.

• You may want to take a look at this post -> http://www.neighborgeek.net/2017/05/server-2016-data-sharing-service.html

  Solution is located further down the page:

  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

  • Proposed as answer by
    Mac MacAnanny
    Monday, November 26, 2018 9:20 PM

• Sc config ualsvc type=own

  Sc config dssvc type=own

  Thank you hutcha! It works!

  ---

  Yuriy

• Hi Hutcha,

  worked for me in Windows Server 2016 using «Sc config dssvc type=own».

  Thank you and kind regards

  Peter

  • Edited by
    Peter Klötzer
    Tuesday, May 8, 2018 7:53 AM

• A year later and this problem still exists. We have a one month old Windows Storage Server 2016 Workgroup edition that’s running natively on Lenovo server / Intel hardware and it just did this for the second time this month. This is a
  fresh install and all this server is doing is serving up data, no extra software on this, nothing questionable, no monitoring apps, no managed services apps, it’s just a file server…

  I suppose this is the new world order where Microsoft is more concerned about cloud services than stable servers…

  I’ve implemented the suggested solution by hutcha and I will report back if it doesn’t work. Thanks hutcha.

• Alexander this is solid work.  Thank you very much — solved a lingering problem.

• Maybe a little overkill, but i have 90+ DCs in my 3 forests.  I run this from an admin PowerShell prompt in each domain to fix all of the DCs in that domain, maybe it’ll help others out too.   Was feeling kinda lazy, and had another engineer
  who needed an example of how to pass variables in to a scriptblock for invoke-command, so i came up with this as a way to kill two birds, one stone.

  Haven’t even hit the member servers yet, but this was my main focus, I guess you can change the $dcs = (Get-ADDomain).ReplicaDirectoryServers line to create your list of 2016 servers, ie… query operatingSystem against computer objects in AD.  Hope
  someone finds it usefull, cuz this still exists in the OCT 2018 Rollup for 1607.

  Also being lazy, i didn’t bother looking up the powershell equivalent for SC… lol

  <#REFERENCE
  
  https://blogs.technet.microsoft.com/ralphkyttle/2015/06/04/powershell-passing-parameters-as-variables-using-remote-management-and-invoke-command/
  
  #>
  FUNCTION Set-DASSVC_UALSVC_SCConfig {
  
  PARAM(
  [string]$dc, 
  [string]$svc
  )
          
  
          $ScriptBlockContent = {
              hostname
              $service = $args[0]
                  cmd /c sc config $service type=own
                  cmd /c net stop $service
                  cmd /c net start $service
              }
              Invoke-Command -ComputerName $dc -ScriptBlock $ScriptBlockContent -ArgumentList $svc
          }
  
  $services=@("ualsvc", "dssvc")
  $dcs = (Get-ADDomain).ReplicaDirectoryServers 
  
  foreach($DC in $DCS)
      {
          foreach($SVC in $services)
          {
          Set-DASSVC_UALSVC_SCConfig  $dc $svc
          }
      }

  • Edited by
    Mac MacAnanny
    Monday, November 26, 2018 9:29 PM

• Yeah, pretty annoying.

  Get this error on multiple WS 2016 installations, even on clean installs without Domain/GPO.

  Every time the DsSvc starts, the SCM 7023 is reported, with the above mentioned Data Sharing Service 3239247874 Error. When started manually the DsSvc fails to start with the message: 0xc1130002: 0xc113002

  €: If started via cmd, it says «File not Found»

  Since the service fails to start, I consider to set it to «disabled». It seems like a new service introduced in WS2016. Since most services are related to the -oh so great- MS Store, and the stupid MS Apps, I believe this service is pretty unnecessary. 

  Any other thoughts on this?

  €2:

  So, if you run it as its own process, it starts fine.

  run in cmd: sc config DsSvc type= own

  Your command worked for me! Thanks!

• Remove From My Forums

All replies

• Hi,

  According to my research, the Data Sharing Service provides data brokering between applications and it is running as LocalSystem in a shared process of svchost.exe. Other services might run in the same process. If Data Sharing Service fails to load or initialize,
  Windows start up proceeds. Make sure that the DsSvc.dll file exists in the %WinDir%System32 folder.

  Please check if the below link helps:

  Event ID 7023 — Service Stop Operations

  https://technet.microsoft.com/en-us/library/cc756318(v=ws.10).aspx

  Best Regards,

  Alvin Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

  • Proposed as answer by

    Friday, March 24, 2017 9:01 AM

• Hi,

  Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

  Best Regards,

  Alvin Wang

  ---

  Please remember to mark the replies as answers if they help.
  If you have feedback for TechNet Subscriber Support, contact
  tnmff@microsoft.com.

• I am getting the same error message on startup with Windows Server 2016 1607 Build 14393.693 (a Hyper-V Server under Windows 10 1607 Build 14393.969 used for development with Visual Studio 2017 and IIS).  %WINDIR%System32dssvc.dll exists.  It
  is «polluting» my event log with errors (3 times):

  The description for Event ID 7023 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
  computer.

  If the event originated on another computer, the display information had to be saved with the event.

  The following information was included with the event: 

  Data Sharing Service
  %%3239247874

  The locale specific resource for the desired message is not present

  I would like to eliminate this error but want to follow best practices on doing so.   This same error message appears if I manually try to start the Windows Service
  Data Sharing Service.  Its startup mode is «Manual (Trigger Start)».  It is logging on as Local System.  I have seen a couple of posts to this with information such as its purpose is «Provides data brokering between
  applications.».  This information is available in the Description of the Windows service.  What appears to be absent is how to eliminate.  Having Server Manager, on startup, show a slew of errors causes us to ignore errors, which is a poor
  habit.

• +1 on this. SFC /scannow turns up nothin’.

  I have spent the past few days wrestling with WS16 with what feels to be a corrupted install for both my local host machine (Hyper-V for VS2017 development, exactly as RaceH20) and also for a WS16Essentials installed as a guest.  Both have had numerous
  DCOM issues where the Network Service/System do not have permissions to services they supposedly own.  Looking into the ACLs, there are orphaned entries from what seems to be former accounts by the same name.

  This is especially troubling as these installs are only a few weeks old.

• Yeah, pretty annoying.

  Get this error on multiple WS 2016 installations, even on clean installs without Domain/GPO.

  Every time the DsSvc starts, the SCM 7023 is reported, with the above mentioned Data Sharing Service 3239247874 Error. When started manually the DsSvc fails to start with the message: 0xc1130002: 0xc113002

  €: If started via cmd, it says «File not Found»

  Since the service fails to start, I consider to set it to «disabled». It seems like a new service introduced in WS2016. Since most services are related to the -oh so great- MS Store, and the stupid MS Apps, I believe this service is pretty unnecessary. 

  Any other thoughts on this?

  €2:

  So, if you run it as its own process, it starts fine.

  run in cmd: sc config DsSvc type= own

  • Edited by
    Alexander Schnitter
    Tuesday, May 9, 2017 1:22 PM
  • Proposed as answer by
    LukaszH
    Thursday, December 28, 2017 9:04 AM

• Yeah that’s great info Alexander.   Thanks for sharing.  I just now got it as well with a new update.  However, that was previous to the install.  I will keep an eye on it and update here if it still occurs.

  The update was released 2 days ago it seems:

  https://support.microsoft.com/en-us/help/4019472/windows-10-update-kb4019472

  Not sure if it has anything to do with this.  What I have done is:

  • Install «clean» (as you note above it is nothing but) from MSDN ISO (date 1/17/17).
  • Get all updates (several rounds)
  • Mount ISO, select «Download updates»
  • Install again, keeping nothing

  This seems to be better for me, but again still getting some errors.  Since I am doing some «real life» work currently I was able to keep this install with an uptime of 2 days, with 0 errors.  The party seems to happen upon reboots, which
  have also been good.  But for some reason this one poked its head up again.

• +1 for me too, exactly the same symptoms as RaceH20. Mine is on a VMWARE ESXi5.5 host and also W2016.

  I am running Exchange server on this platform and don’t especially want to disable the service, as this server is part of a DAG cluster so does need to share data, and with such scant details from MS about what this service does I would rather not disable
  it.

• Ran sc config DsSvc type= own. This fixed my issue with this service not starting properly.
  

• Please do not confuse my «works at MS» status as meaning anything even approaching that I have a clue about what’s actually going on with this…

  I see the same thing having upgraded a VM from Server 2012 R2 to Server 2016.

  DSSVC does seem to be new with Win10 and Server2016. At least it doesn’t show on another very similar VM that I haven’t yet upgraded. And it does show on a Win10 machine. However, on Win10 (according to sc query dssvc) it’s of type «30  WIN32»
  and on Server2016 it’s of type «20  WIN32_SHARE_PROCESS». Hmm.

  I tried sc config dssvc type= (all of the options) & sc query dssvc on Server16 looking for an option that would cause the type to match the 30  WIN32 from Win10. Nothing matched.

   type= own does seem to leave the service able to run, but it results in type: 10  WIN32_OWN_PROCESS. So. Not quite as tidy as one might hope.

• I wonder if option 30 WIN32 is actually 10 <logical OR> 20, sort of ‘both’ WIN32_SHARE_PROCESS and WIN32_OWN_PROCESS. I tried setting type= own and type=share at the same time and consecutively. No love. Also guessed that maybe «type= adapt»
  meant this, but it gave errors. Still mystified. Although I just typed «sc config dssvc type= own» on my two DCs and will probably move on to worry about other things …

• I’m getting the same on one of my own WS 2016 test boxes…

  Seemed to happen right after some Windows Update services became active:

  The Windows Update service entered the running state.
  The Update Orchestrator Service for Windows Update service entered the running state.
  The Windows Insider Service service entered the running state.
  The Data Sharing Service service entered the stopped state.

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

  (in this sequence in the span of about 2 seconds)

  «Data Sharing» makes me think it’s either related to MS telemetry features, or it’s part of the peer-2-peer «delivery optimization» windows update sharing thing.  In which case, I don’t care if it fails.  If it’s purpose is
  to share between local apps, like patching common libraries and components, that sounds more important.

• You may want to take a look at this post -> http://www.neighborgeek.net/2017/05/server-2016-data-sharing-service.html

  Solution is located further down the page:

  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

  • Proposed as answer by
    Mac MacAnanny
    Monday, November 26, 2018 9:20 PM

• Sc config ualsvc type=own

  Sc config dssvc type=own

  Thank you hutcha! It works!

  ---

  Yuriy

• Hi Hutcha,

  worked for me in Windows Server 2016 using «Sc config dssvc type=own».

  Thank you and kind regards

  Peter

  • Edited by
    Peter Klötzer
    Tuesday, May 8, 2018 7:53 AM

• A year later and this problem still exists. We have a one month old Windows Storage Server 2016 Workgroup edition that’s running natively on Lenovo server / Intel hardware and it just did this for the second time this month. This is a
  fresh install and all this server is doing is serving up data, no extra software on this, nothing questionable, no monitoring apps, no managed services apps, it’s just a file server…

  I suppose this is the new world order where Microsoft is more concerned about cloud services than stable servers…

  I’ve implemented the suggested solution by hutcha and I will report back if it doesn’t work. Thanks hutcha.

• Alexander this is solid work.  Thank you very much — solved a lingering problem.

• Maybe a little overkill, but i have 90+ DCs in my 3 forests.  I run this from an admin PowerShell prompt in each domain to fix all of the DCs in that domain, maybe it’ll help others out too.   Was feeling kinda lazy, and had another engineer
  who needed an example of how to pass variables in to a scriptblock for invoke-command, so i came up with this as a way to kill two birds, one stone.

  Haven’t even hit the member servers yet, but this was my main focus, I guess you can change the $dcs = (Get-ADDomain).ReplicaDirectoryServers line to create your list of 2016 servers, ie… query operatingSystem against computer objects in AD.  Hope
  someone finds it usefull, cuz this still exists in the OCT 2018 Rollup for 1607.

  Also being lazy, i didn’t bother looking up the powershell equivalent for SC… lol

  <#REFERENCE
  
  https://blogs.technet.microsoft.com/ralphkyttle/2015/06/04/powershell-passing-parameters-as-variables-using-remote-management-and-invoke-command/
  
  #>
  FUNCTION Set-DASSVC_UALSVC_SCConfig {
  
  PARAM(
  [string]$dc, 
  [string]$svc
  )
          
  
          $ScriptBlockContent = {
              hostname
              $service = $args[0]
                  cmd /c sc config $service type=own
                  cmd /c net stop $service
                  cmd /c net start $service
              }
              Invoke-Command -ComputerName $dc -ScriptBlock $ScriptBlockContent -ArgumentList $svc
          }
  
  $services=@("ualsvc", "dssvc")
  $dcs = (Get-ADDomain).ReplicaDirectoryServers 
  
  foreach($DC in $DCS)
      {
          foreach($SVC in $services)
          {
          Set-DASSVC_UALSVC_SCConfig  $dc $svc
          }
      }

  • Edited by
    Mac MacAnanny
    Monday, November 26, 2018 9:29 PM

• Yeah, pretty annoying.

  Get this error on multiple WS 2016 installations, even on clean installs without Domain/GPO.

  Every time the DsSvc starts, the SCM 7023 is reported, with the above mentioned Data Sharing Service 3239247874 Error. When started manually the DsSvc fails to start with the message: 0xc1130002: 0xc113002

  €: If started via cmd, it says «File not Found»

  Since the service fails to start, I consider to set it to «disabled». It seems like a new service introduced in WS2016. Since most services are related to the -oh so great- MS Store, and the stupid MS Apps, I believe this service is pretty unnecessary. 

  Any other thoughts on this?

  €2:

  So, if you run it as its own process, it starts fine.

  run in cmd: sc config DsSvc type= own

  Your command worked for me! Thanks!