Link to home
Start Free TrialLog in
Avatar of CRL ltd
CRL ltd

asked on

Error When opening Windows server backup

Hi,  we have a client with a server running SBS 2011 Essentials,

when we try to open Windows Server Backup to check the backups we get his error message (see attached file)

can anybody assist with this as everything we've tried doesnt work.  anything else that opens using MMC (DHCP, Services) seems to open OK.

thanks
Windows-Backup.PNG
Avatar of Adam Brown
Adam Brown
Flag of United States of America image

Have you tried uninstalling Windows Server Backup and then Reinstalling it?
Are you getting error events related to same? If yes, Please share.
Avatar of CRL ltd
CRL ltd

ASKER

Thanks for the response, looks like Server manager doesn't work, so it seems to be effecting random things that use MMC.  Services opens fine though.
As per the article  https://community.spiceworks.com/topic/1366159-mmc-could-not-create-the-snap-in-server-2008-r2

installing hotfix for .netframework has fixed the issue.

You can download the hotfix using the link https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=2688730&kbln=en-us

Before installing make sure to perform full backup of the server.
Avatar of CRL ltd

ASKER

Thanks Shreedhar, unfortunately we had no luck with that hotfix, installed it and rebooted but still the same error.
Are you getting error events for the same in Eventvwr? If yes, please share the event description.
Avatar of CRL ltd

ASKER

Event viewer doesnt open either, but i managed to get into the logs a different way, a few of these errors occur;

Faulting application name: ProviderRegistryService.exe, version: 6.1.1840.0, time stamp: 0x4d6dafda
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x000007fe99ac0a15
Faulting process id: 0x16d0
Faulting application start time: 0x01d40cf392b7f543
Faulting application path: C:\Program Files\Windows Server\Bin\ProviderRegistryService.exe
Faulting module path: unknown
Report Id: d0a40aba-78e6-11e8-a478-082e5f32034a


and this error


Application: ProviderRegistryService.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in OnStart: System.InvalidOperationException: Service ServiceRegistryProvider was not found on computer '.'. ---> System.ComponentModel.Win32Exception: The specified service does not exist as an installed service
   --- End of inner exception stack trace ---
   at System.ServiceProcess.ServiceController.GenerateNames()
   at System.ServiceProcess.ServiceController.get_DisplayName()
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.GetDisplayName(String serviceName)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProductConfigurator.LogServiceStartFailure(String serviceName, String info)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderRegistry.ServiceShell.OpenHost()
   at Microsoft.WindowsServerSolutions.Common.Services.WssgServiceBase.OnStart(String[] args)
Stack:
   at System.Environment.FailFast(System.String, System.Exception)
   at Microsoft.WindowsServerSolutions.Common.Services.WssgServiceBase.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.