About

IAM Solutions Architect – FIM/ILM/MIIS Specialist, with 16 years SQL database (+OLAP) and MS.Net applications development/SI background, in particular on the SharePoint platform

8 Responses to About

fosshank says:

April 14, 2020 at 9:17 am

Hi Bob,

I hope this finds you doing well. OK, please steer me in the right direction, but I’m having a heck of a time trying to save a Criteria Based group in MIM. Below is the error I get every time:

Requestor: urn:uuid:b6f04057-68ef-4a53-8db8-0eeab997c777
Correlation Identifier: b56f2c74-0630-4db8-af20-b62bdc4a5773
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)

It’s not a timeout error, or doesn’t appear to be, since the error is thrown about a half second after submitting the group – and this is a security group that is flowed in from AD.

Any ideas are greatly appreciated.

Thanks,
Hank Foss

Reply
- bobbradley1967 says:
  
  April 14, 2020 at 10:30 am
  
  Hi Hank – yes that is a common problem if you are building a query that references an attribute binding doesn’t have a corresponding FilterPermission record. Try updating the Admin Filter Permission to add the binding you’re trying to use – this is an especially common issue if you’ve extended the MIM schema with your own resource/attribute/binding.
  
  Reply
  - fosshank says:
    
    April 14, 2020 at 3:18 pm
    
    Thanks, Bob. I’ll give that a shot. Although all attributes have corresponding filter permission records, I have been through an upgrade and it may be possible the records have to be re-saved.
    
    -Hank
  - fosshank says:
    
    April 15, 2020 at 12:32 pm
    
    Hi Bob,
    
    Still getting the same error. I actually re-added all the attributes, and then in Advanced View / Extended Attributes added the bindings for several attributes I use for criteria-based group logic.
    
    Even restarted the FIM service on the portal, which probably was unnecessary but I didn’t want to leave that out, and still the same error.
    
    Any other ideas are greatly appreciated.
    
    Thanks,
    Hank
  - fosshank says:
    
    April 23, 2020 at 10:14 pm
    
    Hi Bob,
    
    Were you able to duplicate this on your side? Otherwise, I’m going to keep on my Google quest and stay on the prowl for this answer.
    
    In your travels, if you run into a solution for this, please let me know.
    
    Thanks,
    Hank
bobbradley1967 says:

April 23, 2020 at 10:31 pm

Hi Hank
No I’ve not followed that up further mate, but I just remembered something – have a look at the attribute changes on your request in the request history – you are possibly setting an attribute binding where there is no sync permission.
Find out what the guids here resolve to for a clue:

Requestor: urn:uuid:b6f04057-68ef-4a53-8db8-0eeab997c777 Correlation Identifier: b56f2c74-0630-4db8-af20-b62bdc4a5773

Reply
fosshank says:

April 24, 2020 at 2:31 am

I appreciate it, Bob. I’ll check into that.

Thanks,
Hank

Reply
fosshank says:

April 24, 2020 at 2:59 am

Bob,

So I don’t think the attributes are the issue because the failures aren’t event making the request history, not even showing up there. I tested a criteria-base group that is behaving (previous to the upgrade from FIM to MIM) and made a change to it: it successfully wrote to the request history.

But the processing errors are not even getting that far, like the database doesn’t like it.

Thanks,
Hank

Reply