• State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 93 subscribers
  • Views 8419 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

while ADSAccount Update we are getting an error like "A constraint violation occurred ".How can i solve this.

suneethk
over 6 years ago

while updating ADSAccount for user ,it showing an error like this

"

A constraint violation occurred.

Object not committed successfully. Retrying using single property commit.
Property accountExpires should be set.
Property company should be set.
Property department should be set.
Property displayName should be set.
Property msExchExtensionAttribute17 should be set.
Property msExchExtensionAttribute22 should be set.
Property extensionAttribute13 should be set.
Property msExchExtensionAttribute23 should be set.
Property l should be set.
Property postalCode should be set.
Property streetAddress should be set.
Property userPrincipalName should be set

Internal error in COM access layer: number: 8007202F, description: A constraint violation occurred.

A constraint violation occurred.

Property departmentNumber should be set

" .How can find the constrained limit of the each attributes.When i checked in user ,i could see all the above mentioned attributes are set .But it still showing the above error.

Please help me to troubleshoot it.

  • 0 over 6 years ago

    How about contacting support?

    If you do so, do not forget to mention the version you are using.

  • 0 over 6 years ago

    Hi,

    The error comes from Active Directory and unfortunately is not very helpful!  In short, you are trying to set or change an attribute value in AD and AD does not like it.  You need to work with your AD team to find out if they have placed any special constraints or restrictions on the AD data values.

    HTH, Barry.

    The following SQL will tell you what attributes the update job was trying to change - this might help with your analysis:

    Declare @MyTempTable Table
    (
    ParameterValue varchar(max)
    )
    Declare @MyTempTable2 Table
    (
    OpTable varchar(50),
    OpUID varchar(50),
    Display varchar(50),
    Columnname varchar(50),
    OldValue varchar(100),
    NewValue varchar(100)
    )

    DECLARE @X AS XML, @hDoc AS INT

    Insert into @MyTempTable (ParameterValue)
    select p.ParameterValue
    from Jobqueue q
    cross apply dbo.QBM_FCVJobParameterToList(q.ParamIN) p
    where
    JobChainName = 'ADS_ADSAccount_Update/(De-)activate'
    and Ready2EXE = 'frozen'
    and p.ParameterName = 'CausingEntityPatch'

    UPDATE @MyTempTable
    SET ParameterValue = Replace(ParameterValue,'&lt;', '<')
    WHERE ParameterValue LIKE '%&lt;%';

    UPDATE @MyTempTable
    SET ParameterValue = Replace(ParameterValue,'&gt;', '>')
    WHERE ParameterValue LIKE '%&gt;%';

    UPDATE @MyTempTable
    SET ParameterValue = Replace(ParameterValue,'&#x7', '')
    WHERE ParameterValue LIKE '%&#x7%';

    declare XmlList cursor for
    select ParameterValue from @MyTempTable
    OPEN XmlList
    FETCH NEXT FROM XmlList
    INTO @X
    WHILE @@FETCH_STATUS = 0
    BEGIN
    EXEC sp_xml_preparedocument @hDoc OUTPUT, @X

    Insert into @MyTempTable2 (OpTable,
    OpUID,
    Display,
    Columnname,
    OldValue,
    NewValue)
    SELECT OpTable, OpUID, Display, Columnname, OldValue, NewValue
    FROM OPENXML(@hDoc, '/Patch/Diff/Op')
    WITH
    (
    OpTable [varchar](50) '../../Key/T',
    OpUID [varchar](50) '../../Key/P',
    Display [varchar](50) '../../@Display',
    Columnname [varchar](50) '@Columnname',
    OldValue [varchar](100) 'OldValue',
    NewValue [varchar](100) 'Value'
    )

    EXEC sp_xml_removedocument @hDoc

    FETCH NEXT FROM XmlList
    INTO @X
    END
    CLOSE XmlList
    DEALLOCATE XmlList

    Select * from @MyTempTable2 order by 1,2,3,4