If the problem is just that the request id / samAccountname is null, then you could always map another character field to the samAccountName and use that for updating.
Hugo On 6/25/07, Roney Samuel Varghese <[EMAIL PROTECTED]> wrote:
Dear Dmitry, LDAP_OBJECT_CLASS_VIOLATION: Indicates that the add, modify, or modify DN operation violates the object class rules for the entry. For example, the following types of request return this error: 1. The add or modify operation tries to add an entry without a value for a required attribute. 2. The add or modify operation tries to add an entry with a value for an attribute which the class definition does not contain. 3. The modify operation tries to remove a required attribute without removing the auxiliary class that defines the attribute as required. So in your case I believe the 1 or 2nd case holds true. Try to validate all the date before you push the data to the vendor form. If you have problems generating a request id use a Request ID generator form instead. Hope this helps Regards. Roney Samuel Varghese On 6/25/07, Bezhenar, Dmitry <[EMAIL PROTECTED] > wrote: > > ** Hello List, > > I am just curious if it is possible to create AD accounts using vendor > forms? I tried to create one, but got this error - > > The LDAP operation has failed : Object class violation (LDAPERR > 65)0000207B: UpdErr: DSID-03050FB5, problem 6002 (OBJ_CLASS_VIOLATION), data > 0 > (ARERR 3377) > > I think the problem is Request ID field (samAccountname in my case). > Remedy does not allow to enter data into this Request ID field during > request creation and I have absolutely no idea how to avoid this. > > Any help would be highly appreciated. > Thank you. > > > Kind Regards / C уважением > > Dmitry Bezhenar > __20060125_______________________This posting was submitted with HTML in > it___
