This table contains the messages that can be returned to a Windows NT Workstation or Windows NT Server system from an earlier operating system (such as Windows for Workgroups or LAN Manager), which is called, for convenience, a down-level system.
In Chapter 4, "Message Reference," the network messages are presented alphabetically and interspersed with the other system messages. In the following table, they have been arranged numerically. Missing or skipped numbers could be related to simple messages, such as "Password expires," that were not included in the printed version, or they may be in the Windows NT Workstation/Windows NT Server Network Message ID Numbers table, which is provided in the preceding section of this chapter.
ID | Message text |
2103 | The server could not be located. |
2107 | The device is not connected. |
2117 | The operation is invalid on a redirected resource. |
2122 | The Peer service supports only two simultaneous users. |
2127 | A remote API error occurred. |
2131 | An error occurred when opening or reading the configuration file. |
2139 | The requested information is not available. |
2143 | The event name is invalid. |
2149 | A line in the configuration file is too long. |
2152 | The printer destination cannot be found. |
2153 | The printer destination already exists. |
2154 | The printer queue already exists. |
2155 | No more printers can be added. |
2156 | No more print jobs can be added. |
2157 | No more printer destinations can be added. |
2158 | This printer destination is idle and cannot accept control operations. |
2159 | This printer destination request contains an invalid control function. |
2160 | The print processor is not responding. |
2161 | The spooler is not running. |
2162 | This operation cannot be performed on the print destination in its current state. |
2163 | This operation cannot be performed on the printer queue in its current state. |
2164 | This operation cannot be performed on the print job in its current state. |
2165 | A spooler memory allocation failure occurred. |
2166 | The device driver does not exist. |
2167 | The data type is not supported by the print processor. |
2168 | The print processor is not installed. |
2181 | The service table is full. |
2183 | The service does not respond to control actions. |
2188 | The configuration file contains an invalid service program name. |
2190 | The service ended abnormally. |
2192 | The service control dispatcher could not find the service name in the dispatch table. |
2193 | The service control dispatcher pipe read failed. |
2200 | This workstation is already logged on to the local-area network. |
2201 | The workstation is not logged on to the local-area network. |
2204 | The logon processor did not add the message alias. |
2205 | The logon processor did not add the message alias. |
2206 | The logoff processor did not delete the message alias. |
2207 | The logoff processor did not delete the message alias. |
2209 | Network logons are paused. |
2210 | A centralized logon-server conflict occurred. |
2212 | An error occurred while loading or running the logon script. |
2214 | The logon server was not specified. Your computer will be logged on as STANDALONE. |
2215 | The logon server could not be found. |
2216 | There is already a logon domain for this computer. |
2217 | The logon server could not validate the logon. |
2225 | The resource permission list already exists. |
2228 | There are too many names in the user accounts database. |
2230 | The limit of 64 entries per resource was exceeded. |
2231 | Deleting a user with a session is not allowed. |
2232 | The parent directory could not be located. |
2235 | This user is not cached in the user accounts database session cache. |
2238 | This user account is undefined. |
2243 | The password of this user cannot change. |
2244 | This password cannot be used now. |
2248 | No updates are necessary to this replicant network/local security database. |
2252 | This device is currently being shared. |
2271 | The Messenger service is already started. |
2272 | The Messenger service failed to start. |
2275 | This message alias has been added but is still forwarded. |
2279 | Messages cannot be forwarded back to the same workstation. |
2284 | The Messenger service has not been started. |
2286 | The forwarded message alias could not be found on the network. |
2287 | The message alias table on the remote station is full. |
2288 | Messages for this alias are not currently being forwarded. |
2295 | A write fault occurred. |
2300 | This operation is not supported on computers with multiple networks. |
2314 | There is not an open file with that identification number. |
2315 | A failure occurred when executing a remote administration command. |
2316 | A failure occurred when opening a remote temporary file. |
2318 | This device cannot be shared as both a spooled and a non-spooled resource. |
2319 | The information in the list of servers may be incorrect. |
2320 | The computer is not active in this domain. |
2331 | The operation is invalid for this device. |
2332 | This device cannot be shared. |
2333 | This device was not open. |
2334 | This device name list is invalid. |
2335 | The queue priority is invalid. |
2337 | There are no shared communication devices. |
2338 | The queue you specified does not exist. |
2340 | This list of devices is invalid. |
2341 | The requested device is invalid. |
2342 | This device is already in use by the spooler. |
2343 | This device is already in use as a communication device. |
2354 | The string and prefix specified are too long. |
2356 | This path component is invalid. |
2370 | Profile files cannot exceed 64K. |
2371 | The start offset is out of range. |
2372 | The system cannot delete current connections to network resources. |
2373 | The system was unable to parse the command line in this file. |
2374 | An error occurred while loading the profile file. |
2375 | Errors occurred while saving the profile file. The profile was partially saved. |
2377 | Log file filename is full. |
2380 | The source path cannot be a directory. |
2381 | The source path is illegal. |
2382 | The destination path is illegal. |
2383 | The source and destination paths are on different servers. |
2385 | The Run server you requested is paused. |
2389 | An error occurred when communicating with a Run server. |
2391 | An error occurred when starting a background process. |
2392 | The shared resource you are connected to could not be found. |
2400 | The LAN adapter number is invalid. |
2402 | Active connections still exist. |
2405 | The drive letter is in use locally. |
2430 | The specified client is already registered for the specified event. |
2431 | The alert table is full. |
2433 | The alert recipient is invalid. |
2434 | A user's session with this server has been deleted because the user's logon hours are no longer valid. |
2440 | The log file does not contain the requested record number. |
2450 | The user accounts database is not configured correctly. |
2451 | This operation is not permitted when the Netlogon service is running. |
2452 | This operation is not allowed on the last administrative account. |
2454 | Could not set logon information for this user. |
2455 | The Netlogon service has not been started. |
2456 | Unable to add to the user accounts database. |
2458 | A password mismatch has been detected. |
2460 | The server identification does not specify a valid server. |
2461 | The session identification does not specify a valid session. |
2462 | The connection identification does not specify a valid connection. |
2463 | There is no space for another entry in the table of available servers. |
2464 | The server has reached the maximum number of sessions it supports. |
2465 | The server has reached the maximum number of connections it supports. |
2466 | The server cannot open more files because it has reached its maximum number. |
2467 | There are no alternate servers registered on this server. |
2480 | The UPS driver could not be accessed by the UPS service. |
ID | Message text (continued) |
3000 | Drive name is nearly full. Number bytes are available. Please warn users and delete unneeded files. |
3001 | Number errors were logged in the last number minutes. Please review the server's error log. |
3002 | Number network errors occurred in the last number minutes. Please review the server's error log. The server and/or network hardware may need service. |
3003 | There were number bad password attempts in the last number minutes. Please review the server's audit trail. |
3004 | There were number access-denied errors in the last number minutes. Please review the server's audit trail. |
3006 | The error log is full. No errors will be logged until the file is cleared or the limit is raised. |
3007 | The error log is 80% full. |
3008 | The audit log is full. No audit entries will be logged until the file is cleared or the limit is raised. |
3009 | The audit log is 80% full. |
3010 | An error occurred closing file filename. Please check the file to make sure it is not corrupted. |
3011 | The administrator has closed filename. |
3012 | There were number access-denied errors in the last number minutes. |
3025 | A defective sector on drive drive letter 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. |
3026 | A disk error occurred on the HPFS volume in drive drive letter. The error occurred while processing a remote request. |
3027 | The user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the backup made on date at time. Any updates made to the database after this time are lost. |
3028 | The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made on date at time. Any updates made to the database after this time are lost. |
3029 | 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. |
3033 | User user name has exceeded the account limitation text on server name. |
3036 | The replicator attempted to log on at computer name as user name and failed. |
3046 | Cannot log on. User is currently logged on and argument TRYUSER is set to NO. |
3048 | EXPORT path path cannot be found. |
3050 | Replicator failed to update signal file in directory name due to code system error. |
3052 | The required parameter was not provided on the command line or in the configuration file. |
3053 | LAN Manager does not recognize name as a valid option. |
3055 | A problem exists with the system configuration. |
3058 | The configuration file or the command line has an ambiguous option. |
3059 | The configuration file or the command line has a duplicate parameter. |
3063 | There is a conflict in the value or use of these options: name. |
3075 | Bad or missing LAN Manager root directory. |
3076 | The network software is not installed. |
3077 | The server is not started. |
3078 | The server cannot access the user accounts database (NET.ACC). |
3079 | Incompatible files are installed in the LANMAN tree. |
3080 | The LANMAN\LOGS directory is invalid. |
3081 | The domain specified could not be used. |
3082 | The computer name is being used as a message alias on another computer. |
3083 | The announcement of the server name failed. |
3084 | The user accounts database is not configured correctly. |
3085 | The server is not running with user-level security. |
3087 | The workstation is not configured properly. |
3088 | View your error log for details. |
3089 | Unable to write to this file. |
3090 | ADDPAK file is corrupted. Delete LANMAN\NETPROG\ADDPAK.SER and reapply all ADDPAKs. |
3091 | The LM386 server cannot be started because CACHE.EXE is not running. |
3092 | There is no account for this computer in the security database. |
3093 | This computer is not a member of the group SERVERS. |
3094 | The group SERVERS is not present in the local security database. |
3098 | The service failed to authenticate with the primary domain controller. |
3099 | There is a problem with the security database creation date or serial number. |
3101 | The system ran out of a resource controlled by the name option. |
3102 | The service failed to obtain a long-term lock on the segment for network control blocks (NCBs). The error code is the data. |
3103 | The service failed to release the long-term lock on the segment for network control blocks (NCBs). The error code is the data. |
3104 | There was an error stopping service name. The error code from NetServiceControl is the data. |
3105 | Initialization failed because of a system execution failure on path path. The system error code is the data. |
3107 | The network is not started. |
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 |
3109 | Unable to create or open system semaphore name. The error code is the data. |
3110 | Initialization failed because of an open/create error on the file filename. The system error code is the data. |
3111 | An unexpected NetBIOS error occurred. The error code is the data. |
3114 | Some entries in the error log were lost because of a buffer overflow. |
3120 | Initialization parameters controlling resource usage other than net buffers are sized so that too much memory is needed. |
3121 | The server cannot increase the size of a memory segment. |
3122 | Initialization failed because account file filename is either incorrect or not present. |
3123 | Initialization failed because network name was not started. |
3124 | The server failed to start. Either all three chdev parameters must be zero or all three must be nonzero. |
3125 | A remote API request was halted due to the following invalid description string: text. |
3126 | The network name 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: text. |
3127 | The server cannot create the name mailslot needed to send the ReleaseMemory alert message. The error received is: code. |
3128 | The server failed to register for the ReleaseMemory alert, with recipient computer name. The error code from NetAlertStart is the data. |
3129 | The server cannot update the AT schedule file. The file is corrupted. |
3130 | The server encountered an error when calling NetIMakeLMFileName. The error code is the data. |
3131 | Initialization failed because of a system execution failure on path path. There is not enough memory to start the process. The system error code is the data. |
3132 | Longterm lock of the server buffers failed. Check the swap disk's free space and restart the system to start the server. |
3141 | The Message server has stopped due to a lock on the Message server shared data segment. |
3150 | A file system error occurred while opening or writing to the system message log file filename. Message logging has been switched off due to the error. The error code is the data. |
3160 | The workstation information segment is bigger than 64K. The size follows, in DWORD format: text. |
3161 | The workstation was unable to get the name-number of the computer. |
3162 | The workstation could not initialize the Async NetBIOS Thread. The error code is the data. |
3163 | The workstation could not open the initial shared segment. The error code is the data. |
3164 | The workstation host table is full. |
3165 | A bad mailslot server message block (SMB) was received. The SMB is the data. |
3166 | The workstation encountered an error while trying to start the user accounts database. The error code is the data. |
3167 | The workstation encountered an error while responding to an SSI revalidation request. The function code and the error codes are the data. |
3171 | There was an error expanding name as a group name. Try splitting the group into two or more smaller groups. |
3174 | The server could not read the AT schedule file. |
3175 | The server found an invalid AT schedule record. |
3176 | The server could not find an AT schedule file so it created one. |
3177 | The server could not access the name network with NetBiosOpen. |
3178 | The AT command processor could not run application. |
3180 | WARNING: Because of a lazy-write error, drive drive letter now contains some corrupted data. The cache is stopped. |
3181 | A defective sector on drive drive letter 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. |
3182 | A disk error occurred on the HPFS volume in drive drive letter. The error occurred while processing a remote request. |
3183 | The user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the backup made at date. Any updates made to the database after this time are lost. |
3184 | The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made at date. Any updates made to the database after this time are lost. |
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. |
3186 | Local security could not be started because an error occurred during initialization. The error code returned is code. THE SYSTEM IS NOT SECURE. |
3190 | A NetWksta internal error has occurred: code. |
3191 | The redirector is out of a resource: name. |
3192 | A server message block (SMB) error occurred on the connection to name. The SMB header is the data. |
3193 | A virtual circuit error occurred on the session to name. The network control block (NCB) command and return code is the data. |
3194 | Hanging up a stuck session to name. |
3195 | A network control block (NCB) error occurred code. The NCB is the data. |
3196 | A write operation to filename failed. Data may have been lost. |
3197 | Reset of driver name failed to complete the network control block (NCB). The NCB is the data. |
3198 | The amount of resource name requested was more than the maximum. The maximum amount was allocated. |
3204 | The server could not create a thread. The THREADS parameter in the CONFIG.SYS file should be increased. |
3205 | The server could not close filename. The file is probably corrupted. |
3211 | The replicator attempted to log on at computer name as user name and failed. |
3213 | Replicator limit for files in a directory has been exceeded. |
3214 | Replicator limit for tree depth has been exceeded. |
3217 | Cannot log on. User is currently logged on and argument TRYUSER is set to NO. |
3219 | EXPORT path path cannot be found. |
3220 | Replicator failed to update the signal file in directory name due to code system error. |
3221 | Disk Fault Tolerance Error code. |
3225 | An error occurred while updating the logon or logoff information for user name. |
3233 | The UPS driver could not be opened. The error code is the data. |
3250 | Initialization failed because of an invalid or missing parameter in the configuration file filename. |
3251 | Initialization failed because of an invalid line in the configuration file filename. The invalid line is the data. |
3252 | Initialization failed because of an error in the configuration file filename. |
3253 | The file filename has been changed after initialization. The boot-block loading was temporarily terminated. |
3254 | The files do not fit to the boot-block configuration file filename. Change the BASE and ORG definitions or the order of the files. |
3255 | Initialization failed because the dynamic-link library name returned an incorrect version number. |
3256 | There was an unrecoverable error in the dynamic-link library of the service. |
3258 | The fault-tolerance error log file, LANROOT\LOGS\FT.LOG, is more than 64K. |
3259 | The fault-tolerance error log file, LANROOT\LOGS \FT.LOG, had the update in progress bit set upon opening, which means that the system crashed while working on the error log. |
3304 | A network error occurred. |
3400 | There is not enough memory to start the Workstation service. |
3401 | An error occurred when reading the NETWORKS entry in the LANMAN.INI file. |
3402 | This is an invalid argument: name. |
3403 | The text NETWORKS entry in the LANMAN.INI file has a syntax error and will be ignored. |
3404 | There are too many NETWORKS entries in the LANMAN.INI file. |
3406 | An error occurred when opening network device driver name = name. |
3407 | Device driver name sent a bad BiosLinkage response. |
3409 | The redirector is already installed. |
3411 | There was an error installing NETWKSTA.SYS. Press ENTER to continue. |
3412 | Resolver linkage problem. |
ID | Message text (continued) |
3512 | The software requires a newer version of the operating system. |
3526 | The workstation has open files. |
3535 | An error occurred controlling the device. |
3675 | The session from computer name has open files. |
3677 | New connections will not be remembered. |
3678 | An error occurred while saving your profile. The state of your remembered connections has not changed. |
3680 | An error occurred while restoring the connection to name. |
3694 | The shared queue cannot be deleted while a print job is being spooled to the queue. |
3714 | This operation is privileged on systems with earlier versions of the software. |
3717 | The log file has been corrupted. |
3718 | Program filenames must end with .EXE. |
3720 | A bad value is in the units-per-week field of the user record. |
3758 | The destination list provided does not match the destination list of the printer queue. |
3759 | Your password cannot be changed until date. |
3803 | The LANMAN root directory is unavailable. |
3804 | The SCHED.LOG file could not be opened. |
3807 | The AT schedule file is corrupted. |
3808 | The delete failed due to a problem with the AT schedule file. |
3810 | The AT schedule file could not be updated because the disk is full. |
3812 | The AT schedule file is invalid. Please delete the file and create a new one. |
5170 | The workstation must be started with the Net Start command. |
5281 | Drive letter has a remembered connection to name. Do you want to overwrite the remembered connection? path |
5301 | Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS. The NCB is the data. |
5302 | The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the data. |
5303 | The command specified in the network control block (NCB) is illegal. The NCB is the data. |
5304 | The message correlator specified in the network control block (NCB) is invalid. The NCB is the data. |
5306 | An incomplete network control block (NCB) message was received. The NCB is the data. |
5307 | The buffer address specified in the network control block (NCB) is illegal. The NCB is the data. |
5308 | The session number specified in the network control block (NCB) is not active. The NCB is the data. |
5310 | The session specified in the network control block (NCB) was closed. The NCB is the data. |
5311 | The network control block (NCB) command was canceled. The NCB is the data. |
5312 | The message segment specified in the network control block (NCB) is illogical. The NCB is the data. |
5313 | The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is the data. |
5314 | The network adapter name table is full. The network control block (NCB) request was refused. The NCB is the data. |
5315 | The network name has active sessions and is now de-registered. The network control block (NCB) command completed. The NCB is the data. |
5316 | A previously issued Receive Lookahead command is active for this session. The network control block (NCB) command was rejected. The NCB is the data. |
5318 | A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the data. |
5319 | The name number specified in the network control block (NCB) is illegal. The NCB is the data. |
5320 | The call name specified in the network control block (NCB) cannot be found or did not answer. The NCB is the data. |
5321 | The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the data. |
5322 | The name specified in the network control block (NCB) is in use on a remote adapter. The NCB is the data. |
5323 | The name specified in the network control block (NCB) has been deleted. The NCB is the data. |
5324 | The session specified in the network control block (NCB) ended abnormally. The NCB is the data. |
5325 | The network protocol has detected two or more identical names on the network. The network control block (NCB) is the data. |
5326 | An unexpected protocol packet was received. There may be an incompatible remote device. The network control block (NCB) is the data. |
5333 | The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB is the data. |
5335 | The adapter number specified in the network control block (NCB) is illegal. The NCB is the data. |
5336 | The network control block (NCB) command completed while a cancel was occurring. The NCB is the data. |
5337 | The name specified in the network control block (NCB) is reserved. The NCB is the data. |
5338 | The network control block (NCB) command is not valid to cancel. The NCB is the data. |
5351 | There are multiple network control block (NCB) requests for the same session. The NCB request was refused. The NCB is the data. |
5352 | There has been a network adapter error. The only NetBIOS command that may be issued is an NCB RESET. The network control block (NCB) is the data. |
5354 | The maximum number of applications was exceeded. The network control block (NCB) request was refused. The NCB is the data. |
5356 | The requested resources are not available. The network control block (NCB) request was refused. The NCB is the data. |
5364 | A system error has occurred. The network control block (NCB) request was refused. The NCB is the data. |
5365 | A ROM checksum failure has occurred. The network control block (NCB) request was refused. The NCB is the data. |
5366 | A RAM test failure has occurred. The network control block (NCB) request was refused. The NCB is the data. |
5367 | A digital loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data. |
5368 | An analog loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data. |
5369 | An interface failure has occurred. The network control block (NCB) request was refused. The NCB is the data. |
5370 | An unrecognized network control block (NCB) return code was received. The NCB is the data. |
5380 | A network adapter malfunction has occurred. The network control block (NCB) request was refused. The NCB is the data. |
5381 | The network control block (NCB) command is still pending. The NCB is the data. |
5500 | The update log on name is over 80% capacity. The primary domain controller name is not retrieving the updates. |
5501 | The update log on name is full, and no further updates can be added until the primary domain controller name retrieves the updates. |
5502 | The time difference with the primary domain controller name exceeds the maximum allowed skew of number seconds. |
5503 | The account of user user name has been locked out on name due to number bad password attempts. |
5504 | The filename log file cannot be opened. |
5505 | The filename log file is corrupted and will be cleared. |
5506 | The Application log file could not be opened. Filename will be used as the default log file. |
5507 | The filename log file is full. |
5600 | Could not share the User or Script path. |
5713 | The full synchronization request from the server name completed successfully. Number object(s) has (have) been returned to the caller. |
5714 | The full synchronization request from the server name failed. |