When you run a Full Import or a Delta Import on the Microsoft Azure Active Directory (Azure AD) Connector, one of the following actions occur: 1. The following error is logged in the Application Event Log: FIMSynchronizationService Event 6801 The extensible extension returned an unsupported error. The stack trace is: “System.Collections.Generic.KeyNotFoundException: The given key was…
Tag: Synchronization Service
HOWTO: How to loop through proxyAddresses and update the primary SMTP
The purpose of this document is to provide an illustration of how to setup a Management Agent Rules Extension to loop through the list of proxyAddresses and based on the mail suffix set/change the Primary SMTP address. Disclaimer This document is an illustration. It is highly recommended to test this in a test environment…
Support-Tip (MIISACTIVATE.EXE): Logon failure: the user has not been granted the requested logon type at this computer
PRODUCT FOCUS Microsoft Identity Manager Synchronization Service 2016 Forefront Identity Manager Synchronization Service 2010 NOTE MIISACTIVATE.EXE has been around since the days of Microsoft Identity Integration Server 2003 and has had it’s single focus of activating a new Synchronization Server Client with the backend Synchronization Service Database. I mention this, because I be using…
[TROUBLESHOOTING] The Synchronization Service Engine Crashes
Symptom During the process of a Full Import on the Active Directory Management Agent there is a reference on an Active Directory Organizational Unit to an Organizational Unit two levels down, the Synchronization Service Engine will crash. Cause A known issue in the Synchronization Service Engine. Resolution Fixed in build 4.1.3479.0 Additional Information A hotfix…
[Troubleshooting] DirSync FIM Sync Service would not start
Background After installing the Directory Synchronization Appliance, Forefront Identity Manager Synchronization Service would not start. Troubleshooting Actions Attempted to start the Forefront Identity Manager Synchronization Service manually, but it would fail immediately. The Forefront Identity Manager Synchronization Service would not timeout; it would just fail immediately. Reviewed file and registry permissions Reviewed Event Log Information…
Support-Info:(SYNC SERVICE): stopped-server: msidmCompositeType or Asynchronous Processing Scenario
Stopped-Server Checklist 0x80230405 (The operation failed because the object cannot be found Overview The stopped-server status is a common status that is seen in the FIM Synchronization Service Engine when executing an import and/or export run on a given management agent. The following information has been compiled to provide guidance on how to begin troubleshooting…
[Reference:] Refreshing the Interfaces of an ECMA 2.0-based Version of the Lotus Domino Connector
[Reference] Refreshing the Interfaces of an ECMA 2.0-based Version of the Lotus Domino Connector: http://social.technet.microsoft.com/wiki/contents/articles/19101.how-to-refreshing-the-interfaces-of-an-ecma-2-0-based-version-of-the-lotus-domino-connector.aspx
[Troubleshooting] Failed to retrieve schema – Event ID 6331 – A update on the configuration of a MA or MV failed to replicate
[Troubleshooting] Failed to retrieve schema – Event ID 6331 – A update on the configuration of a MA or MV failed to replicate: http://social.technet.microsoft.com/wiki/contents/articles/18544.troubleshooting-failed-to-retrieve-schema-and-event-id-6331.aspx FIM Resources Microsoft Support Team Blog Home Page Forefront Identity Manager TechNet Community Forums Microsoft Support Team Keywords for searching content FIM Landing Page: Resource…
[Reference] Discovery Errors
[Reference] Discovery Errors: http://social.technet.microsoft.com/wiki/contents/articles/17977.reference-discovery-errors.aspx
[Troubleshooting] Event ID 10016 – The application-specific permission settings do not grant Local Activation permission for the COM Server application
[Troubleshooting] Event ID 10016 – The application-specific permission settings do not grant Local Activation permission for the COM Server application: http://social.technet.microsoft.com/wiki/contents/articles/17914.troubleshooting-event-id-10016-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application.aspx