locked
User is now missing from ATA - error occurred while deserializing the DateToAuthenticationKeyToAuthenticationDataMapping property RRS feed

  • Question

  • We have just one user out of thousands who has gone missing from ATA.   Searching by username reveals nothing.   Manually pasting the GUID into the URL yields a blank screen.

    I tried doing an arbitrary write on the AD object to trigger a re-import.  No change.

    The most recent mention of the user's GUID in the ATA logs is from an error message like this:

    2020-02-19 03:26:24.3849 11580 73  Error [BsonClassMapSerializer`1] [message=WebApi action failed [ActionArguments={
      "id": "9999999c-a41c-4473-9c0d-3170a6b36a10"
    }]] System.FormatException: An error occurred while deserializing the DateToAuthenticationKeyToAuthenticationDataMapping property of class Microsoft.Tri.Center.Profiling.Profiles.AccountProfile: AddingDuplicate ---> System.ArgumentException: AddingDuplicate
       at NonBlocking.ConcurrentDictionary`2.Add(TKey key, TValue value)
       at MongoDB.Bson.Serialization.Serializers.DictionarySerializerBase`3.DeserializeArrayRepresentation(BsonDeserializationContext context)
       at ......

    Microsoft.Tri.Center.Management.Controllers.UniqueEntityController.EnhanceUniqueEntityProfileAsync(?)
       at async Microsoft.Tri.Center.Management.Controllers.UniqueEntityController.GetUniqueEntityProfileAsync(?)
       at async System.Threading.Tasks.TaskHelpersExtensions.CastToObject[](?)
       at async System.Web.Http.Controllers.ApiControllerActionInvoker.InvokeActionAsyncCore(?)
       at async System.Web.Http.Controllers.ActionFilterResult.ExecuteAsync(?)
       at async System.Web.Http.Filters.AuthorizationFilterAttribute.ExecuteAuthorizationFilterAsyncCore(?)
       at async System.Web.Http.Filters.AuthorizationFilterAttribute.ExecuteAuthorizationFilterAsyncCore(?)
       at async System.Web.Http.Controllers.ExceptionFilterResult.ExecuteAsync(?)


    • Edited by hukel Wednesday, February 19, 2020 3:31 AM
    Wednesday, February 19, 2020 3:26 AM

All replies

  • Try restarting the Center service and see if it resolves it (hopefully there is a cache problem).

    If it does not help, open a support ticket, as we need to look in the DB to see what happened to the user's document in the DB that made it  unreadable.

    Wednesday, February 19, 2020 6:53 AM