Technical article 100036

netconfig(ADM) reports "corrupt netconfig database: info file missing" error.

OpenServer 5.0.0

Written · Last revised

Problem

LAN Manager has previously been loaded on my SCO OpenServer 5.0 system. It has now been removed and SCO AFPS loaded. However, on system restart, it appears that LAN Manager still exists and the system does not start correctly. Several symptoms are seen.

As an example:

On system reboot, the following errors may be seen.

...
Microsoft Datalink driver: starting dlink - done
/dev/netbeui - no such file or directory
Usage: nbelink [ -d ..........
Advanced Server Starting
SCO AFPS 3.51
...
...
/dev/netbeui: invalid transport provider name
LAN Manager server Starting ... su: /etc/ms_srv not found
...
...

The "net start server" command shows the following message:

The SERVER service is starting ...........................
...................
ASU6126: The SERVER service could not be started. More help
may be obtained by typing NET HELPMSG 6126

If the netconfig(ADM) utility is invoked in order to check the system's protocol and product configuration, it reports the following error:

Network Configuration Manager Starting
OK
Corrupt netconfig database: info file missing

Cause

Both LAN Manager and AFPS protocol chains are present in the configuration of the netconfig database and remnant files of LAN Manager still exist on the system. The two products cannot coexist on the same operating system.

Solution

Several areas related to the problem symptoms must be investigated.

In the above examples, the first major problem is the inability to run the "netconfig" utility. To correct this, follow these steps:

1. As "root", change to the "/usr/lib/netconfig" directory:

#cd /usr/lib/netconfig

2. Save a copy of the current "chains" file:

#cp chains chains.org

3. The existing "chains" file may appear as follows:

# pg chains
sco_tcp#lo0
sco_tcp#net0
sco_nb#sco_tcp
sco_tcp#ppp0
nfs#sco_tcp
lmusrv#netbeui#datalink#net0
lmusrv#sco_nb
netbeui#net0
asusrv#sco_nb
asusrv#netbeui

4. Remove the "lmusrv" chains from the file so it appears as follows:

sco_tcp#lo0
sco_tcp#net0
sco_nb#sco_tcp
sco_tcp#ppp0
nfs#sco_tcp
netbeui#net0
asusrv#sco_nb
asusrv#netbeui

5. Additionally, check in the "/usr/lib/netconfig/info" directory for any associated "lmusrv" chain data and remove it.

The above procedure should now allow "netconfig" to be run without error. Run the utility and confirm that the chains are as required for the AFPS system with respect to any netbios and netbeui protocols.

Reboot the system and re-check for any console error messages.

If the error messages are still seen, check for the existence of the "/dev/datalink" and "/dev/netbeui" device files. In this example, the file "/dev/netbeui" and its corresponding "/etc/conf/packd./ netbeui" directory are missing from the system. The device file must be rebuilt.

Re-run netconfig and remove the existing NetBEUI entry and the AFPS entry that is configured on top of this protocol. Then re-install both protocols again. Relink and rebuild the kernel and reboot the system.

On system reboot, the "dev/netbeui" errors disappear but this error remains:

LAN Manager Server Starting ...su: /etc/ms_srv. not found

The "/etc/rc2.d/S95lmusrv" still exists and contains the following entries that appear on reboot:

echo "LAN Manager Server Starting...\c"
su root -c '/etc/ms_srv start'
echo "done."
As root, remove this file:
#rm /etc/rc2.d/S95lmusrv

Reboot the system and re-check for any error messages in the boot sequence.

See also

IT afps/27, "The AFPS server is not starting; how can I troubleshoot this problem?"

From the Xinuos technical article database, record 100036. Reproduced with permission. The original is at www.sco.com/ta/100036, 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.