Have you tried restarting the FIMSynchronizationService?

Yes. Also tried clearing the connector space where the data come from. No luck. I'm pretty sure I am up against a bug.Keith

I have a metaverse attibute I mistakenly did not set up as multivalued. I had a flow rule (configured in the portal) that was putting data into the attribute, but got errors thanks to my misconfiguration. I removed the inbound flow for that attribute and the attribute shows zero inbound flows in the metaverse, but when I try to remove it, I get "Object reference not set to an instance of an object". This is a custom object type in the metaverse and a custom attribute only used by the new object type. Sync engine is at version 4.0.3558.2. Thoughts?Keith

Keith- Two things: --> 3561 is the latest public QFE build IIRC --> You might try flipping to advanced view and editing the sync rule's XML and uploading it backMy Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Where can I get 3561?Keith

http://support.microsoft.com/kb/2417774My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Fixed. My solution? Wait a day and then try again. Nothing changed, no syncs run, but today it worked. Gotta love that. Thanks for the help though. Now to apply 3561...Keith