Technical article 101611

"LMU6086: Can not add new users to local UNIX system..." error.

OpenServer 5.0.0

Written · Last revised

Problem

This message is a generic LAN Manager error message:

LMU6086:  Can not add new users to local UNIX system. The
operation will be retried later.

It can appear in the output of the "net error" command for several reasons.

Cause

The error usually appears in connection with the creation of, or update of, LAN Manager users on a server, in other words, account replication.

When a LAN Manager Primary Domain Controller (PDC) needs to update
the user accounts database of the other servers within its domain,
the "netlogon" process is used. This is started by default within a
LAN Manager server via the "lanman.ini" file under [netlogon] or
from the command line via "net accounts /sync".  Either way, a
backup domain server (BDC) needs to be able to log in to the
primary controller in its domain and actively synchronize or be
synchronized from the primary domain controller.

Solution

The overall account replication process can fail for several
reasons.  Following are some reasons and their solutions:
(1) The server whose user accounts database (/usr/net/servers/
lanman/datafiles/accounts.lmx) is to be synchronized with the
PDC is itself configured as a PDC in the same domain.  In this
case, "net error" will generate these messages:
LMU6086:  Can not add new users to local UNIX system. The operation
          will be retried later.
NETLOGON            3055                10-26-95 07:59PM
NET3055:  A problem exists with the system configuration: A primary
          domain controller is running in this domain.

Check the role of the server with:

# net accounts
Change the role of the server by reconfiguring "lmusrv" using the
"netconfig" utility.  Remake, relink and reboot the machine;
restart the LAN Manager Server.
(2) The BDC has failed to log in to the PDC in its domain when it
initially started its LAN Manager Server.  This is usually due to
an incorrect ADMIN password being configured into "lmusrv" with
"netconfig".  On LAN Manager startup, a correct login sequence is:

Contacting primary domain controller for domain "sco000" to verify LAN Manager ADMIN password ... verified Logging on to domain sco000 as ADMIN ... done Created an account for this machine (SCO000D7) on primary Configuration of the primary "sco000d2" complete and successful LAN Manager Server Starting ... done

Other reasons for failure at this stage could be the incorrect
configuration of the PDC network details, such as IP address, or
faults with the physical connection.  Also, the creation of an
account for the BDC as detailed above may itself fail.

Check the network connection to the PDC and/or reconfigure the ADMIN password correctly via "netconfig".

(3) Another reason for the failure when creating a LAN Manager user
account can be due to a problem involving the underlying operating
system.  A particular example of this is discussed in IT lmu/99, "LAN
Manager accounts creation or replication fails on 2.2.0, error 6068
is logged."
In this case, the LAN Manager "/usr/net/server/lanman/bin/passmgnt"
utility, which is used to create an equivalent UNIX user account,
fails because a previous execution of this command allowed a blank
field to be inserted into the UNIX "/etc/passwd" file, blocking
any subsequent executions.  This problem has been corrected in LAN
Manager 2.2.2.

From the Xinuos technical article database, record 101611. Reproduced with permission. The original is at www.sco.com/ta/101611, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.