locked
CRM 4 IFD published with TMG(isa) Server : Unable adding users ->ActiveDirectoryUtility.FindUser(String domainAccountName) RRS feed

  • Question

  • Hello,

    I read some forum answer about this but nothing drive me to a solution.
    I have applied the Service providers settings, having potected the users in AD and set the internal CNAME fo each oganization in DNS.

    What is strange is that when I try to add several users, all the user is successfully read from AD and displayed in lookup, but I get a COM error when I press Add User and the crm web service ty to find one ???

    System.Runtime.InteropServices.COMException (0x8007203A): The server is not operational.

    Any help welcome.

    CS

    Sunday, April 18, 2010 8:06 AM

All replies

  • do you install latest update for the crm

    try to install last update http://support.microsoft.com/default.aspx/kb/949256?p=1


    Thanks for any help :) my blog is: http://www.waelk.com

    • Edited by wael_e Thursday, April 22, 2010 6:55 AM add more information and link
    Thursday, April 22, 2010 6:51 AM
  • I have this same problem.  I just patched up CRM 2011 but that didn't help.

     

    [2011-12-13 13:21:22.893] Process: w3wp |Organization:faa8e6a1-ccb2-de11-99b7-001517a8e025 |Thread:   66 |Category: Application |User: 00000000-0000-0000-0000-000000000000 |Level: Error | ActiveDirectoryUtility.FindUser
    >Unable to get find user ibts\ssands: System.Runtime.InteropServices.COMException (0x8007203A): The server is not operational.
    >
    >   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
    >   at System.DirectoryServices.DirectoryEntry.Bind()
    >   at System.DirectoryServices.DirectoryEntry.get_AdsObject()
    >   at System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne)
    >   at System.DirectoryServices.DirectorySearcher.FindOne()
    >   at Microsoft.Crm.Application.Utility.ActiveDirectoryUtility.FindUser(String domainAccountName)

    Tuesday, December 13, 2011 7:23 PM
  • I had a DNS entery for mydomain.mydomain.org that's a left over from my predecessors.  Using Wireshark I was able to determine that the server was doing a lookup on this, then subsequent lookups had the extra "domain." in front fo them causing them to fail.
    Monday, December 19, 2011 11:28 PM