Hi! We had some serious errors with our FIM MA synchroization. The advice from MS was to move the database to the Sync server. So we did, and it solved our sync problem. But. After moving the database FIM is no more able to see new attributes that i have checked in my AD MA. All sync rules in FIM works fine though. Anyone seen this before?

So you moved your FIM Synchronization DB from a remote SQL to a SQL on the FIM Sync server? And now when you check a new attribute in the AD MA configuration you can't use it in the attribute flow section? Or it doesnt appear in the FIM Portal to create new declarative synchronization rules? Or else: where do you expect them to be seen?http://setspn.blogspot.com

1. Yes. 2. It doesnt appear in the synchronization rule, when i want to make an inbound synchronization rule from the MA. /Søren

It's not completely clear to me if you are configuring a rule in the Portal or on the MA (synchronization manager). Have you checked whether there are any errors in the SQL server log? How did you move your DB? You dont happen to have done something similiar to this: http://setspn.blogspot.com/2010/09/case-of-new-attributes-that-didnt-want.html http://setspn.blogspot.com

No errors in the SQL log. I found another error though. And a blog posted having the same error, but had to reinstall fixing it. Not an option in our production environment http://idamd.blogspot.com/2010/06/ma-attributes-not-listed-in-fim-sync.html

Stupid me. Just before DB move we patched the FIM Sync with update 1. But not the FIM service. The installations needs to be at same version.