Today while I was working at a client I made an adjustment to an outbound flow rule. When I imported it from the FIM MA and tried to synchronize it into the MV, I got the “sync-rule-inbound-flow-rules-invalid” error message. This is very concerning because once that error is received, the synchronization rule seems to stop working entirely.
I went through the following steps to try to resolve the issue:
- Went through and validated that the sync rule appeared to be valid and that all the attributes that were being used were still valid.
- Resynchronized the rule but the error still persisted.
- Went back to the synchronization rule definition and changed it to an inbound-outbound type flow rule. (it was previously outbound only).
- Resynchronized the rule and the error was gone.
- Again, went back and changed the synchronization rule to outbound only.
- Resynchronized the rule and the error was still gone and the rule operated normally.
This was interesting behaviour but if you happen to see the message it appears that simply changing the type and resynchronizing seems to clear the error. Then I could change the type back to the desired type (as I didn’t want any inbound flow rules accidently applied in this rule).
This is obviously a much better solution than what I had done previously in new systems where I deleted the synchronization rule and recreated it. I then had to reapply the new rule to all the objects because the ERE’s for the connected directory were now pointing to the wrong object ID, therefore synchronization rule, in the Metaverse which caused futher complications in life.