Dashboard not starting..;

所有回覆

• 2010年9月22日 17:13

  版主

   

   
  

  0
  Have you submitted a bug on Connect?

  ---

  I'm not on the WHS team, I just post a lot. :)

  • 已標示為解答 Jonas Svensson -FST-Microsoft Employee, Owner 2010年9月22日 22:09
  •  
   
• 2010年10月6日 22:27

   

   
  

  0
  Did you find any solution to this problem? I seem to have exactly the same issue.
   
• 2010年10月7日 0:05

   

   
  

  0
  I had this issue once and rebooted Vail and it never happened again. I didn't file a bug because I couldn't reproduce it, figured that with all the beta testing, pushing all the buttons, I just needed the reboot.

  
  --
  Don
   
• 2010年10月7日 20:11

   

   
  

  0

  Rebooting the server does not help in my case. Wanted to add another disk, but without the dasboard...

   
• 2010年10月8日 0:04

  版主

   

   
  

  0

  Rebooting the server does not help in my case. Wanted to add another disk, but without the dasboard...

  And have you submitted a bug on Connect?

  ---

  I'm not on the WHS team, I just post a lot. :)
   
• 2010年10月25日 9:55

   

   
  

  0
  Yes I did, but I realized the server had other issues. The logs were full of othere errors as well, so I decided to re-install the server. After which I got a new problem...
   
• 2010年10月30日 16:17

   

   
  

  0

  I am having the same problem so I rebuilt my server. As a fresh clean server the Dashboard works fine. Then I installed the 50 or so updates and now the Dashboard won't start.

   
• 2011年1月12日 9:05

   

   
  

  1

  I had the same error. Looking into the "C:\ProgramData\Microsoft\Windows Server\Logs\dashboard.log" showed additional information:

  [3516] 110112.105916.8815: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]

  [3516] 110112.105917.1934: WssgCertMgmt: Collection Empty

  [3516] 110112.105917.1934: Sku: Valid machine certificate is not found.

  [3516] 110112.105917.2090: Dashboard.Forms: !!!!FATAL: Dashboard shutting down due to unhandled exception: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception.

  [3516] 110112.105917.4274: Dashboard.Forms: System.TypeInitializationException: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception. ---> Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderException: Machine certificate is not found.

  I checked machine certificates (mmc - Certificates snap-in - Computer account - Personal) there were two of them VAIL and VAIL-CA (VAIL is my server name). Certificates had valid dates, but no root trust. I copied the VAIL_CA certificate and pasted into the Trusted Root Certification Authorities. Certificates got trust, Dashboard successfully started and after server restart everything was back to normal.

  • 已提議為解答 Anim8ED 2011年1月20日 0:40
  •  
   
• 2011年1月14日 22:42

   

   
  

  0

  I am having a similar problem but still not able to get the Dashboard to load.

   

  Faulting application name: Dashboard.exe, version: 6.1.7657.0, time stamp: 0x4c3fcbc8

  Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0

  Exception code: 0xe0434352

  Fault offset: 0x000000000000aa7d

  Faulting process id: 0xd38

  Faulting application start time: 0x01cbb438369240b4

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

  Faulting module path: C:\Windows\system32\KERNELBASE.dll

  Report Id: 7bb3db30-202b-11e0-b336-0014d110e62d

  Also this is another error that I am getting.

   

  Application: Dashboard.exe

  Framework Version: v4.0.30319

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

  Exception Info: System.TypeInitializationException

  Stack:

  at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory.SetupConnector[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1<System.__Canon>)

  at Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Internal.AlertAgentProviderClient.BuildConnector()

  at Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Internal.AlertProviderClientBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InitializeConnector()

  at Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Internal.AlertProviderClientBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor()

  at Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.AlertManager..ctor(Boolean, System.Threading.SynchronizationContext)

  at Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.NetworkAlertManager..ctor(Boolean, System.Threading.SynchronizationContext)

  at Microsoft.WindowsServerSolutions.Console.Controls.SubtabBar.AlertButton.InitHealthStatus()

  at Microsoft.WindowsServerSolutions.Console.Controls.SubtabBar.AlertButton.Initialize()

  at Microsoft.WindowsServerSolutions.Controls.Subtab.SubtabBar.AddStandardContent()

  at Microsoft.WindowsServerSolutions.Controls.Subtab.SubtabBar..ctor()

  at Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.CreateSubtabBar()

  at Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.CreateTabControl(System.Object, System.ComponentModel.IComponent)

  at Microsoft.WindowsServerSolutions.Dashboard.Forms.MainForm.RenderContent(System.Object)

  at Microsoft.WindowsServerSolutions.Dashboard.Program.Main()

  I think it has something to do with the certificates.Is there anyone out there that can help me???????????

  I

   
• 2011年1月19日 5:49

   

   
  

  0

   

  Hello,

   I am also unable to bring up dashboard. I would love to manage the home media server through the dashboard. If someone has found the solution to this please post.

  Faulting application name: Dashboard.exe, version: 6.1.7657.0, time stamp: 0x4c3fcbc8
  Faulting module name: KERNELBASE.dll, version: 6.1.7601.17105, time stamp: 0x4ca464bb
  Exception code: 0xe0434352
  Fault offset: 0x000000000000bd6d
  Faulting process id: 0xd24
  Faulting application start time: 0x01cbb75a83ff744c
  Faulting application path: C:\Program Files\Windows Server\Bin\Dashboard.exe
  Faulting module path: C:\Windows\system32\KERNELBASE.dll
  Report Id: ce0c9560-234d-11e0-a0c9-00151731b5f9

   

  Thank you !
  Harsh-

   
• 2011年1月20日 0:40

   

   
  

  1

  I had the same error. Looking into the "C:\ProgramData\Microsoft\Windows Server\Logs\dashboard.log" showed additional information:

  [3516] 110112.105916.8815: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]

  [3516] 110112.105917.1934: WssgCertMgmt: Collection Empty

  [3516] 110112.105917.1934: Sku: Valid machine certificate is not found.

  [3516] 110112.105917.2090: Dashboard.Forms: !!!!FATAL: Dashboard shutting down due to unhandled exception: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception.

  [3516] 110112.105917.4274: Dashboard.Forms: System.TypeInitializationException: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception. ---> Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderException: Machine certificate is not found.

  I checked machine certificates (mmc - Certificates snap-in - Computer account - Personal) there were two of them VAIL and VAIL-CA (VAIL is my server name). Certificates had valid dates, but no root trust. I copied the VAIL_CA certificate and pasted into the Trusted Root Certification Authorities. Certificates got trust, Dashboard successfully started and after server restart everything was back to normal.

   

   

  Worked Great! Thanks for the info!

   
• 2011年2月25日 17:56

   

   
  

  0

  I just used this solution and it worked, also!

  Thanks for the info!

   
• 2011年4月8日 22:42

   

   
  

  0

  I had the same error. Looking into the "C:\ProgramData\Microsoft\Windows Server\Logs\dashboard.log" showed additional information:

  [3516] 110112.105916.8815: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]

  [3516] 110112.105917.1934: WssgCertMgmt: Collection Empty

  [3516] 110112.105917.1934: Sku: Valid machine certificate is not found.

  [3516] 110112.105917.2090: Dashboard.Forms: !!!!FATAL: Dashboard shutting down due to unhandled exception: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception.

  [3516] 110112.105917.4274: Dashboard.Forms: System.TypeInitializationException: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception. ---> Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderException: Machine certificate is not found.

  I checked machine certificates (mmc - Certificates snap-in - Computer account - Personal) there were two of them VAIL and VAIL-CA (VAIL is my server name). Certificates had valid dates, but no root trust. I copied the VAIL_CA certificate and pasted into the Trusted Root Certification Authorities. Certificates got trust, Dashboard successfully started and after server restart everything was back to normal.

   

   

  Worked Great! Thanks for the info!

  i dont understand how to use this solution.

  Can you explain step by step what should I do?

  
  

   
• 2011年4月8日 23:44

   

   
  

  0
  RC or RTM version?

   

   

  "imocattivo" schreef in bericht news:fd4bb8e4-7a88-4870-a9f0-e4e5fa269f17@communitybridge.codeplex.com...

  I had the same error. Looking into the "C:\ProgramData\Microsoft\Windows Server\Logs\dashboard.log" showed additional information:

  [3516] 110112.105916.8815: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]

  [3516] 110112.105917.1934: WssgCertMgmt: Collection Empty

  [3516] 110112.105917.1934: Sku: Valid machine certificate is not found.

  [3516] 110112.105917.2090: Dashboard.Forms: !!!!FATAL: Dashboard shutting down due to unhandled exception: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception.

  [3516] 110112.105917.4274: Dashboard.Forms: System.TypeInitializationException: The type initializer for 'Microsoft.WindowsServerSolutions.Common.ProviderFramework.ConnectorFactory' threw an exception. ---> Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderException: Machine certificate is not found.

  I checked machine certificates (mmc - Certificates snap-in - Computer account - Personal) there were two of them VAIL and VAIL-CA (VAIL is my server name). Certificates had valid dates, but no root trust. I copied the VAIL_CA certificate and pasted into the Trusted Root Certification Authorities. Certificates got trust, Dashboard successfully started and after server restart everything was back to normal.

   

   

  Worked Great! Thanks for the info!

  i dont understand how to use this solution.

  Can you explain step by step what should I do?

  
  

  ---

  Have a nice day!
   
• 2011年4月26日 8:45

  擁有者

   

   
  

  0

  Hello,

  Have this issue get resolved on your machine?

  It will be great if you can log a connect bug so we can invetigate and help similar cases in the community.

   

  Thanks,

   

  Ning

  ---

  This post is "AS IS" and confers no rights. Ning Kuang[MSFT] Windows HSBS Program Manager
   
• 2011年5月13日 17:38

   

   
  

  0

  Try this:

  1. Remote Desktop to the home server.

  2. Control Panel - Administrative Tools - Certification Authority.

  3. Right click the SERVERNAME-CA. All Tasks - Renew CA Certificate.

  4. Right click the SERVERNAME-CA. All Tasks - Start Service.

  5. Open Dashboard after reboot the server.

   
• 2011年5月22日 3:50

   

   
  

  0

  bg4cip, THANK YOU!

  That solved my problem with StorageService.exe faulting (which pretty much hoses everything).  Turns out that my machine rebooted after a CMOS clear, and thus the date/time was borked. This "expired" the CA.

   

  ATTN Microsoft... don't expire a certificate if the system time is _BEFORE_ the certificate was even issued. That's silly.

   
• 2011年5月22日 8:32

   

   
  

  0

  On Sun, 22 May 2011 03:50:07 +0000, Marc Brooks wrote:

  ATTN Microsoft... don't expire a certificate if the system time is BEFORE the certificate was even issued. That's silly.

  That doesn't expire the certificate. A certificate has a Valid From and a
  Valid To value. If the time on your computer is outside of that period,
  then the certificate is considered to be non-valid. That is simply the
  standard way that X.509 certificates work and is not a Microsoft invention
  it is how the RFC is written. Microsoft is simply following standards which
  is the correct thing for them to be doing.

  ---

  Paul Adare
  MVP - Identity Lifecycle Manager
  http://www.identit.ca
  Never trust a computer you can't lift.  -- Stan Masor