Error 608 illegal attribute, user creation workflow not work

HI,
While running user creation workflow, user not get created and throwing error 608 illegal attribute. Before that as per requirement 9 Boolean attribute added to user class.
After sudden shut down of IDM/Userapp server, workflows are not working. Also removed those newly created Boolean attributes, but the result is same.

What is the solution of these. can anyone tell the exact ndsrepair command if the system get repaired and started working.
  • On 5/27/2019 12:44 PM, prasenjitmass wrote:
    >
    > HI,
    > While running user creation workflow, user not get created and throwing
    > error 608 illegal attribute. Before that as per requirement 9 Boolean
    > attribute added to user class.
    > After sudden shut down of IDM/Userapp server, workflows are not working.
    > Also removed those newly created Boolean attributes, but the result is
    > same.
    >
    > What is the solution of these. can anyone tell the exact ndsrepair
    > command if the system get repaired and started working.


    What is your PRD trying to write to th eobject? Check and make sure
    that in the current state of schema, all the attributes are in a object
    class already on the user.

    I.e. If you had these 9 booleans added to an aux class, make sure the
    user has the aux class.

    ndsrepair is not likely to fix this for you.

    I would check that schema is consistent for these attributes on all
    servers.


  • On 5/27/2019 2:50 PM, Geoffrey Carman wrote:
    > On 5/27/2019 12:44 PM, prasenjitmass wrote:
    >>
    >> HI,
    >> While running user creation workflow, user not get created and throwing
    >> error 608 illegal attribute. Before that as per requirement 9 Boolean
    >> attribute added to user class.
    >> After sudden shut down of IDM/Userapp server, workflows are not working.
    >> Also removed those newly created Boolean attributes, but the result is
    >> same.
    >>
    >> What is the solution of these. can anyone tell the exact ndsrepair
    >> command if the system get repaired and started working.

    >
    > What is your PRD trying to write to th eobject?  Check and make sure
    > that in the current state of schema, all the attributes are in a object
    > class already on the user.
    >
    > I.e. If you had these 9 booleans added to an aux class, make sure the
    > user has the aux class.
    >
    > ndsrepair is not likely to fix this for you.
    >
    > I would check that schema is consistent for these attributes on all
    > servers.


    Put another way... 608 error means you tried to add an attribute to an
    object that schema does not allow.

    613 is schema error - this would mean bad data is passed and fails to
    write to the object. (Bad DN or empty DN to a DN syntax attr. Bad date
    syntax, etc. Too long, too short.)

    So that is why I focus on the aux class and the attributes.