Hi, I I am currently having a lot of grief with a managent agent that I'm unable to delete. The error message reads: "Unable to delete the management agent. The image or delta doesn't have an anchor." I am also unable to perform a full sync on any MA at the moment: Flow errors: DN is unavailable. Unexpected error. Metaverse RetryErrors: sync-rule-flow-provisioning-failed - The cause of the problem was me trying to take a shortcut and be sneaky. I'm using several extensible connectivity MA's to import/expert data with FIM. I had updated the template DSML files and needed to reflect these changes in my MA's. Instead of simply deleting the MA's and making new ones, I made new ones which I exported and then restored to my original MA's. I did this to save myself the hassle of re-mapping attributes in the portal sync-rules. Sadly this didn't work out, and I am now stuck with an MA that has 5 users in its connector space. I have deleted the sync rules from the FIM portal and disabled the add/delete MPR's concerned. I really hope there is a way to resolve the issue, without me having to re-install FIM from scratch. Any help will be greatly appreciated! Thanks, Francis

First, try to bring your environment up to the latest patch level (New build of FIM released (3573), FIM 2010 Build Overview). Then, disable provisioning and try do delete the MA again. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thanks! Is the hotfix to be installed on the sync server, og both (never updated FIM before)? Francis

Both - there are separate files for the synchronization service and the FIM service. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thanks! I just finished downloading the hotfix from here: http://hotfixv4.microsoft.com/Forefront%20Identity%20Manager%202010/nosp/KB2417774_Rev4/4.0.3573.2/free/427322_intl_x64_zip.exe, but it's asking me for a password. Where do I obtain such a password? Francis

By requesting a download link from KB page (http://support.microsoft.com/kb/2417774). Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Got the PW via e-mail when I filled out the request form. Francis

I just succeded installing FIMSyncService_x64_KB2417774 on the sync server (after installing SQL Server 2008 native client), and FIMService_x64_KB2417774 on the portal server. Sadly the updates didn't help to rectify my original problem. Any ideas? EDIT: If it's possible, I don't mind truncating the metaverse, I would only like to keep my configuration, not the data. Thanks, Francis

Sorry for the bump, but I'm rather stressed right now. Is it possible to truncate the metaverse (delete the 5 stuck users from the database) without loosing my settings, or should I go ahead with reinstalling FIM and start all over? Are there perhaps some stored procedures I can use? Thanks, Francis

Ssh don't tell, but I have deleted objects straight out of the tables before when in desperate straights. BACK UP YOUR DATABASE FIRST!! I'm not in front of a server here so these table names are not correct: but you need to track down the object in both the mms_connectorspace table and the mms_csmvlink table. If you delete the entry from both tables you should be fine. Just be very careful you have the right entries! You will also need the GUID of the MA to help you identify the right connectorspace object - you can get that from the mms_managementagents table. http://www.wapshere.com/missmiis

Thanks Carol, you deserve a big hug! truncate table [mms_metaverse] truncate table [mms_csmv_link] truncate table [mms_connectorspace] This finally allowed me to delete the MA. I didn't bother deleting "where ma_id = 'guid' as the only objects present were the ones giving me trouble. Thanks again! Francis

I recently got into this problema with FIM 2010 Update 2. This SQL script helped me fixing problematic csentries while keeping others intact. WARNING: Using SQL directly against FIM DB is unsupported. Backup first and run at your own risk. -- Get your MA GUIDs first to set @maid -- select ma_id, ma_name from mms_management_agent declare @maid as uniqueidentifier set @maid = '6F513A91-99F0-40D9-9392-89C69AAEDFC2' -- Clean mms_csmv_link first ... delete mms_csmv_link from mms_csmv_link csmv inner join mms_connectorspace cs on cs.object_id = csmv.cs_object_id where cs.ma_id = @maid AND anchor is NULL AND not (cs.partition_id IS NULL) -- placeholders have null anchor, so we exclude them -- Then clean mms_connectorspace ... delete mms_connectorspace where ma_id = @maid AND anchor is NULL AND not (mms_connectorspace.partition_id IS NULL) -- placeholders have null anchor, so we exclude them