-
Notifications
You must be signed in to change notification settings - Fork 35
Lync Connector Troubleshooting
The Lync Connector makes use of the logging and tracing capabilities of FIM PowerShell connector. Critical errors will be logged to the Application log on the Synchronization Service server and additional tracing can be enabled by the administrator by configuring the trace levels of the FIM PowerShell connector.
To enable tracing to log to event log:
- Copy the script
Register-EventSource.ps1located in thesrc\LyncConnector\EventLogConfigfolder to a local folder on the FIM Synchronization Server and execute it on an elevate PowerShell command prompt. - The create / edit the <system.diagnostics> configuration elements in application config files as directed in the
app.configfile located in thesrc\LyncConnector\EventLogConfigfolder. After the application config files are updated, restart the FIM Synchronization Service.
The Test Harness scripts, TestHarness-Lync.ps1 and TestHarness.Common.psm1 that are part of the Lync Connector script library are meant to be used for interactive debugging / development in PowerShell ISE. These scripts make it possible to develop / debug the connector scripts in PowerShell ISE independent of FIM Sync Service providing an experience very similar to "Attach to Process" develop / debug experience in Visual Studio for native .NET Connectors.
- Home
- Related Projects
- Skype/Lync Connector
- Exchange Connector
- Flat File Connector
- SharePoint Site, User and Group Management Connector
- Home Drive Provisioning
- Oracle Identity Management Connector
- FAQ