I added few columns to the source SQL table, did refresh schema. When I open inbound syncronization the new attributes are not there. May be it is related to the last upgrade I did. I upgraded from 4.0.2592.0 to 4.0.3531.2. Did anyone experiece this issue?

Have you updated each object definition in the MA properties? Chances are the new attributes appear in the "attributes list" but you may not have updated the "must have" and "may have" attribute bindings per object type defined for your MA.Bob Bradley, www.unifysolutions.net (FIMBob?)

Have you updated each object definition in the MA properties? Chances are the new attributes appear in the "attributes list" but you may not have updated the "must have" and "may have" attribute bindings per object type defined for your MA.Bob Bradley, www.unifysolutions.net (FIMBob?)

I tried creating a new MA on the same SQL source, but when I create a sychronization rule the MA doesn't even show in the list of External Systems.

I tried creating a new MA on the same SQL source, but when I create a sychronization rule the MA doesn't even show in the list of External Systems. You need to force a sync of the MA/MV config to the Portal, probably. This is a good script to do it: http://blog.msresource.net/2011/04/19/re-synchronizing-fim-configuration/. FYI 3576 is the newest build - alot of things fixed.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

I tried creating a new MA on the same SQL source, but when I create a sychronization rule the MA doesn't even show in the list of External Systems. You need to force a sync of the MA/MV config to the Portal, probably. This is a good script to do it: http://blog.msresource.net/2011/04/19/re-synchronizing-fim-configuration/. FYI 3576 is the newest build - alot of things fixed.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Thank you for the advice. Unfortunately the script didn't work. I still don't see the MA.

Hi, I had a similar problem (http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/45d5b787-d0d2-425b-b413-204d1e4802e3), it could be a MA/MV synchronization issue. Have you checked if the event log contains entried like this: A update on the configuration of a MA or MV failed to replicate to a target connector directory that is capable of storing MA/MV configurations. As a result, the MA/MV configuration data in this connector directory is not up to date. Please correct the condition that causes the error, and triggers a resync by updating the password information of the target MA. Cheers, PaoloPaolo Tedesco - http://cern.ch/idm

The evet log has the exact same message. I upgraded FIM Portal to the same version as Synchronization service, reset password for FIM MA, restarted services. Now I can see the new MA and the attributes.