Server is seldom used. Over the summer it stopped working. I get the "one or more services or drivers failed to load" error on startup. The same thing happened with the original installation in 2010. I can't even access the console from the machine
locally. After a minute or two, it starts and immediately shuts down. I see in the task manager that a file, DW20.exe, starts up with the console and runs using 60-98% CPU for several minutes after the console shuts down. I read an earlier post that the log
file might be helpful. I've included that. Thanks for any help! Karl "HomeServerConsole.120128.2210001718.3796.log" __________________________________________________________________________ Created at 1/28/2012 10:10:00 PM ***** Started at 1/28/2012
10:10:00 PM *** ***** Started at 1/28/2012 10:10:00 PM *** [1]120128.221005.4843: BackupConfig: Error: Disconnected Backup Config [1]120128.221005.8437: BackupConfig: Error: Disconnected Backup Config [1]120128.221005.9375: Error: Client b1e5269c-84b5-4785-9798-529643d7ce81
not found by BackupHelpers.FindClient [1]120128.221005.9375: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: b1e5269c-84b5-4785-9798-529643d7ce81 at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9687: Error: Client 31df9dce-9cdf-4519-83b2-cbf18c6e4fc2
not found by BackupHelpers.FindClient [1]120128.221005.9687: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 31df9dce-9cdf-4519-83b2-cbf18c6e4fc2 at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9687: Error: Client 1ce8c9a8-afff-403d-a90b-95c583d4f0e8
not found by BackupHelpers.FindClient [1]120128.221005.9687: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 1ce8c9a8-afff-403d-a90b-95c583d4f0e8 at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9687: Error: Client d25f9058-dde8-4252-becc-213de0fb5c60
not found by BackupHelpers.FindClient [1]120128.221005.9687: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: d25f9058-dde8-4252-becc-213de0fb5c60 at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9687: Error: Client 8e3305a0-6bff-4aeb-b977-968106ec50cb
not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8e3305a0-6bff-4aeb-b977-968106ec50cb at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client e213ecfe-bbad-4df7-ad29-d2038524809f
not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: e213ecfe-bbad-4df7-ad29-d2038524809f at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client 86936416-5b55-4094-bd83-874d31d16227
not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 86936416-5b55-4094-bd83-874d31d16227 at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client 6a9e1b73-86be-4e34-81f4-a6282131c393
not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 6a9e1b73-86be-4e34-81f4-a6282131c393 at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client 00cc5d5e-d078-4b3e-ba2c-3ca25518e168
not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 00cc5d5e-d078-4b3e-ba2c-3ca25518e168 at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client 6e7a175d-77f1-4870-b19c-258d7e296bce
not found by BackupHelpers.FindClient [1]120128.221005.9843: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 6e7a175d-77f1-4870-b19c-258d7e296bce at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot
configurator, Guid pcGuid) at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient [1]120128.221006.4062: BackupConfig: Error: Disconnected Backup
Config [1]120128.221008.1875: Error: Error -2147023728 in SendMessage [8]120128.221012.2968: Error: Backup percentage is -2147483648 [8]120128.221012.2968: Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData
for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281:
Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for
HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for HealthControl [5]120128.221012.3281: Error: Cannot invoke RefreshData for HealthControl [8]120128.221015.2968: Error: Backup percentage is -2147483648 [8]120128.221015.2968: Error: Cannot
invoke RefreshData for HealthControl [1]120128.221015.7031: Error: Exception thrown System.IO.IOException: The network location cannot be reached. For information about network troubleshooting, see Windows Help. at System.IO.__Error.WinIOError(Int32 errorCode,
String maybeFullPath) in mscorlib.dll at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption) in mscorlib.dll at System.IO.DirectoryInfo.GetFiles(String
searchPattern, SearchOption searchOption) in mscorlib.dll at System.IO.DirectoryInfo.GetFiles(String searchPattern) in mscorlib.dll at Microsoft.HomeServer.HomeServerConsoleTab.Storage.AdditionsControl.FillAvailableList(Addition[] known, Addition[] registered)
in HomeServerConsoleTab.Storage.dll at Microsoft.HomeServer.HomeServerConsoleTab.Storage.AdditionsControl.Restore() in HomeServerConsoleTab.Storage.dll at Microsoft.HomeServer.HomeServerConsoleTab.Storage.AdditionsControl..ctor(Int32 width, Int32 height, IConsoleServices
services) in HomeServerConsoleTab.Storage.dll at Microsoft.HomeServer.HomeServerConsoleTab.Storage.AdditionSettingsExtender.get_TabControl() in HomeServerConsoleTab.Storage.dll at Microsoft.HomeServer.Controls.SettingsDialog.AddSettingsPage(ISettingsExtender
tab) in HomeServerControls.dll at Microsoft.HomeServer.Controls.TabFinder.FillSettingContainer(SettingsDialog settingsDialog) in HomeServerControls.dll at Microsoft.HomeServer.HomeServerConsole.MainForm.InitializeComponent() in HomeServerConsole.exe at Microsoft.HomeServer.HomeServerConsole.MainForm.OnLoad(EventArgs
e) in HomeServerConsole.exe at System.Windows.Forms.Form.OnCreateControl() in System.Windows.Forms.dll at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) in System.Windows.Forms.dll at System.Windows.Forms.Control.CreateControl() in System.Windows.Forms.dll
at System.Windows.Forms.Control.WmShowWindow(Message& m) in System.Windows.Forms.dll at System.Windows.Forms.Control.WndProc(Message& m) in System.Windows.Forms.dll at System.Windows.Forms.ScrollableControl.WndProc(Message& m) in System.Windows.Forms.dll at
System.Windows.Forms.ContainerControl.WndProc(Message& m) in System.Windows.Forms.dll at System.Windows.Forms.Form.WmShowWindow(Message& m) in System.Windows.Forms.dll at System.Windows.Forms.Form.WndProc(Message& m) in System.Windows.Forms.dll at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(Message&
m) in System.Windows.Forms.dll at System.Windows.Forms.Control+ControlNativeWindow.WndProc(Message& m) in System.Windows.Forms.dll at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) in System.Windows.Forms.dll
at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow) in System.Windows.Forms.dll at System.Windows.Forms.Control.SetVisibleCore(Boolean value) in System.Windows.Forms.dll at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
in System.Windows.Forms.dll at System.Windows.Forms.Control.set_Visible(Boolean value) in System.Windows.Forms.dll at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll at System.Windows.Forms.Application.Run(Form mainForm) in System.Windows.Forms.dll at Microsoft.HomeServer.HomeServerConsole.MainForm.Main(String[]
args) in HomeServerConsole.exe Sender: Name:HomeServerConsole.exe There are no context policies. [14]120128.221027.9843: Error: Backup percentage is -2147483648 [14]120128.221027.9843: Error: Cannot invoke RefreshData for HealthControl
Karl H.
For me it looks as if you have an issue with the backup database. Maybe its corrupted due to a disk error or a previous server crash, and this can cause the console to crash itself.
If you do not need urgently something from the client backups, you can attempt to delete the entire database, as described in
this thread.
Thanks for the reply. It's actually some files in the one of the backups that I really need. I am working on copying the files to another drive. I am been having some issues there. I think it might be related to the external USB drive and/or the CPU overheating.
It's been a long night:)I'm trying another internal SATA drive at the moment. I have already installed WHS on another machine. I guess I will have to try to get to the files with that machine. I appreciate your input on the console issue. As soon as I can
get the files off of the backups the original machine is going bye-bye. If I have any reliability issues with WHS running the newer machine WHS will go bye-bye as well. It certainly would have been easier just to get the console working for one more session:)Karl H.
The problem with the backup database: Once it is damaged, it is not repairable without damage or at all.
Its biggest benefit - saving storage space with single instance storage - is also its biggest culprit - there is no redundancy. (Microsoft assumes, that usually either the original client still exists, or the backup can recover the client.)
How long is it, that you lost the files?
With Windows 7 you could check, if "previous versions" in the folder properties still contain the file for restore, if the incident is not too far in the past.
That's terrible engineering! The only benifit is the backup service. It's weakest link is the backup service. Whew.... Well I think the issue may be with the PCI SATA controller. Bought it for $10 on eBay. I'll get another one locally snd try that. Really,
the backup service is the only feature of WHS I use in all practicality that I can't get on a Win7 machine. I tired some others but the cost of backing up 5 computers was hundreds of dollars USD just for the software. Thanks for the insight on the database.Karl H.
I disagree; it's a design decision, but not a good or bad one. I don't believe the original design intended that users would archive backups for extended periods of time. If all you want is the ability to restore to the most recent backup, it's much less
of a problem because A) HDDs don't really fail very often once you get past the first few days of life, so it's rare for you to actually experience damage to the backup database (as a point of reference, I've never had to repair the backup database on my V1
server, which has been running since Nov. 2007) and B) in the rare event that you
do have a problem with the database, you still have the computer(s) that are being backed up, so you just repair/reset the database and back everything up again.
What Microsoft didn't allow for (and they can't, really) is the varied hardware choices that hobbyist users of Windows Home Server make. A less than optimal choice of hardware can result in a lot of issues of various sorts, including database corruption
(sometimes repeated).
