locked
GW Service fails to start - DirectoryServicesResolver: Contract exception RRS feed

  • Question

  • Greetings!

    The Gateway service fails to restart, and I have the following in my Gateway-Errors log--It looks like possibly it is not able to bind to AD with the bind user I have set it to use?

    2015-05-12 15:12:33.3434 4088 5   00000000-0000-0000-0000-000000000000 Error [Domain]  Microsoft.Common.ContractException: Contract exception
       at Microsoft.Tri.Common.Data.Entities.Domain.CreateKey(INetworkName name)
       at Microsoft.Tri.Common.Data.Entities.Domain..ctor(DirectoryServicesSearchResult domain, DirectoryServicesSearchResult domainConfiguration)
       at Microsoft.Tri.Gateway.Resolution.DirectoryServicesResolver.<GetDomainsAsync>d__10.MoveNext()

    Thanks

    Tuesday, May 12, 2015 3:18 PM

All replies

  • Hey,

    The binding was actually successful. There was a problem parsing one of the attributes of the domain configuration object that returned from AD.

    Can you check the following attributes:

    1. Is the "dnsRoot" attribute (on the domain configuration object) a valid FQDN?

    2. Does the "nETBIOSName" attribute (on the domain configuration object) contain "."?

    Thanks.


    SK

    Tuesday, May 12, 2015 6:20 PM
  • Ok, I think I know where this is going.... 

    For this domain I inherited, both the dnsRoot & nETBIOSName are identical: "widgets.com"

    Tuesday, May 12, 2015 7:34 PM
  • Yes. The nETBIOSName is the problem here. We currently do not support this but we will in our upcoming version (no ETA yet).

    We will update you when the new version is out.

    Thanks,

    Sivan.


    SK

    Tuesday, May 12, 2015 8:01 PM
  • hmmm too bad.

    Will the new version be out before the 7/29/15 date?

    Tuesday, May 12, 2015 8:53 PM
  • Has the new version been shipped yet?

    Thanks

    Thursday, June 18, 2015 3:56 PM
  • We can't share the exact date but the new version is coming soon.
    Sunday, June 21, 2015 8:12 AM