locked
MS ATA Gateway "Value cannot be whitespace" log error RRS feed

  • Question

  • Hi,

    Our Gateway log file includes following errors every now and then. What could cause this, how to fix this?

    2018-xx-xx xx:35:25.9872 4684 60  Error [Ensure] System.ArgumentException: Value cannot be whitespace
    Parameter name: name
       at Microsoft.Tri.Infrastructure.Utils.Ensure.NotNullOrWhiteSpace(String parameterName, String value)
       at Microsoft.Tri.Common.Data.Common.Name..ctor(String name)
       at Microsoft.Tri.Common.Data.Common.DistinguishedName..ctor(IReadOnlyCollection`1 nameParts)
       at Microsoft.Tri.Common.Data.Common.DistinguishedName.get_Domain()
       at Microsoft.Tri.Common.Data.Common.DistinguishedName.get_DomainDnsName()
       at Microsoft.Tri.Common.Data.Common.DomainSecurityPrincipalName.TryParse(String name)

    Friday, October 26, 2018 1:51 PM

All replies

  • What is the exact ATA  version number?
    Saturday, October 27, 2018 8:56 PM
  • We are running version 1.9.7412.9649 or the latest 1.9 update 1.
    Wednesday, October 31, 2018 8:46 AM
  • I think I have seen this once before:

    (Kind of hard to be sure as you only pasted the top of the stack)

    Just a guess, something is issuing LDAP authentications where they send white space in the domain name in a Distinguished name format (not empty, but white space) , or the DC=X was missing
    It happens when we try to parse the source account name in the ldap bind operation.

    Wednesday, October 31, 2018 3:13 PM
  • Strange.

    Here's the full error message, it seems that the code block element of this forum ate half of the message for some reason:

    Error [Ensure] System.ArgumentException: Value cannot be whitespace
    Parameter name: name
       at Microsoft.Tri.Infrastructure.Utils.Ensure.NotNullOrWhiteSpace(String parameterName, String value)
       at Microsoft.Tri.Common.Data.Common.Name..ctor(String name)
       at Microsoft.Tri.Common.Data.Common.DistinguishedName..ctor(IReadOnlyCollection`1 nameParts)
       at Microsoft.Tri.Common.Data.Common.DistinguishedName.get_Domain()
       at Microsoft.Tri.Common.Data.Common.DistinguishedName.get_DomainDnsName()
       at Microsoft.Tri.Common.Data.Common.DomainSecurityPrincipalName.TryParse(String name)
       at Microsoft.Tri.Gateway.Collection.Network.NetworkActivityBuilders.LdapBindBuilder.BuildInternal(ReferenceValue reference, LdapBind ldapBind, NetworkActivityData networkActivityData)
       at Microsoft.Tri.Gateway.Collection.Network.NetworkActivityBuilders.NetworkActivityBuilder`1.Build(ReferenceValue reference, NetworkActivity networkActivity, NetworkActivityData networkActivityData, NetworkActivity verticalChildNetworkActivity, NetworkActivity horizontalParentNetworkActivity)
       at Microsoft.Tri.Gateway.Collection.Network.NetworkActivityTranslator.BuildHorizontalNetworkActivities(IReadOnlyList`1 values, NetworkActivity networkActivity, NetworkActivity parentNetworkActivity, NetworkActivityData networkActivityData)
       at Microsoft.Tri.Gateway.Collection.Network.NetworkActivityTranslator.BuildVerticalNetworkActivities(MessageData messageData)
       at async Microsoft.Tri.Gateway.Collection.Network.NetworkActivityTranslator.TranslateMessageInternalAsync(?)
       at async Microsoft.Tri.Infrastructure.Blocks.ShardedActionBlockWrapper`1.<>c__DisplayClass6_0.<-ctor>b__1[](?)
       at async Microsoft.Tri.Infrastructure.Blocks.ActionBlockWrapper`1.<>c__DisplayClass10_0.<-ctor>b__0[](?)

    • Edited by Ukkö Monday, November 26, 2018 11:08 AM update code block
    Monday, November 26, 2018 11:06 AM
  • Yes, this confirms this is the issue I mentioned above.

    you can ignore it as there is nothing you can really do to fix it unless you can locate who is creating those broken authentications....

    Monday, November 26, 2018 1:29 PM