AD Connector Crashes with Error "The server does not support the control. The control is critical."

Summary

When using the AD Connector for the Exinda, it is possible to see repeated crashes of the AD Connector Service on the Windows Server with the log error "The server does not support the control. The control is critical."

Overview

The AD Connector is a Domain Controller (Windows environment) application that will connect to any AD Configured Exinda in the domain and provide it in with information linking usernames and the IP addresses of the machines they are logged into so that the monitoring information on the Exinda can be updated with user information. There are occasions where the AD Connector application on the server will randomly crash, and even though restarting the service through the Services Manager will bring it back up, it can crash in the future. When crashing, it will show the following message in the ADConnector.log:

System.DirectoryServices.Protocols.DirectoryOperationException: The server does not support the control. The control is critical.

Cause

That exception is returned when a DirectoryResponse object returned from the Domain Controller has an error in it. The way that the ADConnector dealt with this exception was to log it without proper handling, and thus this exception that occurred would crash the application. Restarting the application would start it without any problem.

Workaround

To work around this problem, in the 'Services' manager on the Domain Controller, the service start type (right click on the 'ADConnector' service and go to Properties) can be set to 'Restart Automatically'. This will ensure that if an unhandled exception occurs, the service will restart after a short amount of time and begin replicating once more.

Resolution

There is no current resolution for this issue. It will be resolved in an upcoming new AD Connector version.

Defect ID

D-02941

Defect URL

https://www4.v1host.com/Exinda/defect.mvc/Summary?oidToken=Defect%3A51481