Dashboard tot nach Installation Lights-Out2

Probleme oder Fragen zum Lights-Out Add-In unter allen Windows Plattformen werden hier beantwortet
Antworten
lfb
Foren-Einsteiger
Beiträge: 6
Registriert: 21. Dez 2008, 16:33

Dashboard tot nach Installation Lights-Out2

Beitrag von lfb » 4. Jun 2017, 13:51

Nach Installation von Lights-Out 2 startet das Dashboard auf einem WHS 2011 nicht mehr. Bei Start kommt eine Auswahl, ein oder zwei Module su deaktivieren. Diese Module wechseln, Unabhängig davon, was man da macht, bricht der Dashboardstart kommentarlos ab. 2 Fehler:
Error 1026 .NET-runtime:
[+] Abschnitt
Anwendung: Dashboard.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.IO.FileNotFoundException
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Controls.AdminListView..ctor(Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IListContent)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.ConsolePageViewFactories.CreateListView(System.Object, System.ComponentModel.IComponent)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.ConsolePageFactory+<>c__DisplayClass4.<CreateConsolePage>b__0()
bei Microsoft.WindowsServerSolutions.Administration.Extensibility.PluginManager.ObjectModelInitialization(System.Object, Microsoft.WindowsServerSolutions.Administration.Extensibility.InitializeObjectModel)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.ConsolePageFactory.CreateConsolePage(System.Object, System.ComponentModel.IComponent)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.GetPages(Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode, Microsoft.WindowsServerSolutions.Dashboard.Forms.ComponentServices.NestedServiceContainer ByRef)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.CreateTopLevelTab(Microsoft.WindowsServerSolutions.Controls.Subtab.SubtabBar, Microsoft.WindowsServerSolutions.Dashboard.Forms.Controls.Tabstrip.TabstripWinformsHost, Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode, Boolean)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.CreateTabControl(System.Object, System.ComponentModel.IComponent)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.MainForm.RenderContent(System.Object)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.MainForm.Create(Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.ContentProvider)
bei Microsoft.WindowsServerSolutions.Dashboard.Program.Main()
Error 1000 Application Error
[+] Abschnitt
Name der fehlerhaften Anwendung: Dashboard.exe, Version: 6.1.8800.16402, Zeitstempel: 0x5115acc7
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.1.7601.23796, Zeitstempel: 0x59029714
Ausnahmecode: 0xe0434352
Fehleroffset: 0x000000000001a06d
ID des fehlerhaften Prozesses: 0x6ec
Startzeit der fehlerhaften Anwendung: 0x01d2dd28350ad7ac
Pfad der fehlerhaften Anwendung: C:\Program Files\Windows Server\Bin\Dashboard.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\KERNELBASE.dll
Berichtskennung: 7f21046c-491b-11e7-be4a-10c37b44f29c
Deinstallation Lightsout2 => keine Änderung
SFC /scannow findet alles in Ordnung

Falls jemand eine gute Idee hat?

Benutzeravatar
larry
Moderator
Beiträge: 9667
Registriert: 22. Dez 2007, 16:13

Re: Dashboard tot nach Installation Lights-Out2

Beitrag von larry » 4. Jun 2017, 14:20

Schaum mal ins Logfile (C:\ProgramData\Microsoft\Windows Server\Logs\Dashboard.log) oder füge es hänge es hier als Dateianhang an.
Da sollten weitere Details aufgeführt sein.

Gruß
Larry

lfb
Foren-Einsteiger
Beiträge: 6
Registriert: 21. Dez 2008, 16:33

Re: Dashboard tot nach Installation Lights-Out2

Beitrag von lfb » 4. Jun 2017, 14:36

Danke für die schnelle Antwort!

Letzter Start des Dashboard
[+] Abschnitt
[588] 170604.142416.5861: General: Initializing...C:\Program Files\Windows Server\Bin\Dashboard.exe
[588] 170604.142417.1009: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[588] 170604.142417.1009: PluginManager: Unable to load type AWIECO.RemoteLauncher.Dashboard.TopLevelTabPageProvider, AWIECO.RemoteLauncher.Dashboard, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null from C:\Program Files\Windows Server\Bin\. Die Datei oder Assembly "AWIECO.RemoteLauncher.Dashboard, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
[4792] 170604.142417.1945: General: Color branding started
[4792] 170604.142417.2101: General: Processing Microsoft default SKU branding colors XML
[4792] 170604.142417.2101: 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 >
[4792] 170604.142417.2725: General: Branding colors XML parsing started
[4792] 170604.142417.2725: General: Branding colors XML parsing ended
[4792] 170604.142417.2725: General: Looking for OEM branding colors XML
[4792] 170604.142417.2725: General: No OEM informations available
[4792] 170604.142417.2725: General: Color branding complete
[588] 170604.142418.4737: safemode: New suspect plugin detected while loading the Dashboard: "serverfolders", "Addins\Storage", Microsoft.WindowsServerSolutions.Console.AddIns.Folders.FoldersPage, Microsoft.WindowsServerSolutions.Console.AddIns.Folders, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[588] 170604.142421.5001: General: Search for object with query: Select * FROM SoftwareLicensingService
[588] 170604.142424.3394: General: Search for object with query: Select * FROM SoftwareLicensingProduct WHERE ApplicationId="55c92734-d682-4d71-983e-d6ec3f16059f" AND PartialProductKey <> null
[588] 170604.142425.8214: General: ActivationStatus.ReArmCount = 3
[588] 170604.142425.8214: General: ActivationStatus.LicenseStatus = 1
[588] 170604.142425.8214: General: ActivationStatus.GracePeriod (minutes) = 0
[588] 170604.142426.1022: Dashboard.Forms: Creating TabControl PrimaryTabs
[588] 170604.142426.1958: General: Loading the external top-level tabs
[588] 170604.142426.2270: PluginManager: Die Datei oder Assembly "Avast.WHS.Dashboard" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
[588] 170604.142426.2270: PluginManager: Plugin will not be loaded as it was determined that type Avast.Whs.Dashboard.AvastWhsTabProvider, Avast.WHS.Dashboard is not valid
[588] 170604.142426.2270: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Primary\AvastWhsAddinConfig.addin
[588] 170604.142430.0646: PluginManager: Die Datei oder Assembly "Avast.WHS.Dashboard" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
[588] 170604.142430.0646: PluginManager: Plugin will not be loaded as it was determined that type Avast.Whs.Dashboard.AvastWhsTabProvider, Avast.WHS.Dashboard is not valid
[588] 170604.142430.0646: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Primary\AvastWhsAddinConfig.addin
[588] 170604.142430.4390: ProviderFramework: Information: [0] : Register to listen to ProviderRegistryConnectionMgmt connected event.
[588] 170604.142430.4390: ProviderFramework: Information: [0] : ProviderRegistryProxy: Beginning connection attempt.
[588] 170604.142430.4546: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
[588] 170604.142430.4702: ProviderFramework: Information: [0] : ConnectionMgmt: _CreateChannel address generated = [net.tcp://cf-home-server:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[588] 170604.142430.4858: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
[588] 170604.142430.4858: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[588] 170604.142430.4858: ProviderFramework: Information: [0] : Address: [net.tcp://cf-home-server:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
[588] 170604.142430.4858: ProviderFramework: Information: [0] : Binding: []
[588] 170604.142430.4858: ProviderFramework: Information: [0] : Identifier: []
[588] 170604.142430.4858: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
[588] 170604.142430.4858: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [None]
[588] 170604.142430.4858: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
[588] 170604.142430.5170: PfBinding: Information: [0] : Adding service dns identity [CF-HOME-SERVER] in proxy endpoint.
[588] 170604.142430.5326: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
[588] 170604.142430.6262: ProviderFramework: Information: [0] : ConnectAsync was NOT able to synchronously connect to the provider registry.
[588] 170604.142430.6886: ProviderFramework: Information: [0] : (current thread: 0x24c): Installing new PfSynchronizationContext.
[588] 170604.142430.6886: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService, False,
[588] 170604.142430.7042: ProviderFramework: Information: [0] : (current thread: 0x24c): Installing new PfSynchronizationContext.
[588] 170604.142430.7042: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService, True,
[4548] 170604.142431.6870: ProviderFramework: Information: [0] : _OnConnected called.
[4548] 170604.142431.6870: ProviderFramework: Information: [0] : _CoreConnected is called.
[4224] 170604.142431.8274: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.wssg_alert_agent/Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService net.tcp://cf-home-server:6602/Microsoft.WindowsServerSolutions.wssg_alert_mgmt_and_sync/Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : CreateWithCallback: Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : CreateWithCallback: Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService]
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : Address: [net.tcp://cf-home-server:6602/Microsoft.WindowsServerSolutions.wssg_alert_mgmt_and_sync/Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService]
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : Binding: [net.tcp]
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.wssg_alert_mgmt_and_sync]
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
[4444] 170604.142431.8430: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService]
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : Address: [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.wssg_alert_agent/Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService]
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : Binding: [net.tcp]
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.wssg_alert_agent]
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowLocalAccessOnly]
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
[4224] 170604.142431.8430: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
[4224] 170604.142431.9054: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
[4444] 170604.142431.9054: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
[4548] 170604.142432.1550: ProviderFramework: Information: [0] : ProviderConnector: Received connection
[4444] 170604.142432.1550: ProviderFramework: Information: [0] : ProviderConnector: Received connection
[4548] 170604.142432.1706: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertAgentProviderService
[4444] 170604.142432.1706: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Service.IAlertManagementProviderService
[4548] 170604.142432.1706: AlertFramework: Subcomponent: NetworkAlertManager > LocalProviderClient_ConnectionOpened:
[4444] 170604.142432.1706: AlertFramework: Subcomponent: NetworkAlertManager > ServerProviderClient_ConnectionOpened:
[4548] 170604.142432.1706: AlertFramework: Subcomponent: NetworkAlertManager > RaiseConnectionOpenClose: Raising event. connected=True.
[4444] 170604.142432.1706: AlertFramework: Subcomponent: NetworkAlertManager > RaiseConnectionOpenClose: Raising event. connected=True.
[588] 170604.142433.4966: Dashboard.Forms: CreateTabstripControl: Could not successfully release the device context for the screen.
[588] 170604.142433.5278: Dashboard.Forms: Creating TabPage for node E14FC830-F3A5-4ae6-BA8F-35A083EA5654 with display name "Start" for TabControl
[588] 170604.142433.6994: Dashboard.Forms: Creating TabPage for node F0F0CF38-4269-44dd-90D1-A284506C4C2E with display name "Benutzer" for TabControl
[588] 170604.142433.8086: Dashboard.Forms: Creating TabPage for node AFA7A628-4DA9-4982-9CCB-10F7458871FD with display name "Computer
und Sicherung" for TabControl
[588] 170604.142433.9334: Dashboard.Forms: Creating TabPage for node D730AA04-07B1-4b9c-9DED-CCB0A723A8EB with display name "Serverordner
und Festplatten" for TabControl
[588] 170604.142434.4326: StorageOM: StorageBacked created successfully.
[588] 170604.142434.4326: StorageOM: Set connection identifier to 1
[588] 170604.142434.4326: ProviderFramework: Information: [0] : (current thread: 0x24c): Installing new PfSynchronizationContext.
[588] 170604.142434.4482: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Storage.IStorageProviderService, True,
[588] 170604.142434.4482: ProviderFramework: Information: [0] : (current thread: 0x24c): PfSynchronizationContext not needed.
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.Storage.IStorageProviderService net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.Storage/Microsoft.WindowsServerSolutions.Storage.IStorageProviderService
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.Storage.IStorageProviderService
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : CreateWithCallback: Microsoft.WindowsServerSolutions.Storage.IStorageProviderService
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Storage.IStorageProviderService]
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : Address: [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.Storage/Microsoft.WindowsServerSolutions.Storage.IStorageProviderService]
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : Binding: [net.tcp]
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.Storage]
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowLocalAccessOnly]
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
[4548] 170604.142434.4482: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
[4548] 170604.142434.4638: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
[588] 170604.142434.4638: ProviderFramework: Information: [0] : (current thread: 0x24c): PfSynchronizationContext not needed.
[4548] 170604.142434.4638: ProviderFramework: Information: [0] : ProviderConnector: Received connection
[4548] 170604.142434.4638: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.Storage.IStorageProviderService
[4548] 170604.142434.4794: StorageOM: Getting storage data from server
[4548] 170604.142434.4794: ProviderFramework: Information: [0] : (current thread: 0x11c4): PfSynchronizationContext not needed.
[4548] 170604.142434.4794: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Users.IUserManagementProvider, True,
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.Users.IUserManagementProvider net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.UserManagementProvider/Microsoft.WindowsServerSolutions.Users.IUserManagementProvider
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.Users.IUserManagementProvider
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : CreateWithCallback: Microsoft.WindowsServerSolutions.Users.IUserManagementProvider
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Users.IUserManagementProvider]
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : Address: [net.tcp://127.0.0.1:65532/Microsoft.WindowsServerSolutions.UserManagementProvider/Microsoft.WindowsServerSolutions.Users.IUserManagementProvider]
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : Binding: [net.tcp]
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.UserManagementProvider]
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowLocalAccessOnly]
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
[4548] 170604.142434.4950: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
[4548] 170604.142434.5418: ProviderFramework: Information: [0] : ProviderConnector: Received connection
[4548] 170604.142434.5418: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.Users.IUserManagementProvider
[4444] 170604.142434.5418: AlertFramework: Subcomponent: AlertManagementProviderClient > GetAllAlertsInfo: trunk.HasMore=False, count=8
[4224] 170604.142434.5418: AlertFramework: Subcomponent: AlertManagementProviderClient > GetAllAlertsInfo: trunk.HasMore=False, count=8
[4444] 170604.142434.5574: AlertFramework: Subcomponent: AlertAgentProviderClient > GetAllAlertsInfo: trunk.HasMore=False, count=4
[4224] 170604.142434.5574: AlertFramework: Subcomponent: AlertAgentProviderClient > GetAllAlertsInfo: trunk.HasMore=False, count=4
[4444] 170604.142434.5574: AlertFramework: GetLocalMachineSID: The local machine Sid is S-1-5-21-3170163110-715113697-3105956378-1010
[4224] 170604.142434.5574: AlertFramework: GetLocalMachineSID: The local machine Sid is S-1-5-21-3170163110-715113697-3105956378-1010
[588] 170604.142434.5574: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[588] 170604.142434.5574: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.Console.AddIns.Folders.FoldersPage, Microsoft.WindowsServerSolutions.Console.AddIns.Folders from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Adorners.PageContentAdorner
[588] 170604.142434.5574: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.Console.AddIns.Folders.FoldersPage, Microsoft.WindowsServerSolutions.Console.AddIns.Folders
[588] 170604.142434.5574: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Storage\serverfolders.addin
[588] 170604.142434.5574: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[588] 170604.142434.5574: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.Console.AddIns.Drives.DrivesPage, Microsoft.WindowsServerSolutions.Console.AddIns.Drives from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Adorners.PageContentAdorner
[588] 170604.142434.5574: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.Console.AddIns.Drives.DrivesPage, Microsoft.WindowsServerSolutions.Console.AddIns.Drives
[588] 170604.142434.5574: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Storage\serverharddrives.addin
[588] 170604.142434.5574: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[588] 170604.142434.5574: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.Console.AddIns.Folders.FoldersPage, Microsoft.WindowsServerSolutions.Console.AddIns.Folders from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Adorners.PageContentAdorner
[588] 170604.142434.5574: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.Console.AddIns.Folders.FoldersPage, Microsoft.WindowsServerSolutions.Console.AddIns.Folders
[588] 170604.142434.5574: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Storage\serverfolders.addin
[588] 170604.142434.5574: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[588] 170604.142434.5574: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.Console.AddIns.Drives.DrivesPage, Microsoft.WindowsServerSolutions.Console.AddIns.Drives from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Adorners.PageContentAdorner
[588] 170604.142434.5574: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.Console.AddIns.Drives.DrivesPage, Microsoft.WindowsServerSolutions.Console.AddIns.Drives
[588] 170604.142434.5574: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Storage\serverharddrives.addin
[588] 170604.142434.7446: Dashboard.Forms: !!!!FATAL: Dashboard shutting down due to unhandled exception: Die Datei oder Assembly "Controls.dll" oder eine Abhängigkeit davon wurde nicht gefunden. Das angegebene Modul wurde nicht gefunden.
[588] 170604.142434.7758: Dashboard.Forms: System.IO.FileNotFoundException: Die Datei oder Assembly "Controls.dll" oder eine Abhängigkeit davon wurde nicht gefunden. Das angegebene Modul wurde nicht gefunden.
Dateiname: "Controls.dll"
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Controls.AdminListView..ctor(IListContent listContent)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.ConsolePageViewFactories.CreateListView(Object content, IComponent owner)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.ConsolePageFactory.<>c__DisplayClass4.<CreateConsolePage>b__0()
bei Microsoft.WindowsServerSolutions.Administration.Extensibility.PluginManager.ObjectModelInitialization(Object objectModelInstance, InitializeObjectModel initializeObjectModel)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.ConsolePageFactory.CreateConsolePage(Object content, IComponent owner)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.GetPages(IContentNode primaryTabNode, NestedServiceContainer& tabPageServiceContainer)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.CreateTopLevelTab(SubtabBar subtabBar, TabstripWinformsHost tabControl, IContentNode tab, Boolean setCurrentTabAsActive)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.Content.TabControlFactory.CreateTabControl(Object content, IComponent owner)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.MainForm.RenderContent(Object content)
bei Microsoft.WindowsServerSolutions.Dashboard.Forms.MainForm.Create(ContentProvider contentProvider)
bei Microsoft.WindowsServerSolutions.Dashboard.Program.Main()
Deinstallation Lightsout2 => keine Änderung
SFC /scannow findet alles in Ordnung
Update rollup 4 deinstalliert und neuinstalliert- keine Änderung
.NET 4.7 deu. und eng. "repariert" keine Änderung
EIne Datei controlls.dll findet sich in C:\Programme\Windows Server\Bin (3/3/2011, 6.1.8800.16385)

Benutzeravatar
larry
Moderator
Beiträge: 9667
Registriert: 22. Dez 2007, 16:13

Re: Dashboard tot nach Installation Lights-Out2

Beitrag von larry » 4. Jun 2017, 15:12

Der erste Fehler scheint wohl dieser zu sein:
Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Storage\serverfolders.addin

Kannst du mal schauen, ob es die Datei gibt und diese ggf. hier als Dateianhang (Nicht als Text!) einfügen.

lfb
Foren-Einsteiger
Beiträge: 6
Registriert: 21. Dez 2008, 16:33

Re: Dashboard tot nach Installation Lights-Out2

Beitrag von lfb » 4. Jun 2017, 15:45

Nochmal Danke!

Aber die Datei gibt es und sie ist identisch mit der vom backup vom Vortag. Ebenso alle anderen in den Unterordnern von C:\Program Files\Windows Server\Bin\Addins (FC: Keine Unterschiede gefunden)

lfb
Foren-Einsteiger
Beiträge: 6
Registriert: 21. Dez 2008, 16:33

Re: Dashboard tot nach Installation Lights-Out2

Beitrag von lfb » 4. Jun 2017, 16:37

WHS 2011 mit Lights-Out 1.6.1.2408
Lights-Out Vail 1.6 deinstalliert (Dashboard)
Lights-Out 2 2.0.3.3562 installiert => Dashboard startet nicht mehr

Felhlermedung siehe vorige Beiträge

Deinstallation Lightsout2 => keine Änderung
SFC /scannow findet alles in Ordnung
Update rollup 4 deinstalliert und neuinstalliert- keine Änderung
.NET 4.7 deu. und eng. "repariert" keine Änderung
Update Rollup für .NET Framework 3.5.1 for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB4014596) nochmal installiert
EIne Datei controlls.dll findet sich in C:\Programme\Windows Server\Bin (3/3/2011, 6.1.8800.16385)

Alle addins sind mit den Versionen von einem 1 Tag altem Backup identisch
Der ganze Verzeichnisbaum C:\Program Files\Windows Server\Bin ist bis auf Lights-Out relatierte Dateien identisch mit dem Backup

Lights-Out 1.6 Vail (1.6.2 Build 2431) wieder installiert, geht wieder???

Hat jemand eine gute Idee? Und nochmal vielen Dank für die Hilfe!

Benutzeravatar
larry
Moderator
Beiträge: 9667
Registriert: 22. Dez 2007, 16:13

Re: Dashboard tot nach Installation Lights-Out2

Beitrag von larry » 5. Jun 2017, 10:44

lfb hat geschrieben:
4. Jun 2017, 16:37
Lights-Out 1.6 Vail (1.6.2 Build 2431) wieder installiert, geht wieder???
War das jetzt eine Frage oder geht es jetzt wieder?

lfb
Foren-Einsteiger
Beiträge: 6
Registriert: 21. Dez 2008, 16:33

Re: Dashboard tot nach Installation Lights-Out2

Beitrag von lfb » 6. Jun 2017, 08:39

Es funktioniert. Ich war nur ziemlich erstaunt, dass die Deinstallation von Lights-Out 1.6 zu so einem Effekt führen kann und sich der Fehler mit einer Reinstallation beheben lässt. Ich habe es nicht auf Reproduzierbarkeit geprüft, da der Rechner gut 1000km von mir entfernt steht.

Dann wird der Rechner halt mit Version 1.6 arbeiten bis zu seinem Ende :-)

Antworten