Hi All, FIM Admin ObjectSID deleted by FIM MA synchronization rule, so now I cannot access the FIM Portal. I'm tyring to get back the ObjectSID using Brad Turner Script, still no luck with notification below: -Account SID : (domain.com\fimadmin) S-1-5-21-1681229994-153652202-3788437857-34961 -Reading Account information Error: Failure on making enumeration web service call. Filter = /Person[AccountName='fimadmin'] Error= The web service client has encountered the following class of error: IdentityIsNotFound Details: Additional Text Details: The requestor's identity was not found. Correlation Identifier: 705c19b5-0d03-45c0-b306-c46553eb804e Failure Message: Request Identifier: anyone can tell me how to fix this? Thanks. Endrik Endrik | blog: itendrik.wordpress.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I guess domain.com\fimadmin is just a property for the actual user name. Check what your sAMAccountname of your fim admin account is and put that one into the filter.

Hi Moritz, FIM Admin Object SID was deleted, how to recover the object SID? I think put FIM Admin into connection filtering cannot recover object SID. I still can find FIM Admin and Builtin Synchronization account on Metaverse. Any other clue? Thanks. EndrikEndrik | blog: itendrik.wordpress.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Best bet is to contact Microsoft support. You're going to need to edit the FIM database to fix this.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Hi Endrik, Is the ObjectSID deleted from FIM metaverse, can try the following steps 1. If not move the FIM admin account to the OU/container seleted under FIM ADMA 2. Create a AD inbound rule, under inbound attribute flow tab map ObectSID => ObjectSID. 3. Run Import & Sync of FIMMA then delta Import , Full Sync of ADMA and finally run FIMMA export 4. Check in metaverse search whether ID is retrieved or not Regards, Varun

Hi Varun, still no luck. The solution is restore back the database, Portal now can access.. I put fim admin and fim adma to the filter like moritz said. Thank you all for the support.Endrik | blog: itendrik.wordpress.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.