Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS 2011 - dashboard no longer opens after system restore RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I had a primary disk failure on my WHS 2011 box. The system restore using Windows backup/restore worked a treat, but after the restore I can't open the dashboard.

    Can't open from server or any of the clients. Tried disabling addins one at a time under dashboard (safe mode).

    I see the dashboard splash screen open, the dashboard sort of opens (all white), and then drops out.

    I did have addins Cloudberry and DrivePool. Cloudberry addin did not appear in safe mode list, so manually uninstalled, still no good.

    DrivePool is still operational and I can access my files on the server.

    Any help would be appreciated.

    Jason

    Two errors from Windows application log:

    Faulting application name: Dashboard.exe, version: 6.1.8800.16395, time stamp: 0x4f0f3073

    Faulting module name: wpfgfx_v0400.dll, version: 4.0.30319.233, time stamp: 0x4d930045

    Exception code: 0xc0000005

    Fault offset: 0x000000000007a1e0

    Faulting process id: 0xac4

    Faulting application start time: 0x01cd4952732f5128

    Faulting application path: C:\Program Files\Windows Server\Bin\Dashboard.exe

    Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll

    Report Id: c2418aa9-b545-11e1-9b54-00248100408c

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

    Application: Dashboard.exe

    Framework Version: v4.0.30319

    Description: The process was terminated due to an unhandled exception.

    Exception Info: exception code c0000005, exception address 00000000701DA1E0

    Wednesday, June 13, 2012 12:00 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    What's the result if you create a new user with administrator privilege? You can also collect and upload your console log file: http://technet.microsoft.com/en-us/library/log-collector-1.aspx

    Also, for crash issues on application level, the root cause can vary. The error message is very general and collecting and analyzing dump files will be the most efficient method to pinpoint the root cause.

    To resolve this issue efficiently, you can open up a service request by following the wizard at http://support.microsoft.com/select/Default.aspx?target=assistance. Microsoft Customer Support Service is the best resource for this kind of issues.

     

     

    Sean Zhu

    TechNet Community Support

    • Marked as answer by JBeeConnect Sunday, June 17, 2012 4:39 AM
    Friday, June 15, 2012 7:44 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    What's the result if you create a new user with administrator privilege? You can also collect and upload your console log file: http://technet.microsoft.com/en-us/library/log-collector-1.aspx

    Also, for crash issues on application level, the root cause can vary. The error message is very general and collecting and analyzing dump files will be the most efficient method to pinpoint the root cause.

    To resolve this issue efficiently, you can open up a service request by following the wizard at http://support.microsoft.com/select/Default.aspx?target=assistance. Microsoft Customer Support Service is the best resource for this kind of issues.

     

     

    Sean Zhu

    TechNet Community Support

    • Marked as answer by JBeeConnect Sunday, June 17, 2012 4:39 AM
    Friday, June 15, 2012 7:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for your suggestions. Setting up a new admin user did not work.

    Decided to reinstall from scratch, end result is a perfectly working system.

    Sunday, June 17, 2012 4:39 AM