locked
WHS Console will not launch from RDC or Connector RRS feed

  • Question

  • In the last couple of days I have been trying to troubleshoot the failure of my WHS Console.  I first noticed the problem when the WHS icon reported a 'critical' status.

    I tried to log in via the standard Connector method using the icon and that failed with a "This computer cannot connect to your Home Server. Check network...." message.  I then tried RDC and I am able to get to the WHS desktop but the Console fails to launch with the message "The Windows Home Server Console experienced a problem..." Retry / Skip.  I have attempted both to no avail.

    I have watched the WHS Console process start (prior to the Retry/Skip message), gain in CPU usage after selection, flash to the screen breifly and then the process will stop. The process DW20.exe starts during this period and remains for a short time after the console process stops before this process stops as well.  I can see all my files on the server (both via RDC and through the Shared Files shortcut but I cannot use them in any way - no way to launch WHSConnector, no picture viewing, nothing.

    I don't see any way to do an attachment to posts so I will post my latest HomeServerConsole.xxx.log as text:

    **************************************************

    Created at 5/20/2010 9:48:26 PM
    ***** Started at 5/20/2010 9:48:26 PM ***
    ***** Started at 5/20/2010 9:48:26 PM ***
    [1]100520.214828.7968: UI: Error: Unfinished DLL: HomeServerConsoleTab.Sharing.dll.  User chose to block.
    [1]100520.214829.4843: BackupConfig: Error: Disconnected Backup Config
    [1]100520.214829.5000: BackupConfig: Error: Disconnected Backup Config
    [1]100520.214829.5000: Error: Client 2cb79c4c-d7ef-4a1f-8c6b-4e4ba9213e62 not found by BackupHelpers.FindClient
    [1]100520.214829.5000: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 2cb79c4c-d7ef-4a1f-8c6b-4e4ba9213e62
       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]100520.214829.5000: Error: Client 3d508426-1c46-4fd7-bc64-9638711bd711 not found by BackupHelpers.FindClient
    [1]100520.214829.5156: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 3d508426-1c46-4fd7-bc64-9638711bd711
       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]100520.214829.5156: Error: Client f3ede317-0f06-4e97-b417-fd618a5455da not found by BackupHelpers.FindClient
    [1]100520.214829.5156: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: f3ede317-0f06-4e97-b417-fd618a5455da
       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]100520.214829.5156: Error: Client 8f8dd45f-0cb0-4cbe-a4bf-8fce8037ffed not found by BackupHelpers.FindClient
    [1]100520.214829.5156: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8f8dd45f-0cb0-4cbe-a4bf-8fce8037ffed
       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]100520.214829.5468: BackupConfig: Error: Disconnected Backup Config
    [12]100520.214831.8593: Error: Backup percentage is -2147483648
    [12]100520.214831.8593: Error: Cannot invoke RefreshData for HealthControl
    [5]100520.214831.8593: Error: Cannot invoke RefreshData for HealthControl
    [5]100520.214831.8593: Error: Cannot invoke RefreshData for HealthControl
    [12]100520.214834.8593: Error: Backup percentage is -2147483648
    [12]100520.214834.8593: Error: Cannot invoke RefreshData for HealthControl
    [1]100520.214840.1406: Error: Error -2147023728 in SendMessage
    [1]100520.214840.3906: Error: Exception thrown
    System.IO.IOException: The network path was not found.

       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.

    [11]100520.214841.8593: Error: Backup percentage is -2147483648
    [11]100520.214841.8593: Error: Cannot invoke RefreshData for HealthControl

    ***************************************************

    Any help would be greatly appreciated.  I will be SO disappointed if i have to do a reinstall.

    Friday, May 21, 2010 3:45 AM

All replies

  • When you noticed the critical icon, did the details in the Console (when you could access it) give any addiitonal informaiton? While connected via Remote Desktop to your WHS server, open up Event Viewer in All Programs --> Administrative Tools and look for Warnings/Errors in the HomeServer log, System log and Application log. Let's see if they reveal any additional info.

     

    Michael Wheatfill

    Friday, May 21, 2010 6:47 AM
  • Hmm. Although you can not be really sure from this info I Expect you have a major hardware failure, possibly harddisk. If you have recently made any changes installed or update Add-in or other third party software (drivers, programs, ......) you could try uninstalling third party software using Add or Remove Programs from the control panel (on the server desktop) 

    You could also have a look at your event logs (on the server desktop do Start Run, type eventvwr.msc and hit Enter). There may be some sensible info there, however I expect the eventlogs will also be flooded with multiple errors.

    Personally I would start with running chkdsk /r on all partition of your server as described in this FAQ. Please note this may take a long time, especially if there are serious disk problems. If this doesn't fix your problem (which it probably won't you can try and run sfc /scannow from a command prompt on the server desktop (requires original WHS install media in server optical drive). This will check and try to fix any errors in protected system files. This will also probably not fix your issue. Last thing then would be to run UMCONSOLE.EXE from C:\WHS. If that also fails I guess server reinstall is your best option.

    Friday, May 21, 2010 3:00 PM
    Moderator
  • Thank you for the responses.  I have started the chkdsk/r as per the FAQ - on stage 5 (Free Space) with no errors reported yet.  I will let it run to the end and check the log after it completes.

    While it is running I have been checking the suggested logs for errors.  Under Applications there is a consistant error ".NET Runtime 2.0 Error Reporting".  Under Systems there is a consistant error "TermServDevices".  The only error that appears under HomerServer is what looks like a failure of backups (based on Source=HomeServer, Catagory=Backup, and the time of day of the error.

    Anyone think a reinstall of .NET 2.0 would fix this?

    Friday, May 21, 2010 5:56 PM
  • Well, nothing has worked so far....chkdsk showed no errors at all...reinstall of .net did nothing....umconsole.exe had no effect.

    Any other suggestions?

    • Proposed as answer by CyPliX Sunday, May 23, 2010 7:57 PM
    • Unproposed as answer by kariya21Moderator Sunday, May 30, 2010 8:11 PM
    Saturday, May 22, 2010 8:52 PM
  • I've had the same problem on a reoccurring basis.

    One thing that worked (occasionally) was to hook up to the server directly.

     

    Saturday, May 22, 2010 9:57 PM
  • I've had many many problems with WHS especially after I install addins.

    The most sensible thing I've done to prevent catastrophic failure like this is to keep a backup of my c:\ / d:\ boot drive.

    I have a raid array which is my e:\ that stores all my data so if and when I need to reinstall the OS all my data is safely tucked away in its own volume.

    I have two 320GB hdd's, one hdd I call my primary and the second ... well my secondary.

    I installed WHS on my primary, made the system nice and stable from scratch

    I create junction points from my D:\ shared folders to my E:\ so that my raid array remains just a storage device.

    When I was happy I imaged my drive onto the secondary disk, if the primary OS fails for some reason I boot from my backup image and my secondary drive now becomes my primary and visa versa for the other drive.

     

    Sunday, May 23, 2010 8:10 PM