MORE INFORMATION
Error 3100
The operation failed because a network software error occurred.
Explanation: A software error occurred.
Action: Contact technical support.
Error 3101
The system ran out of a resource controlled by the *** option.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
system required more of a resource than was available.
Action: Change the value of the listed option in the configuration file to
allow the system to access more of the resource.
Error 3102
The service failed to obtain a long-term lock on the segment for network
control blocks (NCBs). The error code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3103
The service failed to release the long-term lock on the segment for
network control blocks (NCBs). The error code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3104
There was an error stopping service ***. The error code from
NetServiceControl is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3105
Initialization failed because of a system execution failure on path ***.
The system error code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3106
An unexpected network control block (NCB) was received. The NCB is the
data.
Explanation: A software error occurred.
Action: Contact technical support.
Error 3107
The network is not started.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
program or command could not run because LAN Manager is not started or
installed.
Action: Check that LAN Manager is installed and that the Workstation
service is started. Then type the command again.
Error 3108
A DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed. The data shown is in
this format: DWORD approx CS:IP of call to ioctl or fsctl WORD error
code WORD ioctl or fsctl number
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3109
Unable to create or open system semaphore ***. The error code is the
data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3110
Initialization failed because of an open/create error on the file ***.
The system error code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3111
An unexpected NetBIOS error occurred. The error code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3112
An illegal server message block (SMB) was received. The SMB is the data.
Explanation: A software error occurred.
Action: Contact technical support.
Error 3113
Initialization failed because the requested service *** could not be
started.
Explanation: A software error occurred.
Action: Contact technical support.
Error 3114
Some entries in the error log were lost because of a buffer overflow.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
error log is full, and one or more error log entries have been lost.
Action: If you want to save the current error log file, copy it to another
filename. Then clear the error log. You may do this remotely with Event
Viewer.
Error 3120
Initialization parameters controlling resource usage other than net
buffers are sized so that too much memory is needed.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server's main information segment is larger than the largest segment that
can be allocated.
Action: Decrease the values for one or more of the following entries in the
server's configuration file:
MAXCHDEVJOB MAXCONNECTIONS MAXOPENS MAXCHDEVQ MAXLOCKS MAXSHARES
MAXCHDEVS
Then, restart the Server service.
Error 3121
The server cannot increase the size of a memory segment.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server cannot increase the size of a memory segment.
Action: Be sure that the MEMMAN entry in the server's CONFIG.SYS file
allows swapping and that there is at least 1 megabyte of free space on the
swap disk. The swap disk is specified by the SWAPPATH entry in the
Config.sys file. You could also decrease the value of the NUMBIGBUF entry
in the server's configuration file.
Error 3122
Initialization failed because account file *** is either incorrect or
not present.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
user accounts database, Net.acc, is missing, damaged, or in a format that
is incompatible with this version of LAN Manager.
Action: Copy the backup file, Netacc.bkp, to Net.acc. If Netacc.bkp does
not exist, copy Net.acc or Netacc.bkp from a backup floppy or from the LAN
Manager distribution disks. If you have upgraded your LAN Manager software,
you may need to convert the user accounts database to a new format. See the
instructions that came with your upgrade.
Error 3123
Initialization failed because network *** was not started.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. All
networks named in the SRVNETS entry of the server's configuration file must
use the LAN Manager workstation software.
Action: Be sure that all networks named in the SRVNETS entry of the
server's configuration file are also named in the WRKNETS entry of that
file.
Error 3124
The server failed to start. Either all three chdev parameters must be
zero or all three must be nonzero.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
configuration entries CHARWAIT, CHARTIME, and CHARCOUNT must all be zero or
must all have non-zero values.
Action: Correct the entries and restart the Server service.
Error 3125
A remote API request was halted due to the following invalid description
string: ***.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server received an invalid request to run a command. The request may have
been damaged by the network.
Action: No action is needed. If this error occurs frequently, contact
technical support.
Error 3126
The network *** ran out of network control blocks (NCBs). You may need
to increase NCBs for this network. The following information includes
the number of NCBs submitted by the server when this error occurred:
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server found a resource shortage in a network driver when it tried to issue
a network control block (NCB).
Action: Be sure that the NETn entries in the configuration file specify
valid NetBIOS device drivers and that these device drivers are in the
Lanman\Drivers folder. Also, be sure that the Config.sys file contains a
DEVICE line specifying the absolute paths of the device drivers. You may be
able to increase the NCBs for the listed network by changing an option in
the network's NETn entry in the configuration file. See the installation
guide that came with your network adapter for information about those
options. If you need assistance, contact your network administrator.
Error 3127
The server cannot create the *** mailslot needed to send the
ReleaseMemory alert message. The error received is:
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server cannot respond to a ReleaseMemory alert. Otherwise, the server is
functioning normally.
Action: No action is needed.
Error 3128
The server failed to register for the ReleaseMemory alert, with
recipient ***. The error code from NetAlertStart is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server cannot respond to a ReleaseMemory alert. Otherwise, the server is
functioning normally.
Action: No action is needed.
Error 3129
The server cannot update the AT schedule file. The file is corrupted.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
schedule file, Sched.log, in the LOGS directory, is damaged.
Action: Restore the schedule file from a backup copy, or delete the file
and create a new one using the AT utility.
Error 3130
The server encountered an error when calling NetIMakeLMFileName. The
error code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server could not find the Net.msg file.
Action: The NET.MSG file should be in the Lanman\Netprog folder. If it is
not there, copy it from the LAN Manager distribution disks.
Error 3131
Initialization failed because of a system execution failure on path ***.
There is not enough memory to start the process. The system error code
is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. There
is not enough memory available to run the Server service.
Action: Stop other applications and services (except the Workstation
service) that are running on the computer and try again. If the problem
continues, you will have to add memory to the computer.
Error 3132
Longterm lock of the server buffers failed. Check swap disk's free space
and restart the system to start the server.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server was unable to access required memory.
Action: Be sure there is at least 1 megabyte of free space on the swap
disk. The swap disk is specified by the SWAPPATH entry in the Config.sys
file. Then, restart the computer and try to start the Server service again.
Error 3140
The service has stopped due to repeated consecutive occurrences of a
network control block (NCB) error. The last bad NCB follows in raw data.
Explanation: A software error occurred.
Action: Contact technical support.
Error 3141
The Message server has stopped due to a lock on the Message server
shared data segment.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3150
A file system error occurred while opening or writing to the system
message log file ***. Message logging has been switched off due to the
error. The error code is the data.
Error 3151
Unable to display message POPUP due to system VIO call error. The error
code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
Messenger service could not display a message because an error occurred
while the message box was being created.
Action: If message logging was on, the message was still logged to the file
and can be viewed by displaying or printing the message log file.
Error 3152
An illegal server message block (SMB) was received. The SMB is the data.
Explanation: A software error occurred.
Action: Contact technical support.
Error 3160
The workstation information segment is bigger than 64K. The size
follows, in DWORD format:
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
workstation's main information segment is larger than the largest segment
that can be allocated.
Action: Decrease the values for one or more of the following entries in the
[workstation] section of the configuration file. If you need assistance,
contact your network administrator.
MAXCMDS NUMCHARBUF NUMWORKBUF MAXTHREADS NUMDGRAMBUF SIZCHARBUF
NUMALERTS NUMSERVICES SIZERROR
After you change the configuration file, restart the Workstation service.
If you change the MAXCMDS or MAXTHREADS entry, you will have to restart the
computer.
Error 3161
The workstation was unable to get the name-number of the computer.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3162
The workstation could not initialize the Async NetBIOS Thread. The error
code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3163
The workstation could not open the initial shared segment. The error
code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
Workstation service may have been started improperly. Always use the NET
START command to start the workstation; do not run Wksta.exe directly.
Action: To start the Workstation service, type: NET START WORKSTATION
If more problems occur, contact technical support.
Error 3164
The workstation host table is full.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
internal table that maintains information about network servers is full.
You can access all network servers normally, but you may not be able to see
all servers when you type the NET VIEW command. This happens only on very
large networks.
Action: Contact your network administrator. Your administrator may want to
divide the network into domains, using the DOMAIN entry in each computer's
configuration file.
Error 3165
A bad mailslot server message block (SMB) was received. The SMB is the
data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3166
The workstation encountered an error while trying to start the user
accounts database. The error code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
Workstation service failed to start the user accounts database.
Action: Contact technical support.
Error 3167
The workstation encountered an error while responding to an SSI
revalidation request. The function code and the error codes are the
data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3170
The Alerter service had a problem creating the list of alert recipients.
The error code is ***.
Explanation: A software error occurred.
Action: Contact technical support.
Error 3171
There was an error expanding *** as a group name. Try splitting the
group into two or more smaller groups.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. An
error occurred when LAN Manager tried to identify the members of the
specified group. The group is probably too large.
Action: Split the group into two or more smaller groups.
Error 3172
There was an error sending *** the alert message - (***) The error code
is ***.
Explanation: An error occurred when an alert message was sent. The user
name designated to receive the alert may no longer exist.
Action: Use Server Manager to repair the error.
Error 3173
There was an error in creating or reading the Alerter mailslot. The
error code is ***.
Explanation: A software error occurred.
Action: Verify that the Alerter service has been started. If the service
has already been started, contact technical support.
Error 3174
The server could not read the AT schedule file.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. LAN
Manager cannot read the schedule file because the file is damaged.
Action: Restore the schedule file from a backup copy, if you have one. If
not, delete the file and create a new one with the AT utility.
Error 3175
The server found an invalid AT schedule record.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
schedule file contains a record with an invalid format.
Action: Restore the schedule file from a backup copy. If you do not have
one, delete the AT schedule file and create a new one with the AT utility.
Error 3176
The server could not find an AT schedule file so it created one.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server created a schedule file.
Action: No action is needed.
Error 3177
The server could not access the *** network with NetBiosOpen.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
server could not start one of its networks.
Action: Be sure that each network listed in the SRVNETS entry in the
server's configuration file has a corresponding entry in the [networks]
section of the configuration file.
Error 3178
The AT command processor could not run ***.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. You
used the AT utility to specify a program that could not run.
Action: Check the filename of the program you tried to schedule. If it is
in a directory that is not on the computer's search path, be sure to
specify its full path. Be sure that all programs you schedule are
executable.
Error 3180
WARNING: Because of a lazy-write error, drive *** now contains some
corrupted data. The cache is stopped.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. An
error occurred when the lazy-write process tried to write to the specified
hard disk.
Action: Run CHKDSK on the specified drive to check for problems with the
disk or the files affected by the lazy-write process.
Error 3181
A defective sector on drive *** has been replaced (hotfixed). No data
was lost. You should run CHKDSK soon to restore full performance and
replenish the volume's spare sector pool. The hotfix occurred while
processing a remote request.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
fault-tolerance system found a bad disk sector and rerouted data to a good
sector (this is called hotfixing). No data was lost.
Action: Run CHKDSK soon to ensure that enough good disk sectors are
available for hotfixing.
Error 3182
A disk error occurred on the HPFS volume in drive ***. The error
occurred while processing a remote request.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. An
error occurred during an operation on the listed disk because of problems
with the disk. The operation probably did not succeed.
Action: Retry the operation. If the problem persists and you are unable to
recover data from the disk, use backups of the affected files, if you have
any.
Error 3183
The user accounts database (NET.ACC) is corrupted. The local security
system is replacing the corrupted NET.ACC with the backup made at ***.
Any updates made to the database after this time are lost.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
user accounts database file is damaged, so the backup file made at the
listed date is now being used. Changes made to the user accounts database
since this time were lost. Local security is still in effect.
Action: To update the user accounts database, retype changes made to it
since the listed date.
Error 3184
The user accounts database (NET.ACC) is missing. The local security
system is restoring the backup database made at ***. Any updates made to
the database made after this time are lost.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
user accounts database file is missing, so the backup file made at the
listed date is now being used. Changes made to the user accounts database
since this time were lost. Local security is still in effect.
Action: To update the user accounts database, retype changes made to it
since the listed date.
Error 3185
Local security could not be started because the user accounts database
(NET.ACC) was missing or corrupted, and no usable backup database was
present. THE SYSTEM IS NOT SECURE.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. Local
security could not start because the user accounts database file, Net.acc,
is missing or damaged and no backup file exists on the hard disk.
Action: Restore Net.acc from a backup. The backup file will be named either
Net.acc or Netacc.bkp. Then restart the computer. If there is no backup,
reinstall LAN Manager using the Setup program.
Error 3186
Local security could not be started because an error occurred during
initialization. The error code returned is ***. THE SYSTEM IS NOT
SECURE.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. Local
security could not start because of the listed error.
Action: Find and correct the cause of the listed error, and then restart
the computer.
Error 3190
A NetWksta internal error has occurred: ***
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. A
software error occurred.
Action: Contact technical support.
Error 3191
The redirector is out of a resource: ***.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
workstation is out of the specified resource.
Action: Adjust the workstation's configuration file to increase the amount
of this resource. If you need assistance, contact your network
administrator.
Error 3192
A server message block (SMB) error occurred on the connection to ***.
The SMB header is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. An
error occurred on a request that was sent to the specified server. The
workstation may have been connected to a resource that is no longer shared.
Action: Ask a network administrator to reshare the resource so that you can
use it. If this solution fails, contact technical support.
Error 3193
A virtual circuit error occurred on the session to ***. The network
control block (NCB) command and return code is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
connection between your workstation and the specified server was
unexpectedly broken. The server may have been restarted or a network
problem may have occurred.
Action: If the server was restarted, retry the operation to reestablish the
connection. If you need more assistance, contact technical support. This
message displays a network control block (NCB) value and the NCB error that
was returned. Save this information for technical support.
Error 3194
Hanging up a stuck session to ***.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
session with the specified server was ended because the server stopped
responding.
Action: Ask your network administrator if the server is running. If so,
reconnect to the server. The amount of time a workstation waits for a
server to respond to a request is determined by the SESSTIMEOUT entry in
the workstation's configuration file. If your sessions with servers are
frequently ended by this error, you may want to increase the value of
SESSTIMEOUT. If you need assistance, contact your administrator.
Error 3195
A network control block (NCB) error occurred (***). The NCB is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. An
unexpected network control block (NCB) error occurred on the session with
the specified server. The server may have been restarted, or a network
problem may have occurred.
Action: Ask your network administrator if the server was recently
restarted. If you need more assistance, contact technical support. This
message displays an NCB value and the NCB error that was returned. Save
this information for technical support.
Error 3196
A write operation to *** failed. Data may have been lost.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. An
attempt to write data to a file failed.
Action: See if the specified disk is full. Also, be sure that you have
write permission for the target file.
Error 3197
Reset of driver *** failed to complete the network control block (NCB).
The NCB is the data.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
specified NetBIOS driver found a problem that required the network adapter
card to be reset. Resetting the card did not solve the problem.
Action: Contact technical support.
Error 3198
The amount of resource *** requested was more than the maximum. The
maximum amount was allocated.
Explanation: This message should occur only on a down-level computer. Any
action to correct the problem should be performed on that computer. The
amount of the listed resource requested was more than the maximum. The
maximum amount was allocated.
Action: Ask your network administrator check the workstation's
configuration.