Jump to content
RESET Forums (homeservershow.com)

Dashboard won't open


Sorta Oldguy
 Share

Recommended Posts

Noticed a puzzling thing today when trying to restore IE history (yes, I know that's a pretty vain hope).  Dashboard won't open from client. Splash screen appears. But sits there. Two RDP icons appear in taskbar. Eventually have to kill the application with task manager. On the server, sometimes it opens and sometimes not. Every time I try it after killing the client application, it says there's another Dashboard open even thought there no longer is. Have tried it from Win8.1 and Win7 machines with same result. Using the WHS client launcher gives a wrong password error.

 

Eventlog on the server gives two errors for each failure. For whatever reason, I can't paste into this web page and it won't let me upload. Help with that and then the underlying problem would be appreciated.

 

 

Link to comment
Share on other sites

Didn't think to try Firefox. No problem:

 

1st Error from the event log.

 

Log Name:      Security

Source:        Microsoft-Windows-Security-Auditing

Date:          10/22/2014 4:08:49 PM

Event ID:      4625

Task Category: Logon

Level:         Information

Keywords:      Audit Failure

User:          N/A

Computer:      WHS2011

Description:

An account failed to log on.

 

Subject:

Security ID:  SYSTEM

Account Name:  WHS2011$

Account Domain:  WORKGROUP

Logon ID:  0x3e7

 

Logon Type:   3

 

Account For Which Logon Failed:

Security ID:  NULL SID

Account Name: 

Account Domain: 

Failure Information:

Failure Reason:  An Error occured during Logon.

Status:   0xc0000062

Sub Status:  0x0

 

Process Information:

Caller Process ID: 0x2cc

Caller Process Name: C:\Windows\System32\lsass.exe

 

Network Information:

Workstation Name: WHS2011

Source Network Address: -

Source Port:  -

Detailed Authentication Information:

Logon Process:  Schannel

Authentication Package: Kerberos

Transited Services: -

Package Name (NTLM only): -

Key Length:  0

 

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

 

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

 

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

 

The Process Information fields indicate which account and process on the system requested the logon.

 

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

 

The authentication information fields provide detailed information about this specific logon request.

- Transited services indicate which intermediate services have participated in this logon request.

- Package name indicates which sub-protocol was used among the NTLM protocols.

- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />

    <EventID>4625</EventID>

    <Version>0</Version>

    <Level>0</Level>

    <Task>12544</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8010000000000000</Keywords>

    <TimeCreated SystemTime="2014-10-22T21:08:49.752169000Z" />

    <EventRecordID>11050192</EventRecordID>

    <Correlation />

    <Execution ProcessID="716" ThreadID="7712" />

    <Channel>Security</Channel>

    <Computer>WHS2011</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="SubjectUserSid">S-1-5-18</Data>

    <Data Name="SubjectUserName">WHS2011$</Data>

    <Data Name="SubjectDomainName">WORKGROUP</Data>

    <Data Name="SubjectLogonId">0x3e7</Data>

    <Data Name="TargetUserSid">S-1-0-0</Data>

    <Data Name="TargetUserName">

    </Data>

    <Data Name="TargetDomainName">

    </Data>

    <Data Name="Status">0xc0000062</Data>

    <Data Name="FailureReason">%%2304</Data>

    <Data Name="SubStatus">0x0</Data>

    <Data Name="LogonType">3</Data>

    <Data Name="LogonProcessName">Schannel</Data>

    <Data Name="AuthenticationPackageName">Kerberos</Data>

    <Data Name="WorkstationName">WHS2011</Data>

    <Data Name="TransmittedServices">-</Data>

    <Data Name="LmPackageName">-</Data>

    <Data Name="KeyLength">0</Data>

    <Data Name="ProcessId">0x2cc</Data>

    <Data Name="ProcessName">C:\Windows\System32\lsass.exe</Data>

    <Data Name="IpAddress">-</Data>

    <Data Name="IpPort">-</Data>

  </EventData>

</Event>


Here's the second error from the event log:

 

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          10/22/2014 4:08:49 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      WHS2011
Description:
An account failed to log on.

Subject:
    Security ID:        NULL SID
    Account Name:        -
    Account Domain:        -
    Logon ID:        0x0

Logon Type:            3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:        
    Account Domain:        

Failure Information:
    Failure Reason:        The NetLogon component is not active.
    Status:            0xc0000192
    Sub Status:        0x80090325

Process Information:
    Caller Process ID:    0x0
    Caller Process Name:    -

Network Information:
    Workstation Name:    -
    Source Network Address:    -
    Source Port:        -

Detailed Authentication Information:
    Logon Process:        Schannel
    Authentication Package:    Microsoft Unified Security Protocol Provider
    Transited Services:    -
    Package Name (NTLM only):    -
    Key Length:        0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-22T21:08:49.752169000Z" />
    <EventRecordID>11050193</EventRecordID>
    <Correlation />
    <Execution ProcessID="716" ThreadID="7712" />
    <Channel>Security</Channel>
    <Computer>WHS2011</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">
    </Data>
    <Data Name="TargetDomainName">
    </Data>
    <Data Name="Status">0xc0000192</Data>
    <Data Name="FailureReason">%%2306</Data>
    <Data Name="SubStatus">0x80090325</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">Schannel</Data>
    <Data Name="AuthenticationPackageName">Microsoft Unified Security Protocol Provider</Data>
    <Data Name="WorkstationName">-</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
  </EventData>
</Event>

Link to comment
Share on other sites

Nope, not helpful, and 99% certain that it's not related. 

 

If it's opening the dashboard enough to show the splashscreen, then it's already logged in.

 

 

Check "C:\ProgramData\Microsoft\Windows Server\Logs" for any of the "dashboard" logs. It should be by date (or nothing after dashboard). It may provide some indicator as why it's not loading right.

Additionally, if you use the "Options" section and select the "Allow me to choose which add-in's to load", disable  the 3rd party ones, one by one until the dashboard comes up. One or more add-ins may be crashing the dashboard.

Link to comment
Share on other sites

Thanks for the tips. Eventually found something in the log file about AWEICO manager and Cloudberry Backup but hard to interpret. Managed to get safe mode Dashboard to load and disabled manage plugins which was the only relevant option and it loaded. It said there was an update to AWEICO addin manager and Cloudberry. Installed the Cloudberry update and then uninstalled AWEICO from the control panel. After that, it seems to load normally. Don't know which was the problem but I suppose it doesn't matter.

 

Thanks again.

Link to comment
Share on other sites

Well, glad I could help.

 

Though if you could post the specific error, or email me the logs, I can probably give you a good indication based on what you've said.

Link to comment
Share on other sites

  • 4 weeks later...

Sorry I didn't get back to you on this. Various stuff came up and just this just popped back into my head when I got a message digest. If you are still interested I can try to find the log, though it's not a big deal to me since it's working again.

 

Thanks again.

Link to comment
Share on other sites

Not a problem. Life happens. :)

 

And yeah, please feel free to email me the logs.

Easiest way is to grab the entire "C:\ProgramData\Microsoft\Windows Server\Logs" folder. Email it to me at drashna(at)live.com

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...