Loadusers utility problem

 17 Replies
 0 Subscribed to this topic
 16 Subscribed to this forum
Sort:
Author
Messages
jcote1
New Member Send Private Message
Posts: 0
New Member

OK, I have the following code setup in my loadusers.xml script.  For the life of me, I cannot figure out why this works when I don't have the Email tag setup.  If I put in the email bit, it fails.  Can anyone shine a light on this?

FYI, Agency, UnixID, ProxyUserID WfUser are custom fields and work fine.  I've tested all of them individually.  The only one that fails is email.

       

John Henley
Send Private Message
Posts: 3351

When you say "custom fields", do you mean you customized the LDAP schema, and loadusers is updating those attributes? As far as I know, loadusers only supports a handful of fields, which does not include email address.

Thanks for using the LawsonGuru.com forums!
John
jcote1
New Member Send Private Message
Posts: 0
New Member

Interestingly enough, as long as you get the LDAP field, it seems to work.

Even more interesting, now it works just fine.  Go figure.

 

 

Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member
JC - I'm working on loadusers as well - what did you use to create the XML file?
trueblueg8tor
Advanced Member Send Private Message
Posts: 41
Advanced Member

Go to $GENDIR/system and there should be a loadusers.xml.template file.

jcote1
New Member Send Private Message
Posts: 0
New Member

I wrote a script in VBA to export the user from a custom database.  I use Loadusers to create the account and then ssoconfig to add the identities.  Unfortunately, according to Lawson, there is no way to directly manipulate the Lawson Environment Information using a script, so if you have things you need in there, you have to touch all the accounts.  Something with it being stored in the GEN database.

In order to get the template file, we exported one from ssoconfig I believe, but I think it would give the same response as what trublug8r said.

Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member
Thanks, the bulk of our users are ESS/MSS and we only have to enter data in the Employee and SSOP records in manage identities. Will we still need to run ssoconfig manually for each user to update these items?
jcote1
New Member Send Private Message
Posts: 0
New Member

I believe the answer to that is yes.

What I do is export 2 files from my database.  The first one (loadusers.xml) has the loadusers information (the stuff that would be in "Edit RM Information".  The second file (ssoconfig.xml) has the "Manage Identities" information in it...things like Employee or SSOP.  Then I log into LID and run loadusers -f loadusers.xml  and then ssoconfig -c and go through the process on page 121ish of the Lawson Security Administrator Handbook to create the identities.

You have to be careful with this though...so far i've managed to change passwords on production users and eradicate my administrator privs.  It's been a learning experience...

Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member

Has anyone ever gotten these errors from the loadusers utility?

RMDirectoryException: Could not create object of type People

LDAP: error code 16 - 00000057: LdapErr: DSID-0C090B3D, comment: Error in attribute conversion operation

jcote1
New Member Send Private Message
Posts: 0
New Member

I got those when there was a mistake in the XML format.  For me, it was usually either a syntax issue (I missed a close/open tag) or I had the field name spelled wrong.

Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member
Is there a Lawson document with the field names? Some of the fields in RM have spaces ie: Portal Administrator
Ben Coonfield
Veteran Member Send Private Message
Posts: 146
Veteran Member

Posted By Joe O'Toole on 4/24/2008 8:16 AM Is there a Lawson document with the field names? Some of the fields in RM have spaces ie: Portal Administrator

I believe that these are the right names for loadusers.xml:

Access  Addins  CheckLS  FirstName  Group  ISOLocale  LastName  Name  OLEDBC  PortalAdmin  PortalRole  PrimaryGroup  ProductLine  Role  WFUser  AcgrpCollect  ActivityList  AllowJobQueue  CreateTimeStamp  CreatorsId  DefValSep  Email  ModifiersId  ModifyTimeStamp  PrimaryStructure  PSAStandAlone  SLDTFUNC  SLDTOBS  SNotesServer  ULDTFUNC  ULDTOBS  USERENVSR-COMPANY00  USERENVSR-DM-INV  USERENVSR-DM-REC  USERENVSR-IM-INV  USERENVSR-IM-REC  USERENVSR-INVAOC  USERENVSR-LOCK  USERENVSR-RECAOC  USERENVSR-RECEIPTS  USERENVSR-RECON  USERENVSR-START  USERENVSR-VENDOR00  USERENVSR-VENLIST00  UTZOFFSET  WKDAYEXPR 

I got these names by using a LDAP browser (e.g. JXplorer)

Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member
Thanks, I was going to try that if nobody had the names. JobQueueAccess was the culprit - the loadusers worked fine after I changed it to AllowJobQueue.
GregSl
Veteran Member Send Private Message
Posts: 38
Veteran Member

Can somebody please share a loadusers.xml (Lawson default file) ? I searched all over GENDIR/System and not available. I also tried the knowledge base.

 

Thanks in advance.

Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
Uhh, there is $GENDIR/system/loadusers.xml.template
GregSl
Veteran Member Send Private Message
Posts: 38
Veteran Member
Unfortunately, not in the IFS folder.
John Henley
Send Private Message
Posts: 3351

Here's an article showing some examples:

 

https://www.danalytics.co.../archive/2007-06.htm

The XML file format information is in the Lawson Resources/Security manual.

Thanks for using the LawsonGuru.com forums!
John
GregSl
Veteran Member Send Private Message
Posts: 38
Veteran Member

Thank very much !!!