Skype for Business attribute synchronization fails on Connector Server
search cancel

Skype for Business attribute synchronization fails on Connector Server

book

Article ID: 144261

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

The Connector Server fails to read Skype for Business attributes from Active Directory (AD). This issue typically manifests during account modification or creation when the system cannot establish a proper remote shell session with the Skype for Business server.

Symptoms

  • Primary Error: JNDI: [LDAP: error code 1 - Unable to get Skype for Business attributes: System.Management.Automation.Remoting.PSRemotingTransportException: Starting a command on remote server failed... The request for the Windows Remote Shell with ShellId XXXXXXX failed because the shell was not found on the server.]
  • Secondary Error (Code 70): Unable to determine Skype for Business User Enabled status: No management object found for identity
  • UI Symptom: The SIP domain does not appear in the "Specify a SIP URI" field within the Provisioning Manager or Identity Manager UI.
  • Temporary Workaround: Symptoms are temporarily resolved by restarting the Connector Server service but recur shortly after.

Environment

All Identity Suite

Cause

The ADS_LYNC_SESSION_PERSISTS system environment variable is not defined on the Connector Server machine. Without this variable set to 0, the session management for PowerShell remoting fails to correctly recycle or identify the remote shell, leading to JNDI/LDAP communication errors.

Resolution

To resolve this issue, you must disable Lync session persistence by adding a system environment variable:

  1. Log in to the Connector Server machine with administrative privileges.
  2. Open System Properties > Advanced > Environment Variables.
  3. Under System Variables, click New.
  4. Enter the following details:
    • Variable name: ADS_LYNC_SESSION_PERSISTS
    • Variable value: 0
  5. Click OK to save the variable.
  6. Restart the Connector Server service for the changes to take effect.