none
FIM Hotfix 4.1.3419.0 does not seem to resolve FIM Portal issue RRS feed

  • Question

  • Hello all,

    I have applied hotfix 4.1.3419.0 on a FIM solution to try and resolve this issue in the release notes:

    FIM service and portal

    Issue 1

    If a user who has access to advanced pages for a group (typically, an administrator) made a change to the object in this view, the group would contain invalid members. If the user was trying to delete the group, the system would be in a state in which no additional requests could be processed.

    After applying the update and attempting to delete the problem group, the Portal becomes in a state where it can not service any new object creation requests.

    I have attempted to delete the groups via the Portal, via deprovisioning and via PowerShell but all methods trigger the problem. Similarly new objects cannot be created in the Portal or by provisioning or through PowerShell.

    The error presented in the portal is:

    Error processing your request: There was a problem with the supplied attribute(s).

    Reason: The required attribute value has not been provided.

    Attributes: MembershipLocked

    Correlation ID: xxx

    Details: An attribute is required to complete the operation.

    A subsequent warning is logged in the FIM Service event log:

    Request '55411fb1-38f2-4489-bafc-346b35afa9e4' failed while trying to commit the changes to the database.  Exception: 'Target(s): 5AC010E0-7BC4-479E-A1D7-B0D777C610B9, B3D44B95-4E81-49EF-AFC2-893F5A35B601, 6EFB607E-ED0A-40FB-8EB7-2CE1840B2349, 2C24B9FD-F55F-444D-8E02-384D599A7753, 5920B702-A7F5-4E51-9C53-1C54BCC62144, 739CB715-08FF-4EFA-B16A-A27F40449813, 4C4EBE08-CF09-4918-88E2-A31C4661DBAE, 5FDD204C-C56F-46FF-95C2-0875F28711D3, B1391C1F-2CD8-4771-8B0F-D77ACB824DE7, 79B9BCB0-49B9-4A0B-B08B-B3AC095B5009, 919BC494-CB79-483F-9D27-E127B16AE18D, B11586C7-6D4D-43E2-ADB8-B32ED0B4B510, 331BD4C2-EB0E-4E8F-893B-EA6080E79BA9, 9A7A8F2C-D408-49B8-9439-9837CA87E592, kjasd, Attribute Failure Code: 'RequiredValueIsMissing', Attribute Name: 'MembershipLocked''.

    The 15 object ID's in the 'Targets' are the 15 corrupted groups that I deleted.

    If I remove the "required" from the MembershipLocked attribute the error would just move to another attribute.

    This prevents me from creating new objects only, changing existing objects seems to be okay.

    The only advice I can find is from FIM R2 release notes stating that  delta run cycle should clear this error...which it doesn't.

    Any help would be greatly appreciated!

    Jason

    Tuesday, April 9, 2013 12:05 PM

Answers

  • Jason,

    If this started when you were on build 4.1.3114.0, this is a known issue. Please open a case with MS support for this, it should be straightforward fix.

    • Marked as answer by J-Rev Wednesday, April 10, 2013 8:39 AM
    Tuesday, April 9, 2013 3:20 PM

All replies

  • Jason,

    If this started when you were on build 4.1.3114.0, this is a known issue. Please open a case with MS support for this, it should be straightforward fix.

    • Marked as answer by J-Rev Wednesday, April 10, 2013 8:39 AM
    Tuesday, April 9, 2013 3:20 PM
  • Many thanks to Glenn who had the fix to this problem ready to deploy. Problem was resolved in a few minutes.

    Anyone else unlucky enough to have caught this bug should follow Glenn's advice and get a call logged, he advised me as this is a bug fix it shouldn't incur any support costs, much easier to log a call then try and resolve the issue yourself (which is a SQL related issue.)

    Wednesday, April 10, 2013 8:39 AM
  • hi 

    we are encountering the same issue. 

    do you have the fix , how to fix it?


    MM

    Wednesday, April 10, 2013 9:15 AM
  • I am also having this issue.

    Anyone got the fix? seems overkill to raise a PSS incident for a known issue

    - Ross


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    Tuesday, July 2, 2013 6:06 AM
  • Hello

    We are experiencing the same issue, on build 4.1.3114.0

    Where can I find the fix?

    Thanks.

    Tuesday, October 29, 2013 3:45 AM
  • Hello. We also have encountered this issue on one of our ustomers but the support need some kind of KB Number or something to identify this "fix". Can someone please provide that?

    Thursday, December 3, 2015 2:39 PM