Imanami Community

Join or create discussions about common issues and solutions.
Welcome to Imanami Community Sign in | Join | Help
in Search

Problem with AD Update - inconsistent error messages

Last post 01-11-2008, 7:15 AM by jstrathern. 5 replies.
Sort Posts: Previous Next
  •  01-10-2008, 10:19 AM 449

    Problem with AD Update - inconsistent error messages

    We have a DTM Job that reads our HR database (SQLServer) every night and updates a few attributes within AD. It's been working fine for a number of months and occasionally errors on records with insufficient rights (easily fixed in AD). We have one error, which corpped up 2 weeks ago that we cannot troubleshoot. The summary page indicates one error is encountered at source, the reports tabs shows an update error "Redundant update as there is more than one source object that matches the destination for the LDAP Key Filter:(&(samaccountname=chenan))" and the detailed log (Verbose) has this as the error;

    === Begin Object ===

    Searching for (&(samaccountname=ilyasa)) at root: LDAP://*OMITTED TEXT*

    Found matching entry of type user at: LDAP://*OMITTED TEXT*/CN=Ilyas\, Akbar,OU=Edmonton Users,OU=Bantrel Users,*OMITTED TEXT*

    Schema type: user

    Property value unchanged: [department = Process]

    Property value unchanged: [physicalDeliveryOfficeName = EdPE022]

    Property value unchanged: [telephoneNumber = 780-577-4731]

    Property value unchanged: [ExtensionAttribute1 = 12/28/2007 12:00:00 AM]

    Property value unchanged: [company = Bantrel]

    Property value unchanged: [employeeID = *OMITTED TEXT*]

    Changes already committed

    @=

     

    We've check both AD entries in the error and they appear fine (no rights issuse for IlyasA - no duplicate entries for Chenan)

    The updates to both entires appear to be working and the job is showing as "successful"

     

    Thanks,

     

    Joe

  •  01-10-2008, 1:12 PM 450 in reply to 449

    Re: Problem with AD Update - inconsistent error messages

    Hello Joe,

    Did you check the SQL database for duplicates?  The error is referring to a duplicate account in your source database.

  •  01-10-2008, 2:16 PM 451 in reply to 450

    Re: Problem with AD Update - inconsistent error messages

    Yes, for both Ilyasa and Chenan, there are only 1 record and the data appears fine

     

    Joe

  •  01-10-2008, 2:44 PM 452 in reply to 449

    Re: Problem with AD Update - inconsistent error messages

    Hello Joe,

    Based on the information provided above it seems the job is running and updating the accounts in the destination.  So the issue is the error message not being consistent with the results of the job run.  Is this correct?

  •  01-10-2008, 7:47 PM 453 in reply to 451

    Re: Problem with AD Update - inconsistent error messages

    What is the key field relationship?

    samaccountname = ?

  •  01-11-2008, 7:15 AM 454 in reply to 453

    Re: Problem with AD Update - inconsistent error messages

    Yes, the key field relationship is samaccountname. AD IS being updated, so the issue is ;

    1 - the indication (falsely?) that an error is being encountered

    2- the inconsistecny between the report tab and the error log on what the error is

     

    As of this morning (first time in 14 days), the error is NOT being reported. Perhaps we can ignore until (or if) it re-occurs. One AD field (the field that updates AD Extensionattribute1) was updated at the source for a large percentage of rows (including the problematic record). I'll test it with the old value to see if it's value specific.

    Thanks for you help,

     

    Joe 

     

     

    Joe

View as RSS news feed in XML
Powered by Community Server (Personal Edition), by Telligent Systems