locked
Console shuts down RRS feed

  • Question

  • After installing PP3 the WHS console shuts down and returns to the WHS desktop. This occurs when I access the console when I log directly to it (Home Brew WHS with KVM). If I conect to the console via a client computer, all is well and works without problem. This started after upgrading the firmware of my D-Link DIR-655 router to version 1.32. If I remove PP3 and log directly into the WHS and go to the console, all is well again. Any suggestions as to what may cause this? Is anyone else seeing this problem? I have contacted D-Link support and am awaiting a reply.

    Note: D-Link firmware 1.32 (just released) corrected a problem with UPnP and WHS caused by the release of version 1.31.  V1.32 works very well with WHS, except for the above when bets PP3 is installed 
    Bud - Alameda, CA
    Saturday, July 25, 2009 6:42 PM

Answers

  • I assume that's AndreasMs Update history. Are you runnging the latest version?
    http://www.home-server-addins.com/downloads

    Should you still have problems with PP3 please contact the Author.
    LightsOut - Power Management for Windows Home Server http://www.home-server-blog.de/add-ins/lightsout/#en
    Tuesday, July 28, 2009 6:32 AM
    Moderator
  • Martin,

    you're right, Update History is causing the console crash because querying the systems' update history is denied. I've just installed PP3 Beta and am unable to reproduce the behavior. Both logging on locally and remotely to the server and starting the WHS console with the Update History addin installed works just fine.

    @budgall: Which user account do you use to log on locally when the console crash happens? Please make sure to log on as "Administrator" using your WHS password. If you're using a different account, please make sure it is member of the "Administrators" and "Windows Home Server Users" groups.

    Andreas M.
    Tuesday, July 28, 2009 7:26 PM

All replies

  • If you think that PP3 may be the culprit I would suggest you log a bug on Connect so that Microsoft can investigate.

    Andrew
    MVP - Windows Home Server
    Saturday, July 25, 2009 8:31 PM
    Moderator
  • You may look at the latest homeserverconsole.xxx.log when the crash has happend. This file is stored in the directory %qlogs% (click Start->Run, enter %qlogs%).
    Or you may post parts of it here for investigation.
    LightsOut - Power Management for Windows Home Server http://www.home-server-blog.de/add-ins/lightsout/#en
    Monday, July 27, 2009 4:45 PM
    Moderator
  • Here is the log file

    Bud


    Created at 7/27/2009 3:50:14 PM
    ***** Started at 7/27/2009 3:50:14 PM ***
    ***** Started at 7/27/2009 3:50:14 PM ***
    [1]090727.155021.5625: Error: Error -2147023728 in SendMessage
    [1]090727.155021.5937: Error: Error -2147023728 in SendMessage
    [1]090727.155021.5937: Error: Error -2147023728 in SendMessage
    [1]090727.155022.6093: BackupConfig: Error: Disconnected Backup Config
    [1]090727.155022.6406: BackupConfig: Error: Disconnected Backup Config
    [1]090727.155022.6562: Error: Client ca93f849-7c0a-4f4e-833b-d187d6906d60 not found by BackupHelpers.FindClient
    [1]090727.155022.6562: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: ca93f849-7c0a-4f4e-833b-d187d6906d60
       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]090727.155022.6562: Error: Client b08a80f3-3529-47e8-88c8-fe1bf5cb39fd not found by BackupHelpers.FindClient
    [1]090727.155022.6562: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: b08a80f3-3529-47e8-88c8-fe1bf5cb39fd
       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]090727.155022.6562: Error: Client f3d4a127-472d-49e2-b2dc-3bb789b3bc0d not found by BackupHelpers.FindClient
    [1]090727.155022.6562: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: f3d4a127-472d-49e2-b2dc-3bb789b3bc0d
       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]090727.155022.6562: Error: Client 23b13f61-07c0-49d9-899a-b4589e9660fa not found by BackupHelpers.FindClient
    [1]090727.155022.6562: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 23b13f61-07c0-49d9-899a-b4589e9660fa
       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]090727.155022.6562: Error: Client 783a305d-2937-463e-a8a4-0b9c8e7fed21 not found by BackupHelpers.FindClient
    [1]090727.155022.6562: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 783a305d-2937-463e-a8a4-0b9c8e7fed21
       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]090727.155022.6562: Error: Client 9013482e-1014-4686-8b30-aa07bf97a7cb not found by BackupHelpers.FindClient
    [1]090727.155022.6562: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 9013482e-1014-4686-8b30-aa07bf97a7cb
       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]090727.155022.6562: Error: Client 9b1b682a-4cc6-42e7-87b8-3310b4cd897c not found by BackupHelpers.FindClient
    [1]090727.155022.6718: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 9b1b682a-4cc6-42e7-87b8-3310b4cd897c
       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]090727.155022.7031: BackupConfig: Error: Disconnected Backup Config
    [6]090727.155024.0000: Error: Cannot invoke RefreshData for HealthControl
    [6]090727.155024.0000: Error: Cannot invoke RefreshData for HealthControl
    [6]090727.155024.0000: Error: Cannot invoke RefreshData for HealthControl
    [6]090727.155024.0000: Error: Cannot invoke RefreshData for HealthControl
    [6]090727.155024.0000: Error: Cannot invoke RefreshData for HealthControl
    [6]090727.155024.0000: Error: Cannot invoke RefreshData for HealthControl
    [6]090727.155024.0000: Error: Cannot invoke RefreshData for HealthControl
    [10]090727.155024.0156: Error: Backup percentage is -2147483648
    [10]090727.155024.0156: Error: Cannot invoke RefreshData for HealthControl
    [1]090727.155024.1718: Error: Error -2147023728 in SendMessage
    [10]090727.155027.0156: Error: Backup percentage is -2147483648
    [10]090727.155027.0156: Error: Cannot invoke RefreshData for HealthControl
    [1]090727.155029.0312: Error: Cannot invoke RefreshData for HealthControl
    [1]090727.155029.0312: Error: Error -2147023728 in SendMessage
    [1]090727.155031.7812: Error: Exception thrown
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: An exception occurred during the operation, making the result invalid.  Check InnerException for exception details. ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
       at WUApiLib.IUpdateSearcher.GetTotalHistoryCount() in Interop.WUApiLib.dll
       at AndreasM.WHSUpdateHistory.UpdateHistory.GetUpdateHistory() in HomeServerConsoleTab.WHSUpdateHistory.dll
       at Microsoft.HomeServer.HomeServerConsoleTab.WHSUpdateHistory.MainTabUserControl.backgroundWorker1_DoWork(Object sender, DoWorkEventArgs e) in HomeServerConsoleTab.WHSUpdateHistory.dll
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) in System.dll
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) in System.dll
       --- End of inner exception stack trace ---
       at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary() in System.dll
       at System.ComponentModel.RunWorkerCompletedEventArgs.get_Result() in System.dll
       at Microsoft.HomeServer.HomeServerConsoleTab.WHSUpdateHistory.MainTabUserControl.backgroundWorker1_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e) in HomeServerConsoleTab.WHSUpdateHistory.dll
       at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e) in System.dll
       at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg) in System.dll
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) in mscorlib.dll
       at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) in mscorlib.dll
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) in mscorlib.dll
       at System.Delegate.DynamicInvokeImpl(Object[] args) in mscorlib.dll
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) in System.Windows.Forms.dll
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) in System.Windows.Forms.dll
       at System.Threading.ExecutionContext.runTryCode(Object userData) in mscorlib.dll
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) in mscorlib.dll
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) in mscorlib.dll
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) in mscorlib.dll
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) in System.Windows.Forms.dll
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks() in System.Windows.Forms.dll
       at System.Windows.Forms.Control.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.UnsafeNativeMethods.DispatchMessageW(MSG& msg) in System.Windows.Forms.dll
       at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) 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.


    Bud - Alameda, CA
    Monday, July 27, 2009 11:00 PM
  • I did
    Bud - Alameda, CA
    Monday, July 27, 2009 11:00 PM
  • I assume that's AndreasMs Update history. Are you runnging the latest version?
    http://www.home-server-addins.com/downloads

    Should you still have problems with PP3 please contact the Author.
    LightsOut - Power Management for Windows Home Server http://www.home-server-blog.de/add-ins/lightsout/#en
    Tuesday, July 28, 2009 6:32 AM
    Moderator
  • Martin,

    you're right, Update History is causing the console crash because querying the systems' update history is denied. I've just installed PP3 Beta and am unable to reproduce the behavior. Both logging on locally and remotely to the server and starting the WHS console with the Update History addin installed works just fine.

    @budgall: Which user account do you use to log on locally when the console crash happens? Please make sure to log on as "Administrator" using your WHS password. If you're using a different account, please make sure it is member of the "Administrators" and "Windows Home Server Users" groups.

    Andreas M.
    Tuesday, July 28, 2009 7:26 PM
  • @budgall: Which user account do you use to log on locally when the console crash happens? Please make sure to log on as "Administrator" using your WHS password. If you're using a different account, please make sure it is member of the "Administrators" and "Windows Home Server Users" groups.

    Andreas M.

    Yes I am loging in as the Administrator and am using my WHS password

    Am I reading the the response right that your add-in is where the conflict is??  I have both AAC 0.5.0 and Update History 0.2.0 installed on my server.

    Bud
    Bud - Alameda, CA
    • Edited by budgall Tuesday, July 28, 2009 8:48 PM
    Tuesday, July 28, 2009 8:37 PM
  • Hmm, you don't by any chance happen to have any practice using Process Monitor (http://live.sysinternals.com/procmon.exe), do you?

    In order to get a clue which resource access is denied to, you could download and run Process Monitor in your WHS session and then launch the WHS console. Process Monitor will log all file system and registry activity (and a little more). After the console crash has occured, the Process Monitor log may contain several entries with result = ACCESS DENIED. Maybe you could post these entries here or even better save the Process Monitor log (in PM's native format) and send it to me so I can review it. If you want to contact me directly, please do so via http://www.home-server-addins.com/contact

    Andreas M.

    Tuesday, July 28, 2009 8:47 PM
  • Hmm, you don't by any chance happen to have any practice using Process Monitor (http://live.sysinternals.com/procmon.exe), do you?

    Andreas M.


    No I have never used Process Monitor, have looked at it in the past but never really got into it. I will go get it and try to get your requested info.

    Bud
    Bud - Alameda, CA
    Tuesday, July 28, 2009 9:02 PM
  • OK Have a log how do i send to you. Also sent the how to to the contact address you gave.

    Bud
    Bud - Alameda, CA
    Tuesday, July 28, 2009 9:33 PM
  • I have received your process monitor logfile and reviewed it. Unfortnately I have no clue what exactly is causing the "access denied" error. Since I cannot reproduce the behaviour and since it only happens when logging on locally (which is not supported) I have to say that I will not look deeper into the problem at this point.

    Andreas M.
    Monday, August 3, 2009 3:52 PM
  • I have received your process monitor logfile and reviewed it. Unfortnately I have no clue what exactly is causing the "access denied" error. Since I cannot reproduce the behaviour and since it only happens when logging on locally (which is not supported) I have to say that I will not look deeper into the problem at this point.

    Andreas M.

    As an update, I just uninstalled your Update History Add-in for Windows Home Server and the problem has now gone away. I no longer get kicked out on the console and can stay and work from within without problem. So for now, I will not use the add-in, perhaps a later version or the final released PP3 will fix the problem I am having.

    In my opinion, you do have a problem with the add-in and that you do need to fix it. I know from my own experiences the differculty of fixing a software bug that you cannot duplicate. Thank you for looking and trying to solve the problem.

    Question: Where do you find something that says local logons are not supported by Microsoft, I have never seen anything on that? 

    Bud
    Bud - Alameda, CA
    Tuesday, August 4, 2009 4:52 PM