locked
Sporadic Error: The server is unavailable. RRS feed

  • Question

  • User164680748 posted

    Ok, fairly new to all this and having this error intermittently. It works 90% of the time, so it has me puzzled. It is just a Membership Login Control, that is using AD for authentication. Any help would be greatly appreciated.

    web.config info

    <connectionStrings>
    <add name="ADConnectionString" connectionString="LDAP://domain/DC=domain,DC=com"/>
    </
    connectionStrings>

    <authentication mode="Forms">
    <
    forms name=".ADAuthCookie" timeout="5" loginUrl="Login.aspx" defaultUrl="Default.aspx"></forms>
    </
    authentication>

    <authorization>
       <
    deny users="?"/>
       <
    allow users="*"/>
    </
    authorization>

    <membership defaultProvider="DomainLoginMembershipProvider">
       <
    providers>
       <
    add name="DomainLoginMembershipProvider"    type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0,Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"  connectionStringName="ADConnectionString" connectionUsername="Domain\SomeUser" connectionPassword="thePassword" attributeMapUsername="sAMAccountName" />
    </
    providers>
    </
    membership>

     

    The error description is as follows :

    <?XML:NAMESPACE PREFIX = O /><O:P> </O:P>

    System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The server is unavailable.

       at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)

       at System.DirectoryServices.Protocols.LdapConnection.Bind(NetworkCredential newCredential)

       at System.Web.Security.ActiveDirectoryMembershipProvider.ValidateCredentials(String username, String password)

       at System.Web.Security.ActiveDirectoryMembershipProvider.ValidateUserCore(String username, String password)

       at System.Web.Security.ActiveDirectoryMembershipProvider.ValidateUser(String username, String password)

       at System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e)

       at System.Web.UI.WebControls.Login.AttemptLogin()

       at System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e)

       at System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args)

       at System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e)

       at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)

       at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)

       at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)

       at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)

       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

       --- End of inner exception stack trace ---

       at System.Web.UI.Page.HandleError(Exception e)

       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

       at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

       at System.Web.UI.Page.ProcessRequest()

       at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)

       at System.Web.UI.Page.ProcessRequest(HttpContext context)

       at ASP.login_aspx.ProcessRequest(HttpContext context)

       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    Thursday, February 12, 2009 1:14 PM

All replies

  • User472117617 posted

    check the event log of your domain controller.  also, if it is utilizing most of its resources (high cpu, high mem usage) it may have issues like this.

    Thursday, February 12, 2009 3:04 PM
  • User164680748 posted

    All 12 of my DC's? Wouldn't it hit the least busy....

    I don't see any thing that would point to a issue. No PC login issues or anything.

     

    Thursday, February 12, 2009 6:37 PM
  • User472117617 posted

    Actually I'm not sure how great the load balancing is with LDAP.  I have seen this error myself and the only explanation we ever get from sys admins is, "weird."  At least check your PDC.

    Thursday, February 12, 2009 10:57 PM
  • User-1661535498 posted

    Have you found any solution to this? 

    I receive this same error about 5% of the time.  Once I receive the error I keep receiving it every time I try to login, UNTIL I do an IIS reset on my local machine.  Then it works again for a while.

    Friday, May 8, 2009 10:44 AM