Earlier this week, I did a clean install of Windows Server R2 Essentials.  Before performing any setup functions, I installed all of the updates that Windows Update provided.  Now, I am unable to perform any of the Setup functions from the Dashboard.  Each link fails with a different error message.

The probable cause, IMHO, is that the Windows Server Essentials Management Service is not running and can not be forced to start. I get the message "Error 1067: The process terminated unexpectedly".   Can any one help?

Thanks,

Phil

• Marked as answer by Andy QiMicrosoft contingent staff, Moderator Monday, November 04, 2013 5:29 PM

• Marked as answer by Andy QiMicrosoft contingent staff, Moderator Monday, November 04, 2013 5:29 PM

In the services console, for WseMgmtSvc which is the "Log On As" option set to. In a clean Install it should be Set to Local System ideally. If it is set to something else you can change that to "Local System" and attempt to start the service. 

• Edited by Input_Output Monday, November 11, 2013 8:54 PM

• Edited by Input_Output Monday, November 11, 2013 8:54 PM

The only thing I can think of, it hadn't occurred to me before, is that I had added 2 extra hard drives around that time?

Anyway, thanks to Swapnil, who spent several hours remoted onto the machine yesterday, for sorting it out.

Also thanks to Susan for generating the service request at MS.

Still have the problem with the dashboard crashing though!

Currently I am managing Windows Server 2012 Essentials machine which has, on 2 consecutive occasions now, thrown the Essentials Management Service error at me. Both times followed the installation of required updates & a reboot of the system. Both times, as well, this solution worked for me (wbadmin delete catalog). If this happens again, I will be sure to try "wbadmin delete rebuild" to see if there are less destructive methods to this madness.

Is there any hope of Microsoft addressing this issue? I feel that it must be as the result of deploying before a certain set of updates, but cannot be sure without further testing.

Any progress on this issue? I'm seeing the same thing on Windows Server 2012 R2 Essentials. I've installed it 4 times now. The last time I simply did the following:

• Install WS 2012 R2 E on a physical system.
• Disable automatic updates in order to exclude any updates causing the issue.
• Set up Server Backup from the dashboard.
• Initiated a server backup.
• After the server backup completes, restart the computer.

After than point, the Windows Server Essentials Management Service refuses to start. Disabling the backup service or deleting the backup catalog has no effect and there is no way I can figure out how to get it working again.

Below is a list of some error events I see. Thanks in advance for any help with this issue.

I plan to start a 5th install from scratch but this time skip setting up Server Backup in the hope that it is the one and only culprit.

----------------------------------------------------------------

Log Name:      Application
Source:        Application Error
Date:          1/21/2014 12:53:51 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.DOMAIN.local
Description:
Faulting application name: SharedServiceHost.exe, version: 6.3.9600.16384, time stamp: 0x5215ca62
Faulting module name: ServerBeacon.dll, version: 6.3.9600.16384, time stamp: 0x5215f0fe
Exception code: 0xc0000025
Fault offset: 0x0000000000007b94
Faulting process id: 0xa50
Faulting application start time: 0x01cf16eae30c31ba
Faulting application path: C:\Windows\System32\Essentials\SharedServiceHost.exe
Faulting module path: C:\Windows\System32\Essentials\ServerBeacon.dll
Report Id: 212b2fc6-82de-11e3-80ba-002522aa4eaf
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-21T20:53:51.000000000Z" />
    <EventRecordID>1136</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SharedServiceHost.exe</Data>
    <Data>6.3.9600.16384</Data>
    <Data>5215ca62</Data>
    <Data>ServerBeacon.dll</Data>
    <Data>6.3.9600.16384</Data>
    <Data>5215f0fe</Data>
    <Data>c0000025</Data>
    <Data>0000000000007b94</Data>
    <Data>a50</Data>
    <Data>01cf16eae30c31ba</Data>
    <Data>C:\Windows\System32\Essentials\SharedServiceHost.exe</Data>
    <Data>C:\Windows\System32\Essentials\ServerBeacon.dll</Data>
    <Data>212b2fc6-82de-11e3-80ba-002522aa4eaf</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

----------------------------------------------------------------

Log Name:      System
Source:        Service Control Manager
Date:          1/21/2014 1:46:44 PM
Event ID:      7034
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.DOMAIN.local
Description:
The Windows Server Essentials Management Service service terminated unexpectedly.  It has done this 4 time(s).
Event Xml:
<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="2014-01-21T21:46:44.959961600Z" />
    <EventRecordID>2644</EventRecordID>
    <Correlation />
    <Execution ProcessID="540" ThreadID="1732" />
    <Channel>System</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Windows Server Essentials Management Service</Data>
    <Data Name="param2">4</Data>
    <Binary>5700730065004D0067006D0074005300760063000000</Binary>
  </EventData>
</Event>

-------------------------------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-CertificationAuthority
Date:          1/21/2014 12:54:21 PM
Event ID:      46
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      Server.DOMAIN.local
Description:
The "Windows default" Exit Module "Notify" method returned an error. The media is write protected. The returned status code is 0x80070013 (19).  The Certification Authority was unable to send an email notification for EXITEVENT_SHUTDOWN to Unavailable.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-CertificationAuthority" Guid="{6A71D062-9AFE-4F35-AD08-52134F85DFB9}" />
    <EventID>46</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-21T20:54:21.403341700Z" />
    <EventRecordID>1149</EventRecordID>
    <Correlation />
    <Execution ProcessID="1416" ThreadID="1420" />
    <Channel>Application</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData Name="MSG_E_EXIT_ERROR">
    <Data Name="ExitModuleDescription">Windows default</Data>
    <Data Name="MethodName">Notify</Data>
    <Data Name="ErrorCode">0x80070013 (19)</Data>
    <Data Name="param4">The Certification Authority was unable to send an email notification for EXITEVENT_SHUTDOWN to Unavailable.
</Data>
    <Data Name="ErrorString">The media is write protected.</Data>
  </EventData>
</Event>

--------------------------------------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-CertificationAuthority
Date:          1/21/2014 12:55:37 PM
Event ID:      91
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      Server.DOMAIN.local
Description:
Could not connect to the Active Directory.  Active Directory Certificate Services will retry when processing requires Active Directory access.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-CertificationAuthority" Guid="{6A71D062-9AFE-4F35-AD08-52134F85DFB9}" />
    <EventID>91</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-21T20:55:37.416852800Z" />
    <EventRecordID>1153</EventRecordID>
    <Correlation />
    <Execution ProcessID="1432" ThreadID="1436" />
    <Channel>Application</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData Name="MSG_E_DS_RETRY">
  </EventData>
</Event>

• Edited by BitFlipper Tuesday, January 21, 2014 10:07 PM

Any progress on this issue? I'm seeing the same thing on Windows Server 2012 R2 Essentials. I've installed it 4 times now. The last time I simply did the following:

• Install WS 2012 R2 E on a physical system.
• Disable automatic updates in order to exclude any updates causing the issue.
• Set up Server Backup from the dashboard.
• Initiated a server backup.
• After the server backup completes, restart the computer.

After than point, the Windows Server Essentials Management Service refuses to start. Disabling the backup service or deleting the backup catalog has no effect and there is no way I can figure out how to get it working again.

Below is a list of some error events I see. Thanks in advance for any help with this issue.

I plan to start a 5th install from scratch but this time skip setting up Server Backup in the hope that it is the one and only culprit.

----------------------------------------------------------------

Log Name:      Application
Source:        Application Error
Date:          1/21/2014 12:53:51 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.DOMAIN.local
Description:
Faulting application name: SharedServiceHost.exe, version: 6.3.9600.16384, time stamp: 0x5215ca62
Faulting module name: ServerBeacon.dll, version: 6.3.9600.16384, time stamp: 0x5215f0fe
Exception code: 0xc0000025
Fault offset: 0x0000000000007b94
Faulting process id: 0xa50
Faulting application start time: 0x01cf16eae30c31ba
Faulting application path: C:\Windows\System32\Essentials\SharedServiceHost.exe
Faulting module path: C:\Windows\System32\Essentials\ServerBeacon.dll
Report Id: 212b2fc6-82de-11e3-80ba-002522aa4eaf
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-21T20:53:51.000000000Z" />
    <EventRecordID>1136</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SharedServiceHost.exe</Data>
    <Data>6.3.9600.16384</Data>
    <Data>5215ca62</Data>
    <Data>ServerBeacon.dll</Data>
    <Data>6.3.9600.16384</Data>
    <Data>5215f0fe</Data>
    <Data>c0000025</Data>
    <Data>0000000000007b94</Data>
    <Data>a50</Data>
    <Data>01cf16eae30c31ba</Data>
    <Data>C:\Windows\System32\Essentials\SharedServiceHost.exe</Data>
    <Data>C:\Windows\System32\Essentials\ServerBeacon.dll</Data>
    <Data>212b2fc6-82de-11e3-80ba-002522aa4eaf</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

----------------------------------------------------------------

Log Name:      System
Source:        Service Control Manager
Date:          1/21/2014 1:46:44 PM
Event ID:      7034
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.DOMAIN.local
Description:
The Windows Server Essentials Management Service service terminated unexpectedly.  It has done this 4 time(s).
Event Xml:
<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="2014-01-21T21:46:44.959961600Z" />
    <EventRecordID>2644</EventRecordID>
    <Correlation />
    <Execution ProcessID="540" ThreadID="1732" />
    <Channel>System</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Windows Server Essentials Management Service</Data>
    <Data Name="param2">4</Data>
    <Binary>5700730065004D0067006D0074005300760063000000</Binary>
  </EventData>
</Event>

-------------------------------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-CertificationAuthority
Date:          1/21/2014 12:54:21 PM
Event ID:      46
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      Server.DOMAIN.local
Description:
The "Windows default" Exit Module "Notify" method returned an error. The media is write protected. The returned status code is 0x80070013 (19).  The Certification Authority was unable to send an email notification for EXITEVENT_SHUTDOWN to Unavailable.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-CertificationAuthority" Guid="{6A71D062-9AFE-4F35-AD08-52134F85DFB9}" />
    <EventID>46</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-21T20:54:21.403341700Z" />
    <EventRecordID>1149</EventRecordID>
    <Correlation />
    <Execution ProcessID="1416" ThreadID="1420" />
    <Channel>Application</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData Name="MSG_E_EXIT_ERROR">
    <Data Name="ExitModuleDescription">Windows default</Data>
    <Data Name="MethodName">Notify</Data>
    <Data Name="ErrorCode">0x80070013 (19)</Data>
    <Data Name="param4">The Certification Authority was unable to send an email notification for EXITEVENT_SHUTDOWN to Unavailable.
</Data>
    <Data Name="ErrorString">The media is write protected.</Data>
  </EventData>
</Event>

--------------------------------------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-CertificationAuthority
Date:          1/21/2014 12:55:37 PM
Event ID:      91
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      Server.DOMAIN.local
Description:
Could not connect to the Active Directory.  Active Directory Certificate Services will retry when processing requires Active Directory access.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-CertificationAuthority" Guid="{6A71D062-9AFE-4F35-AD08-52134F85DFB9}" />
    <EventID>91</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-21T20:55:37.416852800Z" />
    <EventRecordID>1153</EventRecordID>
    <Correlation />
    <Execution ProcessID="1432" ThreadID="1436" />
    <Channel>Application</Channel>
    <Computer>Server.DOMAIN.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData Name="MSG_E_DS_RETRY">
  </EventData>
</Event>

• Edited by BitFlipper Tuesday, January 21, 2014 10:07 PM

OK after the 5th install of WS 2012 R2 E, I did not set up the server backup this time. All I did was reboot once after the all automated default setup tasks completed, and now I have the same issue once again. This is an absolute clean installation with zero updates, and no configuration changes whatsoever. None of the Essentials dashboard tasks have been configured.

I get the error events shown in the previous post in the following chronological sequence:

1. CertificationAuthority (Could not connect to the AD)
2. Application Error (SharedServiceHost.exe, ServerBeacon.dll crashes)
3. Service Control Manager (Essentials Management Service terminated unexpectedly)

I'm at a loss. I will install all updates now but I have a feeling it isn't going to help since it didn't help in any of the previous installs.

Any help appreciated.

• Edited by BitFlipper Tuesday, January 21, 2014 11:38 PM

OK after the 5th install of WS 2012 R2 E, I did not set up the server backup this time. All I did was reboot once after the all automated default setup tasks completed, and now I have the same issue once again. This is an absolute clean installation with zero updates, and no configuration changes whatsoever. None of the Essentials dashboard tasks have been configured.

I get the error events shown in the previous post in the following chronological sequence:

1. CertificationAuthority (Could not connect to the AD)
2. Application Error (SharedServiceHost.exe, ServerBeacon.dll crashes)
3. Service Control Manager (Essentials Management Service terminated unexpectedly)

I'm at a loss. I will install all updates now but I have a feeling it isn't going to help since it didn't help in any of the previous installs.

Any help appreciated.

• Edited by BitFlipper Tuesday, January 21, 2014 11:38 PM

Email me at susan-at-msmvps.com (change the -at- to @) and how about we get you looked at by support so we can figure out what's going on.

Updates won't help. I'd rather you stop right here and leave the system in it's state so we can see what's going on.

Susan,

OK I was able to cancel the updates before it actually installed anything. I will email you.

Just an update...

Support has been working on this issue for about a week now without much success. While they were using the physical server, I experimented with installing WS 2012 R2 E in a VM, and got the same result with WseMgmtSvc not starting after rebooting.

After some experimentation it became clear that this has something to do with the network, since if I set the VM network to an isolated network, the problem does not reproduce. Change the network to connect to the real network again, and the problem returns.

More testing showed that if I disable IPv6, the problem also no longer reproduces. I have not tried this in the physical server yet but I'm sure I will get the same result. I don't want to change anything on the physical server right now since I don't want to interfere with support's ongoing testing.

Maybe this is some incompatibility with some NICs/routers/switches/repeaters' IPv6 implementations, not sure. 

So, the bottom line is that if you run into this problem, disable IPv6 on the server's NIC if you don't need it, then reboot.

MS support has spent a lot of time narrowing down this issue in my environment. They are taking this seriously and I believe they have a good understanding of the root cause now. I'm sure this issue will be fixed in an upcoming patch.

This has something to do with ServerBeacon.dll crashing when your server is not assigned an IPv6 address. Normally it should be, but in some rare cases it is not (buggy router maybe). The last thing support was trying to determine was why the server is not getting an IPv6 address assigned.

But the ultimate solution would be to fix ServerBeacon.dll to handle this edge case properly.

• Edited by BitFlipper Sunday, March 02, 2014 6:37 PM

MS support has spent a lot of time narrowing down this issue in my environment. They are taking this seriously and I believe they have a good understanding of the root cause now. I'm sure this issue will be fixed in an upcoming patch.

This has something to do with ServerBeacon.dll crashing when your server is not assigned an IPv6 address. Normally it should be, but in some rare cases it is not (buggy router maybe). The last thing support was trying to determine was why the server is not getting an IPv6 address assigned.

But the ultimate solution would be to fix ServerBeacon.dll to handle this edge case properly.

• Edited by BitFlipper Sunday, March 02, 2014 6:37 PM

This has just happened to me on server 2012 Essential R2. Applied latest updates reboot and service not able to start.

What makes it work I'm running software type raid with parity that uses NZFS and its service cannot be started as well, just because of the latest updates. 

Removing  them does not help :(  Not happy at all!

If you scroll back up above the fix was to remove and restore an devices.xml file. 

Susan I think that was tried in my case but it didn't help. In my case, the only thing you had to do after a completely clean installation was to reboot the server and the issue would reproduce. No patches even needed to be installed.

I think this issue specifically happens when no IPv6 address gets assigned to the server for some unknown reason.

• Edited by BitFlipper Sunday, March 16, 2014 4:41 PM

If you scroll back up above the fix was to remove and restore an devices.xml file. 

Susan I think that was tried in my case but it didn't help. In my case, the only thing you had to do after a completely clean installation was to reboot the server and the issue would reproduce. No patches even needed to be installed.

I think this issue specifically happens when no IPv6 address gets assigned to the server for some unknown reason.

• Edited by BitFlipper Sunday, March 16, 2014 4:41 PM

This has just happened to me on server 2012 Essential R2. Applied latest updates reboot and service not able to start.

What makes it work I'm running software type raid with parity that uses NZFS and its service cannot be started as well, just because of the latest updates. 

Removing  them does not help :(  Not happy at all!

Check to see if the server has an IPv6 address assigned. If not, disable IPv6, reboot and see if the problem goes away.

My suspicion is that it wasn't the patches that triggered the issue, but the reboot.

• Edited by BitFlipper Sunday, March 16, 2014 4:44 PM

This has just happened to me on server 2012 Essential R2. Applied latest updates reboot and service not able to start.

What makes it work I'm running software type raid with parity that uses NZFS and its service cannot be started as well, just because of the latest updates. 

Removing  them does not help :(  Not happy at all!

Check to see if the server has an IPv6 address assigned. If not, disable IPv6, reboot and see if the problem goes away.

My suspicion is that it wasn't the patches that triggered the issue, but the reboot.

• Edited by BitFlipper Sunday, March 16, 2014 4:44 PM

I am also getting error 1067, I have disabled IP v6 and have renamed the deviceinfo.xml file and still have the same error 1067 when trying to start the WseMgmtSvc service. Any new development or suggestions on this?

Home user, made the transition from WHS. (Happy for many years)

I had this problem a few times, restored a previous backup as an easy solution but that doesn't work now.
I disabled IPv6, renamed the deviceinfo.xml but without succes.

Is there a fix for this problem yet? I definitely need help because I'm out of ideas.

Home user, made the transition from WHS. (Happy for many years)

I had this problem a few times, restored a previous backup as an easy solution but that doesn't work now.
I disabled IPv6, renamed the deviceinfo.xml but without succes.

Is there a fix for this problem yet? I definitely need help because I'm out of ideas.

Ok this is getting frustrating now. I'm in the same position as kwauters with still no resolve in sight.

is this fixable or is Server 2012 a dud and not worth upgrading to in the work place.

an update to this issue would be welcome.

• Edited by afacciponti Thursday, April 17, 2014 11:49 PM

Home user, made the transition from WHS. (Happy for many years)

I had this problem a few times, restored a previous backup as an easy solution but that doesn't work now.
I disabled IPv6, renamed the deviceinfo.xml but without succes.

Is there a fix for this problem yet? I definitely need help because I'm out of ideas.

Ok this is getting frustrating now. I'm in the same position as kwauters with still no resolve in sight.

is this fixable or is Server 2012 a dud and not worth upgrading to in the work place.

an update to this issue would be welcome.

• Edited by afacciponti Thursday, April 17, 2014 11:49 PM

Well looks like I have the exact same issue now and already had IPV6 disabled in the NIC, so I guess I will have to start trying to figure this out.  Will post back if I can get it working reliably again. 

The server was fine up until I re-IP'd it and installed it in the clients office.  I also changed the IP of the Intel AMT interface for remote management.  Just in case that info is helpful to the debuggers out there in Microsoft land.

I have now tried everything listed above and have even removed the essentials role and attempted to re-install it after a reboot.  When I try to configure essentials experience when it checks the system I get an error saying "The certificate authority is installed on this system".  Well duh.  Either this is a typo in the error message or I will have to turn off the CA next which I am not even sure is possible.  Sure hope someone figures this out soon.  Tomorrow I will try a backup from when the system was working.  Hope it stays working but I am not very confident it will.

BTW the device...xml file gets modified at boot time so restoring it has zero effect.  Once you reboot it just gets done over again.

Grrrr

Hi gff1stof3

out of interest did you install the media pack.

after multiple installs and following all work rounds mentioned in this thread thst failed to resolve this issue I have installed it ws2012e r2 as a virtual machine under W8 8.1update.

So far 7 days in I have not seen this issue. Not sure if its due to being a virtual machine (although I do believe somebody mentioned replicating the issue in a vm above) or due to the fact that I have not installed the media pack.

Antonio

Thanks Antonio.  I assume you mean the media foundation feature.  It is installed as its a default apparently on Essentials R2.  I can try removing it at this point.  I think from the VM method mentioned above it would duplicate connected to an active network.  Its starting to sound a lot like a NIC driver issue or setting or the IPV6 stuff. 

If I get anything to work I will post back.  This is really irritating as I have to go live tomorrow, so I may have no choice but to just leave essentials disabled and run the rest of the server for now.

I believe we are talking about the same thing... I am running Essentials R2 but you have to install the media pack separate http://www.microsoft.com/en-gb/download/details.aspx?id=40837.

In the VM I am passing through two internal Real Nics from my mother board and teaming them in this case i have not disable anything as i was hoping to see if I could replicate the issue through the VM.  

But yes this also concerns me if I have to go live with it.

Have you tried tommie76 answer 'After a delete of server backup things are up and running (use in powershell: wbadmin delete catalog)'

I have not been keen on deleting my back up catalog but would have tried it had it failed on the VM.

• Edited by afacciponti Friday, April 25, 2014 9:32 AM

I believe we are talking about the same thing... I am running Essentials R2 but you have to install the media pack separate http://www.microsoft.com/en-gb/download/details.aspx?id=40837.

In the VM I am passing through two internal Real Nics from my mother board and teaming them in this case i have not disable anything as i was hoping to see if I could replicate the issue through the VM.  

But yes this also concerns me if I have to go live with it.

Have you tried tommie76 answer 'After a delete of server backup things are up and running (use in powershell: wbadmin delete catalog)'

I have not been keen on deleting my back up catalog but would have tried it had it failed on the VM.

• Edited by afacciponti Friday, April 25, 2014 9:32 AM

This bug is STILL present in 2012 Essentials and 2012 R2 Essentials. It can be reproduced by changing the server disk configuration which affects the server backup assigned disk number enumeration (such as switching the backup disk port with another disk's)

When this happens, I have to run wbadmin delete catalog) resulting the loss of all the server backups

Can we get a proper fix?

http://www.tachytelic.net/2014/05/windows-server-2012-r2-configuration-encountered-issues/

This is the Fix

This worked for us!

Thank you Susan, for sharing as I thought I was going to have to rebuild the server! But after replacing the file service would start again.

DB

• Edited by AccordanceBlue Tuesday, October 28, 2014 8:54 AM

This worked for us!

Thank you Susan, for sharing as I thought I was going to have to rebuild the server! But after replacing the file service would start again.

DB

• Edited by AccordanceBlue Tuesday, October 28, 2014 8:54 AM

Shut down the Backup Service by creating 1 registry key!

I had the same problem with the Essentials dashboard service on a new installation and none of the above solutions worked for me.  The problem occurred after we setup the client backup service in the Essentials dashboard.   I tried the solutions listed here and it got everything back up and working without having to delete our backups.   http://technet.microsoft.com/en-us/library/dn293413.aspx

Finally!  Hopefully this can help someone else some time and trouble.

Ive tried all the suggestions on this and some other webpages, but they dont fix the problem.

After many long days I have finally found the solution, that seems to work pretty well for me.

Ive tried to write down all the steps in a word document.

If anybody still has interest on it, then just let me know.

• Edited by solala10 Friday, February 20, 2015 9:28 AM

Ive tried all the suggestions on this and some other webpages, but they dont fix the problem.

After many long days I have finally found the solution, that seems to work pretty well for me.

Ive tried to write down all the steps in a word document.

If anybody still has interest on it, then just let me know.

• Edited by solala10 Friday, February 20, 2015 9:28 AM

Hi gerard,

please be patient for a while, i have to translate the file into english first, then i can send it as a pdf-file to you or try to post it here in the forum.

I am having a similar issue with the Windows Server Essentials Management Service terminating unexpectedly.  It started right after I added a new internal SATA hard drive.  After searching forums and google quite a bit, it seems that the new drive volume number messed up the existing assignments for all the dashboard dependencies.  As soon as I unplugged the new drive and rebooted, all the services problems went away and the dashboard began behaving normally.  So, has anyone figured out a way to force the volume ordering so that adding a new hard drive is not so problematic?

Collapse
Solution | swaran	11/14/2013 16:41

August 29th, 2015 2:16am

---

She does not figure it out.  She just has great memory recall  LOL

Free Windows Admin Tool Kit Click here and download it now

August 29th, 2015 7:03am

---

I opened a support case is how I figured that out. I still don't know what the trigger is why this occurs.

August 29th, 2015 12:01pm

---

I opened a support case is how I figured that out.

I'd call that the brute-force method  ;-)

Thanks,
Jeff Bowman
Fairbanks, Alaska

Free Windows Admin Tool Kit Click here and download it now

August 29th, 2015 3:41pm

---

She does not figure it out.  She just has great memory recall  LOL

Better than mine!

Thanks,
Jeff Bowman
Fairbanks, Alaska

August 29th, 2015 3:41pm

---

This topic is archived. No further replies will be accepted.

Other recent topics

Remote Administration For Windows. Easy remote access of Windows 7, XP, 2008, 2000, and Vista Computers

Click here to find out more

Reboot Hundreds of computers, disable flash drives, deploy power managements settings.

Click here to get your free copy of Network Administrator. Over 25 plugins to make your life easier

Symptom: The "Windows Server Essentials Management Service" terminated unexpectedly Cause: Corruption in C:\ProgramData\Microsoft\Windows Server\Data\DevicesInfo.xml file Resolution: Replaced the file from DevicesInfo.xml.bak was able to start the service successfully What the heck is causing that?