locked
Dashboard Fails to Launch After Update 1607 RRS feed

  • Question

  • After Windows 1607 update, the dashboard failed to load from the client computer. The computer will backup automatically and run backups via the Launchpad. I can remote in to the server and use the dashboard but not from the client computer. I tried to reinstall the connector but it would not install. I did a reset and uninstalled the 1607 update, installed the connector and then installed the 1607 update again. I still have the same problem.

    This is from the logs when the dashboard was working before the update.  

    [7024] 151119.225005.0246: General: Initializing...C:\Program Files\Windows Server\Bin\DashboardClient.exe

    After the update the logs show this. The last 8 lines of the log show the dashboard crashing.

    Any ideas on how to fix this problem? The server is a WHS 2011

    [7024] 151119.225005.2621: General: Color branding started

    [7024] 151119.225005.2621: General: Processing Microsoft default SKU branding colors XML

    [7024] 151119.225005.2778: General: Validating branding colors XML:

    <?xml version="1.0"?>

    <!-- Vail color scheme -->

    <DashboardTheme xmlns="http://www.microsoft.com/HSBS/Dashboard/Branding/2010">

      <!-- Hex color values overwriting default SKU theme colors -->

      <TabstripColor1 HexValue="FFD9EA9C"/>

      <TabstripColor2 HexValue="FF52A22E"/>

      <TabstripColor3 HexValue="00D9EA9C"/>

      <TabstripColor4 HexValue="FFFFFFFF"/>

      <FontColor HexValue="FF000000"/>

      <SubtabColor1 HexValue="FFB1C7A2"/>

      <SubtabColor2 HexValue="FFF7FBE6"/>

      <SubtabColor3 HexValue="FFCEE5A9"/>

      <ListViewColor HexValue="FFFFFFFF"/>

      <DashboardClientColor1 HexValue="FFC2DB67"/>

      <DashboardClientColor2 HexValue="FF8CC65C"/>

      <DashboardClientColor3 HexValue="FF094208"/>

      <LaunchpadColor1 HexValue="FF7FC15A"/>

      <ClientFontColor1 HexValue="FFFFFFFF"/>

      <ClientFontColor2 HexValue="FF000000"/>

      <ClientGlyphColor HexValue="FFFFFFFF"/>

    </DashboardTheme >

    [7024] 151119.225005.2778: General: Branding colors XML parsing started

    [7024] 151119.225005.2778: General: Branding colors XML parsing ended

    [7024] 151119.225005.2778: General: Looking for OEM branding colors XML

    [7024] 151119.225005.2778: General: No OEM informations available

    [7024] 151119.225005.2778: General: Color branding complete

    [6336] 151119.225044.1462: General: DashboardClient trying to sign in and launch the RAIL application.

    [6336] 151119.225047.1870: General: Successfully launched the RDP session for the RAIL application.

    [7024] 151119.225047.1910: General: Loading screen: Using the default value for the timeout.

    [7024] 151119.225047.1910: General: Showing the loading screen for 60 seconds

    [6832] 151119.225047.4246: General: Loading screen: Using the default value for the timeout.

    [6832] 151119.225047.4256: General: Showing the loading screen for 60 seconds

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

    [10036] 151119.235805.0223: General: DashboardClient started with argument /dashboardLoading.

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

    [1448] 151120.000309.4019: General: DashboardClient started with argument /dashboardClosed.

    [1448] 151120.000309.4872: General: Dashboard.exe has closed/crashed. Removing the cached credentials.

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

    Thursday, August 11, 2016 7:08 PM

Answers

  • Hi,

    good that you tested this. Result shows, that there is nothing wrong with the dashboard itself and not with the computer, eventually some stuff in the registry is messed up in HKEY_CURRENT_USER or some running software interferes.

    Is the troublesome account a local one or a Microsoft ID? The later ones are known for strange behavior in LAN environment sometimes. (And WHS doesn't know anything about those either.)

    Best greetings from Germany
    Olaf

    • Marked as answer by illiam Thursday, August 18, 2016 2:52 PM
    Thursday, August 18, 2016 11:29 AM

All replies

  • Hi,

    According to your description, my understanding is that the dashboard failed to load from the client computer after Windows 1607 update.

    I would recommend you to disable IPv6 on both client and WHS if it is not in used. Then, have a reboot and check the result. 

    If the problem persists, any error is prompted when client failed to load the Dashboard? 

    Check the event viewer and make sure if any related event has been logged.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 12, 2016 8:02 AM
  • I disabled the IPv6 on the client computer and server. Rebooted and nothing changed. I then disabled IPv6 using a Microsoft tool but still no change (kb/929852).

    I go through Launchpad and click on Dashboard icon. I put my password in and click on the arrow. The Dashboard page show loading for 60 seconds and then disappears. There is not an error message.

    I checked the client and Windows Server event viewers and the only thing on them were successful backups. The event logs in the first message is the only logs I could find that show anything wrong.

    Thanks

    illiam

    Monday, August 15, 2016 12:08 AM
  • Also no error message in the event log? (usually in the application log, eventually system log)

    Does the dashboard still function, if you use Remote Desktop client to your server (username yourserver\Administrator) and click the shortcut there?

    Best greetings from Germany
    Olaf

    Tuesday, August 16, 2016 10:21 AM
  • When I remote in to the server, the dashboard works. The client computer will do backups automatically and manually. Also shared folders is accessible. The only problem is starting the dashboard from Launchpad. I cannot find any errors in the event viewer that happens when I try to sign on to the dashboard.

    A second client computer without the update operates normally with the dashboard working.

    Thanks

    illiam  

    Tuesday, August 16, 2016 1:18 PM
  • Is the network still set to private and network discovery set to on in Network and Sharing Center?

    Best greetings from Germany
    Olaf

    Wednesday, August 17, 2016 3:30 PM
  • I checked the computer and the network is set to private and network discovery was set to off. I changed network discovery to on and restarted the computer. The results were the same with dashboard not starting.

    I changed user accounts on the computer and the dashboard works like it should. I added another administrator account and the dashboard worked again. I have no idea why this is. Unless you know of a fix, I will probably just change my user account and be done with it. Thank you for the help.

    Wednesday, August 17, 2016 4:39 PM
  • Hi,

    good that you tested this. Result shows, that there is nothing wrong with the dashboard itself and not with the computer, eventually some stuff in the registry is messed up in HKEY_CURRENT_USER or some running software interferes.

    Is the troublesome account a local one or a Microsoft ID? The later ones are known for strange behavior in LAN environment sometimes. (And WHS doesn't know anything about those either.)

    Best greetings from Germany
    Olaf

    • Marked as answer by illiam Thursday, August 18, 2016 2:52 PM
    Thursday, August 18, 2016 11:29 AM
  • The account is a Microsoft ID. Thanks again for the help.

    illiam

    Thursday, August 18, 2016 3:15 PM
  • Hi,

    As you mentioned that the new user account works as it should be. I would recommend you to use the new working account. And manually move data from the old broken account to the new one if necessary.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 23, 2016 5:28 AM