I havetwo Management Agents in ILM 2: SQL Server and Active DirectoryI wastesting performanceand tried to provision 60000 accounts from SQL to AD.After successfully processing around 3000 records, Export to ILM MAfailed withthe error message "failed-creation-via-web-services".Ideleted the Connector Spaces. Now I have 3000 records in the ILM Portal and Metaverse. Does someone know how can I delete the records from the portal and Metaverse?

The easiest way to get rid of metaverse objects is to make sure that the objects is to remove all linked relationships of the objects by clearing all connector spaces. The easiest way to bulk delete objects in the portal database is to stage a deletion on them. However, these steps seem to be too complicated for what you really need. The most efficient way to get an environment into a clean state is to use database backups. That way, you can always restore to a known state. If you are planning on moving on with your testing, you are better off reinstalling FIM. You can then take backups of various states of your deployment. For example, one after the installation and then another one after the initial configuration, etc.Markus Vilcinskas, Technical Content Developer, Microsoft Corporation

If you don't wish to follow Marcus advise or if you don't have a backupyou could delete all objects from the portal and then run a full import/sync but be sure to keep the Built in syncronization account and the account you use to log on to the portal.//HenrikHenrik Nilsson - Cortego http://blog.softconstruction.se

Thank you Markus. I wouldn't like to lose some other changes when I go back to clean database backup.How can I stage a deletion? Would you have a reference on how to do it?

First you have to figure out what your criteria is for creating accounts.. I am guessing you used codeless to create the accounts in the ILM MA? yes or no?Since you have errored out accounts they are considered pending exports... so if you can remove the metaverse object they should be removed also if you remove them from the criteria..Can you limit your criteria to not allow these 3000 accounts??? Maybe by a connector filter in the datasource.. Its hard to give you more advice without knowing what your scenario is setup like..HTH,JoeJoe Stepongzi - Identity Management Consultant - ILM MVP - www.microsoftIdM.com,ilmXframework.codeplex.com

This has been documented here.Please let me know if you have questions.Cheers,MarkusMarkus Vilcinskas, Technical Content Developer, Microsoft Corporation