AD problem. There are currently no logon servers available to service the logon request RRS feed

  • Question

  • I have a cluster with HPC Pack Sp2 Beta on it and I got the following error when I want to run Diagnostic or when I access he web portal:

    There are currently no logon servers available to service the logon request.

    I installed the cluster with a LOCAL administrator account, because I didn't find exactly which rights needed for install. Also the cluster build for evaluation purpose and I can't change the network configuration on it. The nodes is part of an enterprise network, and the AD controller is working well, but I don't have write access on it.

    Can somebody suggest something how can I find a workaround for the problem?

    P.S: The cluster build for evaluation.  I don't use any auto deploying features, just azure burst scenarios. 

    Tuesday, June 28, 2011 10:35 AM

All replies

  • I use the following user to run tests and install: CCNT\s138782 and Domain controller:

    The following details I found in the logs:

    Authentication failed when I want to start the diagnostic:

    - <Event xmlns="">
    - <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <TimeCreated SystemTime="2011-06-29T11:03:26.580797300Z" />
    <Correlation />
    <Execution ProcessID="544" ThreadID="4320" />
    <Security />
    - <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">MS-HPC-HEAD$</Data>
    <Data Name="SubjectDomainName">CCNT</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName" />
    <Data Name="TargetDomainName" />
    <Data Name="Status">0xc000005e</Data>
    <Data Name="FailureReason">%%2304</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">C</Data>
    <Data Name="AuthenticationPackageName">Kerberos</Data>
    <Data Name="WorkstationName">MS-HPC-HEAD</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x5e8</Data>
    <Data Name="ProcessName">C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\HpcDiagnostics.exe</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>

    Hpc event about the error:

    - <Event xmlns="">
    - <System>
    <Provider Name="Microsoft-HPC-Diagnostics" Guid="{5FD636C3-5ADD-4564-93A3-C8BAB2527FCA}" />
    <TimeCreated SystemTime="2011-06-29T11:03:26.583727100Z" />
    <Correlation />
    <Execution ProcessID="1512" ThreadID="1716" />
    <Channel>Windows HPC Server</Channel>
    <Security UserID="S-1-5-18" />
    - <EventData>
    <Data Name="Message">There are currently no logon servers available to service the logon request.</Data>
    <Data Name="ExceptionString">Exception detail: System.Security.SecurityException: There are currently no logon servers available to service the logon request. at System.Security.Principal.WindowsIdentity.KerbS4ULogon(String upn) at System.Security.Principal.WindowsIdentity..ctor(String sUserPrincipalName, String type) at System.Security.Principal.WindowsIdentity..ctor(String sUserPrincipalName) at Microsoft.Hpc.Diagnostics.Controller.Utilities.CreateJob(ISchedulerStore store, String requestedBy, StoreProperty[] jobProps) at Microsoft.Hpc.Diagnostics.Controller.PreStepFinishedHandler.ScheduleRunWithTaskResult(DiagnosticTestRun testRun, DiagnosticTest test, StepResult result) at Microsoft.Hpc.Diagnostics.Controller.PreStepFinishedHandler.ExecuteInternal(DiagnosticTestRun testRun) at Microsoft.Hpc.Diagnostics.Controller.StateHandlerBase.Execute() The Zone of the assembly that failed was: MyComputer Current stack: at Microsoft.Hpc.Diagnostics.DiagnosticsTracing.TraceException(String facility, Exception exception) at Microsoft.Hpc.Diagnostics.Controller.StateHandlerBase.Execute() at Microsoft.Hpc.Diagnostics.Controller.DiagnosticsController.RunStateHandlers(Object o) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)</Data>
    Wednesday, June 29, 2011 11:08 AM
  • You probably need Domain Admin rights to setup the HPC Cluster to be part of the domain correctly.  You may want to setup a test domain first, then setup your HPC eval on that test domain.  I wouldn't use the production domain to run the eval.
    Friday, August 5, 2011 3:07 PM