none
Eventlog: Given key not found and resource missing

    Question

  • Hello at all,

    I having a strange issue in one of my customers environments.

    My eventlog is filled with many many error saying either "The given key was not present in the dictionary." and "Resource is missing".

    Here are the full details on both eventlogs:

    Requestor: urn:uuid:e1603551-065e-4f84-a236-acb00d1c8e18
    Correlation Identifier: 3fdbcc5d-45d2-4541-830d-a7ccffed9327
    Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
       at System.ThrowHelper.ThrowKeyNotFoundException()
       at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
       at Microsoft.ResourceManagement.Query.QueryParametersGenerator.WriteRequestedAttributes()
       at Microsoft.ResourceManagement.Query.QueryParametersGenerator.BuildParameterString()
       at Microsoft.ResourceManagement.Query.QueryProcessor.BuildSqlCommand(Query objectRepresentation, Boolean countResultsOnly)
       at Microsoft.ResourceManagement.Query.QueryProcessor.ExecuteQuery(Query query, Nullable`1 maximumTime, Boolean& endOfSequence, Boolean countResultsOnly, Int64& resultCount, Int64& executionTime)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecutePullActionImpl(PullRequestParameter pullParameter)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteEnumerateAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey, Boolean isRedispatch)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Enumerate(Message request)
       --- End of inner exception stack trace ---


    Requestor: urn:uuid:b3694817-313e-449f-b471-6484b3917c02
    Correlation Identifier: 3fae4696-f7de-490f-bb77-a3603fce43f0
    Microsoft.ResourceManagement.Service: Microsoft.ResourceManagement.WebServices.Exceptions.PermissionDeniedException: ResourceIsMissing
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteGetAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey, Boolean isRedispatch)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Get(Message request)

    and also some short snippet from the FIM Service trace in verbose mode:

    Microsoft.ResourceManagement Verbose: 0 : Request '' status was updated in-memory from 'NotFound' to 'Validating'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4651988Z
    Microsoft.ResourceManagement Verbose: 0 : Request created: ''
    
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4671990Z
    Microsoft.ResourceManagement Verbose: 0 : Entered RequestDispatcher with Request Object; RequestIdentifier 'dd715f67-ccba-4496-bb6e-1fba39283358'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4681991Z
    Microsoft.ResourceManagement Verbose: 0 : Add request 'dd715f67-ccba-4496-bb6e-1fba39283358' to cache with RequestStatus 'Validating'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4681991Z
    Microsoft.ResourceManagement Information: 1 : RequestDispatcher enter processing pipeline;  RequestIdentifier 'dd715f67-ccba-4496-bb6e-1fba39283358'; Operation 'Get'; Object ''; RequestStatus 'Validating'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4691992Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier 'dd715f67-ccba-4496-bb6e-1fba39283358' for a 'Get' operation on object '' with RequestStatus 'Validating'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4701993Z
    Microsoft.ResourceManagement Verbose: 0 : Request 'dd715f67-ccba-4496-bb6e-1fba39283358' status was updated in-memory from 'Validating' to 'Validated'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4761999Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier 'dd715f67-ccba-4496-bb6e-1fba39283358' for a 'Get' operation on object '' with RequestStatus 'Validated'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4772000Z
    Microsoft.ResourceManagement Verbose: 0 : Executing initial authentication.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4782001Z
    Microsoft.ResourceManagement Verbose: 0 : Request 'dd715f67-ccba-4496-bb6e-1fba39283358' status was updated in-memory from 'Validated' to 'Authenticating'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4792002Z
    Microsoft.ResourceManagement Verbose: 0 : Request 'dd715f67-ccba-4496-bb6e-1fba39283358' status was updated in-memory from 'Authenticating' to 'Authenticated'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4802003Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier 'dd715f67-ccba-4496-bb6e-1fba39283358' for a 'Get' operation on object '' with RequestStatus 'Authenticated'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4802003Z
    Microsoft.ResourceManagement Verbose: 0 : Request 'dd715f67-ccba-4496-bb6e-1fba39283358' status was updated in-memory from 'Authenticated' to 'Authorized'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4812004Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier 'dd715f67-ccba-4496-bb6e-1fba39283358' for a 'Get' operation on object '' with RequestStatus 'Authorized'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4822005Z
    Microsoft.ResourceManagement Information: 1 : WS: Action.Get.Execute.Enter
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4822005Z
    Microsoft.ResourceManagement Verbose: 0 : XPathDialectParser.ParseXPathExpression.Enter(/Person[ObjectID='fb89aefa-5ea1-47f1-8890-abe7797d6497'])
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4842007Z
    Microsoft.ResourceManagement Verbose: 0 : XPathDialectParser.Enumerate.BuilderResult(/Person[ObjectID = 'fb89aefa-5ea1-47f1-8890-abe7797d6497'])
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4872010Z
    Microsoft.ResourceManagement Verbose: 0 : XPathDialectParser.ParseXPathExpression.Exit(/Person[ObjectID = 'fb89aefa-5ea1-47f1-8890-abe7797d6497'])
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4872010Z
    Microsoft.ResourceManagement Information: 1 : Query: QueryProcessor.ExecuteQuery.ExecuteReader.Enter
        ThreadId=16
        DateTime=2013-12-19T14:14:23.4882011Z
    Microsoft.ResourceManagement Information: 1 : Query: QueryProcessor.ExecuteQuery.ExecuteReader.Exit
        ThreadId=16
        DateTime=2013-12-19T14:14:23.6252148Z
    Microsoft.ResourceManagement Verbose: 0 : Request 'dd715f67-ccba-4496-bb6e-1fba39283358' status was updated in-memory from 'Authorized' to 'Denied'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.6282151Z
    Microsoft.ResourceManagement Information: 1 : RequestIdentifier 'dd715f67-ccba-4496-bb6e-1fba39283358' exited RequestDispatcher with RequestStatus 'Denied'.
        ThreadId=16
        DateTime=2013-12-19T14:14:23.6282151Z
    Microsoft.ResourceManagement Information: 1 : WS: Get:PermissionDenied
        ThreadId=16
        DateTime=2013-12-19T14:14:23.6302153Z
    Microsoft.ResourceManagement Error: 3 : Requestor: urn:uuid:0aac2c9a-5a8b-44c7-ba8b-909d459a3d66
    Correlation Identifier: 771ee212-67a9-410a-bffe-fef76a78e366
    Microsoft.ResourceManagement.Service: Microsoft.ResourceManagement.WebServices.Exceptions.PermissionDeniedException: ResourceIsMissing
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteGetAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey, Boolean isRedispatch)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Get(Message request)
        ThreadId=16
        DateTime=2013-12-19T14:14:23.6312154Z
    Microsoft.ResourceManagement Information: 1 : WS: Get: exit
        ThreadId=16
        DateTime=2013-12-19T14:14:24.0012524Z
    Microsoft.ResourceManagement Information: 1 : WS: Get: enter
        ThreadId=16
        DateTime=2013-12-19T14:14:24.0792602Z
    Microsoft.ResourceManagement Information: 1 : WS: ObjectType,ObjectID,DisplayName,Locale
        ThreadId=16
        DateTime=2013-12-19T14:14:24.0822605Z
    Microsoft.ResourceManagement Information: 1 : WS: GetCurrentUserFromSecurityIdentifier.Enter: S-1-5-21-1343024091-790525478-839522115-44293
        ThreadId=16
        DateTime=2013-12-19T14:14:24.0832606Z
    Microsoft.ResourceManagement Information: 1 : WS: GetCurrentUserFromSecurityIdentifier.Exit
        ThreadId=16
        DateTime=2013-12-19T14:14:24.0842607Z
    Microsoft.ResourceManagement Information: 1 : Get(fb89aefa-5ea1-47f1-8890-abe7797d6497)
        ThreadId=16
        DateTime=2013-12-19T14:14:24.0852608Z
    

    Tracelog is nearly identical on the "key not present" error, after authorized, the request (which i can see is a read/get) is switched back to denied.

    The only thing that in common in all errors in the tracelog is that it occurs on a get of a guid/reference.

    In Portal everthing is working like expected i see no errors, all data is displayed like it should, not resources oder value are missing.

    But at the most places I click in portal it generates one of the to event, even if I switch from one user tab to another, but only this ones which holds group reporting controls (no errors on tab where manager and assistant are displayed).

    Eventlogs also apperas on displaying all users or searching for them and even in request history and MPR list.

    I am the initial administrator and in addition give (for testing) explicit read to all objects with all attributes to the admin set

    So the problem is not that urgent as all is working like expected but it fills up my eventlog, making it hard to seperate this errors from real issues.

    Environment ist FIM 2010 R2 Sp1 with latest Hotfix (4.1.3496.0) running on SharePoint Foundation 2013 on a Server 2008 R2. SP2013 was installed with the help on the guide from FimSpecialist.

    Anyone a hint on how to solve this ?

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    vendredi 20 décembre 2013 11:32

Réponses

  • Hello Peter,

    Try the steps in the KB for the hotfix.

    http://support.microsoft.com/kb/2906832/en-us

    The hotfix includes a new feature to optionally hide the advanced search option in the portal, but it requires manual schema changes.  I had the same errors after installing the hotfix 4.1.3496.0, but they stopped after manually updating the schema as instructed in the article.

    I left the option unchecked, as I did not want to hide the advanced search, but I had to add the attribute and binding to stop the errors every time I ran a search in the portal.


    Andrew Weiss

    • Proposé comme réponse Sameera_man mercredi 22 janvier 2014 02:52
    • Marqué comme réponse Peter_Stapf mercredi 22 janvier 2014 12:13
    mardi 21 janvier 2014 23:33

Toutes les réponses

  • So what is that request doing? Does it have workflow attached?

    Thanks, Brian

    vendredi 20 décembre 2013 20:30
  • Hello Brian,

    it is not a request that had to do with workflows, it is just clicking in the portal, MPR List, Users, Groups, Search Request and nearly all other Navigation links.

    In Addition also when you have an users ui open an click from one tab to another, but there it is only on tabs with references, except the tab with the manager and assistant.

    So I assume it is the normal read request each time the Portal has to search for the objects that should be displyed. Sadly this requests will not be logged anywhere only in the tracelog above.

    What I dont understand is that this issue also occur as "the" administrator for which I created a MPR for testing to read all attributes on all resources. So why do I get denies like in the log above. And wuy ist still everything working as expected.

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    samedi 21 décembre 2013 08:50
  • Peter,


    The above excerpt from you service trace shows a query for the built-in sync account. The GUId is a well-known one for that objects. Were you specifically looking at this object in users or were you querying for something completely different and this shows up? Unless you were looking at the built-in sync account itself, this would seem like an odd object to look for when querying anything else.

    dimanche 22 décembre 2013 07:06
  • Hello Glenn,

    the above tracelog is just a sample entry, both error, "key not found" and "missing resource" appears on many different guids for example also on a search scope query which I use for group reporting in the UserUI.

    When I test this query in creating a new searchscope wizard, that error also occurs, but the result from that query is 100% correct.

    This query checks for existence of an existing guid in the explicit-member attribute of an group for example.
    So i dont know why it throws an error when the result is ok. very strange behavior.

    In the above case I did not explicitly search for the built in sync account, i'm not 100% sure but i think ist either from displaying entrys in Search Requests or because the sync-account it the owner ob the objects.

    I can post some more examples of the tracelog if that may be helpful.

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    dimanche 22 décembre 2013 10:58
  • So here is another sample snippet from the tracelog.
    The request and behavior is very similar to the other just that it throws the other error. I am not quite sure at the moment if that are 2 different errors or just 1 error with different exceptions thrown.

    Microsoft.ResourceManagement Verbose: 0 : Request '' status was updated in-memory from 'NotFound' to 'Validating'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3243848Z
    Microsoft.ResourceManagement Verbose: 0 : Request created: 'Enumerate Request'
    
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3243848Z
    Microsoft.ResourceManagement Verbose: 0 : Entered RequestDispatcher with Request Object; RequestIdentifier '9267e65b-f070-41fb-9631-da5e1d3295e2'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3253849Z
    Microsoft.ResourceManagement Verbose: 0 : Add request '9267e65b-f070-41fb-9631-da5e1d3295e2' to cache with RequestStatus 'Validating'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3263850Z
    Microsoft.ResourceManagement Information: 1 : RequestDispatcher enter processing pipeline;  RequestIdentifier '9267e65b-f070-41fb-9631-da5e1d3295e2'; Operation 'Enumerate'; Object ''; RequestStatus 'Validating'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3273851Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '9267e65b-f070-41fb-9631-da5e1d3295e2' for a 'Enumerate' operation on object '' with RequestStatus 'Validating'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3273851Z
    Microsoft.ResourceManagement Verbose: 0 : Request '9267e65b-f070-41fb-9631-da5e1d3295e2' status was updated in-memory from 'Validating' to 'Validated'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3303854Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '9267e65b-f070-41fb-9631-da5e1d3295e2' for a 'Enumerate' operation on object '' with RequestStatus 'Validated'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3303854Z
    Microsoft.ResourceManagement Verbose: 0 : Executing initial authentication.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3313855Z
    Microsoft.ResourceManagement Verbose: 0 : Request '9267e65b-f070-41fb-9631-da5e1d3295e2' status was updated in-memory from 'Validated' to 'Authenticating'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3323856Z
    Microsoft.ResourceManagement Verbose: 0 : Request '9267e65b-f070-41fb-9631-da5e1d3295e2' status was updated in-memory from 'Authenticating' to 'Authenticated'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3323856Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '9267e65b-f070-41fb-9631-da5e1d3295e2' for a 'Enumerate' operation on object '' with RequestStatus 'Authenticated'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3333857Z
    Microsoft.ResourceManagement Verbose: 0 : Request '9267e65b-f070-41fb-9631-da5e1d3295e2' status was updated in-memory from 'Authenticated' to 'Authorized'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3343858Z
    Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '9267e65b-f070-41fb-9631-da5e1d3295e2' for a 'Enumerate' operation on object '' with RequestStatus 'Authorized'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3343858Z
    Microsoft.ResourceManagement Information: 1 : WS: Action.Enumerate.Execute.Enter
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3353859Z
    Microsoft.ResourceManagement Information: 1 : Query: QueryProcessor.ExecuteQuery.ExecuteReader.Enter
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3353859Z
    Microsoft.ResourceManagement Verbose: 0 : Request '9267e65b-f070-41fb-9631-da5e1d3295e2' status was updated in-memory from 'Authorized' to 'Denied'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3373861Z
    Microsoft.ResourceManagement Information: 1 : RequestIdentifier '9267e65b-f070-41fb-9631-da5e1d3295e2' exited RequestDispatcher with RequestStatus 'Denied'.
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3383862Z
    Microsoft.ResourceManagement Information: 1 : WS: Enumerate:UnwillingToPerform
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3423866Z
    Microsoft.ResourceManagement Error: 3 : Requestor: urn:uuid:0aac2c9a-5a8b-44c7-ba8b-909d459a3d66
    Correlation Identifier: 9695ba96-37de-482f-b75d-3f92046013fe
    Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
       at System.ThrowHelper.ThrowKeyNotFoundException()
       at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
       at Microsoft.ResourceManagement.Query.QueryParametersGenerator.WriteRequestedAttributes()
       at Microsoft.ResourceManagement.Query.QueryParametersGenerator.BuildParameterString()
       at Microsoft.ResourceManagement.Query.QueryProcessor.BuildSqlCommand(Query objectRepresentation, Boolean countResultsOnly)
       at Microsoft.ResourceManagement.Query.QueryProcessor.ExecuteQuery(Query query, Nullable`1 maximumTime, Boolean& endOfSequence, Boolean countResultsOnly, Int64& resultCount, Int64& executionTime)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecutePullActionImpl(PullRequestParameter pullParameter)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteEnumerateAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey, Boolean isRedispatch)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Enumerate(Message request)
       --- End of inner exception stack trace ---
        ThreadId=12
        DateTime=2013-12-19T14:14:15.3453869Z
    Microsoft.ResourceManagement Verbose: 0 : HostActivator refreshing active host cache.
        ThreadId=8
        DateTime=2013-12-19T14:14:17.3145838Z
    Microsoft.ResourceManagement Verbose: 0 : HostActivator finished refreshing active host cache.
        ThreadId=8
        DateTime=2013-12-19T14:14:17.3325856Z
    Microsoft.ResourceManagement Verbose: 0 : Post Processing Manager is checking Requests for completion.
        ThreadId=8
        DateTime=2013-12-19T14:14:18.8757399Z
    Microsoft.ResourceManagement Verbose: 0 : The scan to check for Completed Requests started with Request Key '0' and ended at Key '0'.
        ThreadId=8
        DateTime=2013-12-19T14:14:18.8927416Z
    Microsoft.ResourceManagement Verbose: 0 : Post Processing Manager has finished checking Requests for completion.
        ThreadId=8
        DateTime=2013-12-19T14:14:18.8937417Z
    Microsoft.ResourceManagement Verbose: 0 : HostActivator refreshing active host cache.
        ThreadId=9
        DateTime=2013-12-19T14:14:22.3370860Z
    Microsoft.ResourceManagement Verbose: 0 : HostActivator finished refreshing active host cache.
        ThreadId=9
        DateTime=2013-12-19T14:14:22.3500873Z
    Microsoft.ResourceManagement Information: 1 : WS: Get: enter
        ThreadId=16
        DateTime=2013-12-19T14:14:22.8591382Z
    Microsoft.ResourceManagement Information: 1 : WS: ObjectID,AccountName,CreatedTime,Creator,DeletedTime,Department,Description,DetectedRulesList,DisplayedOwner,DisplayName,Domain,DomainConfiguration,Email,ExpectedRulesList,ExpirationTime,ExplicitMember,Filter,Locale,MailNickname,MembershipAddWorkflow,MembershipLocked,MVObjectID,ObjectSID,ObjectType,Owner,ResourceTime,Scope,SIDHistory,Temporal,Type,msidmDeferredEvaluation,ShowAppInfoTab,AssignCondition,TechnicalOfficer,ResponsiblePerson,ResponsibleGroup,InfoURL,LicenseCount,TeamID,TeamLeaderAssistant,Tea
        ThreadId=16
        DateTime=2013-12-19T14:14:22.8631386Z
    Microsoft.ResourceManagement Information: 1 : WS: GetCurrentUserFromSecurityIdentifier.Enter: S-1-5-21-1343024091-790525478-839522115-44293
        ThreadId=16
        DateTime=2013-12-19T14:14:22.8631386Z
    Microsoft.ResourceManagement Information: 1 : WS: GetCurrentUserFromSecurityIdentifier.Exit
        ThreadId=16
        DateTime=2013-12-19T14:14:22.8641387Z
    Microsoft.ResourceManagement Information: 1 : Get(20e7fb47-7ebf-42ed-a89b-0cd771f24390)
        ThreadId=16
        DateTime=2013-12-19T14:14:22.8651388Z


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    dimanche 22 décembre 2013 11:06
  • Any ideas in the new year on this.

    Issue is still there.

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    mardi 7 janvier 2014 10:59
  • Hello Peter,

    Try the steps in the KB for the hotfix.

    http://support.microsoft.com/kb/2906832/en-us

    The hotfix includes a new feature to optionally hide the advanced search option in the portal, but it requires manual schema changes.  I had the same errors after installing the hotfix 4.1.3496.0, but they stopped after manually updating the schema as instructed in the article.

    I left the option unchecked, as I did not want to hide the advanced search, but I had to add the attribute and binding to stop the errors every time I ran a search in the portal.


    Andrew Weiss

    • Proposé comme réponse Sameera_man mercredi 22 janvier 2014 02:52
    • Marqué comme réponse Peter_Stapf mercredi 22 janvier 2014 12:13
    mardi 21 janvier 2014 23:33
  • Hello Andrew,

    this solved the problem, thanks for this.

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    mercredi 22 janvier 2014 12:14