Unable to add attribute flow in sync rules through the portal
Hi, We have 2 development boxes. One has Version 4.0.3531.2 (I'll refer to it as FIM01) and the other 4.0.3573.2 (I'll refer to it as FIM02). Recently I migrated all configuration from FIM01 to FIM02. Everything went well and the migration was successful. Now, if I try to change an existing sync rule on FIM02 (newer version) and try to add an attribute flow in the inbound sync rule, it doesn't process my request. There is an action on the window for a split second, but nothing happens. There is no error displayed on the screen and nothing logged in the event log. It only happens if I try to add or change an attribute flow. If I delete an attribute flow, it lets me. I haven't changed anything in the configuration after migrating. The funny thing is I don't have any problem in the FIM01 box (older version) when trying to add/delete/change attribute flows. Has anybody else encountered the same issue? Is it a bug in Version 4.0.3573.2? Or is it that I cannot migrate configuration from an old version to a newer version? if that was the case then it shouldn't let me do anything, but it still lets me delete attribute flows. Appreciate your help. Regards
July 27th, 2011 10:23am

Dear Tidiv, we had exactly the same issue on one of our development systems. The poor solution was to reinstall it completely, even an upgrade to 3576 didn't solve that issue. We have raised a call with PSS and they couldn't solve that problem, too / it took too long to wait for a solution. Proposed workaround was the reinstallation of FIM Portal. I assume that his problem occurs if you install the patches in the wrong order. Regards, Moritz
Free Windows Admin Tool Kit Click here and download it now
August 5th, 2011 9:44am

Why not just take a proper backup of the lowest FIM version environment. And then do an upgrade so they are both on the same level. Isn't migrating between different versions just asking for problems?http://setspn.blogspot.com
August 5th, 2011 10:04am

Hi All, The problem was the difference in the version numbers - as Thomas says, never a good idea to migrate configuration/policies between environments running different versions of FIM. Sorry for posting this reply after years but thought someone might benefit from this experience. Cheers
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2012 1:17pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics