Accelerator AD Synchronizer Error 34
Please help with:
Event Type: Error
Event Source: Accelerator AD Synchronizer
Event Category: None
Event ID: 34
Date: 9/14/2009
Time: 12:01:17 PM
User: N/A
Computer: DHSVDISCOVER
Description:
APP AT - Customer ID: 1 - An error occured in ProfileSynchroniser::SynchroniseEmployeeProfile while retrieving properties. System.Runtime.InteropServices.COMException (0x8007054B): The specified domain either does not exist or could not be contacted. (Exception from HRESULT: 0x8007054B)
at ActiveDs.NameTranslateClass.Init(Int32 lnSetType, String bstrADsPath)
at KVS.Accelerator.ActiveDirectory.ADProfileSynchroniser.SynchroniseEmployeeProfile(ProfileRow profileRow)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Comments
Can you have a look inside
Can you have a look inside table tblPrincipal within your customer database do you have any entries in there that do not have any information in the SID and LDAP_Path columns?
EV Backline Technical Support Engineer APJ Region
Yes, we do have entries that
Yes, we do have entries that do not have any information in the SID and LDAP_Path columns.
Is that the problem? And if so, what is the resolution?
From what I read these are
From what I read these are accounts that no longer exist in AD and that is the problem. I think when I looked at it yesterday the entries were deleted but as this is SQL deletions I would recommend opening a case with us so somebody can spend a bit more time on it and ensure that this is the correct course of action.
EV Backline Technical Support Engineer APJ Region
I will be opening a case
I will be opening a case today.
Any resolution?
Did you get a resolution to this case? I am having the same error. I did delete the Active Directory accounts referenced in the event log error so I know what caused the problem. I am looking for a way to clear the errors.
Thanks,
Alan
resolved
Not that there was a clear resolution, but here are a few things that we had to do.
In DA we lowered the chunks. The SQL I/O was still at 100% disk util, however, it may have helped as the DELETE did complete and our SQL, DA, and EV servers are back to normal operation.
Would you like to reply?
Login or Register to post your comment.