Problem
When I try to run the Account Manager, via the SCOadmin account or through the desktop icon, the Manager starts to list the users and then it fails. An error is written to /tmp/tclerror.XXXX.log similar to this:
Uncaught error in Tcl program: accountGUI:
can't read "users(15)": no such element in array
------------------------------------------------------------Error code = NONE------------------------------------------------------------
can't read "users(15)": no such element in array
while executing
"keylget users($item) name"
invoked from within
"lappend itemlist [keylget users($item) name]..."
("loop" body line 3)
invoked from within
"loop item 1 $size {
set itemlist [list NO_ICON NO_ICON NO_ICON]
lappend itemlist [keylget users($item) name]
lappend itemlist [keylget users($it ..."
invoked from within
"if {$uData(showIcons)} {
loop item 1 $size {
set itemlist {}
set lockstatus [keylget users($item) lockstatus]
if {$lockstatus} {
set ..."
invoked from within
"if {$uData(listView) == "users"} {
SetUserListTitle
VtDrawnListDeleteItem $uData(mainlist) -all
set size [array size users]
incr size
if {$uData( ..."
(procedure "UpdateMainList" line 5)
invoked from within
"UpdateMainList "
(procedure "DisplayMainScreen" line 131)
invoked from within
"DisplayMainScreen"
(procedure "AccountGUIMain" line 10)
invoked from within
"AccountGUIMain"
("uplevel" body line 1)
invoked from within
"uplevel $command"============================================================The following is another error you may see both on the console and in /etc/tclerrorlog:
fatal error: [Vtcl interp] failed reading receive message length unknown, error: [Vtcl interp] no server connection -missing Vtopen
Also, authck -av will report an error similar to this:
<username> not in /etc/passwd but in Protected Password database
Cause
This failure is happening because the list of system users in /etc/passwd does not match the list of system users in the Protected Password database.
This typically happens when you upgrade from an earlier version of the operating system or you bring the password file from another system. The user that is typically missing from /etc/passwd is the user "backup", but the error will happen if any of the necessary system users is missing.
Solution
1. Log in as root and use your favorite text editor (such as vi) to edit /etc/passwd and add the missing user(s). The list of system users in /etc/passwd should look similar to this:
root:x:0:3:Superuser:/:
daemon:x:1:1:System daemons:/etc:
bin:x:2:2:Owner of system commands:/bin:
sys:x:3:3:Owner of system files:/usr/sys:
adm:x:4:4:System accounting:/usr/adm:
uucp:x:5:5:UUCP administrator:/usr/lib/uucp:
nuucp:x:6:5:Anonymous UUCP site:/usr/spool/uucplogins/nuucp:/usr/lib/uucp/uucico
auth:x:7:21:Authentication administrator:/tcb/files/auth:
asg:x:8:8:Assignable devices:/:
cron:x:9:16:Cron daemon:/usr/spool/cron:
sysinfo:x:11:11:System information:/usr/bin:
dos:x:16:11:DOS device:/:
mmdf:x:17:22:MMDF administrator:/usr/mmdf:
network:x:18:10:MICNET administrator:/usr/network:
backup:x:19:19:Backup administrator:/usr/backup:/bin/sh
nouser:x:28:28:Network user with no access privileges:/:/bin/false
listen:x:37:4:Network daemons:/usr/net/nls:
lp:x:71:18:Printer administrator:/usr/spool/lp:
audit:x:79:17:Audit administrator:/tcb/files/audit:2. Run the command:# pwunconv3. Then run the command:# pwconv4. Edit the file /etc/shadow and update the second field for that user with an asterisk. For example, if you added the "backup" user to /etc/passwd, the entry in /etc/shadow should look like this before editing:
backup:::0:0:134512312After editing, it should look like this:
backup:*::0:0:1345123125. Now, enter the Account Manager, highlight the added user(s), and choose to Modify under the Users pulldown menu. Click OK on the Modify user account screen. This will create the user's home directory if it doesn't already exist.
6. Finally, run the command:# authck -av -yThis will update the Protected Password database.
NOTE: The recommended method for transferring user account information
from one system to another is the ap (account profile) command.
Use the command:# ap -dgv > /u/acct_infoThis will write account profile information for all users listed in the password file to the file "/u/acct_info". The /u/acct_info file can then be restored onto the new system. Once it is there, the command:
# ap -ro -f /u/acct_infowill restore the user account information from the /u/acct_info file onto the new system.
See also
The manual pages for pwconv(ADM), pwunconv(ADM), and ap(ADM)ta105825, "Organizing UNIX filesystems for easy migration."
ta105411, "Filesystem Repair Utilities for SCO OpenServer 5.0.0, 5.0.2 and 5.0.4."