5 Troubleshooting

These tables list solutions to some issues associated with the Exchange connector.

Table 5-1 lists solutions to some commonly encountered issues associated with the Exchange connector:

Table 5-1 Troubleshooting Common Connector Issues

Problem Description Solution

Problem Description	Solution
The Exchange connector throws the following error: `Could not find domain controller for user <user_name>`	The connector tries to get the domain controller where the Active Directory (AD) user was created using the value provided in the User Logon Name field. This value must be same as the value provided for the User Principal Name field during AD provisioning. If there is any mismatch, the connector throws this error. Ensure the values provided for these two fields are same.
The Exchange connector does not log any information. Logging is enabled for the connector in ConnectorServer.exe.Config file. The line <add name="ExchangeSwitch" value="4" /> has been added and connector server has been restarted.	Ensure the log file location and name as specified in the ConnectorServer.exe.Config file is valid. Also, ensure the user who is running the connector server has write permission on the log file. Then, restart the connector server.
The Exchange connector throws the following error: `ConnectorServer.exe Error 0 Problem while PowerShell execution System.Management.Automation.Remoting.PSRemotingTransportException: Starting a command on remote server failed with the following error message : The Windows Remote Shell cannot process the request; the selector value 93523BF3-968A-47AA-BCE9-8DD59CFD53E9 specified in the request was not found. For more information, see the about_Remote_Troubleshooting Help topic.`	The problem is caused by the Timeout setting of the "Exchange Connector Server" IT resource. To troubleshoot this problem, increase the value specified for the Timeout parameter in the "Exchange Connector Server" IT resource. See Table 2-3 for detailed information about this parameter.

The Exchange connector throws the following error:

Could not find domain controller for user <user_name>

The connector tries to get the domain controller where the Active Directory (AD) user was created using the value provided in the User Logon Name field.

This value must be same as the value provided for the User Principal Name field during AD provisioning. If there is any mismatch, the connector throws this error. Ensure the values provided for these two fields are same.

The Exchange connector does not log any information. Logging is enabled for the connector in ConnectorServer.exe.Config file. The line <add name="ExchangeSwitch" value="4" /> has been added and connector server has been restarted.

Ensure the log file location and name as specified in the ConnectorServer.exe.Config file is valid.

Also, ensure the user who is running the connector server has write permission on the log file.

Then, restart the connector server.

The Exchange connector throws the following error:

ConnectorServer.exe Error 0 Problem while PowerShell execution System.Management.Automation.Remoting.PSRemotingTransportException: Starting a command on remote server failed with the following error message : The Windows Remote Shell cannot process the request; the selector value 93523BF3-968A-47AA-BCE9-8DD59CFD53E9 specified in the request was not found. For more information, see the about_Remote_Troubleshooting Help topic.

The problem is caused by the Timeout setting of the "Exchange Connector Server" IT resource. To troubleshoot this problem, increase the value specified for the Timeout parameter in the "Exchange Connector Server" IT resource. See Table 2-3 for detailed information about this parameter.

Table 5-2 lists solution to commonly encountered issue associated with the connector when using Exchange 2010:

Table 5-2 Troubleshooting Connector Issues with Exchange 2010

Problem Description Solution

Problem Description	Solution
The Exchange connector throws the following error: `ConnectorServer.exe Error: 0 : System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : Logon failure: unknown user name or bad password. For more information, see the about_Remote_Troubleshooting Help topic.`	Ensure the username and password specified are correct. The username must be in the format DomainName\UserName. User distinguished name (DN) must not be mentioned as a value for the ExchangeUser IT resource parameter. If this does not solve the issue, verify if you can connect to Exchange Server from the computer hosting the connector server using a remote PowerShell window using the same credentials by following below commands: `$cred = Get-Credential` //provide same credentials as specified in the IT resource `$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<ExchangeServerHostName>/PowerShell/ -Authentication Kerberos -Credential $cred` //provide same Exchange Server host name as provided in the IT resource parameter `Import-PSSession $session` //this should import Exchange cmdlets without any issues. Ideally by this step, you should encounter the issue. `Remove-PSSession -Session $Session` // remove newly created test session If the above steps complete without any error, then check Windows event logs for more information. Alternate Solution: Run the Enable-PSRemoting cmdlet to configure the Exchange Server computer to receive Windows PowerShell remote commands that are sent by using the WS-Management technology. For more information about the Enable-PSRemoting cmdlet, see: `http://technet.microsoft.com/en-us/library/hh849694.aspx`

The Exchange connector throws the following error:

ConnectorServer.exe Error: 0 : System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : Logon failure: unknown user name or bad password. For more information, see the about_Remote_Troubleshooting Help topic.

Ensure the username and password specified are correct. The username must be in the format DomainName\UserName.

User distinguished name (DN) must not be mentioned as a value for the ExchangeUser IT resource parameter.

If this does not solve the issue, verify if you can connect to Exchange Server from the computer hosting the connector server using a remote PowerShell window using the same credentials by following below commands:

$cred = Get-Credential //provide same credentials as specified in the IT resource

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<ExchangeServerHostName>/PowerShell/ -Authentication Kerberos -Credential $cred //provide same Exchange Server host name as provided in the IT resource parameter

Import-PSSession $session //this should import Exchange cmdlets without any issues. Ideally by this step, you should encounter the issue.

Remove-PSSession -Session $Session // remove newly created test session

If the above steps complete without any error, then check Windows event logs for more information.

Alternate Solution:

Run the Enable-PSRemoting cmdlet to configure the Exchange Server computer to receive Windows PowerShell remote commands that are sent by using the WS-Management technology. For more information about the Enable-PSRemoting cmdlet, see:

http://technet.microsoft.com/en-us/library/hh849694.aspx

Table 5-3 lists solution to commonly encountered issue associated with the connector when using Exchange 2007:

Table 5-3 Troubleshooting Connector Issues with Exchange 2007

Problem Description Solution

Problem Description	Solution
The Exchange connector throws the following error while adding a user to a distribution group: `ConnectorServer.exe Error: 0 : Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Active Directory operation failed on MachineName.connectordevroot1.com. This error is not retriable. Additional information: Insufficient access rights to perform the operation.` `Active directory response: 00002098: SecErr: DSID-03150BB9, problem 4003 (INSUFF_ACCESS_RIGHTS)`	For Exchange 2007, the service account must be a member of the Exchange Recipient Administrator role and the Account Operator role in every domain where the distribution group exists. Add the user to the Account Operator role of the domain where the distribution group exists and restart the connector server.

The Exchange connector throws the following error while adding a user to a distribution group:

ConnectorServer.exe Error: 0 : Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Active Directory operation failed on MachineName.connectordevroot1.com. This error is not retriable. Additional information: Insufficient access rights to perform the operation.

Active directory response: 00002098: SecErr: DSID-03150BB9, problem 4003 (INSUFF_ACCESS_RIGHTS)

For Exchange 2007, the service account must be a member of the Exchange Recipient Administrator role and the Account Operator role in every domain where the distribution group exists.

Add the user to the Account Operator role of the domain where the distribution group exists and restart the connector server.