locked
Bind operation is invalid

    Question

  • I get this error when I open the Exchange Management Console and it tries to populate the mailbox view.

     

    I can't find much posted on t'interweb except a thread referencing the same error but relating specifically to exporting mailboxes. 

     

    All help will be gratefully appreciated!

     

    --------------------------------------------------------
    Microsoft Exchange Error
    --------------------------------------------------------
    The following error(s) were reported while loading topology information:

    get-ExchangeServer
    Failed
    Error:
    Active Directory operation failed on [DC machine]. The supplied credential for [user account] on Bind operation is invalid. Error Code: 0x31.

    The supplied credential is invalid.

     

     

    get-UMServer
    Failed
    Error:
    Active Directory operation failed on [DC machine]. The supplied credential for [user account] on Bind operation is invalid. Error Code: 0x31.

    The supplied credential is invalid.

     


    --------------------------------------------------------
    OK
    --------------------------------------------------------

    Monday, May 19, 2008 4:17 PM

Answers

  • Hi,

     

    The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.

     

    The current issue can be caused by the following factors.

     

    1. The administrative workstation is not a member of a domain, or there is a problem with its domain membership.

    2. An invalid user name or password has been stored on the administrative workstation for use when connecting to a particular domain controller. This stored credential is overriding your current logon credentials.

    3. Network issue.

     

    At this time, I suggest using the following steps to troubleshoot the issue.

     

    Step 1
    ============
    Please log in with another account(I suggest using domain admin) and test the isuse. If it doesn’t work, please let me know if you can open Exchange Management Console on another computer without problem.

     

    If the issue persists, let’s move on.

     

    Step 2
    ============
    Please use dcdiag and netdiag to test if there is any DC or connection issue. Regarding how to use those tools, you can refer to the links below.  

     

    http://technet2.microsoft.com/WindowsServer/en/Library/5237db58-a1e8-40cd-ae8a-7f52848a90f21033.mspx?mfr=true

     

    http://support.microsoft.com/kb/321708/

     

    If the issue persists, please check the error with event viewer and paste the application errors here for our further discussion. Thank you for your efforts and I await your reply,

     

    Elvis 


     

     

    Wednesday, May 21, 2008 11:15 AM

All replies

  • Hi,

     

    The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.

     

    The current issue can be caused by the following factors.

     

    1. The administrative workstation is not a member of a domain, or there is a problem with its domain membership.

    2. An invalid user name or password has been stored on the administrative workstation for use when connecting to a particular domain controller. This stored credential is overriding your current logon credentials.

    3. Network issue.

     

    At this time, I suggest using the following steps to troubleshoot the issue.

     

    Step 1
    ============
    Please log in with another account(I suggest using domain admin) and test the isuse. If it doesn’t work, please let me know if you can open Exchange Management Console on another computer without problem.

     

    If the issue persists, let’s move on.

     

    Step 2
    ============
    Please use dcdiag and netdiag to test if there is any DC or connection issue. Regarding how to use those tools, you can refer to the links below.  

     

    http://technet2.microsoft.com/WindowsServer/en/Library/5237db58-a1e8-40cd-ae8a-7f52848a90f21033.mspx?mfr=true

     

    http://support.microsoft.com/kb/321708/

     

    If the issue persists, please check the error with event viewer and paste the application errors here for our further discussion. Thank you for your efforts and I await your reply,

     

    Elvis 


     

     

    Wednesday, May 21, 2008 11:15 AM
  • Hello Elvis:

    I'm experiencing the exact same problem.  I wonder if I could pop in and ask a few questions?  I can't find a netdiag for windows 2008, and the username/password being used is the administrative account for the domain, so I'm not sure what to change.

    Any suggestions?
    Tuesday, June 03, 2008 3:18 PM
  • Hi,

     

    Can you please paste the detail error in event log here for our further discussion? I await your reply. Thanks,

     

    Elvis

     

    Tuesday, June 10, 2008 7:05 AM
  • Elvis,

     

    Thanks for that.  I'm all sorted now, although embarrassingly it was the simple oversight of logging on as local admin, which had the same credentials as the domain admin (someone else had obviously logged on as local admin since I last went onto the box).  Hence, logging in as domain admin unsurprisingly made the problem go away!

     

    Thanks  Surprise)

    Tuesday, June 10, 2008 10:15 AM
  • Hi.

    I've exactly the same problem.. but using domin administrator !

    I've installer exchange management console on a workstation and when I login with my personnal credentials (mathieu) on the server itself or on the workstation, all is working. Using domain admin, i've this error message:

    --------------------------------------------------------
    Microsoft Exchange Error
    --------------------------------------------------------
    The following error(s) were reported while loading topology information:

    get-ExchangeServer
    Failed
    Error:
    Active Directory operation failed on Core.xxx.xx. The supplied credential for 'XXX\Administrator' on Bind operation is invalid. Error Code: 0x31.

    The supplied credential is invalid.

    get-UMServer
    Failed
    Error:
    Active Directory operation failed on Core.xxx.xx. The supplied credential for 'XXX\Administrator' on Bind operation is invalid. Error Code: 0x31.

    The supplied credential is invalid.


    --------------------------------------------------------
    OK
    --------------------------------------------------------

    Thanks in advance...
    Thursday, April 30, 2009 5:03 PM
  • I am also having the same issue.  I have three users in question names changed to protect the innocent!):

    Domain\Sandra - this is my account, and this is the account Exchange 2007 was installed under.    I can log in and do anything with Exchange.
    Domain\Administrator - Domain admin, local admin on Server.  Via Exchange 2007 tools, has been assinged Exchange Full Administrator (organization).  Can't load Exchange Managment Console.
    Domain\ITRep - same as administrator.  Domain Administrator, Exchange Full (Organizational), Local Admin group.  Can't load Exchange Management Console.

    SIngle domain envirnment.  One other Exchange Server running Exchange 2003 in envirnment.  Exchange 2003 server is core install only, no mailboxes or connectors.  Pending removal, but is attached to BES server that needs to be reconfigured first.  All services have been migrated to Exchange 2007.

    No one other than user Domain\Sandra has been ever able to maintain Exchange 2007 server.

    When attempting administrator or ITRep login, I get this:

    Error:
    Active Directory operation failed on abc.domain.local. The supplied credential for 'EXCALIBUR\Administrator' on Bind operation is invalid. Error Code: 0x31

    Excalibur is the name of the Exchange 2007 Server


    Tuesday, February 02, 2010 7:17 PM
  • Today I had the exact same issue.  Turns out that Elvis was right: SBS2008, control panel - users - Change account type - Advanced tab, Manage Passwords.

    I somehow had 3 entries in there that referenced a non-admin account.  Go figure!

    Deleted those entries, and now I'm working in the Exchange Management Console.

    Strange, but true.

    Thanks Elvis!
    • Proposed as answer by amlitnod Thursday, September 29, 2016 4:53 PM
    Sunday, February 21, 2010 1:43 AM
  • Had the same problem after some updates were installed and system rebooted.

    Fixed it with this steps:

    Removed the Exchange Server 2007 from the domain and reintegrated it then. -->  Had no luck with this.

    Then checked the User Accounts with "control userpasswords2", only the local accounts were shown.  Inserted the domain credentials exactly like the local ones (local admin --> domain admin)

    Finally solved the problem by reconfiguring the saved RDP connection. The RDP session logged in as local user of the Exchange Server.

    After reconfiguring to domain account everything was fine again

     

    Best regards from Germany

    T.Paulat

    • Proposed as answer by Anthony Maw Tuesday, December 24, 2013 6:10 PM
    Saturday, April 10, 2010 11:48 PM
  • Just FYI.

    Had the same trouble on a demo machine (all in one, AD, Exchange, SQL, FIM, ...)
    I was able to solve it by clearing the cached credentials on the server.
    Go to Control Panel > User Account > Manage your network passwords

    Control Panel > User Accounts

    Remove credentials

    Then (after backup ;) ) remove the stored username and passwords for your account.

    HTH,
    Peter


    Peter Geelen - Sr. Consultant IDA (http://www.fim2010.be)

    [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

    Tuesday, June 29, 2010 1:50 PM
  • Hi,

    I had the same problem . I ran the dcdiag command and I found the error that " this computer does not have access from network right". So i opened secpol.msc - user rights assisgnemnt and added administrator user /administrators group here. And it worked.

    Thursday, September 23, 2010 11:02 AM
  • Going to the Control Panel and then to "Stored User Names and Passwords" and removing the entries there solved the problem for me.
    • Proposed as answer by Y'all Tech Thursday, August 11, 2011 2:12 PM
    Monday, July 25, 2011 4:39 PM
  • Going to the Control Panel and then to "Stored User Names and Passwords" and removing the entries there solved the problem for me.
    This worked for me as well. 
    Thursday, August 11, 2011 2:12 PM
  • LOL yeah this fixed my problem thanks.  The problem has absolutely nothing to do with Exchange server mis-configuration. When connecting by RDP is it is easy to forget to put in the domain\ qualifier so if you just log in as local administrator you get the strange error message.  Based on the discussion I see that Systems Admins have spent much time unnecessarily testing and reconfiguring their servers for a very trivial but not so obvious cause! Thanks again from Vancouver Canada.

    anthony maw/vancouver/canada

    Tuesday, December 24, 2013 6:12 PM