Darryn_Chang | 2018-07-16 06:51:34 UTC | #1
Since the 12th July we have been receiving an error on the Active Directory Connector and the Bridge Server Internal Error during Data Sync. Unable load configuration from Directory When attempting a data preview an error is received and refers to check the history for more details.
I have searched log files and identified the following errors but need assistance from the developer team to identify where and possibly how to fix the error.
[Error] ::API::log: plugin: (datasync\OBSession.cpp:382)-Failed WinHttpSendRequest with error lastErr=12029 [Error] ::API::log: plugin: (datasync\DataSync.cpp:643)-Exception was thrown: what=Unable load configuration from Directory
"$Id: //edge/mainsystest/int/src/bridge/bridgehost/hostedplugin_impl.cpp#50 $" not found.
[Error] ::API::log: plugin: (datasync\OBSession.cpp:382)-Failed WinHttpSendRequest with error lastErr=12030 [Error] ::API::log: plugin: (datasync\DataSync.cpp:643)-Exception was thrown: what=Unable load configuration from Directory
Also receiving
Get User Schema failed for domain. Cause The Specified directory object cannot be found.
The error is preventing AD server from updating in Purecloud, in turn forcing Admins to manually create the user in Purecloud as opposed to the AD server auto updating.
Raised it with Purecloud support and provided log files but still have no clear direction as to what it is or what is causing the issue. Can confirm TLS 1.1 or higher is being used. Credentials are validating with the servers
Have spoken with other orgs who have also advised they are experiencing the same issue.
Has there been a change in the Active-Directory Connector anyone know? Have tried uninstalling and re-installing and still no avail.
tim.smith | 2018-07-16 13:03:37 UTC | #2
This issue will be best handled through support.
Greg_Cunningham | 2018-07-16 13:18:43 UTC | #3
Development is investigating this issue.
Darryn_Chang | 2018-07-17 01:47:25 UTC | #4
Thanks @Greg_Cunningham
Greg_Cunningham | 2018-07-17 12:46:38 UTC | #5
This issue can be resolved by applying the following change to default secure protocols described in the following Microsoft article. We have reproduced this problem and the fix on older versions of Windows Server (2008 and 2012). Also note for the change in default setting to work, the OS must at least have the Windows/System32/WinHttp.dll dated 08-Mar-2016.
https://support.microsoft.com/da-dk/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-a-default-secure-protocols-in
jcp | 2018-07-19 10:34:09 UTC | #7
Hi,
This resolved the issue for us. Many thanks, Jean-Christophe
Darryn_Chang | 2018-07-20 02:24:22 UTC | #8
@Greg_Cunningham Is this update applied only to the Bridge Servers or does it need to be applied to AD servers as well to align both?
jcp | 2018-07-20 14:05:13 UTC | #9
Hi, We only updated the Bridge servers. Note that we had to make sure the correct settings were put in the Registry key (xA00) for TLS 1.1 and TLS 1.2.
Greg_Cunningham | 2018-07-20 14:15:36 UTC | #10
Bridge Servers only.
Darryn_Chang | 2018-07-24 01:01:52 UTC | #11
Does the change affect other webservices that sit alongside of the AD in the bridge servers?
Darryn_Chang | 2018-07-24 04:51:10 UTC | #12
Does dev support have a screenshot they can provide of the registry changes? Our network teams are a bit cautious in making the changes and want to ensure they make the right changes on the bridge servers.
Jason_Mathison | 2018-07-24 12:45:19 UTC | #13
Darryn_Chang, post:11, topic:3185, full:true
Does the change affect other webservices that sit alongside of the AD in the bridge servers?
What webservices are you concerned about?
Darryn_Chang, post:12, topic:3185, full:true
Does dev support have a screenshot they can provide of the registry changes? Our network teams are a bit cautious in making the changes and want to ensure they make the right changes on the bridge servers.
I actually messed up the registry entries the first time that I tried to make them. I would recommend using the "Easy Fix" .msi file that Microsoft provides. That will ensure that it is done correctly. Note that your best bet is to reboot the bridge server after applying the fix (either via regedit or the .msi file).
system | 2018-08-24 12:45:23 UTC | #14
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 3185