none
Storage Service Crash after a few Minutes RRS feed

  • Question

  • Hello all,

    since a few Months my Storage Service from my Server 2016 Essentials crash a few minutes after start (or restart).

    I have searched the internet and the forum and found a lot of infos and try it. But my Exactly problem i did nor found and no Sollutions are working. The Service is on Autostart, the account is the local system account. The error from Eventviewer is :

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> 
      <EventID Qualifiers="49152">7034</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Opcode>0</Opcode> 
      <Keywords>0x8080000000000000</Keywords> 
      <TimeCreated SystemTime="2018-09-24T11:52:11.510183800Z" /> 
      <EventRecordID>244327</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="748" ThreadID="12740" /> 
      <Channel>System</Channel> 
      <Computer>not shown in this log :) </Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data Name="param1">Windows Server Essentials-Speicherdienst</Data> 
      <Data Name="param2">3</Data> 
      <Binary>570073006500530074006F0072006100670065005300760063000000</Binary> 
      </EventData>
      </Event>

    I also found in the Storageservice Log:

    [09/24/2018 13:51:10 3454] [wmain] entered.
    ------------------------------------------------------
    [09/24/2018 13:51:10 3454] [wmain] logging initialized.
    [09/24/2018 13:51:10 3454] [wmain] version 10.0.14393.2273
    [09/24/2018 13:51:10 3454] [wmain] initializing COM.
    [09/24/2018 13:51:10 3454] [InitializeCOM] COM initialized.
    [09/24/2018 13:51:10 3454] [wmain] starting service.
    [09/24/2018 13:51:10 218c] [StorageService] SCM start event.
    [09/24/2018 13:51:10 218c] [StorageService] service status = INIT
    [09/24/2018 13:51:10 218c] [StorageService] service status set to START_PENDING
    [09/24/2018 13:51:10 218c] [StorageService] creating Manager.
    [09/24/2018 13:51:10 218c] ++++ Manager::Manager
    [09/24/2018 13:51:10 218c] [Manager] initializing test hooks.
    [09/24/2018 13:51:10 218c] [TestHook] initialize.
    [09/24/2018 13:51:10 218c] [Manager] initializing SMProxy
    [09/24/2018 13:51:10 218c] ++++ SMProxy::SMProxy
    [09/24/2018 13:51:10 218c] [SMProxy] object created.
    [09/24/2018 13:51:10 218c] ---- SMProxy::SMProxy
    [09/24/2018 13:51:10 218c] [Manager] object created.
    [09/24/2018 13:51:10 218c] ---- Manager::Manager
    [09/24/2018 13:51:10 218c] [StorageService] registering CLSID_Manager.
    [09/24/2018 13:51:10 218c] ++++ Manager::Start
    [09/24/2018 13:51:10 218c] [Manager] starting Manager.
    [09/24/2018 13:51:10 218c] [Manager] initializing VSS writer.
    [09/24/2018 13:51:10 218c] [VssWriter] initializing VssWriter.
    [09/24/2018 13:51:10 218c] ++++ Manager::InitializeProvider
    [09/24/2018 13:51:10 218c] [Manager] initializing service provider.
    [09/24/2018 13:51:10 218c] [Manager] provider initialized.
    [09/24/2018 13:51:10 218c] ---- Manager::InitializeProvider
    [09/24/2018 13:51:10 218c] [Manager] loading server backup disks.
    [09/24/2018 13:51:10 218c] ++++ Manager::LoadServerBackupDisks
    [09/24/2018 13:51:10 218c] [Manager] loading server backup disks.
    [09/24/2018 13:51:10 218c] ---- Manager::LoadServerBackupDisks
    [09/24/2018 13:51:10 28f8] ++++ Manager::VdsEventsThread
    [09/24/2018 13:51:10 1e3c] ++++ Manager::LanShareServiceMonitorThread
    [09/24/2018 13:51:10 1e3c] [Manager] starting folder monitor thread.
    [09/24/2018 13:51:10 218c] ---- Manager::Start
    [09/24/2018 13:51:10 218c] [StorageService] service is running.
    [09/24/2018 13:51:10 19e4] ++++ Manager::WatcherThread
    [09/24/2018 13:51:10 19e4] [Manager] starting watcher thread.
    [09/24/2018 13:51:10 28f8] [Manager] starting VDS events thread.
    [09/24/2018 13:51:10 35c4] ++++ Manager::VdsRegistrationThread
    [09/24/2018 13:51:10 26dc] [Manager] starting folder quota monitor thread.
    [09/24/2018 13:51:10 218c] [StorageService] service status set to RUNNING
    [09/24/2018 13:51:10 35c4] [Manager] registering with VDS proxy.
    [09/24/2018 13:51:10 35c4] ++++ SMProxy::Register
    [09/24/2018 13:51:10 35c4] [SMProxy] registering interface.
    [09/24/2018 13:51:10 35c4] [SMSession] TRACE: AddRef @ 0xdba4ebd0, Ref = 1
    [09/24/2018 13:51:10 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:10 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:11 11b0] ++++ Manager::Advise
    [09/24/2018 13:51:11 11b0] [Manager] registering provider advise interface.
    [09/24/2018 13:51:11 11b0] ++++ Manager::SendEvent
    [09/24/2018 13:51:11 11b0] [Manager] VSSWRITER_INIT event sent.
    [09/24/2018 13:51:11 11b0] ---- Manager::SendEvent
    [09/24/2018 13:51:11 11b0] [Manager] provider advise interface registered, cookie = 0
    [09/24/2018 13:51:11 11b0] ---- Manager::Advise
    [09/24/2018 13:51:12 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:12 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:14 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:14 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:16 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:16 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:18 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:18 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:20 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:20 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:22 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:22 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:25 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:25 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:27 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:27 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:29 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:29 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:31 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:31 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:33 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:33 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:35 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:35 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:37 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:37 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:39 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:39 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:41 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:41 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:43 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:43 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:45 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:45 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:47 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:47 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:49 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:49 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:51 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:51 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:53 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:53 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:55 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:55 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:57 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:57 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:51:59 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:51:59 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:52:01 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:52:01 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:52:03 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:52:03 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:52:05 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:52:05 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:52:07 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:52:07 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:52:09 35c4] [SMUtil] TRACE: TestConnection failed with result 1
    [09/24/2018 13:52:09 35c4] [SMProxy] test MI_Session connection: 0
    [09/24/2018 13:52:11 35c4] ---- SMProxy::Register
    [09/24/2018 13:52:11 35c4] [Manager] ERROR: failed to register Storage management proxy, 0x80004005

    I did not found any Sollution for this Error in the net ( aka Google).

    I have Tryed a lot of sollutions ( Change Reg Entrys, delet GUID and so on) But nothing works.

    The only thing i never Tryed was to reinstall WSE because the is a life System and i wont crash it.

    The Server2016 Essentials runs as a Virtual Machine ( Hyper-V) on a Server 2016 Host.

    Can anyone please help me ?

    Many Thanks and best regards

    Michi


    Monday, September 24, 2018 12:18 PM

All replies

  • hi,

    1 Please check the symptom in a clean boot (refer to windows 10 steps) environment if it is possible. Ensure the latest update has been installed to avoid known issue.
    https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
    2 What's the result when you enter winmgmt /verifyrepository in command prompt(opened as administrator)
    3 can you enter msinfo32 in command prompt and look the os name on hyper-v host?
    4 do you have essentials server backup or only snapshot?



    Tuesday, September 25, 2018 11:51 AM
    Moderator
  • hi,

    1 Please check the symptom in a clean boot (refer to windows 10 steps) environment if it is possible. Ensure the latest update has been installed to avoid known issue.
    https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
    2 What's the result when you enter winmgmt /verifyrepository in command prompt(opened as administrator)
    3 can you enter msinfo32 in command prompt and look the os name on hyper-v host?
    4 do you have essentials server backup or only snapshot?



    Hello,

    1 i have made a clean Boot and i have also checked ybout the updates , i have also initiated a Online Update. Same thing happens. Short after Restart the service Crash and teh log is the same.

    2 The Repository is consent

    3 msinfo32 Name : Microsoft Windows Server 2016 Essentials  Version : 10.0.14393 Build 14393

    4 I use a third party Backup sollution ( Acronis ) but a recovery is not an option. Because the Service is crashing for more than 3 months. And in the meantime a lot of changes was made.

    Thank you for your answer

    Wednesday, September 26, 2018 7:20 PM
  • After the last update, the Error is still Pending. Nobody an idee ?
    Monday, October 15, 2018 1:48 PM
  • Hello,

    i have exactly the same problem. Was it possible for you to fix it ?

    Best Regards

    Michi Haupt

    Wednesday, May 15, 2019 8:13 AM