〖0〗-The operation completed successfully.
〖1〗-Function error.
〖2〗-The system cannot find the specified file.
〖3〗-The system cannot find the specified path.
〖4〗-The system cannot open the file.
〖5〗-Access denied.
〖6〗-The handle is invalid.
〖7〗-The storage control block is damaged.
〖8〗-Insufficient storage space to process this command.
〖9〗-The storage control block address is invalid.
〖10〗-Environment error.
〖11〗-An attempt was made to load a malformed program.
〖12〗-The access code is invalid.
〖13〗-The data is invalid.
〖14〗-Insufficient memory to complete this operation.
〖15〗-The system cannot find the specified drive.
〖16〗-The directory cannot be deleted.
〖17〗-The system cannot move the file to a different drive.
〖18〗-No more files.
〖19〗-The media is write-protected.
〖20〗-The system cannot find the specified device.
〖21〗-The device is not ready.
〖22〗-The device does not recognize this command.
〖23〗-Data error (cyclic redundancy check).
〖24〗-The program issued a command, but the command length was incorrect.
〖25〗 - The drive cannot find the location of a specific area or track on the disk.
〖26〗-The specified disk or floppy cannot be accessed.
〖27〗 - The drive cannot find the requested sector.
〖28〗-The printer is out of paper.
〖29〗-The system cannot write to the specified device.
〖30〗-The system cannot read from the specified device.
〖31〗-The device connected to the system is not functioning.
〖32〗 - The process cannot access the file because it is in use by another program.
〖33〗 - The process cannot access the file because another program has locked part of the file.
〖36〗-There are too many open files for sharing.
〖38〗 - End of file reached.
〖39〗-The disk is full.
〖50〗-Network requests are not supported.
〖51〗-The remote computer is unavailable.
〖52〗-There is a duplicate name on the network.
〖53〗-The network path cannot be found.
〖54〗-The network is busy.
〖55〗-The specified network resource or device is no longer available.
〖56〗-The network BIOS command limit has been reached.
〖57〗-Network adapter hardware error.
〖58〗-The specified server cannot run the requested operation.
〖59〗-An unexpected network error occurred.
〖60〗-The remote adapter is incompatible.
〖61〗-The printer queue is full.
〖62〗 - Unable to obtain space on the server to save the file to be printed.
〖63〗-Delete files waiting to be printed.
〖64〗-The specified network name is no longer available.
〖65〗-Network access denied.
〖66〗-Wrong network resource type.
〖67〗-The network name cannot be found.
〖68〗-Exceeded the name limit of the local computer network card.
〖69〗-Network BIOS session limit exceeded.
〖70〗-The remote server has been paused or is in the process of starting.
〖71〗-No more connections can be made to this remote computer because the computer's connection limit has been reached.
〖72〗-The specified printer or disk device has been suspended.
〖80〗-The file exists.
〖82〗-The directory or file cannot be created.
〖83〗-INT 24 failed.
〖84〗 - Unable to obtain storage space to handle this request.
〖85〗-The local device name is already in use.
〖86〗-The specified network password is incorrect.
〖87〗-Parameter error.
〖88〗-A write error occurred on the network.
〖89〗-The system cannot start another process at this time.
〖100〗 - Unable to create another system semaphore.
〖101〗-Another process owns an exclusive semaphore.
〖102〗-The signal light has been set and cannot be turned off.
〖103〗-The signal light can no longer be set.
〖104〗 - Unable to request exclusive semaphore on interrupt.
〖105〗-The previous ownership of this semaphore has ended.
〖107〗 - The program stopped because a replacement floppy disk was not inserted.
〖108〗-The disk is in use or locked by another process.
〖109〗-The pipeline has ended.
〖110〗-The system cannot open the specified device or file.
〖111〗-The file name is too long.
〖112〗-Insufficient disk space.
〖113〗-The identification of the internal file can no longer be obtained.
〖114〗-The identification of the target internal file is incorrect.
〖117〗-The IOCTL call made by the application is wrong.
〖118〗-The switching parameter value written in the verification is wrong.
〖119〗-The system does not support the requested command.
〖120〗-This function is only supported by this system.
〖121〗-The signal light timeout time has expired.
〖122〗 - The data area passed to the system call is too small.
〖123〗-The file name, directory name, or volume label syntax is incorrect.
〖124〗-System call level error.
〖125〗-The disk has no volume label.
〖126〗-The specified module cannot be found.
〖127〗-The specified program cannot be found.
〖128〗-There are no waiting child processes.
〖130〗 - An attempt was made to use the file handle of an open disk partition for operations other than raw disk I/O.
〖131〗-Attempt to move the file pointer before the beginning of the file.
〖132〗 - The file pointer cannot be set on the specified device or file.
〖133〗 - The JOIN or SUBST command cannot be used on a drive that contains a previously joined drive.
〖134〗 - An attempt was made to use a JOIN or SUBST command on a drive that has been merged.
〖135〗 - An attempt was made to use a JOIN or SUBST command on a drive that has been merged.
〖136〗-The system attempted to unjoin a drive that was not merged.
〖137〗 - The system attempted to unsubstitute a drive that was not substituted.
〖138〗 - The system attempted to merge the drive into a directory on the merged drive.
〖139〗 - The system attempted to replace the drive with a directory on the replacement drive.
〖140〗 - The system attempted to merge the drive to a directory on an alternative drive.
〖141〗 - The system attempted to replace the drive with a directory on the merged drive.
〖142〗-The system cannot run JOIN or SUBST at this time.
〖143〗 - The system cannot merge or replace drives to a directory on the same drive.
〖144〗-The directory is not a subdirectory under the root directory.
〖145〗-The directory is not empty.
〖146〗-The specified path is already used in an alternative.
〖147〗 - Insufficient resources to process this command.
〖148〗-The specified path cannot be used at this time.
〖149〗 - An attempt was made to merge or replace a drive to a drive whose directory was the target of a previous replacement.
〖150〗-System trace information is not specified in the CONFIG.SYS file, or tracing is not allowed.
〖151〗-The number of semaphore events specified for DosMuxSemWait is incorrect.
〖152〗-DosMuxSemWait is not operable. Too many traffic lights have been set.
〖153〗-DosMuxSemWait manifest error.
〖154〗-The entered volume label exceeds the length limit of the target file system
〖155〗-Cannot create another thread.
〖156〗-The receiving process has rejected this signal.
〖157〗-The segment has been abandoned and cannot be locked.
〖158〗-The segment has been unlocked.
〖159〗-The address of the thread ID is wrong.
〖160〗 - The parameter string passed to DosExecPgm is wrong.
〖161〗-The specified path is invalid.
〖162〗-The signal has been suspended.
〖164〗 - Unable to create more threads in the system.
〖167〗-The file area cannot be locked.
〖170〗-The requested resource is in use.
〖173〗 - A request to provide a cancellation zone for locking is not obvious.
〖174〗-The file system does not support minimum unit changes of lock type.
〖180〗-The system detected the wrong segment number.
〖183〗-The file cannot be created when the file already exists.
〖186〗-Wrong flag passed.
〖187〗-The specified system semaphore name cannot be found.
〖196〗-The operating system cannot run this application.
〖197〗-The operating system is not currently configured to run this application.
〖199〗-The operating system cannot run this application.
〖200〗-The code segment cannot be greater than or equal to 64K.
〖203〗-The operating system cannot find the environment option that was entered.
〖205〗-The process in the command subtree has no signal handler.
〖206〗-The file name or extension is too long.
〖207〗-The 2nd ring stack is occupied.
〖208〗-The file name wildcard character * or ? was not entered correctly, or too many file name wildcard characters were specified.
〖209〗-The signal being sent is wrong.
〖210〗-The signal handler cannot be set.
〖212〗 - The segment is locked and cannot be reallocated.
〖214〗-There are too many dynamic link modules connected to the program or dynamic link module.
〖215〗-LoadModule cannot be nested.
〖230〗-The pipeline status is invalid.
〖231〗-All pipeline instances are in use.
〖232〗-The pipeline is being closed.
〖233〗-There is no process on the other end of the pipe.
〖234〗 - More data available.
〖240〗-Cancel session.
〖254〗-The specified extended attribute name is invalid.
〖255〗-The extended attributes are inconsistent.
〖258〗-The waiting operation is expired.
〖259〗-No more data available.
〖266〗-The copy function cannot be used.
〖267〗-The directory name is invalid.
〖275〗 - Extended attributes are not applicable in buffers.
〖276〗-The extended attributes file installed on the file system is damaged.
〖277〗-The extended attribute table file is full.
〖278〗-The specified extended attribute handle is invalid.
〖282〗-The mounted file system does not support extended attributes.
〖288〗 - An attempt was made to release a multi-user terminal executable that is not owned by the calling party.
〖298〗-Too many requests to the semaphore.
〖299〗-Only a partial ReadProcessMemoty or WriteProcessMemory request was completed.
〖300〗-The operation lock request was rejected.
〖301〗 - The system received an invalid operation lock confirmation.
〖487〗 - An attempt was made to access an invalid address.
〖534〗-The arithmetic result exceeds 32 digits.
〖535〗-There is a process at the other end of the pipe.
〖536〗-Waiting to open the process at the other end of the pipe.
〖994〗-Access to extended attributes is denied.
〖995〗 - The I/O operation was abandoned due to thread exit or application request.
〖996〗 - Overlapping I/O event is not in signal state.
〖997〗-An overlapped I/O operation is in progress.
〖998〗-Invalid memory allocation access.
〖999〗-Error running in-page operation.
〖1001〗-Recursion too deep; stack overflow.
〖1002〗 - The window cannot operate on the sent message.
〖1003〗-This function cannot be completed.
〖1004〗-Invalid flag.
〖1005〗-This volume does not contain a recognized file system. Please make sure that all requested file system drivers are loaded and that the volume is not corrupted.
〖1006〗-The volume on which the file resides has been externally altered, so the open file is no longer valid.
〖1007〗 - The requested operation cannot be run in full screen mode.
〖1008〗 - An attempt was made to reference a token that does not exist.
〖1009〗-The configuration registry database is damaged.
〖1010〗-The configuration registry key is invalid.
〖1011〗-The configuration registry key cannot be opened.
〖1012〗-The configuration registry key cannot be read.
〖1013〗-The configuration registry key cannot be written.
〖1014〗-A file in the registry database must be restored using logging or alternative replication. The restore completed successfully.
〖1015〗-The registry is damaged. One of the file structures containing registry data is damaged, or the system's file memory image is damaged, or the file cannot be recovered because replacement copies or logs are missing or damaged.
〖1016〗-Recovery of I/O operations initiated by the registry failed. The registry cannot read, write, or clear any of the files containing the registry system image.
〖1017〗-The system attempted to load or restore a file to the registry, but the specified file was not in the registry file format.
〖1018〗 - An attempt was made to run an illegal operation on a registry key marked for deletion.
〖1019〗-The system cannot configure the requested space in the registry log.
〖1020〗 - A symbolic link cannot be created in a registry key that already has a subkey or value.
〖1021〗 - Unable to create stable child under volatile parent.
〖1022〗 - Notification that the change request is being completed and the information has not been returned to the caller's buffer. The current caller must enumerate the file to find changes.
〖1051〗 - Stop control has been sent to a service that is dependent on other running services.
〖1052〗-The requested control is not valid for this service
〖1053〗-The service did not respond to the start or control request in a timely manner.
〖1054〗-Unable to create a thread for this service.
〖1055〗-Lock the service database.
〖1056〗-The instance of the service is already running.
〖1057〗-The account name is invalid or does not exist, or the password is invalid for the specified account name.
〖1058〗 - The service cannot be started, either because it is disabled or the device associated with it is not started.
〖1059〗-Cyclic service dependency is specified.
〖1060〗-The specified service does not exist as an installed service.
〖1061〗-The service cannot accept control information at this time.
〖1062〗-The service is not started.
〖1063〗-The service process cannot connect to the service controller.
〖1064〗 - An exception occurred in the service while processing the control request.
〖1065〗-The specified database does not exist.
〖1066〗-The service has returned a specific service error code.
〖1067〗-The process terminated unexpectedly.
〖1068〗-The dependent service or group cannot be started.
〖1069〗-The service cannot be started due to failed login.
〖1070〗-After starting, the service stays in startup pause state.
〖1071〗-The specified service database lock is invalid.
〖1072〗-The specified service has been marked for deletion.
〖1073〗-The specified service already exists.
〖1074〗-The system is currently running with the latest valid configuration.
〖1075〗-The dependent service does not exist or has been marked for deletion.
〖1076〗 - Use current boot as the last valid control setting has been accepted.
〖1077〗-No attempt has been made to boot the service since the last startup.
〖1078〗-The name is already used as a service name or service display name.
〖1079〗 - The account for this service is different from the account of other services running on the same process.
〖1080〗-The failure operation can only be set for Win32 services, not for drivers.
〖1081〗 - This service runs the same process as the Service Control Manager. Therefore, if the service handler terminates unexpectedly, the service control manager cannot take any action.
〖1082〗-This service has not yet set up a recovery procedure.
〖1083〗-The service configured to run in this executable program cannot execute the service.
〖1100〗-The actual end of the tape has been reached.
〖1101〗-Tape access has reached the file mark.
〖1102〗-The beginning of the tape or disk partition has been reached.
〖1103〗-Tape access has reached the end of a set of files.
〖1104〗-There is no more data on the tape.
〖1105〗-The tape cannot be partitioned.
〖1106〗 - When accessing a new tape for a multi-volume partition, the current block size is incorrect.
〖1107〗-When loading the tape, the partition information was not found.
〖1108〗-The media eject function cannot be locked.
〖1109〗-The media cannot be unmounted.
〖1110〗-The media in the drive may have been changed.
〖1111〗-Reset the I/O bus.
〖1112〗 - There is no media in the drive.
〖1113〗 - There is no character to which this Unicode character can be mapped in the multibyte target code page.
〖1114〗-Dynamic link library (DLL) initialization routine failed.
〖1115〗-System shutdown is in progress.
〖1116〗-The system shutdown cannot be interrupted because there is no shutdown process in progress.
〖1117〗-This request cannot be run because of an I/O device error.
〖1118〗-No serial device was initialized successfully. The serial driver will be uninstalled.
〖1119〗 - A device that is sharing an interrupt request (IRQ) with another device cannot be opened. At least one other device using this IRQ is open.
〖1120〗-The serial I/O operation has been completed by writing to another serial port. (IOCTL_SERIAL_XOFF_COUNTER has reached zero.)
〖1121〗-The serial I/O operation is completed because the timeout period has expired. (IOCTL_SERIAL_XOFF_COUNTER has not reached zero.)
〖1122〗-The ID address tag cannot be found on the floppy disk.
〖1123〗-The floppy disk sector ID character field does not match the floppy disk controller track address.
〖1124〗-The floppy disk controller reported an error that the floppy disk driver cannot recognize.
〖1125〗-The floppy disk controller returned inconsistent results in its registers.
〖1126〗-When accessing the hard disk, the recalibration operation failed and retry still failed.
〖1127〗-When accessing the hard disk, the disk operation failed and retry still failed.
〖1128〗-When accessing the hard disk, the disk controller must still be reset even if it fails.
〖1129〗-The end of the tape has been reached.
〖1130〗-The server has insufficient storage space to process this command.
〖1131〗-Potential deadlock condition detected.
〖1132〗 - The specified base address or file offset is not properly aligned.
〖1140〗 - An attempt to change the system power state was vetoed by another application or driver.
〖1141〗-System BIOS failed to attempt to change the system power supply status.
〖1142〗-An attempt was made to create more links on a file than the system allows.
〖1150〗-Specifies that the program requires a newer version of Windows.
〖1151〗-The specified program is not a Windows or MS-DOS program.
〖1152〗-Only one instance of the specified program can be started.
〖1153〗-This specified program is for older Windows versions.
〖1154〗-One of the library files required to execute this application is damaged.
〖1155〗-No application is associated with the specified file for this operation.
〖1156〗-An error occurred while sending instructions to the application.
〖1157〗-One of the library files required to execute the application cannot be found.
〖1158〗-The current program has used all handles allowed by the system to the Window Manager object.
〖1159〗 - Messages can only be used with synchronous operations.
〖1160〗-The indicated source element has no media.
〖1161〗-The indicated target element already contains media.
〖1162〗-The specified element does not exist.
〖1163〗-The indicated element is part of a storage resource that is not shown.
〖1164〗-The display device needs to be reinitialized because of a hardware error.
〖1165〗 - The device shows that it needs to be cleared before attempting further operations.
〖1166〗-The device shows that its door is still open.
〖1167〗-The device is not connected.
〖1168〗-Element not found.
〖1169〗-There is no entry in the index that matches the specified entry.
〖1170〗-The specified property set does not exist on the object.
〖1171〗 - The point passed to GetMouseMovePoints is not in the buffer.
〖1172〗-The tracking (workstation) service is not running.
〖1173〗-Volume ID not found.
〖1175〗-The file to be replaced cannot be deleted.
〖1176〗-The replacement file cannot be moved to the file to be replaced. Files to be replaced retain their original names.
〖1177〗-The replacement file cannot be moved to the file to be replaced. The file to be replaced has been renamed to the backup name.
〖1178〗-The volume change record was deleted.
〖1179〗-The volume change logging service is not active.
〖1180〗-A file was found, but it may not be the correct file.
〖1181〗-The log entry was deleted from the log.
〖1200〗-The specified device name is invalid.
〖1201〗-The device is not currently connected, but it is a logged connection.
〖1202〗-An attempt was made to log a device that has been previously logged.
〖1203〗-No network provider accepts the specified network path.
〖1204〗-The specified network provider name is invalid.
〖1205〗-The network connection profile cannot be opened.
〖1206〗-The network connection configuration file is damaged.
〖1207〗 - Empty vector cannot be enumerated.
〖1208〗-An extension error occurred.
〖1209〗-The specified group name format is invalid.
〖1210〗-The specified computer name format is invalid.
〖1211〗-The specified event name format is invalid.
〖1212〗-The specified domain name format is invalid.
〖1213〗-The specified service name format is invalid.
〖1214〗-The specified network name format is invalid.
〖1215〗-The specified share name format is invalid.
〖1216〗-The specified password format is invalid.
〖1217〗-The specified message name format is invalid.
〖1218〗-The specified message target format is invalid.
〖1219〗-The provided credentials conflict with an existing credential set.
〖1220〗 - An attempt was made to create a session to the network server, but too many sessions have been created for the server.
〖1221〗-The workgroup or domain name is already in use by another computer on the network.
〖1222〗-The network is not connected or started.
〖1223〗-The operation has been canceled by the user.
〖1224〗 - The requested operation cannot be performed on a file opened using a user-mapped area.
〖1225〗-The remote system refused the network connection.
〖1226〗-The network connection has been closed appropriately.
〖1227〗 - The network transport endpoint already has an address associated with it.
〖1228〗 - The address is still not associated with the network endpoint.
〖1229〗-An attempt was made to operate on a non-existent network connection.
〖1230〗-An invalid operation was attempted on an active network connection.
〖1231〗-The network location cannot be accessed. For information about network troubleshooting, see Windows Help.
〖1232〗-The network location cannot be accessed. For information about network troubleshooting, see Windows Help.
〖1233〗-The network location cannot be accessed. For information about network troubleshooting, see Windows Help.
〖1234〗 - No services are operating on the target network endpoint on the remote system.
〖1235〗-The request was terminated.
〖1236〗-The network connection was terminated by the local system.
〖1237〗-The operation cannot be completed. Should try again.
〖1238〗 - The server cannot be connected because the maximum number of simultaneous connections for this account has been reached.
〖1239〗-An attempt was made to log in during a time when this account was not authorized.
〖1240〗-This account is not authorized to log in from this workstation.
〖1241〗-The requested operation cannot use this network address.
〖1242〗-The server has been registered.
〖1243〗-The specified service does not exist.
〖1244〗-The requested operation cannot be performed because the user has not been authenticated.
〖1245〗-Because the user has not logged in to the network, the required operation cannot be performed. The specified service does not exist.
〖1246〗-Continuing work.
〖1247〗 - An initial operation was attempted, but initialization was completed.
〖1248〗-No more local devices.
〖1249〗-The specified site does not exist.
〖1250〗-A domain controller with the specified name already exists.
〖1251〗-This operation is only supported when connected to the server.
〖1252〗-The Group Policy Framework should call the extension even if there are no changes.
〖1253〗-The specified user does not have a valid profile.
〖1254〗-Microsoft Small Business Server does not support this operation.
〖1300〗 - Not all of the referenced privileges are assigned to the calling party.
〖1301〗-Some mapping between account names and security identities is not complete.
〖1302〗 - There is no system quota limit specifically set for this account.
〖1303〗-No encryption key available. A known encryption key was returned.
〖1304〗-The password is too complex and cannot be converted to the LAN Manager password. The LAN Manager password returned is an empty string.
〖1305〗-Revision level unknown.
〖1306〗-Indicates that the two revision levels are incompatible.
〖1307〗 - This security ID cannot be assigned as the owner of this object.
〖1308〗 - This security identity cannot be assigned as the primary group of the object.
〖1309〗-A thread that is not currently impersonating a client is trying to operate an impersonation token.
〖1310〗 - The group may not be disabled.
〖1311〗 - There is currently no login server available to service the login request.
〖1312〗-The specified login session does not exist. May have been terminated.
〖1313〗-The specified privilege does not exist.
〖1314〗-The client does not have the required privileges.
〖1315〗-The name provided is not the correct form of account name.
〖1316〗-The specified user already exists.
〖1317〗-The specified user does not exist.
〖1318〗-The specified group already exists.
〖1319〗-The specified group does not exist.
〖1320〗-The specified user account is already a member of the specified group, or the specified group cannot be deleted because the group contains members.
〖1321〗-The specified user account is not a member of the specified group account.
〖1322〗 - The last remaining system administration account cannot be disabled or deleted.
〖1323〗-Unable to update password. The value provided as the current password is incorrect.
〖1324〗-Unable to update password. The value supplied to the new password contains a value that is not allowed in passwords.
〖1325〗-Unable to update password. The value provided for the new password does not meet the length, complexity, or history requirements for the character domain.
〖1326〗-Login failed: Unknown username or wrong password.
〖1327〗-Login failed: User account restriction.
〖1328〗-Login failed: Account login time limit violated.
〖1329〗-Login failed: The user is not allowed to log on to this computer.
〖1330〗-Login failed: The specified account password has expired.
〖1331〗-Login failed: Disable current account.
〖1332〗-No mapping between account name and security ID is completed.
〖1333〗 - Too many local user identifiers (LUIDs) were requested at one time.
〖1334〗 - No more local user identifiers (LUIDs) available.
〖1335〗 - The secondary authorization portion of the security ID is invalid for this particular usage.
〖1336〗-The access control list (ACL) structure is invalid.
〖1337〗-The security ID structure is invalid.
〖1338〗-The security descriptor structure is invalid.
〖1340〗-Unable to create an inherent access control list (ACL) or access control entry (ACE).
〖1341〗 - The server is currently disabled.
〖1342〗-The server is currently enabled.
〖1343〗-The value provided to the identification number authority is an invalid value.
〖1344〗-No more memory available to update security information.
〖1345〗-The specified attribute is invalid or incompatible with the attributes of the entire group.
〖1346〗 - The specified simulation level is invalid, or the supplied simulation level is invalid.
〖1347〗-Unable to open anonymous level security token.
〖1348〗-The requested authentication information category is invalid.
〖1349〗 - The token's type is inappropriate for the method it is trying to use.
〖1350〗 - Security operations cannot be run on objects that are not associated with security.
〖1351〗-Failed to read configuration information from the domain controller, either because the machine is unavailable or access is denied.
〖1352〗 - The Security Account Manager (SAM) or Local Security Authority (LSA) server is in an error state running security operations.
〖1353〗 - The domain is in an error state for running security operations.
〖1354〗 - This operation is only possible for the domain's primary domain controller.
〖1355〗-The specified domain does not exist or cannot be contacted.
〖1356〗-The specified domain already exists.
〖1357〗-An attempt was made to exceed the limit on the number of domains per server.
〖1358〗 - The requested operation cannot be completed due to a severe media failure or data structure corruption on the disk.
〖1359〗-An internal error occurred.
〖1360〗 - A generic access type is contained in an access mask that has been mapped to a non-generic type.
〖1361〗-The security descriptor is not in the correct format (absolute or autorelative).
〖1362〗-The request operation is limited to the login process. The calling process is not registered as a login process.
〖1363〗-Cannot start a new session using an identity that is already in use.
〖1364〗-Unknown specified authentication packet.
〖1365〗 - The login session is not in a state consistent with the requested operation.
〖1366〗-The login session ID is already in use.
〖1367〗 - The login request contains an invalid login type value.
〖1368〗 - Unable to simulate via a named pipe before reading data using the pipe.
〖1369〗-The transaction status of the registry subtree is inconsistent with the request status.
〖1370〗-The security database is internally damaged.
〖1371〗 - This operation cannot be run on the built-in account.
〖1372〗 - This operation cannot be run on the built-in special group.
〖1373〗 - This operation cannot be run on the built-in special user.
〖1374〗 - The user cannot be removed from the group because the current group is the user's primary group.
〖1375〗 - The token has been used as the primary token.
〖1376〗-The specified local group does not exist.
〖1377〗-The specified account name is not a member of the local group.
〖1378〗-The specified account name is already a member of the local group.
〖1379〗-The specified local group already exists.
〖1380〗 - Login failed: The user was not granted the requested login type on this computer.
〖1381〗-The maximum number of secrets that can be saved in a single system has been exceeded.
〖1382〗-The length of the secret exceeds the maximum allowed length.
〖1383〗-The local security authority database contains internal inconsistencies.
〖1384〗 - During the login attempt, the user's security context accumulated too many security identities.
〖1385〗 - Login failed: The user was not granted the requested login type on this computer.
〖1386〗-A cross-encrypted password is required when changing user passwords.
〖1387〗 - The member cannot be added to or removed from the local group because the member does not exist.
〖1388〗 - The new member cannot be added to the local group because the member has the wrong account type.
〖1389〗-Too many security IDs have been specified.
〖1390〗 - A cross-encrypted password is required when changing this user's password.
〖1391〗-Indicates that the ACL does not contain any inheritable components.
〖1392〗-The file or directory is damaged and cannot be read.
〖1393〗-The disk structure is damaged and cannot be read.
〖1394〗-There is no user session entry for the specified login session.
〖1395〗-The service being accessed has a target authorization limit on the number of connections. At this time, it is no longer possible to connect because the upper limit of the number of acceptable connections has been reached.
〖1396〗-Login failed: The target account name is incorrect.
〖1397〗-Mutual authentication failed. The server's domain controller password has expired.
〖1398〗-There is a time difference between the client and the server.
〖1400〗-Invalid window handle.
〖1401〗-Invalid menu handle.
〖1402〗-Invalid cursor handle.
〖1403〗-Invalid accelerator table handle.
〖1404〗-Invalid hook handle.
〖1405〗-Invalid multiple window position structure handle.
〖1406〗-The top-level subwindow cannot be created.
〖1407〗-Window category not found.
〖1408〗 - Invalid window; it belongs to another thread.
〖1409〗-The hotkey has been registered.
〖1410〗-The category already exists.
〖1411〗-Category does not exist.
〖1412〗-The category still has open windows.
〖1413〗-Invalid index.
〖1414〗-Invalid icon handle.
〖1415〗-Use special DIALOG window words.
〖1416〗-The list box identifier cannot be found.
〖1417〗 - Wildcard character not found.
〖1418〗-The thread does not have an open clipboard.
〖1419〗-No hotkey registered.
〖1420〗-The window is not a legal dialog window.
〖1421〗-The control ID cannot be found.
〖1422〗-Because there is no editing control, the message of the combo box is invalid.
〖1423〗-The window is not a combo box.
〖1424〗-The height must be less than 256.
〖1425〗 - Invalid device context (DC) handle.
〖1426〗 - Invalid hook program type.
〖1427〗-Invalid hook program.
〖1428〗 - Unable to set up non-native hooks without a module handle.
〖1429〗-This hook-up program can only be set as a whole.
〖1430〗-Journal Hook program has been installed.
〖1431〗-Hook has not been installed.
〖1432〗-Invalid message for single selection list box.
〖1433〗-LB_SETCOUNT is sent to a non-passive list box.
〖1434〗-This list box does not support tab key width.
〖1435〗 - An object created by another thread cannot be destroyed.
〖1436〗-The subwindow has no menu.
〖1437〗-The window has no system menu.
〖1438〗-Invalid message dialog style.
〖1439〗 - Invalid system-wide (SPI_*) parameters.
〖1440〗-The screen is locked.
〖1441〗 - All handles to windows in a multiple window position structure must have the same parent.
〖1442〗-The window is not a child window.
〖1443〗-Invalid GW_* command.
〖1444〗-Invalid thread ID.
〖1445〗 - Unable to process messages in non-Multiple Document Interface (MDI) windows.
〖1446〗-The pop-up menu has been activated.
〖1447〗-The window has no scroll bars.
〖1448〗-The scroll bar range cannot be larger than MAXLONG.
〖1449〗 - The window cannot be displayed or deleted in the specified manner.
〖1450〗-Insufficient system resources to complete the requested service.
〖1451〗-Insufficient system resources to complete the requested service.
〖1452〗-Insufficient system resources to complete the requested service.
〖1453〗-Insufficient quota to complete the requested service.
〖1454〗-Insufficient quota to complete the requested service.
〖1455〗-The page file is too small to complete the operation.
〖1456〗-Menu item not found.
〖1457〗-The keyboard layout handle is invalid.
〖1458〗-Hook type is not allowed.
〖1459〗-This operation requires an interactive window workstation.
〖1460〗-The operation returned because the timeout period has expired.
〖1461〗-Invalid monitor handle.
〖1500〗-The event log file is damaged.
〖1501〗-The event log file cannot be opened and the event log service is not started.
〖1502〗-The event log file is full.
〖1503〗 - The event log file has changed between reads.
〖1601〗-The Windows Installation service cannot be accessed. Please contact technical support personnel to confirm whether the Windows installation service is registered correctly.
〖1602〗-The user canceled the installation.
〖1603〗-A serious error occurred during installation
〖1604〗-The installation has been hung and is not completed.
〖1605〗-This operation is only valid for the currently installed product.
〖1606〗-Function ID is not registered.
〖1607〗-The component ID is not registered.
〖1608〗-Unknown attribute.
〖1609〗-The handle is in an incorrect state.
〖1610〗-The configuration data of this product is corrupted. Please contact technical support.
〖1611〗-The component qualifier does not exist.
〖1612〗-The installation source for this product cannot be used. Please verify that the source exists and is accessible.
〖1613〗-The Windows Installer service cannot install this installation package. You must install the Windows Service Park, which contains a new version of Windows Installer Services.
〖1614〗-The product was not uninstalled.
〖1615〗-SQL query syntax is incorrect or not supported.
〖1616〗-The record character field does not exist.
〖1617〗-The device has been deleted.
〖1618〗-Another installation operation is in progress. Please complete that operation before continuing with this installation operation.
〖1619〗-The installation package could not be opened. Please verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package.
〖1620〗-The installation package could not be opened. Please contact the application vendor to verify whether this is a valid Windows Installer package.
〖1621〗-There is an error when starting the Windows Installation Service user interface. Please contact technical support.
〖1622〗-Error opening the installation log file. Please verify that the specified log file location exists and can be written to.
〖1623〗-The language of the installation package is not supported by the system.
〖1624〗-Error when applying transformation. Please verify that the specified transform path is valid.
〖1625〗-System policy prohibits this installation. Please contact your system administrator.
〖1626〗-The function cannot be executed.
〖1627〗-During execution, there was a problem with the function.
〖1628〗 - An invalid or unknown table was specified.
〖1629〗-The data type provided is incorrect.
〖1630〗-This type of data is not supported.
〖1631〗-The Windows Installation service failed to start. Please contact technical support.
〖1632〗 -The temporary folder is full or unavailable. Please verify whether the temporary folder exists and whether it can be written.
〖1633〗 -The type of processor does not support the installation program package. Please contact the product supplier.
〖1634〗 -Capons are not used on this computer.
〖1635〗 -In the unable to open the repair program package. Please verify whether the repair program package exists and can be accessed; or contact the application supplier to verify whether this is a repair program package for Windows installation services.
〖1636〗 -In the unable to open the repair program package. Please contact the application supplier to verify whether this is a repair program package for Windows installation services.
〖1637〗 -Windows installation service cannot handle this inserting program package. You must install a new version of Windows Service Pack containing Windows installation services.
〖1638〗 -In the installation of this product. The installation of this version cannot continue. To configure or delete the existing version of this product, use the "Add/Delete Program" on the "Control Panel".
〖1639〗 -Awrite command line parameters. For detailed order help, please check the SDK of Windows installation services.
[1640]-During the terminal service remote session, only the administrator has the permissions of adding, deleting or configured server software. If you want to install or configure software on the server, contact the network administrator.
〖1641〗-The required operation has successfully concluded. To take effect, the system must be restarted.
〖1642〗 -Windows installation service cannot install the upgrade repair program, because the upgraded program may be lost or the upgrade repair program may update a different version of this program. Please confirm that the upgraded program is correct on your computer and your upgrade repair program is correct.
〖1700〗 -Stial binding is invalid.
〖1701〗-The type of binding handle is incorrect.
〖1702〗 -The binding handle is invalid.
〖1703〗 -The RPC protocol sequence is not supported.
〖1704〗 -RPC protocol sequence is invalid.
〖1705〗 -Stop string universal uniform logo (UUID) is invalid.
〖1706〗 -The end-of-point format is invalid.
〖1707〗 -The network address is invalid.
〖1708〗 -It cannot find the terminal.
〖1709〗 -The timeout is invalid.
〖1710〗 -In universal universal logo (UUID).
〖1711〗 -The universal universal logo (UUID) is registered.
〖1712〗 -The type universal unique logo (UUID) is registered.
〖1713〗 -RPC server is listening.
〖1714〗 -We registered any protocol sequence.
〖1715〗 -RPC server is not listened.
〖1716〗 -In unknown manager type.
〖1717〗 -In unknown interface.
〖1718〗-No link.
〖1719〗 -Weless order of agreement.
〖1720〗 -Instage to create an end point.
〖1721〗 -The resources are insufficient and cannot be completed.
〖1722〗 -RPC server is not available.
〖1723〗 -RPC server is too busy to complete this operation.
〖1724〗 -The network option is invalid.
〖1725〗 -In this thread, the remote process call is not used.
〖1726〗 -The remote process call fails.
〖1727〗 -The remote process call fails and does not run.
〖1728〗 -The remote process call (RPC) protocol errors.
〖1730〗 -RPC server does not support transmission syntax.
〖1732〗 -The universal unique identification (UUID) type is not supported.
〖1733〗 -The mark is invalid.
〖1734〗 -Addling boundary is invalid.
〖1735〗 -Links does not include the project name.
〖1736〗 -Name grammar is invalid.
〖1737〗 -The name grammar is not supported.
〖1739〗 -The network address that can be used to create a unique identifier (UUID).
〖1740〗-The ending is a backup.
〖1741〗-The type of unknown verification.
〖1742〗-The maximum number of calls is too small.
〖1743〗 -The string is too long.
〖1744〗 -In the order of the RPC protocol.
〖1745〗 -Endon number exceeds the range.
〖1746〗-Binding does not include any verification information.
〖1747〗 -In unknown verification service.
〖1748〗 -In unknown verification level.
〖1749〗 -S safety context is invalid.
〖1750〗 -On unknown authorization service.
〖1751〗 -The project is invalid.
〖1752〗 -The server ending cannot be operated.
〖1753〗 -The no available terminal point in the ending table of the end point.
〖1754〗 -Weless exported interface.
〖1755〗 -The project name is incomplete.
〖1756〗 -The version option is invalid.
〖1757〗-No other members.
〖1758〗 -Weless content does not export.
〖1759〗 -The interface was not found.
〖1760〗 -The project exists.
〖1761〗 -In the project.
〖1762〗 -The unusable name service.
〖1763〗 -The network address family is invalid.
〖1764〗 -The operations that do not support request.
〖1765〗 -The unavailable security context to allow simulation.
〖1766〗 -In internal error occurred in the remote process call (RPC).
〖1767〗 -RPC server tries to remove the integer with zero.
〖1768〗 -An address error occurred in the RPC server.
〖1769〗 -The floating-point operation on the RPC server is divided into zero.
〖1770〗 -The floating point overflow occurred on the RPC server.
〖1771〗 -The floating point overflow occurred on the RPC server.
〖1772〗 -The RPC server list that can be used for automatic handle is used up.
〖1773〗 -In cannot open the character translation table file.
〖1774〗 -The files containing the character translation table are less than 512 bytes.
〖1775〗 -In the remote process call, pass the empty context handle from the customer to the host.
〖1777〗 -In long-range process calls, the context sentence has been changed.
〖1778〗 -The binding handle passed to the remote process call does not match.
〖1779〗 -The undertind the handle of the remote process cannot be obtained.
〖1780〗 -Prive the empty reference pointer to the undertaking body.
〖1781〗 -The list of values exceeds the range.
〖1782〗 -Expected number is too small.
〖1783〗 -The undertake body receives bad data.
〖1784〗 -The user buffer provided to the request operation is invalid.
〖1785〗 -D disk media cannot be recognized. It may not be formatted.
〖1786〗 -The workstation has no trust in confidence.
〖1787〗 -The security database on the server does not have a computer account for the trust relationship of this workstation.
〖1788〗 -The trust relationship between the main domain and the trust domain failed.
〖1789〗 -The trust relationship between this workstation and the main domain failed.
〖1790〗 -The online login failed.
〖1791〗 -The remote process call of this thread is in progress.
〖1792〗 -The tried to log in, but the online login service is not started.
〖1793〗 -The user account expires.
〖1794〗 -The forwarding procedure has been occupied and cannot be uninstalled.
〖1795〗-The specified printer driver has been installed.
〖1796〗-The specified port is unknown.
〖1797〗 -In unknown printer driver.
〖1798〗 -In unknown printer processor.
〖1799〗-The specified separation page file is invalid.
〖1800〗-The specified priority is invalid.
〖1801〗 -The printer name is invalid.
〖1802〗 -In printers already exist.
〖1803〗-The printer command is invalid.
〖1804〗-The specified data type is invalid.
〖1805〗-The specified environment is invalid.
〖1806〗 -ward without more binding.
〖1807〗-The account used is a domain trust account. Please use your global user account or local user account to visit this server.
〖1808〗-The account used is a computer account. Use your global user account or local user account to visit this server.
〖1809〗 -A used accounts are the server trust account. Use your global user account or local user account to visit this server.
〖1810〗 -The name or security identification (SID) of the specified domain is inconsistent with the trust information of the domain.
〖1811〗 -The server cannot be uninstalled during use.
〖1812〗-The specified image file does not contain resource areas.
〖1813〗 -In the type of resource type specified in the image file.
〖1814〗 -In the name of the resource specified in the image file.
〖1815〗 -It cannot find the resource language logo specified in the image file.
〖1816〗 -The quota is insufficient and cannot handle this command.
〖1817〗 -Wei registered interface.
〖1818〗 -The remote process call is canceled.
〖1819〗-The binding handle does not include the information of all needs.
〖1820〗 -The communication failure during the remote process calls.
〖1821〗 -The verification level that does not support requests.
〖1822〗 -Wei registered any name.
〖1823〗-The specified error is not an effective Windows RPC error code.
〖1824〗 -The UUID that has only been effective on this computer.
〖1825〗 -The unique error of a safety package occurs.
〖1826〗 -The thread is not canceled.
〖1827〗 -Fatflement/decoding handle operation.
〖1828〗 -The version of the serialized packaging is not compatible.
〖1829〗 -RPC's version of the body is not compatible.
〖1830〗 -RPC pipeline object is invalid or damaged.
〖1831〗 -In the ineffective operation on RPC pipeline objects.
〖1832〗 -Exposed RPC pipeline version.
〖1898〗 -In found members of the group.
〖1899〗 -The unable to create an end-of-point mapping table database item.
〖1900〗 -The universal universal identification (UUID) is Nil UUID.
〖1901〗-The specified time is invalid.
〖1902〗-The specified format name is invalid.
〖1903〗-The size of the specified format is invalid.
〖1904〗-The specified printer handle is waiting
〖1905〗 -The deleted printer.
〖1906〗-The status of the printer is invalid.
〖1907 第一-before the first login, the user password must be changed.
〖1908〗 -In the domain controller of this domain.
〖1909〗 -Added account is currently locked and may not be logged in.
〖1910〗 -to did not find the specified exporter of this object
〖1911〗 -to did not find the specified object.
〖1912〗 -to did not find the specified object parser.
〖1913〗-Some data to be sent are still in the request buffer.
〖1914〗 -Colid the handle of the invalid asynchronous long-range process.
〖1915〗 -The asynchronous RPC call handle of this operation is incorrect.
〖1916〗 -RPC pipeline object has been closed.
〖1917〗 -The all the pipelines before the RPC call is completed.
〖1918〗-No other available data comes from the RPC pipeline.
〖1919〗 -This machine has no site name.
〖1920〗 -The system cannot access this file.
〖1921〗 -The system cannot recognize file names.
〖1922〗 -The project is not the type of it.
〖1923〗 -The UUID of all objects cannot be exported to the specified item.
〖1924〗 -The interface cannot be directed to the specified item.
〖1925〗 -In the specified configuration file item cannot be added.
〖1926〗 -In cannot be added to the specified configuration file element.
〖1927〗 -In cannot delete the specified configuration file element.
〖1928〗 -The group elements cannot be added.
〖1929〗 -The group element cannot be deleted.
〖2000〗 -Infoyal pixel format.
〖2001〗-The specified driver is invalid.
〖2002〗 -When style or category attributes are invalid for this.
〖2003〗 -Added operation of the request.
〖2004〗 -This does not support request transformation operations.
〖2005〗 -Stop operation that does not support requests.
〖2010〗-The specified color management module is invalid.
〖2011〗-The color file configuration formulated is invalid.
〖2012〗 -In the specified logo.
〖2013〗 -In the required logo.
〖2014〗-The specified logo already exists.
〖2015〗-The specified color file configuration is not related to any device.
〖2016〗 -In the configuration of the specified color file
〖2017〗-The specified color space is invalid.
〖2018〗 -It image color management is not started.
[2019]-There is an error in deleting the color transmission.
〖2020〗 -The specified color transmission is invalid.
〖2021〗 -The change of transformation does not match the color space of the bitmap.
〖2022〗 -Then the specified naming color index does not exist in the configuration file.
〖2102〗 -It did not install the workstation driver.
〖2103〗 -The server cannot be located.
〖2104〗 -In internal errors, the network cannot access the shared memory segment.
〖2105〗 -The network resources are insufficient.
〖2106〗 -S workstation does not support this operation.
〖2107〗 -The device is not connected.
〖2108〗 -The network connection is successful, but it is necessary to prompt that users enter a password different from the original specified.
〖2114〗 -to did not start the server service.
〖2115〗 -The queue empty.
〖2116〗 -The device or directory does not exist.
〖2117〗 -The cannot perform this operation on the redirect resources.
〖2118〗 -The name has been shared.
〖2119〗 -The server cannot currently provide the required resources.
〖2121〗 -In additional required items exceed the allowable upper limit.
〖2122〗 -Pyingcomer only supports two users who operate at the same time.
〖2123〗 -API returns the buffer too small.
〖2127〗 -Sarm API error.
〖2131〗 -Eyrals when open or read the configuration file.
〖2136〗 -A general network error occurred.
〖2137〗 -The status of the workstation service is inconsistent. Before restarting the workstation service, first restart the computer.
〖2138〗 -The workstation service is not started.
〖2139〗 -In required information.
〖2140〗 -Windows 2000 internal errors occur.
〖2141〗 -The server does not set transaction processing.
〖2142〗 -The remote server does not support request APIs.
〖2143〗 -The event name is invalid.
〖2144〗 -The computer name on the Internet. Please rename it after renaming.
〖2146〗 -The configuration information cannot find the specified component.
〖2147〗 -Coard the specified parameter in the configuration information.
〖2149〗 -The command line in the configuration file is too long.
〖2150〗 -In printer does not exist.
〖2151〗 -The print operation does not exist.
〖2152〗 -In the printer target cannot be found.
〖2153〗-The printer target already exists.
〖2154〗-The printer queue already exists.
〖2155〗 -It cannot add other printers.
〖2156〗 -It cannot add other printing operations.
〖2157〗 -In other printer targets.
〖2158〗 -The printer target is in idle and does not accept control operations.
〖2159〗 -This "Printer target request" contains invalid control functions.
〖2160〗 -The print processing program does not respond.
〖2161〗 -The background processing program is not running.
〖2162〗 -In the current status of the target and cannot perform this operation.
〖2163〗 -In the current situation of the printer queue, this operation cannot be performed.
〖2164〗 -In the current situation of printing operations, this operation cannot be performed.
〖2165〗-cannot allocate memory for the background processing program.
〖2166〗 -The device driver does not exist.
〖2167〗 -The print processing program does not support this data type.
〖2168〗 -It did not install the printing process.
〖2180〗 -Lock the service database.
〖2181〗 -The service table is full.
〖2182〗 -The service of request has been started.
〖2183〗 -This service does not respond to control.
〖2184〗-The service has not yet started.
〖2185〗-The service name is invalid.
〖2186〗 -An service without response control function.
〖2187〗 -Awidity control is busy.
〖2188〗 -The configuration file contains invalid service program names.
〖2189〗 -In the current situation cannot control the service.
〖2190〗 -Add service abnormal termination.
〖2191〗 -The "suspension" or "stop" operation that cannot accept the request.
〖2192〗 -Awrite control "Planning Procedure" cannot find the service name in the "plan form".
〖2193〗 -In the unable to read the service control plan program pipeline.
〖2194〗 -In the unable to create a new service thread.
〖2200〗 -The workstation has logged in to the LAN.
〖2201〗 -The workstation is not logged in to the LAN.
〖2202〗-The designated user name is invalid.
〖2203〗 -The password parameters are invalid.
〖2204〗 -The login processor does not add message aliases.
〖2205〗 -The login processor does not add message aliases.
〖2206〗 -The logout processor does not delete message aliases.
〖2207〗 -Luton the processor without deleting message aliases.
〖2209〗 -Stouled online login.
〖2210〗 -Card the center login server conflict.
〖2211〗 -The server does not set the correct user path.
〖2212〗 -Wly error when loading or running a login script.
〖2214〗 -It did not specify the login server. The login status of the computer is a stand-alone operation.
〖2215〗 -The login server cannot be found.
〖2216〗 -The computer already has a login domain.
〖2217〗 -The login server cannot verify the login.
〖2219〗 -S safety database cannot be found.
〖2220〗 -The group name cannot be found.
〖2221〗 -The username cannot be found.
〖2222〗 -The resource name cannot be found.
〖2223〗 -The group already exists.
〖2224〗-Account already exists.
〖2225〗 -The list of resource use rights has existed.
〖2226〗 -This can only be performed on the main domain controller of the domain.
〖2227〗 -S safety database is not started.
〖2228〗 -The name in the user account database is too much.
〖2229〗 -D disk I/O failed.
〖2230〗 -The restrictions on 64 projects per resource.
〖2231〗 -Wepen users must not be deleted.
〖2232〗 -In the upper directory cannot be found.
〖2233〗 -In the unable to add to the high-speed cache section of the safety database session.
〖2234〗-This operation cannot be performed on this special group.
〖2235〗 -The user account database session high-speed cache did not record this user.
〖2236〗 -The users have belonged to this group.
〖2237〗 -The users do not belong to this group.
〖2238〗 -The user account is not defined.
〖2239〗 -The user account has expired.
〖2240〗 -The user must not log in to the network from this workstation.
〖2241〗 -The users are not allowed to log in to the network at this time.
〖2242〗 -The password of this user has expired.
〖2243〗 -The password of this user cannot be changed.
〖2244〗 -In this password cannot be used now.
〖2245〗 -The password does not meet the needs of the password strategy. Check the needs of the minimum password length, password complexity and the history of password history.
〖2246〗 -The password of this user has only been used recently, and it cannot be changed now.
〖2247〗 -A safety database has been damaged.
〖2248〗 -whelmed network/local security database that is not required to update this copy.
〖2249〗 -The database copy of this copy is outdated; please process the data synchronously.
〖2250〗 -The connection of this network does not exist.
〖2251〗 -The this asg_type is invalid.
〖2252〗 -This device is currently being shared.
〖2270〗 -The computer name cannot be added as a message aliases. There may already be this name on the Internet.
〖2271〗 -The messenger service has been launched.
〖2272〗 -The messenger service fails.
〖2273〗 -The news of the news on the Internet cannot be found.
〖2274〗 -The news of this news has been reposted.
〖2275〗 -This has already added this message aliases, but it is still forwarded.
〖2276〗 -The news of this news has existed locally.
〖2277〗 -In addition to the number of message aliases has exceeded the upper limit.
〖2278〗 -The computer name cannot be deleted.
〖2279〗 -In the message cannot be reposted back to the same workstation.
〖2280〗 -Lore message processor error.
〖2281〗-The message has been sent out, but the recipient has suspended the service.
〖2282〗-The message has been sent out, but it has not been received.
〖2283〗 -In information alias are currently in use. Please try again for a while.
〖2284〗 -The messenger service has not yet started.
〖2285〗 -The name is not on the local computer.
〖2286〗 -In the information on the Internet cannot be found.
〖2287〗 -The news table of the remote communication station is full.
〖2288〗 -The news of this alias is not in the forwarding.
〖2289〗 -The news of the broadcast is intercepted.
〖2294〗 -Expressing the device name.
〖2295〗 -writing error.
〖2297〗 -Enoma on the Internet repeats.
〖2298〗 -This name will be deleted later.
〖2299〗 -Welemia message aliases from all networks.
〖2300〗-This operation cannot be executed on a computer using a variety of networks.
〖2310〗 -This resource does not exist.
〖2311〗 -The device is not shared.
〖2312〗 -As a session with this computer name does not exist.
〖2314〗 -The files that are not opened in this recognition number.
〖2315〗 -The execution of remote management command failed.
〖2316〗 -The open temporary file failure.
〖2317〗-The data returned from the remote management command has been cut into 64K.
〖2318〗 -This equipment cannot be shared at the same time as background processing resources and non-background processing resources.
〖2319〗 -The information in the server list may not be correct
〖2320〗 -The computer is not in activity in this domain
〖2321〗 -In before deleting sharing, you need to delete the sharing from the distributed file system.
〖2331〗 -The cannot perform this operation in this device
〖2332〗 -This device cannot be shared.
〖2333〗 -This equipment is not opened.
〖2334〗 -The list of this device is invalid.
〖2335〗 -The queue priority is invalid.
〖2337〗 -The communication equipment without any shared.
〖2338〗-The specified queue does not exist.
〖2340〗 -The list of this device is invalid.
〖2341〗-The device requested is invalid.
〖2342〗 -The background processing program is using this device.
〖2343〗 -This equipment has been used as a communication device.
〖2351〗 -The computer name is invalid.
〖2354〗 -The specified string and prefix are too long.
〖2356〗 -The components of this path are invalid.
〖2357〗-cannot judge the input type.
〖2362〗-The type buffer is not large enough.
〖2370〗 -The configuration file must not exceed 64K.
〖2371〗 -The initial offset crossing the border.
〖2372〗 -The system cannot delete the current connection of network resources.
〖2373〗 -The system cannot analyze the command line in this file.
〖2374〗 -Wly an error when loading the configuration file. /
〖2375〗 -Weo when preserving the configuration file, the configuration file is only preserved.
〖2378〗 -This files have changed between two times before and after.
〖2380〗 -The resource path cannot be a directory.
〖2381〗 -The resource path is invalid.
〖2382〗 -The target path is invalid.
〖2383〗 -The source path and target path are divided into different servers.
〖2385〗 -The Run server requested is now suspended.
〖2389〗 -Ma and error occurred during communication with the RUN server.
〖2391〗 -Wly errors when starting the background processing.
〖2392〗 -In the shared resource you connected.
〖2400〗 -LAN adapter number is invalid.
〖2401〗 -This connection of this network is opened or requests to hang.
〖2402〗-The connection in use still exists.
〖2403〗 -This sharing or password is invalid.
〖2404〗 -The device is being used by the activity process and cannot be disconnected.
〖2405〗 -This driver number has been used locally.
〖2430〗 -In specified customers are already registered in the specified event.
〖2431〗 -An alert watch is full.
〖2432〗-The name of the alarm issued is invalid or does not exist.
〖2433〗 -Enicist receiver is invalid.
〖2434〗 -The user's login time is no longer legal. So the user has been deleted with the server with the server.
〖2440〗 -The record number of no request in the log file.
〖2450〗 -The user account database is not configured correctly.
〖2451〗 -When the Netlogon service is running, this operation is not allowed.
〖2452〗 -This operation cannot be performed on the final management account.
〖2453〗 -In the domain controller of this domain.
〖2454〗 -The login information of this user cannot be set.
〖2455〗 -Netlogon service has not yet started.
〖2456〗 -It cannot be added to the user account database.
〖2457〗 -The clock of this server is inconsistent with the clock of the main domain controller.
〖2458〗 -Stochrios are not matched.
〖2460〗 -The server recognition code does not specify a effective server.
〖2461〗 -An session logo does not specify effective sessions.
〖2462〗 -The connection recognition code does not specify an effective connection.
〖2463〗 -It cannot add other items in the server table.
〖2464〗 -The server has reached the upper limit of the number of support sessions.
〖2465〗 -The server has reached the upper limit of the number of supported connections.
〖2466〗 -The files opened by the server reaches the upper limit and cannot open more files.
〖2467〗 -This server does not register the replacement server.
〖2470〗-Please use a low-level API (remote management protocol).
〖2480〗 -UPS service cannot access the UPS driver.
〖2481〗 -UPS service settings error.
〖2482〗 -UPS service cannot access the specified communication port (Commm Port).
〖2483〗 -UPS display line interrupt or battery is insufficient, and the service is not started.
〖2484〗 -UPS service cannot perform the operation of the system shutdown.
〖2500〗-The program below returns an MS-DOS error code:
〖2501〗-The procedure below requires more memory:
〖2502〗 -The MS-DOS function of the following program calls:
〖2503〗 -The workstation cannot be started.
〖2504〗 -The files below have been damaged.
〖2505〗 -The no guidance program is not specified in the start-defined file.
〖2506〗 -Netbios Return Error: NCB and SMB data dial storage.
〖2507〗 -D disk I/O error.
〖2508〗 -It cannot replace the image parameters.
〖2509〗 -The image parameters across the disk sector range are too many.
〖2510〗 -It is not an image generated from the/s formatted MS-DOS floppy disk.
〖2511〗 -In the remote start later.
〖2512〗 -In cannot call the remote startup server.
〖2513〗 -In cannot be connected to the remote startup server.
〖2514〗 -In the unable to open the image file on the remote start-up server.
〖2515〗 -In the connection to the remote start-up server ...
〖2516〗 -In the connection to the remote start-up server ...
〖2517〗 -The remote start-up service has stopped, please detect the error record file and find out the reason for the error.
〖2518〗 -The long-range start failure, please check the error log file and find out the reason for the error.
〖2519〗 -The second remote startup resource connection is not allowed.
〖2550〗 -The browse service is set to MaintainServerlist = NO.
〖2610〗-Because there is no network card to start with this service, the service cannot be started.
〖2611〗 -In because the startup information in the registry is incorrect, the service cannot be activated.
〖2612〗 -It cannot start the service because its database cannot be found or damaged.
〖2613〗-Because the resource shared by RPLFiles cannot be found, the service cannot be started.
〖2614〗-Because the RPLUSER group cannot be found, the service cannot be started.
〖2615〗 -The cannot enumerate service records.
〖2616〗 -The workstation record information has been damaged.
〖2617〗 -Stimeter record cannot be found.
〖2618〗 -It other workstations are using this workstation name.
〖2619〗 -The configuration file record is damaged.
〖2620〗 -The configuration file record cannot be found.
〖2621〗 -The other configuration files are using this name.
〖2622〗-Many workstations are using this configuration file.
〖2623〗 -The configuration record has been damaged.
〖2624〗 -The configuration record cannot be found.
〖2625〗 -The adapter recognition record has been damaged.
〖2626〗 -Error errors internal service.
〖2627〗 -A supplier recognition records have been damaged.
〖2628〗 -The start-up record is damaged.
〖2629〗 -In the user account records of this workstation.
〖2630〗 -RPluser local group cannot find it.
〖2631〗 -In can't find the startup record.
〖2632〗-The selected configuration file is not compatible with this workstation.
〖2633〗 -In other workstations are using the selected network card.
〖2634〗-Some configuration files are using this configuration.
〖2635〗 -Intable workstations, configuration files or configurations are using this startup block.
〖2636〗-The service cannot make the backup of remote startup database.
〖2637〗 -In can't find the adapter record.
〖2638〗 -In cannot find the supplier's record.
〖2639〗 -In other supplier records are using this supplier name.
〖2640〗 -In other startup area records are using the startup name or supplier identification record.
〖2641〗 -The other configuration is using this configuration name.
〖2660〗 -In internal database maintained by DFS service, it has been damaged
〖2661〗 -On a record in the internal database has been damaged
〖2662〗 -The input item path does not match the roll path
〖2663〗 -Defente
〖2664〗-The designated server sharing has been shared in DFS
〖2665〗-The server sharing displayed does not support the displayed DFS volumes displayed
〖2666〗 -This operation is invalid on non-leaf rolls.
〖2667〗 -This operation is invalid on the leaf roll.
〖2668〗 -This operation is unclear because there are multiple servers in this volume.
〖2669〗-cannot create a connection point
〖2670〗 -The server is not recognized by DFS
〖2671〗-The specified heavy name target path is invalid.
〖2672〗 -Dimben DFS Roll off line
〖2673〗-The designated server does not serve for this
〖2674〗 -The ring circuit in the DFS name is detected
〖2675〗 -The does not support the operation on the server-based DFS
〖2676〗 -This of this volume has been supported by the designated server
〖2677〗 -In the last server sharing support of this volume cannot be deleted
〖2678〗 -Inter-DFS volume does not support the operation
〖2679〗 -The internal state of DFS service has become inconsistent
〖2680〗 -DFS service has been installed on the designated server
〖2681〗 -The coordinated DFS data is the same
〖2682〗-cannot delete the DFS root directory volume-if necessary, please uninstall DFS
〖2683〗 -The shared sub-directory or parent directory already exists in a DFS
〖2690〗 -DFS internal error
〖2691〗 -This machine has been added to the domain.
〖2692〗 -This machine has not yet joined the domain.
〖2693〗-This machine is a domain controller and cannot be exited from the domain.
〖2694〗 -The target domain controller does not support the machine account created in OU.
〖2695〗-The specified working group name is invalid
〖2696〗-The default language used on the specified computer name is not compatible with the default language used on the domain controller.
〖2697〗 -In can't find the designated computer account.
〖2999〗 -This is the last error in the NERR range.
〖3000〗 -In the specified unknown printing monitor.
〖3001〗-The specified printer driver is currently in use.
〖3002〗 -In cannot find a buffer file.
〖3003〗 -Startdocprinter is not sent.
〖3004〗 -ADDJOB call is not sent.
〖3005〗-The specified print processor has been installed.
〖3006〗-The specified print monitor has been installed.
〖3007〗 -This printer monitor does not have the required functions.
〖3008〗 -This printer is in use.
〖3009〗 -This requests when the printer is arranged into a queue is not allowed.
〖3010〗 -The request operation is successful. It will not take effect until the change of the system will not take effect.
〖3011〗 -The request operation is successful. It will not take effect until the change of the service will not take effect.
〖3012〗 -In can't find a printer.
〖3023〗 -The shutdown command file specified by the user, its configuration is problematic. However, the UPS service has been launched.
〖3029〗-Because the user account database (Net.ACC) cannot be found or damaged, and there is no backup database that can be used, the local security mechanism cannot be started. The system is not safe!
〖3037〗-@i *login hours
〖3039〗 -The restrictions on copying of the file in a directory.
〖3040〗 -The deeper limit of the directory tree that has exceeded the copy of the copy.
〖3046〗-cannot log in. The user is currently logged in, and the parameter Tryuser is set to NO.
〖3052〗 -We command line or configuration file does not provide necessary parameters.
〖3054〗 -In cannot meet the requests of resources.
〖3055〗 -The system configuration is problematic.
〖3056〗 -The system errors.
〖3057〗 -The internal consistency error.
〖3058〗 -The options for configuration files or command lines are not clear.
〖3059〗 -The parameters of the configuration file or command line are repeated.
〖3060〗 -Ad the service without response control, and the DoskillProc function has stopped the service.
〖3061〗 -Error the error occurred when running the service program.
〖3062〗 -It cannot start secondary services.
〖3064〗 -The file problem.
〖3070〗 -Mine
〖3071〗 -D disk space
〖3072〗-thread
〖3073〗-Process
〖3074〗 -S safety failure.
〖3075〗 -LAN Manager root directory is incorrect or unable to find.
〖3076〗 -Onfilers are not installed.
〖3077〗 -The server is not started.
〖3078〗 -The server cannot access the user account database (Net.ACC).
〖3079〗-The files installed in the Lanman tree are not compatible.
〖3080〗 -LANMAN/LOGS directory is invalid.
〖3081〗-The specified domain cannot be used.
〖3082〗 -In another computer is using this computer as a message aliases.
〖3083〗 -Chimonally announce the failure of the server name.
〖3084〗 -The user account database is not configured correctly.
〖3085〗 -The server does not run user-level security functions.
〖3087〗 -The workstation settings are incorrect.
〖3088〗 -Chat your error log file to understand the details.
〖3089〗 -It cannot be written to this file.
〖3090〗 -Addpak file is damaged. Please delete Lanman/netprog/addpak.ser and re -apply all AddPak.
〖3091〗-Because it does not run cache.exe, the LM386 server cannot be started.
〖3092〗 -The account of this computer cannot be found in the security database.
〖3093〗 -This computer is not a member of the Servers group.
〖3094〗 -Servers group is not in the local security database.
〖3095〗 -The Windows NT computer is set to members of a group, not members of the domain. There is no need to run the Netlogon service under this configuration.
〖3096〗 -In the Windows NT domain controller of this domain.
〖3098〗 -Add service cannot be verified with the main domain controller.
〖3099〗 -The safety database file creation date or serial number problem.
〖3100〗 -In because the network software is wrong, the operation cannot be performed.
〖3102〗 -This service cannot lock the segment of the network control block (NCB) for a long time. The error code is related data.
〖3103〗 -This service cannot lock the long-term lock in the network control block (NCB) segment. The error code is related data.
〖3106〗 -Well the unexpected network control block (NCB). NCB is related data.
〖3107〗 -The network is not started.
〖3108〗 -DOSDEVIOCTL or DOSFSCTL calls inNetwksta.Sys failed. The displayed data is the following format: DWORD value means calling the CS: IP Word error code Word IOCTL or FSCTL number of IOCTL or FSCTL
〖3111〗 -In accident Netbios errors. The error code is related data.
〖3112〗 -The server message block (SMB) received. SMB is related data.
〖3114〗-Because the buffer is overflowing, the items in part of the error log file are lost.
〖310〗 -The initialization parameters of the amount of resource dosage outside the network buffer are set, so there are too much memory.
〖3121〗 -The server cannot increase the size of the memory segment.
〖3124〗 -The server fails. Three CHDEV parameters must be zero or at the same time.
〖3129〗 -The server cannot update the AT program file. The file is damaged.
〖3130〗 -Error error occurred when the server calls NetMakelMFILENAME. The error code is related data.
〖3132〗 -It cannot lock the server buffer for a long time. Please check the available space of the exchange disk, and then restart the system to start the server.
〖3140〗 -On stop service due to multiple continuous network control block (NCB) errors. The last bad NCB appeared in the form of original data.
〖3141〗-Because the data segment shared by the message server is locked, the message server has stopped running.
〖3151〗-Because VIO calls an error, the display message cannot be popped up. The error code is related data.
〖3152〗 -The server message block (SMB) received. SMB is related data.
〖3160〗 -The workstation information section is greater than 64K. The size is as follows (format in DWORD value):
〖3161〗 -The workstation cannot get the computer name number.
〖3162〗-工作站无法初始化Async NetBIOS 线程。错误码就是相关数据。
〖3163〗-工作站无法打开最前面的共享段。错误码就是相关数据。
〖3164〗-工作站主机表已满。
〖3165〗-收到的邮筒服务器消息块(SMB) 有问题，SMB 就是相关数据。
〖3166〗-工作站启动用户帐户数据库时出错。错误码就是相关数据。
〖3167〗-工作站响应SSI 重新验证请求时出错。函数码及错误码就是相关数据。
〖3174〗-服务器无法读取AT 计划文件。
〖3175〗-服务器发现错误的AT 计划记录。
〖3176〗-服务器找不到AT 计划文件，所以创建一个计划文件。
〖3185〗-因为用户帐户数据库(NET.ACC) 找不到或损坏，而且也没有可用的备份数据库，所以不能启动本地安全机制。系统不安全！
〖3204〗-服务器无法创建线程。CONFIG.SYS 中的THREADS 参数必须加大。
〖3213〗-已经超过一个目录中文件的副本复制的限制。
〖3214〗-已经超过副本复制的目录树深度限制。
〖3215〗-邮筒中收到的消息无法识别。
〖3217〗-无法登录。用户当前已经登录，同时参数TRYUSER设置为NO。
〖3230〗-检测到服务器的电源中断。
〖3231〗-UPS 服务已经关掉服务器。
〖3232〗-UPS 服务没有完成执行用户指定的关机命令文件。
〖3233〗-无法打开UPS 驱动程序。错误码就是相关数据。
〖3234〗-电源已经恢复。
〖3235〗-用户指定的关机命令文件有问题。
〖3256〗-该项服务的动态链接库发生无法修复的错误。
〖3257〗-系统返回意外的错误码。错误码就是相关数据。
〖3258〗-容错错误日志文件- LANROOT/LOGS/FT.LOG超过64K。
〖3259〗-容错错误日志文件- LANROOT/LOGS/FT.LOG，在被打开时就已设置更新进度位，这表示上次使用错误日志时，系统死机。
〖3301〗-Remote IPC
〖3302〗-Remote Admin
〖3303〗-Logon server share
〖3304〗-网络出错。
〖3400〗-内存不足，无法启动工作站服务。
〖3401〗-读取LAMAN.INI 文件的NETWORKS 项目出错。
〖3404〗-LAMAN.INI 文件中的NETWORKS 项目太多。
〖3408〗-程序无法用在此操作系统。
〖3409〗-已经安装转发程序。
〖3411〗-安装NETWKSTA.SYS 时出错。请按ENTER 继续。
〖3412〗-求解程序链接问题。
〖3419〗-您已经打开文件或设备，强制断开会造成数据丢失。
〖3420〗-内部用的默认共享
〖3421〗-信使服务
〖3500〗-命令成功完成。
〖3501〗-使用的选项无效。
〖3503〗-命令包含无效的参数个数。
〖3504〗-命令运行完毕，但发生一个或多个错误。
〖3505〗-使用的选项数值不正确。
〖3510〗-命令使用了冲突的选项。
〖3512〗-软件需要新版的操作系统。
〖3513〗-数据多于Windows 2000 所能够返回的。
〖3515〗-此命令只能用在Windows 2000 域控制器。
〖3516〗-这个指令不能用于一个Windows 2000 域控制器。
〖3520〗-已经启动以下Windows 2000 服务:
〖3525〗-停止工作站服务也会同时停止服务器服务。
〖3526〗-工作站有打开的文件。
〖3533〗-服务正在启动或停止中，请稍候片刻后再试一次。
〖3534〗-服务没有报告任何错误。
〖3535〗-正在控制设备时出错。
〖3660〗-这些工作站在这台服务器上有会话:
〖3661〗-这些工作站有会话打开了此台服务器上的文件:
〖3666〗-消息别名已经转发出去。
〖3670〗-您有以下的远程连接:
〖3671〗-继续运行会取消连接。
〖3676〗-会记录新的网络连接。
〖3677〗-不记录新的网络连接。
〖3678〗-保存配置文件时出错，原先记录的网络连接状态没有更改。
〖3679〗-读取配置文件时出错。
〖3682〗-没有启动任何网络服务。
〖3683〗-清单是空的。
〖3689〗-工作站服务已经在运行中，Windows 2000 会忽略工作站的命令选项。
〖3694〗-在打印作业正在后台处理到队列时，无法删除共享的队列。
〖3710〗-打开帮助文件时出错。
〖3711〗-帮助文件是空的。
〖3712〗-帮助文件已经损坏。
〖3714〗-这是专为那些安装旧版软件的系统提供的操作。
〖3716〗-设备类型未知。
〖3717〗-日志文件已经损坏。
〖3718〗-程序文件名后必须以.EXE 结束。
〖3719〗-找不到匹配的共享，因此没有删除。
〖3720〗-用户记录中的“单位/星期” 的值不正确。
〖3725〗-删除共享时出错。
〖3726〗-用户名无效。
〖3727〗-密码无效。
〖3728〗-密码不匹配。
〖3729〗-永久连接没有完全还原。
〖3730〗-计算机名或域名错误。
〖3732〗-无法设置该资源的默认权限。
〖3734〗-没有输入正确的密码。
〖3735〗-没有输入正确的名称。
〖3736〗-该资源无法共享。
〖3737〗-权限字符串包含无效的权限。
〖3738〗-您只能在打印机或通讯设备上执行这项操作。
〖3743〗-服务器没有设置远程管理的功能。
〖3752〗-这台服务器上没有用户的会话。
〖3756〗-响应无效。
〖3757〗-没有提供有效的响应。
〖3758〗-提供的目标清单与打印机队列目标清单不匹配。
〖3761〗-指定的时间范围中结束的时间比开始的时间早。
〖3764〗-提供的时间不是整点。
〖3765〗-12 与24 小时格式不能混用。
〖3767〗-提供的日期格式无效。
〖3768〗-提供的日期范围无效。
〖3769〗-提供的时间范围无效。
〖3770〗-NET USER 的参数无效。请检查最短的密码长度和/或提供参数。
〖3771〗-ENABLESCRIPT 的值必须是YES。
〖3773〗-提供的国家(地区)代码无效。
〖3774〗-用户已经创建成功，但是无法添加到USERS 本地组中。
〖3775〗-提供的用户上下文无效。
〖3777〗-文件发送功能已不再支持。
〖3778〗-您可能没有指定ADMIN$ 及IPC$ 共享的路径。
〖3784〗-只有磁盘共享可以标记为可以缓存。
〖3802〗-此计划日期无效。
〖3803〗-LANMAN 根目录无法使用。
〖3804〗-SCHED.LOG 文件无法打开。
〖3805〗-服务器服务尚未启动。
〖3806〗-AT 作业标识不存在。
〖3807〗-AT 计划文件已损坏。
〖3808〗-因为AT 计划文件发生问题，所以无法运行删除操作。
〖3809〗-命令行不得超过259 个字符。
〖3810〗-因为磁盘已满，所以AT 计划文件无法更新。
〖3812〗-AT 计划文件无效。请删除此文件并创建新的文件。
〖3813〗-AT 计划文件已经删除。
〖3814〗 -此命令的语法是:AT [id] [/DELETE]AT 时间[/EVERY:日期| /NEXT:日期] 命令AT 命令会在以后的指定日期及时间，安排程序在服务器上运行。它也会显示安排运行的程序及命令的清单。您可以将日期指定为M、T、W、Th、F、Sa、Su 或1-31 的格式。您可以将时间指定为HH:MM的二十四小时格式。
〖3815〗-AT 命令已经超时。 Please try again later.
〖3816〗-用户帐户的密码使用最短期限不得大于密码最长使用期限。
〖3817〗-指定的数值与安装下层软件的服务器不兼容。请指定较小的值。
〖3901〗-****
〖3902〗-**** 意外到达消息的结尾****
〖3905〗-请按ESC 退出
〖3906〗-...
〖3912〗-找不到时间服务器。
〖3915〗-无法判断用户的主目录。
〖3916〗-没有指定用户的主目录。
〖3920〗-已经没有可用的驱动器号。
〖3936〗-这台计算机目前没有配置成使用一个指定的SNTP 服务器。
〖3953〗-语法错误。
〖3960〗-指定的文件号码无效。
〖3961〗-指定的打印作业号码无效。
〖3963〗-指定的用户或组帐户找不到。
〖3965〗-已添加用户，但NetWare 的文件和打印服务无法启用。
〖3966〗-没有安装NetWare 的文件和打印服务。
〖3967〗-无法为NetWare 的文件和打印服务设置用户属性。
〖3969〗-NetWare 兼容登录
〖4000〗-WINS 在处理命令时遇到错误。
〖4001〗-本地的WINS 不能删除。
〖4002〗-文件导入操作失败。
〖4003〗-备份操作失败。是否先前已作过完整备份?
〖4004〗-备份操作失败。请检查您备份数据库的目录。
〖4005〗-WINS 数据库中没有这个名称。
〖4006〗-不允许复制一个尚未配置的伙伴。
〖4100〗-DHCP 客户获得一个在网上已被使用的IP 地址。 直到DHCP 客户可以获得新的地址前，本地接口将被禁用。
〖4200〗-无法识别传来的GUID 是否为有效的WMI 数据提供程序。
〖4201〗-无法识别传来的实例名是否为有效的WMI 数据提供程序。
〖4202〗-无法识别传来的数据项目标识符是否为有效的WMI 数据提供程序。
〖4203〗-无法完成WMI 请求，应该重试一次。
〖4204〗-找不到WMI 数据提供程序。
〖4205〗-WMI 数据提供程序引用到一个未注册的实例组。
〖4206〗-WMI 数据块或事件通知已启用。
〖4207〗-WMI 数据块不再可用。
〖4208〗-WMI 数据服务无法使用。
〖4209〗-WMI 数据提供程序无法完成要求。
〖4210〗-WMI MOF 信息无效。
〖4211〗-WMI 注册信息无效。
〖4212〗-WMI 数据块或事件通知已禁用。
〖4213〗-WMI 数据项目或数据块为只读。
〖4214〗-WMI 数据项目或数据块不能更改。
〖4300〗-媒体标识符没有表示一个有效的媒体。
〖4301〗-库标识符没有表示一个有效的库。
〖4302〗-媒体缓冲池标识符没有表示一个有效的媒体缓冲池。
〖4303〗-驱动器和媒体不兼容或位于不同的库中。
〖4304〗-媒体目前在脱机库中，您必须联机才能运行这个操作。
〖4305〗-操作无法在脱机库中运行。
〖4306〗-库、驱动器或媒体缓冲池是空的。
〖4307〗-库、磁盘或媒体缓冲池必须是空的，才能运行这个操作。
〖4308〗-在这个媒体缓冲池或库中目前没有可用的媒体。
〖4309〗-这个操作所需的资源已禁用。
〖4310〗-媒体标识符没有表示一个有效的清洗器。
〖4311〗-无法清洗驱动器或不支持清洗。
〖4312〗-对象标识符没有表示一个有效的对象。
〖4313〗-无法读取或写入数据库。
〖4314〗-数据库已满。
〖4315〗-媒体与设备或媒体缓冲池不兼容。
〖4316〗-这个操作所需的资源不存在。
〖4317〗-操作标识符不正确。
〖4318〗-媒体未被安装，或未就绪。
〖4319〗-设备未就绪。
〖4320〗-操作员或系统管理员拒绝了请求。
〖4321〗-驱动器标识符不代表一个有效的驱动器。
〖4322〗-程序库已满。没有可使用的插槽。
〖4323〗-传输程序不能访问媒体。
〖4324〗-无法将媒体加载到驱动器中。
〖4325〗-无法检索有关驱动器的状态。
〖4326〗-无法检索有关插槽的状态。
〖4327〗-无法检索传输的状态。
〖4328〗-因为传输已在使用中，所以无法使用。
〖4329〗-无法打开或关闭弹入/弹出端口。
〖4330〗-因为媒体在驱动器中，无法将其弹出。
〖4331〗-清洗器插槽已被保留。
〖4332〗-没有保留清洗器插槽。
〖4333〗-清洗器墨盒已进行了最大次数的驱动器清洗。
〖4334〗-意外媒体标识号。
〖4335〗-在这个组或源中最后剩下的项目不能被删除。
〖4336〗-提供的消息超过了这个参数所允许的最大尺寸。
〖4337〗-该卷含有系统和页面文件。
〖4338〗-由于库中至少有一个驱动器可以支持该媒体类型，不能从库中删除媒体类型。
〖4339〗-由于没有可以使用的已被启动的驱动器，无法将该脱机媒体装入这个系统。
〖4340〗-(Y/N) [Y]
〖4341〗-(Y/N) [N]
〖4342〗-错误
〖4343〗-OK
〖4344〗-Y
〖4345〗-N
〖4346〗-任何
〖4347〗-A
〖4348〗-P
〖4349〗-(找不到)
〖4350〗-远程存储服务无法撤回文件。
〖4351〗-远程存储服务此时不可操作。
〖4352〗-远程存储服务遇到一个媒体错误。
〖4354〗-请键入密码:
〖4358〗-请键入用户的密码:
〖4359〗-请键入共享资源的密码:
〖4360〗-请键入您的密码:
〖4361〗-请再键入一次密码以便确认:
〖4362〗-请键入用户的旧密码:
〖4363〗-请键入用户的新密码:
〖4364〗-请键入您的新密码:
〖4365〗-请键入复制器服务密码:
〖4368〗-请键入您的用户名:
〖4372〗-打印作业详细信息
〖4378〗-控制下列正在运行的服务:
〖4379〗-统计数据可用于正在运行的下列服务:
〖4381〗-此命令的语法是:
〖4382〗-此命令的选项是:
〖4383〗-请键入主域控制器的名称:
〖4385〗-Sunday
〖4386〗-Monday
〖4387〗-Tuesday
〖4388〗-Wednesday
〖4389〗-Thursday
〖4390〗-此文件或目录不是一个重解析点。
〖4391〗-重解析点的属性不能被设置，因为它与已有的属性冲突。
〖4392〗-在重解析点缓冲区中的数据无效。
〖4393〗-在重解析点缓冲区中的标签无效。
〖4394〗-请求中指定的标签和重解析点中的不匹配。
〖4395〗-W
〖4396〗-Th
〖4397〗-F
〖4398〗-S
〖4399〗-Sa
〖4401〗-组名
〖4402〗-注释
〖4403〗-成员
〖4406〗-别名
〖4407〗-注释
〖4408〗-成员
〖4411〗-用户名
〖4412〗-全名
〖4413〗-注释
〖4414〗-用户的注释
〖4415〗-参数
〖4416〗-国家(地区)代码
〖4417〗-权限等级
〖4418〗-操作员权限
〖4419〗-帐户启用
〖4420〗-帐户到期
〖4421〗-上次设置密码
〖4422〗-密码到期
〖4423〗-密码可更改
〖4424〗-允许的工作站
〖4425〗-磁盘空间上限
〖4426〗-无限制
〖4427〗-本地组会员
〖4428〗-域控制器
〖4429〗-登录脚本
〖4430〗-上次登录
〖4431〗-全局组成员
〖4432〗-可允许的登录小时数
〖4433〗-全部
〖4434〗-无
〖4436〗-主目录
〖4437〗-需要密码
〖4438〗-用户可以更改密码
〖4439〗-用户配置文件
〖4440〗-已锁定
〖4450〗-计算机名
〖4451〗-用户名
〖4452〗-软件版本
〖4453〗-工作站活动在
〖4454〗-Windows NT 根目录
〖4455〗-工作站域
〖4456〗-登录域
〖4457〗-其它域
〖4458〗-COM 打开超时(秒)
〖4459〗-COM 发送计数(字节)
〖4460〗-COM 发送超时(毫秒)
〖4461〗-DOS 会话打印超时(秒)
〖4462〗-错误日志文件大小上限(K)
〖4463〗-高速缓存上限(K)
〖4464〗-网络缓冲区数
〖4465〗-字符缓冲区数
〖4466〗-域缓冲区大小
〖4467〗-字符缓冲区大小
〖4468〗-计算机全名
〖4469〗-工作站域DNS 名称
〖4470〗-Windows 2000
〖4481〗-服务器名称
〖4482〗-服务器注释
〖4483〗-发送管理警报到
〖4484〗-软件版本
〖4485〗-对等服务器
〖4486〗-Windows NT
〖4487〗-服务器等级
〖4488〗-Windows NT Server
〖4489〗-服务器正运行于
〖4492〗-服务器已隐藏
〖4500〗-零备份存储在这个卷上不可用。
〖4506〗-登录的用户数量上限
〖4507〗-同时可并存的管理员数量上限
〖4508〗-资源共享数量上限
〖4509〗-资源连接数量上限
〖4510〗-服务器打开的文件数量上限
〖4511〗-每个会话打开的文件数量上限
〖4512〗-文件锁定数量上限
〖4520〗-空闲的会话时间(分)
〖4526〗-共享等级
〖4527〗-用户等级
〖4530〗-未限制的服务器
〖4570〗-强制用户在时间到期之后多久必须注销?:
〖4571〗-多少次密码不正确后锁住帐户?:
〖4572〗-密码最短使用期限(天):
〖4573〗-密码最长使用期限(天):
〖4574〗-密码长度下限:
〖4575〗-保持的密码历史记录长度:
〖4576〗-计算机角色:
〖4577〗-工作站域的主域控制器:
〖4578〗-锁定阈值:
〖4579〗-锁定持续时间(分):
〖4580〗-锁定观测窗口(分):
〖4600〗-统计开始于
〖4601〗-接受的会话
〖4602〗-会话超时
〖4603〗-会话出错
〖4604〗-发送的KB
〖4605〗-接收的KB
〖4606〗-平均响应时间(毫秒)
〖4607〗-网络错误
〖4608〗-访问的文件
〖4609〗-后台处理的打印作业
〖4610〗-系统出错
〖4611〗-密码违规
〖4612〗-权限违规
〖4613〗-访问的通讯设备
〖4614〗-会话已启动
〖4615〗-重新连接的会话
〖4616〗-会话启动失败
〖4617〗-断开的会话
〖4618〗-网络I/O 执行
〖4619〗-文件及管道被访问
〖4620〗-时间缓冲区耗尽
〖4621〗-大缓冲区
〖4622〗-请求缓冲区
〖4626〗-已做连接
〖4627〗-连接失败
〖4630〗-接收的字节数
〖4631〗-接收的服务器消息块(SMB)
〖4632〗-传输的字节数
〖4633〗-传输的服务器消息块(SMB)
〖4634〗-读取操作
〖4635〗-写入操作
〖4636〗-拒绝原始读取
〖4637〗-拒绝原始写入
〖4638〗-网络错误
〖4639〗-已做连接
〖4640〗-重新连接
〖4641〗-服务器断开
〖4642〗-会话已启动
〖4643〗-会话挂起
〖4644〗-失败的会话
〖4645〗-操作失败
〖4646〗-使用计数
〖4647〗-使用计数失败
〖4655〗-消息名称转发已经取消。
〖4661〗-密码已经更改成功。
〖4664〗-消息已经发给网络上所有的用户。
〖4666〗-消息已经送到此服务器上的所有用户。
〖4696〗-Windows NT Server
〖4697〗-Windows NT Workstation
〖4698〗-MS-DOS 增强型工作站
〖4700〗-服务器名称注释
〖4701〗-资源共享名类型用途注释
〖4702〗-(UNC)
〖4703〗-...
〖4704〗-Domain
〖4706〗-其它可用的网络:
〖4710〗-Disk
〖4711〗-Print
〖4712〗-Comm
〖4713〗-IPC
〖4714〗-状态本地远程网络
〖4715〗-OK
〖4716〗-休止
〖4717〗-已暂停
〖4718〗-断开
〖4719〗-错误
〖4720〗-正在连接
〖4721〗-正在重新连接
〖4722〗-状态
〖4723〗-本地名称
〖4724〗-远程名称
〖4725〗-资源类型
〖4726〗-# 打开
〖4727〗-# 连接
〖4728〗-不可用
〖4730〗-共享名资源注释
〖4731〗-共享名
〖4732〗-资源
〖4733〗-后台处理
〖4734〗-权限
〖4735〗-最多用户
〖4736〗-无限制
〖4737〗-用户
〖4740〗-识别码路径用户名# 锁定
〖4741〗-文件识别码
〖4742〗-锁定
〖4743〗-权限
〖4750〗-计算机用户名客户类型打开空闲时间
〖4751〗-计算机
〖4752〗-会话时间
〖4753〗-空闲时间
〖4754〗-资源共享名类型# 打开
〖4755〗-客户类型
〖4756〗-来宾登录
〖4770〗-脱机缓存被启用:手动恢复
〖4771〗-脱机缓存被启用:自动恢复
〖4772〗-脱机缓存被启用:用户之间没有共享
〖4773〗-脱机缓存被停用
〖4774〗-自动
〖4775〗-手动
〖4800〗-名称
〖4801〗-转发到
〖4802〗-已经从下列位置转发给您
〖4803〗-这台服务器的用户
〖4804〗-用户已经按Ctrl+Break 中断网络发送。
〖4810〗-名称作业编号大小状态
〖4811〗-作业
〖4812〗-打印
〖4813〗-名称
〖4814〗-作业#
〖4815〗-大小
〖4816〗-状态
〖4817〗-分隔文件
〖4818〗-注释
〖4819〗-优先级
〖4820〗-打印后于
〖4821〗-打印直到
〖4822〗-打印处理程序
〖4823〗-附加信息
〖4824〗-参数
〖4825〗-打印设备
〖4826〗-打印机活动中
〖4827〗-打印机搁置
〖4828〗-打印机出错
〖4829〗-正在删除打印机
〖4830〗-打印机状态未知
〖4841〗-作业#
〖4842〗-正在提交用户
〖4843〗-通知
〖4844〗-作业数据类型
〖4845〗-作业参数
〖4846〗-正在等候
〖4847〗-搁置于队列
〖4848〗-正在后台处理
〖4849〗-已暂停
〖4850〗-脱机
〖4851〗-错误
〖4852〗-缺纸
〖4853〗-需要干预
〖4854〗-正在打印
〖4855〗-on
〖4862〗-驱动程序
〖4930〗-用户名类型日期
〖4931〗-锁定
〖4932〗-服务
〖4933〗-服务器
〖4934〗-服务器已启动
〖4935〗-服务器已暂停
〖4936〗-服务器已继续操作
〖4937〗-服务器已停止
〖4938〗-会话
〖4939〗-登录来宾
〖4940〗-登录用户
〖4941〗-登录管理员
〖4942〗-正常注销
〖4943〗-登录
〖4944〗-注销错误
〖4945〗-注销自动断开
〖4946〗-注销管理员断开
〖4947〗-注销受登录限制
〖4948〗-服务
〖4957〗-帐户
〖4964〗-已修改帐户系统设置
〖4965〗-登录限制
〖4966〗-超过限制: 未知
〖4967〗-超过限制: 登录时间
〖4968〗-超过限制: 帐户过期
〖4969〗-超过限制: 工作站识别码无效
〖4970〗-超过限制: 帐户停用
〖4971〗-超过限制: 帐户已删除
〖4972〗-资源
〖4978〗-密码不正确
〖4979〗-需要管理员特权
〖4980〗-访问
〖4984〗-拒绝访问
〖4985〗-未知
〖4986〗-其它
〖4987〗-持续时间:
〖4988〗-持续时间: 无效
〖4989〗-持续时间: 1 秒以下
〖4990〗-(无)
〖4994〗-访问结束
〖4995〗-登录到网络
〖4996〗-拒绝登录
〖4997〗-程序消息时间
〖4999〗-管理员已解除帐户的锁定状态
〖5000〗-注销网络
〖5001〗-因为其它资源需要它，不能将群集资源移到另一个组。
〖5002〗-找不到此群集资源的依存。
〖5003〗-因为已经处于依存状态，此群集资源不能依存于指定的资源。
〖5004〗-此群集资源未联机。
〖5005〗-此操作没有可用的群集节点。
〖5006〗-没有群集资源。
〖5007〗-找不到群集资源。
〖5008〗-正在关闭群集。
〖5009〗-因为联机，群集节点无法从群集中脱离。
〖5010〗-对象已存在。
〖5011〗-此对象已在列表中。
〖5012〗-新请求没有可用的群集组。
〖5013〗-找不到群集组。
〖5014〗-因为群集组未联机，此操作不能完成。
〖5015〗-群集节点不是此资源的所有者。
〖5016〗-群集节点不是此资源的所有者。
〖5017〗-群集资源不能在指定的资源监视器中创建。
〖5018〗-群集资源不能通过资源监视器来联机。
〖5019〗-因为群集资源联机，此操作不能完成。
〖5020〗-由于是仲裁资源，群集资源不能被删除或脱机。
〖5021〗-由于没有能力成为仲裁资源，此群集不能使指定资源成为仲裁资源。
〖5022〗-群集软件正关闭。
〖5023〗-组或资源的状态不是执行请求操作的正确状态。
〖5024〗-属性已被存储，但在下次资源联机前，不是所有的修改将生效。
〖5025〗-由于不属于共享存储类别，群集不能使指定资源成为仲裁资源。
〖5026〗-由于是内核资源，无法删除群集资源。
〖5027〗-仲裁资源联机失败。
〖5028〗-无法成功创建或装入仲裁日志。
〖5029〗-群集日志损坏。
〖5030〗-由于该日志已超出最大限量，无法将记录写入群集日志。
〖5031〗-群集日志已超出最大限量。
〖5032〗-群集日志没有发现检查点记录。
〖5033〗-不满足日志所需的最小磁盘空间。
〖5034〗-群集节点未能控制仲裁资源，因为它被另一个活动节点拥有。
〖5035〗-这个操作的群集网络无效。
〖5036〗-此操作没有可用的群集节点。
〖5037〗-所有群集节点都必须运行才能执行这个操作。
〖5038〗-群集资源失败。
〖5039〗-该群集节点无效。
〖5040〗-该群集节点已经存在。
〖5041〗-一个节点正在加入该群集。
〖5042〗-找不到群集节点。
〖5043〗-找不到群集本地节点信息。
〖5044〗-群集网络已经存在。
〖5045〗-找不到群集网络。
〖5046〗-群集网络界面已经存在。
〖5047〗-找不到群集网络界面。
〖5048〗-群集请求在这个对象中无效。
〖5049〗-群集网络提供程序无效。
〖5050〗-群集节点坏了。
〖5051〗-无法连接到群集节点。
〖5052〗-该群集节点不是群集的一个成员。
〖5053〗-群集加入操作正在进行中。
〖5054〗-该群集网络无效。
〖5055〗-Mar
〖5056〗-该群集节点可以使用。
〖5057〗-该群集IP 地址已在使用中。
〖5058〗-该群集节点没有中止。
〖5059〗-没有有效的群集安全上下文。
〖5060〗-该群集网络不是为内部群集通讯配置的。
〖5061〗-群集节点已经开始。
〖5062〗-群集节点已经坏了。
〖5063〗-群集网络已经联机。
〖5064〗-群集网络已经脱机。
〖5065〗-群集节点已经是该群集的成员。
〖5066〗-该群集网络是唯一个为两个或更多活动群集节点进行内部群集通讯的配置。不能从网络上删除内部通讯能力。
〖5067〗-一个或更多的群集资源依靠网络来向客户提供服务。不能从网络上删除客户访问能力。
〖5068〗-该操作不能在群集资源上作为仲裁资源执行。您不能将仲裁资源脱机或修改它的所有者名单。
〖5069〗-该群集仲裁资源不允许有任何依存关系。
〖5070〗-该群集节点暂停。
〖5071〗-群集资源不能联机。所有者节点不能在这个资源上运行。
〖5072〗-群集节点没有准备好，不能执行所请求的操作。
〖5073〗-群集节点正在关闭。
〖5074〗-放弃群集节点加入操作。
〖5075〗-由于加入节点和支持者之间的软件版本不兼容，该群集加入操作失败。
〖5076〗-由于该群集已经到达其所能监督的资源限制，不能创建这个资源。
〖5077〗-系统配置在群集加入或形成操作时已更改。放弃加入或形成操作。
〖5078〗-找不到指定的资源种类。
〖5079〗-指定的节点不支持这种资源，这也许是由于版本不一致或是由于在这个节点上没有资源DLL。
〖5080〗-该资源DLL 不支持指定的资源名称。这可能是由于一个提供给源DLL 名称是错误的(或经过更改的)。
〖5081〗-不能在RPC 服务器上注册任何身份验证包。
〖5082〗-由于组的所有者不在组的首选列表中，不能将组联机。要改变组的所有者节点，请移动组。
〖5083〗-群集数据库的系列号已改变，或者与锁定程序节点不相容，因此加入操作没有成功。如果在加入操作期间群集数据库有任何改动，这都可能发生。
〖5084〗-资源在其当前状态下，资源监视器不允许执行失败操作。资源处于挂起状态时，这都可能发生。
〖5085〗-非锁定程序代码收到一个为全局更新保留锁定的请求。
〖5086〗-群集服务找不到仲裁磁盘。
〖5087〗-已备份的群集数据库可能已损坏。
〖5088〗-DFS 根目录已在这个群集节点中。
〖5089〗-由于与另一个现有属性冲突，未能修改资源属性。
〖5090〗-西班牙
〖5091〗-丹麦
〖5092〗-瑞典
〖5093〗-挪威
〖5094〗-德国
〖5095〗-澳大利亚
〖5096〗-日本
〖5097〗-韩国
〖5098〗-中国
〖5099〗-台湾
〖5100〗-亚洲
〖5101〗-葡萄牙
〖5102〗-芬兰
〖5103〗-阿拉伯
〖5104〗-希伯莱
〖5153〗-UPS 服务即将执行最后的关机操作。
〖5170〗-工作站必须用NET START 才能启动。
〖5175〗-远程IPC
〖5176〗-远程管理
〖5177〗-默认共享
〖5291〗-永不
〖5292〗-永不
〖5293〗-永不
〖5295〗-NETUS.HLP
〖5296〗-NET.HLP
〖5300〗-网络控制块(NCB) 请求运行成功。NCB 是相关数据。
〖5301〗-SEND DATAGRAM、SEND BROADCAST、ADAPTER STATUS 或SESSION STATUS 的网络控制块(NCB) 缓冲区长度无效。NCB 是相关数据。
〖5302〗-网络控制块(NCB) 指定的数据描述数组无效。NCB 是相关数据。
〖5303〗-网络控制块(NCB) 指定的命令无效。NCB 是相关数据。
〖5304〗-网络控制块(NCB) 指定的消息交换码无效。NCB 是相关数据。
〖5305〗-网络控制块(NCB) 命令超时。会话可能异常终止。NCB 是相关数据。
〖5306〗-接收的网络控制块(NCB) 消息不完整。NCB 是相关数据。
〖5307〗-网络控制块(NCB) 指定的缓冲区无效。NCB 是相关数据。
〖5308〗-网络控制块(NCB) 指定的会话号码没有作用。NCB 是相关数据。
〖5309〗-网卡没有任何资源可用。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5310〗-网络控制块(NCB) 指定的会话已经关闭。NCB 是相关数据。
〖5311〗-网络控制块(NCB) 命令已经取消。NCB 是相关数据。
〖5312〗-网络控制块(NCB) 指定的消息块不合逻辑。NCB 是相关数据。
〖5313〗-该名称已经存在于本地适配器名称表中。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5314〗-网卡名称表已满。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5315〗-网络名称已经有活动的会话，现在取消注册。网络控制块(NCB) 命令运行完毕。NCB 是相关数据。
〖5316〗-先前发出的Receive Lookahead 命令对此会话仍起作用。网络控制块(NCB) 命令被拒绝。NCB 是相关数据。
〖5317〗-本地会话表已满。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5318〗-拒绝打开网络控制块(NCB) 会话，远程计算机上没有侦听命令在执行。NCB 是相关数据。
〖5319〗-网络控制块(NCB) 指定的名称号码无效。NCB 是相关数据。
〖5320〗-网络控制块(NCB) 中指定的调用名称找不到，或者没有应答。NCB 是相关数据。
〖5321〗-网络控制块(NCB) 中指定的名称找不到。无法将“*”或00h 填入NCB 名称。NCB 是相关数据。
〖5322〗-网络控制块(NCB) 中指定的名称正用于远程适配器。NCB 是相关数据。
〖5323〗-网络控制块(NCB) 中指定的名称已经删除。NCB 是相关数据。
〖5324〗-网络控制块(NCB) 中指定的会话异常终止。NCB 是相关数据。
〖5325〗-网络协议在网络上检测两个或数个相同的名称。 网络控制块(NCB) 是相关数据。
〖5326〗-收到意外的协议数据包。远程设备可能不兼容。网络控制块(NCB) 是相关数据。
〖5333〗-NetBIOS 界面正忙。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5334〗-未完成的网络控制块(NCB) 命令太多。NCB 请求被拒绝。NCB 是相关数据。
〖5335〗-网络控制块(NCB) 中指定的适配器号无效。NCB 是相关数据。
〖5336〗-网络控制块(NCB) 命令在取消的同时运行完毕。NCB 是相关数据。
〖5337〗-网络控制块(NCB) 指定的名称已经保留。NCB 是相关数据。
〖5338〗-网络控制块(NCB) 命令无法取消。NCB 是相关数据。
〖5351〗-同一个会话有多个网络控制块(NCB)。NCB 请求被拒绝。NCB 是相关数据。
〖5352〗-网卡出错。唯一可能发出的NetBIOS 命令是NCB RESET。网络控制块(NCB) 是相关数据。
〖5354〗-超过应用程序数目上限。网络控制区(NCB) 请求被拒绝，NCB 是相关数据。
〖5356〗-请求的资源无法使用。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5364〗-系统出错。网络控制块(NCB) 请求被拒绝。NCB 即为数据。
〖5365〗-“ROM 校验和”失败。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5366〗-RAM 测试失败。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5367〗-数字式环回失败。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5368〗-模拟式环回失败。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5369〗-界面失败。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5370〗-收到的网络控制块(NCB) 返回码无法识别。NCB 是相关数据。
〖5380〗-网卡故障。网络控制块(NCB) 请求被拒绝。NCB 是相关数据。
〖5381〗-网络控制块(NCB) 命令仍然处于搁置状态。NCB 是相关数据。
〖5509〗-Windows 2000 无法按指定的配置启动，将换用先前可工作的配置。
〖5600〗-无法共享用户或脚本路径。
〖5601〗-计算机的密码在本地安全数据库中找不到。
〖5602〗-访问计算机的本地或网络安全数据库时，发生内部错误。
〖5705〗-Netlogon 服务用于记录数据库更改数据的日志高速缓存已损坏。Netlogon 服务正在复位更改日志文件。
〖5728〗-无法加载任何传输。
〖5739〗-此域的全局组数目超过可以复制到LanMan BDC 的限制。请删除部分的全局组或删除域中的LanManBDC。
〖5742〗-服务无法检索必要的消息，所以无法运行远程启动客户。
〖5743〗-服务发生严重的错误，无法从远程启动3Com 3Start 远程启动客户。
〖5744〗-服务发生严重的系统错误，即将关机。
〖5760〗-服务在分析RPL 配置时出错。
〖5761〗-服务在创建所有配置的RPL 配置文件时出错。
〖5762〗-服务在访问注册表时出错。
〖5763〗-服务在替换可能过期的RPLDISK.SYS 时出错。
〖5764〗-服务在添加安全帐户或设置文件权限时出错。这些帐户是独立RPL 工作站的RPLUSER 本地组以及用户帐户。 .
〖5765〗-服务无法备份它的数据库。
〖5766〗-服务无法从它的数据库初始化。数据库可能找不到或损坏。服务会试图从备份数据库恢复该数据库。
〖5767〗-服务无法从备份数据库还原它的数据库。服务将不启动。
〖5768〗-服务无法从备份数据库还原它的数据库。
〖5769〗-服务无法从它还原的数据库初始化。服务将不启动。
〖5771〗-远程启动数据库采用NT 3.5 / NT 3.51 格式。NT 正在转换其为NT 4.0 格式。完成转换后，JETCONV 转换器将写出应用事件日志。
〖5773〗-该DC 的DNS 服务器不支持动态DNS。将文件$1$SystemRoot/System32/Config/netlogon.dns$1$中的DNS 记录添加到伺服那个文件中引用的域的DNS 服务器。
〖5781〗-由于没有可以使用的DNS 服务器，一个或更多DNS 记录的动态注册和注销未成功。
〖6000〗-无法加密指定的文件。
〖6001〗-指定的文件无法解密。
〖6002〗-指定的文件已加密，而且用户没有能力解密。
〖6003〗-这个系统没有有效的加密恢复策略配置。
〖6004〗-所需的加密驱动程序并未加载到系统中。
〖6005〗-文件加密所使用的加密驱动程序与目前加载的加密驱动程序不同。
〖6006〗-没有为用户定义的EFS 关键字。
〖6007〗-指定的文件并未加密。
〖6008〗-指定的文件不是定义的EFS 导出格式。
〖6009〗-指定的文件是只读文件。
〖6010〗-已为加密而停用目录。
〖6011〗-不信任服务器来进行远程加密操作。
〖6118〗-此工作组的服务器列表当前无法使用
〖6200〗-要正常运行，任务计划程序服务的配置必须在系统帐户中运行。单独的任务可以被配置成在其他帐户中运行。
〖7001〗-指定的会话名称无效。
〖7002〗-指定的协议驱动程序无效。
〖7003〗-在系统路径上找不到指定的协议驱动程序。
〖7004〗-在系统路径上找不到指定的终端连接。
〖7005〗-不能为这个会话创建一个事件日志的注册键。
〖7006〗-同名的一个服务已经在系统中存在。
〖7007〗-在会话上一个关闭操作挂起。
〖7008〗-没有可用的输出缓冲器。
〖7009〗-找不到MODEM.INF 文件。
〖7010〗-在MODEM.INF 中没有找到调制解调器名称。
〖7011〗-调制解调器没有接受发送给它的指令。验证配置的调制解调器与连接的调制解调器是否匹配。
〖7012〗-调制解调器没有接受发送给它的指令。验证该调制解调器是否接线正确并且打开了电源开关。
〖7013〗-运载工具检测失败或者由于断开连接，运载工具已被丢弃。
〖7014〗-在要求的时间内没有发现拨号音。 确定电话线连接正确并可使用。
〖7015〗-在远程站点回叫时检测到了占线信号。
〖7016〗-在回叫时远程站点上检测到了声音。
〖7017〗-传输驱动程序错误
〖7022〗-找不到指定的会话。
〖7023〗-指定的会话名称已处于使用中。
〖7024〗-由于终端连接目前正在忙于处理一个连接、断开连接、复位或删除操作，无法完成该请求的操作。
〖7025〗-试图连接到其视频模式不受当前客户支持的会话。
〖7035〗-应用程序尝试启动DOS 图形模式。不支持DOS 图形模式。
〖7037〗-您的交互式登录权限已被禁用。 Please contact your administrator.
〖7038〗-该请求的操作只能在系统控制台上执行。这通常是一个驱动程序或系统DLL 要求直接控制台访问的结果。
〖7040〗-客户未能对服务器连接消息作出响应。
〖7041〗-不支持断开控制台会话。
〖7042〗-不支持重新将一个断开的会话连接到控制台。
〖7044〗-远程控制另一个会话的请求被拒绝。
〖7045〗-拒绝请求的会话访问。
〖7049〗-指定的终端连接驱动程序无效。
〖7050〗-不能远程控制该请求的会话。这也许是由于该会话被中断或目前没有一个用户登录。而且，您不能从该系统控制台远程控制一个会话或远程控制系统控制台。并且，您不能远程控制您自己的当前会话。
〖7051〗-该请求的会话没有配置成允许远程控制。
〖7052〗-拒绝连接到这个终端服务器。终端服务器客户许可证目前正在被另一个用户使用。请与系统管理员联系，获取一份新的终端服务器客户，其许可证号码必须是有效的、唯一的。
〖7053〗-拒绝连接到这个终端服务器。还没有为这份终端服务器客户输入您的终端服务器客户许可证号码。请与系统管理员联系，为该终端服务器客户输入一个有效的、唯一的许可证号码。
〖7054〗-系统已达到其授权的登录限制。请以后再试一次。
〖7055〗-您正在使用的客户没有使用该系统的授权。您的登录请求被拒绝。
〖7056〗-系统许可证已过期。您的登录请求被拒绝。
〖8001〗-文件复制服务API 被错误调用。
〖8002〗-无法启动文件复制服务。
〖8003〗-无法停止文件复制服务。
〖8004〗-文件复制服务API 终止了请求。事件日志可能有详细信息。
〖8005〗-该文件复制服务中断了该请求。事件日志可能有详细信息。
〖8006〗-无法联系文件复制服务。事件日志可能有详细信息。
〖8007〗-由于该用户没有足够特权，文件复制服务不能满足该请求。事件日志可能有详细信息。
〖8008〗-由于验证的RPC 无效，文件复制服务不能满足该请求。事件日志可能有详细信息。
〖8009〗-由于该用户在域控制器上没有足够特权，文件复制服务不能满足该请求。事件日志可能有详细信息。
〖8010〗-由于在域控制器上的验证的RPC 无效，文件复制服务不能满足该请求。事件日志可能有详细信息。
〖8011〗-该文件复制服务无法与在域控制器上的文件复制服务通讯。事件日志可能有详细信息。
〖8012〗-在域控制器上的文件复制服务无法与这台计算机上的文件复制服务通讯。事件日志可能有详细信息。
〖8013〗-由于内部错误，该文件复制服务不能进入该系统卷中。事件日志可能有详细信息。
〖8014〗-由于内部超时，该文件复制服务不能进入该系统卷中。事件日志可能有详细信息。
〖8015〗-该文件复制服务无法处理此请求。该系统卷仍在忙于前一个请求。
〖8016〗-由于内部错误，该文件复制服务无法停止复制该系统卷。事件日志可能有详细信息。
〖8017〗-该文件复制服务检测到一个无效参数。
〖8200〗-在安装目录服务时出现一个错误。有关详细信息，请查看事件日志。
〖8201〗-目录服务在本地评估组成员身份。
〖8202〗-指定的目录服务属性或值不存在。
〖8203〗-指定给目录服务的属性语法无效。
〖8204〗-指定给目录服务的属性类型未定义。
〖8205〗-指定的目录服务属性或值已经存在。
〖8206〗-目录服务忙。
〖8207〗-该目录服务无效。
〖8208〗-目录服务无法分配相对标识号。
〖8209〗-目录服务已经用完了相对标识号池。
〖8210〗-由于目录服务不是该类操作的主控，未能执行操作。
〖8211〗-目录服务无法初始化分配相对标识号的子系统。
〖8212〗-该请求的操作没有满足一个或多个与该对象的类别相关的约束。
〖8213〗-目录服务只可以在一个页状对象上运行要求的操作。
〖8214〗-目录服务不能在一个对象的RDN 属性上执行该请求的操作。
〖8215〗-目录服务检测出修改对象类别的尝试。
〖8216〗-不能执行请求的通过域的移动操作。
〖8217〗-无法联系全局编录服务器。
〖8218〗-策略对象是共享的并只可在根目录上修改。
〖8219〗-策略对象不存在。
〖8220〗-请求的策略信息只在目录服务中。
〖8221〗-域控制器升级目前正在使用中。
〖8222〗-域控制器升级目前不在使用中
〖8224〗-出现一个操作错误。
〖8225〗-出现一个协议错误。
〖8226〗-已经超过这个请求的时间限制。
〖8227〗-已经超过这个请求的大小限制。
〖8228〗-已经超过这个请求的管理限制。
〖8229〗-比较的响应为假。
〖8230〗-比较的响应为真。
〖8231〗-这个服务器不支持请求的身份验证方式。
〖8232〗-这台服务器需要一个更安全的身份验证方式。
〖8233〗-不适当的身份验证。
〖8234〗-未知的身份验证机制。
〖8235〗-从服务器返回了一个建议。
〖8236〗-该服务器不支持该请求的关键扩展。
〖8237〗-这个请求需要一个安全的连接。
〖8238〗-不恰当的匹配。
〖8239〗-出现一个约束冲突。
〖8240〗-在服务器上没有这样一个对象。
〖8241〗-有一个别名问题。
〖8242〗-指定了一个无效的dn 语法。
〖8243〗-该对象为叶对象。
〖8244〗-有一个别名废弃问题。
〖8245〗-该服务器不愿意处理该请求。
〖8246〗-检查到一个循环。
〖8247〗-有一个命名冲突。
〖8248〗-结果设置太大。
〖8249〗-该操作会影响到多个DSA。
〖8250〗-该服务器不可操作。
〖8251〗-出现一个本地错误。
〖8252〗-出现一个编码错误。
〖8253〗-出现一个解码错误。
〖8254〗-无法识别寻找筛选器。
〖8255〗-一个或多个参数非法。
〖8256〗-不支持指定的方式。
〖8257〗-没有返回结果。
〖8258〗-该服务器不支持该指定的控制。
〖8259〗-客户检测到一个参考循环。
〖8260〗-超过当前的参考限制。
〖8301〗-根目录对象必须是一个命名上下文的头。该根目录对象不能有实例父类。
〖8302〗-不能执行添加副本操作。名称上下文必须可写才能创建副本。
〖8303〗-出现一个对架构中未定义的一个属性的参考。
〖8304〗-超过了一个对象的最大尺寸。
〖8305〗-尝试向目录中添加一个已在使用中的名称的对象。
〖8306〗-尝试添加一个对象，该对象属于那类在架构中没有一个RDN 定义的类别。
〖8307〗-尝试添加一个使用RDN 的对象，但该RDN 不是一个在架构中定义的RDN 。
〖8308〗-在对象中找不到任何请求的属性。
〖8309〗-用户缓冲区太小。
〖8310〗-在操作中指定的属性不出现在对象上。
〖8311〗-修改操作非法。不允许该修改的某个方面。
〖8312〗-指定的对象太大。
〖8313〗-指定的实例类别无效。
〖8314〗-操作必须在主控DSA 执行。
〖8315〗-必须指定对象类别属性。
〖8316〗-一个所需的属性丢失。
〖8317〗-尝试修改一个对象，将一个对该类别来讲是非法的属性包括进来。
〖8318〗-在对象上指定的属性已经存在。
〖8320〗-指定的属性不存在或没有值。
〖8321〗-为只有一个值的属性指定了多个值。
〖8322〗-属性值不在接受范围内。
〖8323〗-指定的值已存在。
〖8324〗-由于不存在于对象上，不能删除该属性。
〖8325〗-由于不存在于对象上，不能删除该属性值。
〖8326〗-指定的根对象不能是子参考。
〖8327〗-不允许链接。
〖8328〗-不允许链接的评估。
〖8329〗-由于对象的父类不是未实例化就是被删除了，所以不能执行操作。
〖8330〗-不允许有一个用别名的父类。别名是叶对象。
〖8331〗-对象和父类必须是同一种类，不是都是原件就是都是副本。
〖8332〗-由于子对象存在，操作不能执行。这个操作只能在叶对象上执行。
〖8333〗-没有找到目录对象。
〖8334〗-别名对象丢失。
〖8335〗-对象名语法不对。
〖8336〗-不允许一个别名参考另一个别名。
〖8337〗-别名不能解除参考。
〖8338〗-操作超出范围。
〖8340〗-不能删除DSA 对象。
〖8341〗-出现一个目录服务错误。
〖8342〗-操作只能在内部主控DSA 对象上执行。
〖8343〗-对象必须为DSA 类别。
〖8344〗-访问权不够不能执行该操作。
〖8345〗-由于父类不在可能的上级列表上，不能添加该对象。
〖8346〗-由于该属性处于“安全帐户管理器” (SAM)，不允许访问该属性。
〖8347〗-名称有太多部分。
〖8348〗-名称太长。
〖8349〗-名称值太长。
〖8350〗-目录服务遇到了一个错误分列名称。
〖8351〗-目录服务找不到一个名称的属性种类。
〖8352〗-该名称不能识别一个对象; 该名称识别一个幻象。
〖8353〗-安全描述符太短。
〖8354〗-安全描述符无效。
〖8355〗-为删除的对象创建名称失败。
〖8356〗-一个新子参考的父类必须存在。
〖8357〗-该对象必须是一个命名上下文。
〖8358〗-不允许添加一个不属于系统的属性。
〖8359〗-对象的类别必须是有结构的; 您不能实例化一个抽象的类别。
〖8360〗-找不到架构的对象。
〖8361〗-有这个GUID (非活动的的或活动的)的本地对象已经存在。
〖8362〗-操作不能在一个后部链接上执行。
〖8363〗-找不到指定的命名上下文的互交参考。
〖8364〗-由于目录服务关闭，操作不能执行。
〖8365〗-目录服务请求无效。
〖8366〗-无法读取角色所有者属性。
〖8367〗-请求的FSMO 操作失败。不能连接当前的FSMO 盒。
〖8368〗-不允许跨过一个命名上下文修改DN。
〖8369〗-由于属于系统，不能修改该属性。
〖8370〗-只有复制器可以执行这个功能。
〖8371〗-指定的类别没有定义。
〖8372〗-指定的类别不是一个子类别。
〖8373〗-名称参考无效。
〖8374〗-交叉参考已经存在。
〖8375〗-不允许删除一个主控交叉参考。
〖8376〗-只在NC 头上支持子目录树通知。
〖8377〗-通知筛选器太复杂。
〖8378〗-架构更新失败: 重复的RDN。
〖8379〗-架构更新失败: 重复的OID。
〖8380〗-架构更新失败: 重复的MAPI 识别符。
〖8381〗-架构更新失败: 复制架构id GUID。
〖8382〗-架构更新失败: 重复的LDAP 显示名称。
〖8383〗-架构更新失败: 范围下部少于范围上部。
〖8384〗-架构更新失败: 语法不匹配。
〖8385〗-架构更新失败: 属性在必须包含中使用。
〖8386〗-架构更新失败: 属性在可能包含中使用。
〖8387〗-架构更新失败: 可能包含中的属性不存在。
〖8388〗-架构更新失败:必须包含中的属性不存在。
〖8389〗-架构更新失败: 在辅助类别列表中的类别不存在或不是一个辅助类别。
〖8390〗-架构更新失败: poss-superior 中的类别不存在。
〖8391〗-架构更新失败: 在subclassof 列表中的类别不存在或不能满足等级规则。
〖8392〗-架构更新失败: Rdn-Att-Id 语法不对。
〖8393〗-架构更新失败: 类别作为辅助类别使用。
〖8394〗-架构更新失败: 类别作为子类别使用。
〖8395〗-架构更新失败: 类别作为poss superior 使用。
〖8396〗-架构更新在重新计算验证缓存时失败。
〖8397〗-目录树删除没有完成。要继续删除目录树，必须再次发出请求。
〖8398〗-不能执行请求的删除操作。
〖8399〗-不能读取架构记录管理类别识别符。
〖8400〗-属性架构语法不对。
〖8401〗-不能缓存属性。
〖8402〗-不能缓存类别。
〖8403〗-不能从缓存删除属性。
〖8404〗-无法从缓存中删除类别。
〖8405〗-无法读取特殊名称的属性。
〖8406〗-丢失一个所需的子参考。
〖8407〗-不能检索范例种类属性。
〖8408〗-出现一个内部错误。
〖8409〗-出现一个数据错误。
〖8410〗-丢失一个属性GOVERNSID。
〖8411〗-丢失一个所需要的属性。
〖8412〗-指定的命名上下文丢失了一个交叉参考。
〖8413〗-出现一个安全检查错误。
〖8414〗-没有加载架构。
〖8415〗-架构分配失败。请检查机器内存是否不足。
〖8416〗-为属性架构获得所需语法失败。
〖8417〗-全局编录验证失败。全局编录无效或不支持操作。目录的某些部分目前无效。
〖8418〗-由于有关服务器之间的架构不匹配，复制操作失败。
〖8419〗-找不到DSA 对象。
〖8420〗-找不到命名上下文。
〖8421〗-在缓存中找不到命名上下文。
〖8422〗-无法检索子对象。
〖8423〗-由于安全原因不允许修改。
〖8424〗-操作不能替换该隐藏的记录。
〖8425〗-等级无效。
〖8426〗-尝试建立等级表失败。
〖8427〗-目录配置参数在注册中丢失。
〖8428〗-尝试计算地址簿索引失败。
〖8429〗-等级表的分配失败。
〖8430〗-目录服务遇到一个内部失败。
〖8431〗-目录服务遇到一个未知失败。
〖8432〗-根对象需要一个$1$top$1$ 类别。
〖8433〗-这个目录服务器已关闭，并且不能接受新上浮单一主机操作角色的所有权。
〖8434〗-目录服务没有必需的配置信息，并且不能决定新上浮单一主机操作角色的所有权。
〖8435〗-该目录服务无法将一个或多个上浮单一主机操作角色传送给其它服务器。
〖8436〗-复制操作失败。
〖8437〗-为这个复制操作指定了一个无效的参数。
〖8438〗-目录服务太忙，现在无法完成这个复制操作。
〖8439〗-为这个复制操作指定的单一名称无效。
〖8440〗-为这一个复制操作所指定的命名上下文无效。
〖8441〗-为这个复制操作指定的单一名称已经存在。
〖8442〗-复制系统遇到一个内部错误。
〖8443〗-复制操作遇到数据库不一致问题。
〖8444〗-不能连接到为这个复制操作指定的服务器上。
〖8445〗-复制操作遇到一个有无效范例类型的对象。
〖8446〗-复制操作无法分配内存。
〖8447〗-复制操作遇到一个邮件系统错误。
〖8448〗-目标服务器的复制参考信息已经存在。
〖8449〗-目标服务器的复制参考信息不存在。
〖8450〗-由于是由另一台服务器上复制的，因此不能删除命名上下文。
〖8451〗-复制操作遇到一个数据库错误。
〖8452〗-命名上下文要被删除或没有从指定的服务器上复制。
〖8453〗-复制访问被拒绝。
〖8454〗-这个版本的目录服务不支持请求的操作。
〖8455〗-取消复制远程过程呼叫。
〖8456〗-源服务器目前拒绝复制请求。
〖8457〗-目标服务器当前拒绝复制请求。
〖8458〗-由于对象名称冲突，复制操作失败。
〖8459〗-复制源已被重新安装。
〖8460〗-由于一个所需父对象丢失，复制操作失败。
〖8461〗-复制操作被抢先。
〖8462〗-由于缺乏更新，放弃复制同步尝试。
〖8463〗-由于系统正在关闭，复制操作被中断了。
〖8464〗-由于目标部分属性设置不是一个源部分属性设置的子设置，复制同步尝试失败。
〖8465〗-由于主复制尝试从部分复制同步，复制同步尝试失败。
〖8466〗-已经与为这个复制操作的指定的服务器联系，但是该服务器无法与完成这个操作所需的另外一个服务器联系。
〖8467〗-在副本安装时，检测到一个使用的源和内部版本之间的架构不匹配，不能安装该副本。
〖8468〗-架构更新失败: 有同一连接标识符的属性已经存在。
〖8469〗-名称翻译: 常见处理错误。
〖8470〗-名称翻译: 不能找到该名称或权限不够，不能看到名称。
〖8471〗-名称翻译: 输入名称映射到多个输出名称。
〖8472〗-名称翻译: 找到输出名称，但是找不到相应的输出格式。
〖8473〗-名称翻译: 不能完全解析，只找到了域。
〖8474〗-名称翻译: 不接到线上，无法在客户机上执行纯粹的语法映射。
〖8475〗-不允许一个构造att 修改。
〖8476〗-指定的OM-Object 类别对指定语法的一个属性是不正确的。
〖8477〗-复制请求已暂停; 等待回答。
〖8478〗-要求的操作需要一个目录服务，但没有可用的。
〖8479〗-类别或属性的LDAP 显示名称含有非ASCII 字符。
〖8480〗-请求的查找操作只支持基本查找。
〖8481〗-查找未能从数据库检索属性。
〖8482〗-架构更新操作试图添加一个反向链接，但该反向链接没有相应的正向链接。
〖8483〗-跨域移动的来源和目标在对象日期上不一致。或者是来源，或者是目标没有对象的最后一个版本。
〖8484〗-跨域移动的来源和目标在对象当前的名称上不一致。或者是来源，或者是目标没有对象的最后一个版本。
〖8485〗-域间移动的来源和目标是一样的。调用程序应该使用本地移动操作，而不是域间移动操作。
〖8486〗-域间移动的来源和目标与目录林中的命名上下文不一致。来源或目标没有分区容器的最近版本。
〖8487〗-跨域移动的目标不是目标命名上下文的权威。
〖8488〗-跨域移动的来源和目标提供的来源对象的身份不一样。 来源或目标没有来源对象的最近版本。
〖8489〗-跨域移动的对象应该已经被目标服务器删除。来源服务器没有来源对象的最近版本。
〖8490〗-要求对PDC FSMO 的专门访问权的另一个操作正在进行中。
〖8491〗-跨域移动没有成功，导致被移动对象有两个版本- 一个在来源域，一个在目标域。需要删除目标对象，将系统还原到一致状态。
〖8492〗-因为不允许这个类别的跨域移动，或者对象有一些特点，如: 信任帐户或防止移动的受限制的RID；所以不能将该对象跨域移动。
〖8493〗-一旦移动，不能将带有成员身份的对象跨域移动，这会侵犯帐户组的成员身份条件。从帐户组成员身份删除对象，再试一次。
〖8494〗-命名上下文标题必须是另一个命名上下文标题的直接子标题，而不是一个内节点的子标题。
〖8495〗-因为目录没有提议的命名上下文上面的命名上下文的副本，所以无法验证所提议的命名上下文的名称。请保证充当域命名主机的服务器已配置成全局编录服务器，并且服务器及其复制伙伴是最新的。
〖8496〗-目标域必须在本机模式中。
〖8497〗-因为服务器在指定域中没有基础结构容器，所以无法执行操作。
〖8498〗-不允许跨域移动帐户组。
〖8499〗-不允许跨域移动资源组。
〖8500〗-属性的搜索标志无效。ANR 位只在Unicode 或Teletex 字符串的属性上有效。
〖8501〗-不允许在将NC 头作为子体的对象开始删除目录树。
〖8502〗-因为目录树在使用中，目录服务未能为删除目录树而将其锁定。
〖8503〗-删除目录树时，目录服务未能识别要删除的对象列表。
〖8505〗-只有管理员才能修改管理组的成员列表。
〖8506〗-不能改变域控制器帐户的主要组ID。
〖8507〗-试图修改基础架构。
〖8508〗-不允许进行下列操作: 为现有类别添加新的强制属性；从现有类别删除强制属性；为没有向回链接属性的特殊类别"Top" 添加可选属性，向回链接属性指的是直接或通过继承。例如: 添加或删除附属类别。
〖8509〗-该域控制器上不允许架构更新。没有设置注册表项，或者DC 不是架构FSMO 角色所有者。
〖8510〗-无法在架构容器下创建这个类别的对象。在架构容器下，您只能创建属性架构和类别架构对象。
〖8511〗-副本/子项安装未能获取源DC 上的架构容器的objectVersion 属性。架构容器上的属性不存在，或者提供的凭据没有读取属性的权限。
〖8512〗-副本/子项安装未能读取system32 目录中的文件schema.ini 的SCHEMA 段中的objectVersion 属性。
〖8513〗-指定的组类型无效。
〖8514〗-如果域是安全启用的，在混合型域中不能嵌套全局组。
〖8515〗-如果域是安全启用的，在混合型域中不能嵌套本地组。
〖8516〗-全局组不能将本地组作为成员。
〖8517〗-全局组不能将通用组作为成员。
〖8518〗-通用组不能将本地组作为成员。
〖8519〗-全局组不能有跨域成员。
〖8520〗-本地组不能将另一个跨域本地组作为成员。
〖8521〗-包含主要成员的组不能改变为安全停用的组。
〖8522〗-架构缓冲加载未能转换类架构对象上的字符串默认值SD。
〖8523〗-只有配置成全局编录服务器的DSAs 才能充当域命名主机FSMO 的角色。
〖8524〗-由于DNS 查找故障，DSA 操作无法进行。
〖8525〗-处理一个对象的DNS 主机名改动时，服务主要名称数值无法保持同步。
〖8526〗-未能读取安全描述符属性。
〖8527〗-没有找到请求的对象，但找到了具有那个密钥的对象。
〖8528〗-正在添加的链接属性的语法不正确。正向链接只能有语法2.5.5.1、2.5.5.7 和2.5.5.14，而反向链接只能有语法2.5.5.1
〖8529〗-安全帐户管理员需要获得启动密码。
〖8530〗-安全帐户管理员需要从软盘获得启动密钥。
〖8531〗-目录服务无法启动。
〖8532〗-未能启动目录服务。
〖8533〗-客户和服务器之间的连接要求数据包保密性。
〖8534〗-来源域跟目标域不在同一个目录林中。
〖8535〗-目标域必须在目录林中。
〖8536〗-该操作要求启用目标域审核。
〖8537〗-该操作无法为来源域找到DC。
〖8538〗-来源对象必须是一个组或用户。
〖8539〗-来源对象的SID 已经在目标目录林中。
〖8540〗-来源对象和目标对象必须属于同一类型。
〖8542〗-在复制请求中不能包括架构信息。
〖8543〗-由于架构不兼容性，无法完成复制操作。
〖8544〗-由于前一个架构的不兼容性，无法完成复制操作。
〖8545〗-因为源和目标都没有收到有关最近跨域启动操作的信息，所以无法应用复制更新。
〖8546〗-因为还有主控这个域的域控制器，所以无法删除请求的域。
〖8547〗-只能在全局编录服务器上执行请求的操作。
〖8548〗-本地组只能是同一个域中其他本地组的成员。
〖8549〗-外部安全主要成员不能是通用组的成员。
〖8550〗-出于安全，无法将属性复制到GC。
〖8551〗-由于目前正在处理的修改太多，无法采取PDC 的检查点。
〖8552〗-操作需要启用那个源域审核。
〖8553〗-安全主要对象仅能在域命名环境菜单中创建。
〖8554〗-服务主要名称(SPN) 无法建造，因为提供的主机名格式不适合。
〖8555〗-筛选器已传递建造的属性。
〖8556〗-unicodePwd 属性值必须括在双引号中。
〖8557〗-您的计算机无法加入域。已超出此域上允许创建的计算机帐户的最大值。请同系统管理员联系，复位或增加此限定值。
〖8558〗-由于安全原因，操作必须在目标DC 上运行。
〖8559〗-由于安全原因，源DC 必须是Service Pack 4 或更新版本。
〖8560〗-在树目录删除的操作中不能删除“关键目录服务系统”对象。数目录删除操作可能只进行了一部分。