Lift of error messages Code Detail

Lift of error messages Code Detail

Code Error Message
0 The operation completed successfully.
1 Incorrect function.
2 The system cannot find the file specified.
3 The system cannot find the path specified.
4 The system cannot open the file.
5 Access is denied.

continued

2519 A second connection to a Remoteboot resource is not allowed.
2550 The browser service was configured with MaintainServerList=No.
2610 Service failed to start since none of the network adapters started with this service.
2611 Service failed to start due to bad startup information in the registry.
2612 Service failed to start because its database is absent or corrupt.
2613 Service failed to start because RPLFILES share is absent.
2614 Service failed to start because RPLUSER group is absent.
2615 Cannot enumerate service records.
2616 Workstation record information has been corrupted.
2617 Workstation record was not found.
2618 Workstation name is in use by some other workstation.
2619 Profile record information has been corrupted.
2620 Profile record was not found.
2621 Profile name is in use by some other profile.
2622 There are workstations using this profile.
2623 Configuration record information has been corrupted.
2624 Configuration record was not found.
2625 Adapter id record information has been corrupted.
2626 An internal service error has occurred.
2627 Vendor id record information has been corrupted.
2628 Boot block record information has been corrupted.
2629 The user account for this workstation record is missing.
2630 The RPLUSER local group could not be found.
2631 Boot block record was not found.
2632 Chosen profile is incompatible with this workstation.
2633 Chosen network adapter id is in use by some other workstation.
2634 There are profiles using this configuration.
2635 There are workstations, profiles or configurations using this boot block.
2636 Service failed to backup Remoteboot database.
2637 Adapter record was not found.
2638 Vendor record was not found.
2639 Vendor name is in use by some other vendor record.
2640 (boot name, vendor id) is in use by some other boot block record.
2641 Configuration name is in use by some other configuration.
2660 The internal database maintained by the Dfs service is corrupt
2661 One of the records in the internal Dfs database is corrupt
2662 There is no volume whose entry path matches the input Entry Path
2663 A volume with the given name already exists
2664 The server share specified is already shared in the Dfs
2665 The indicated server share does not support the indicated Dfs volume
2666 The operation is not valid on a non-leaf volume
2667 The operation is not valid on a leaf volume
2668 The operation is ambiguous because the volume has multiple servers
2669 Unable to create a junction point
2670 The server is not Dfs Aware
2671 The specified rename target path is invalid
2672 The specified Dfs volume is offline
2673 The specified server is not a server for this volume
2674 A cycle in the Dfs name was detected
2675 The operation is not supported on a server-based Dfs
2676 This volume is already supported by the specified server-share
2677 Can't remove the last server-share supporting this volume
2678 The operation is not supported for an Inter-Dfs volume
2679 The internal state of the Dfs Service has become inconsistent
2680 The Dfs Service has been installed on the specified server
2681 The Dfs data being reconciled is identical
2682 The Dfs root volume cannot be deleted - Uninstall Dfs if required
2683 A child or parent directory of the share is already in a Dfs
2690 Dfs internal error
2691 This machine is already joined to a domain.
2692 This machine is not currently joined to a domain.
2693 This machine is a domain controller and cannot be unjoined from a domain.
2694 The destination domain controller does not support creating machine accounts in OUs.
2695 The specified workgroup name is invalid
2696 The specified computer name is incompatible with the default language used on the domain controller.
2697 The specified computer account could not be found.
2999 This is the last error in NERR range.
3000 The specified print monitor is unknown.
3001 The specified printer driver is currently in use.
3002 The spool file was not found.
3003 A StartDocPrinter call was not issued.
3004 An AddJob call was not issued.
3005 The specified print processor has already been installed.
3006 The specified print monitor has already been installed.
3007 The specified print monitor does not have the required functions.
3008 The specified print monitor is currently in use.
3009 The requested operation is not allowed when there are jobs queued to the printer.
3010 The requested operation is successful. Changes will not be effective until the system is rebooted.
3011 The requested operation is successful. Changes will not be effective until the service is restarted.
3012 No printers were found.
3023 There is a problem with a configuration of user specified shut down command file. The UPS service started anyway.
3029 Local security could not be started because the user accounts database (NET.ACC) was missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE.
3037 @I *LOGON HOURS
3039 Replicator limit for files in a directory has been exceeded.
3040 Replicator limit for tree depth has been exceeded.
3046 Cannot log on. User is currently logged on and argument TRYUSER is set to NO.
3052 The required parameter was not provided on the command line or in the configuration file.
3054 A request for resource could not be satisfied.
3055 A problem exists with the system configuration.
3056 A system error has occurred.
3057 An internal consistency error has occurred.
3058 The configuration file or the command line has an ambiguous option.
3059 The configuration file or the command line has a duplicate parameter.
3060 The service did not respond to control and was stopped with the DosKillProc function.
3061 An error occurred when attempting to run the service program.
3062 The sub-service failed to start.
3064 There is a problem with the file.
3070 memory
3071 disk space
3072 thread
3073 process
3074 Security Failure.
3075 Bad or missing LAN Manager root directory.
3076 The network software is not installed.
3077 The server is not started.
3078 The server cannot access the user accounts database (NET.ACC).
3079 Incompatible files are installed in the LANMAN tree.
3080 The LANMAN\LOGS directory is invalid.
3081 The domain specified could not be used.
3082 The computer name is being used as a message alias on another computer.
3083 The announcement of the server name failed.
3084 The user accounts database is not configured correctly.
3085 The server is not running with user-level security.
3087 The workstation is not configured properly.
3088 View your error log for details.
3089 Unable to write to this file.
3090 ADDPAK file is corrupted. Delete LANMAN\NETPROG\ADDPAK.SER and reapply all ADDPAKs.
3091 The LM386 server cannot be started because CACHE.EXE is not running.
3092 There is no account for this computer in the security database.
3093 This computer is not a member of the group SERVERS.
3094 The group SERVERS is not present in the local security database.
3095 This Windows NT computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration.
3096 The Windows NT domain controller for this domain could not be located.
3098 The service failed to authenticate with the primary domain controller.
3099 There is a problem with the security database creation date or serial number.
3100 The operation failed because a network software error occurred.
3102 The service failed to obtain a long-term lock on the segment for network control blocks (NCBs). The error code is the data.
3103 The service failed to release the long-term lock on the segment for network control blocks (NCBs). The error code is the data.
3106 An unexpected network control block (NCB) was received. The NCB is the data.
3107 The network is not started.
3108 A DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed. The data shown is in this format: DWORD approx CS:IP of call to ioctl or fsctl WORD error code WORD ioctl or fsctl number
3111 An unexpected NetBIOS error occurred. The error code is the data.
3112 An illegal server message block (SMB) was received. The SMB is the data.
3114 Some entries in the error log were lost because of a buffer overflow.
3120 Initialization parameters controlling resource usage other than net buffers are sized so that too much memory is needed.
3121 The server cannot increase the size of a memory segment.
3124 The server failed to start. Either all three chdev parameters must be zero or all three must be nonzero.
3129 The server cannot update the AT schedule file. The file is corrupted.
3130 The server encountered an error when calling NetIMakeLMFileName. The error code is the data.
3132 Longterm lock of the server buffers failed. Check swap disk's free space and restart the system to start the server.
3140 The service has stopped due to repeated consecutive occurrences of a network control block (NCB) error. The last bad NCB follows in raw data.
3141 The Message server has stopped due to a lock on the Message server shared data segment.
3151 Unable to display message POPUP due to system VIO call error. The error code is the data.
3152 An illegal server message block (SMB) was received. The SMB is the data.
3160 The workstation information segment is bigger than 64K. The size follows, in DWORD format:
3161 The workstation was unable to get the name-number of the computer.
3162 The workstation could not initialize the Async NetBIOS Thread. The error code is the data.
3163 The workstation could not open the initial shared segment. The error code is the data.
3164 The workstation host table is full.
3165 A bad mailslot server message block (SMB) was received. The SMB is the data.
3166 The workstation encountered an error while trying to start the user accounts database. The error code is the data.
3167 The workstation encountered an error while responding to an SSI revalidation request. The function code and the error codes are the data.
3174 The server could not read the AT schedule file.
3175 The server found an invalid AT schedule record.
3176 The server could not find an AT schedule file so it created one.
3185 Local security could not be started because the user accounts database (NET.ACC) was missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE.
3204 The server could not create a thread. The THREADS parameter in the CONFIG.SYS file should be increased.
3213 Replicator limit for files in a directory has been exceeded.
3214 Replicator limit for tree depth has been exceeded.
3215 Unrecognized message received in mailslot.
3217 Cannot log on. User is currently logged on and argument TRYUSER is set to NO.
3230 A power failure was detected at the server.
3231 The UPS service performed server shut down.
3232 The UPS service did not complete execution of the user specified shut down command file.
3233 The UPS driver could not be opened. The error code is the data.
3234 Power has been restored.
3235 There is a problem with a configuration of user specified shut down command file.
3256 There was an unrecoverable error in the dynamic- link library of the service.
3257 The system returned an unexpected error code. The error code is the data.
3258 The fault-tolerance error log file, LANROOT\LOGS\FT.LOG, is more than 64K.
3259 The fault-tolerance error-log file, LANROOT\LOGS\FT.LOG, had the update in progress bit set upon opening, which means that the system crashed while working on the error log.
3301 Remote IPC
3302 Remote Admin
3303 Logon server share
3304 A network error occurred.
3400 There is not enough memory to start the Workstation service.
3401 An error occurred when reading the NETWORKS entry in the LANMAN.INI file.
3404 There are too many NETWORKS entries in the LANMAN.INI file.
3408 The program cannot be used with this operating system.
3409 The redirector is already installed.
3411 There was an error installing NETWKSTA.SYS. Press ENTER to continue.
3412 Resolver linkage problem.
3419 You have open files or devices, and a forced disconnection may cause you to lose data.
3420 Default Share for Internal Use
3421 Messenger Service
3500 The command completed successfully.
3501 You used an invalid option.
3503 The command contains an invalid number of arguments.
3504 The command completed with one or more errors.
3505 You used an option with an invalid value.
3510 A command was used with conflicting switches.
3512 The software requires a newer version of the operating system.
3513 More data is available than can be returned by Windows 2000.
3515 This command can be used only on a Windows 2000 Domain Controller.
3516 This command cannot be used on a Windows 2000 Domain Controller.
3520 These Windows 2000 services are started:
3525 Stopping the Workstation service also stops the Server service.
3526 The workstation has open files.
3533 The service is starting or stopping. Please try again later.
3534 The service did not report an error.
3535 An error occurred controlling the device.
3660 These workstations have sessions on this server:
3661 These workstations have sessions with open files on this server:
3666 The message alias is forwarded.
3670 You have these remote connections:
3671 Continuing will cancel the connections.
3676 New connections will be remembered.
3677 New connections will not be remembered.
3678 An error occured while saving your profile. The state of your remembered connections has not changed.
3679 An error occured while reading your profile.
3682 No network services are started.
3683 There are no entries in the list.
3689 The Workstation service is already running. Windows 2000 will ignore command options for the workstation.
3694 The shared queue cannot be deleted while a print job is being spooled to the queue.
3710 An error occurred while opening the Help file.
3711 The Help file is empty.
3712 The Help file is corrupted.
3714 This operation is privileged on systems with earlier versions of the software.
3716 The device type is unknown.
3717 The log file has been corrupted.
3718 Program filenames must end with .EXE.
3719 A matching share could not be found so nothing was deleted.
3720 A bad value is in the units-per-week field of the user record.
3725 An error occurred when the share was deleted.
3726 The user name is invalid.
3727 The password is invalid.
3728 The passwords do not match.
3729 Your persistent connections were not all restored.
3730 This is not a valid computer name or domain name.
3732 Default permissions cannot be set for that resource.
3734 A valid password was not entered.
3735 A valid name was not entered.
3736 The resource named cannot be shared.
3737 The permissions string contains invalid permissions.
3738 You can only perform this operation on printers and communication devices.
3743 The server is not configured for remote administration.
3752 No users have sessions with this server.
3756 This is an invalid response.
3757 No valid response was provided.
3758 The destination list provided does not match the destination list of the printer queue.
3761 The time range specified ends before it starts.
3764 Time supplied is not exactly on the hour.
3765 12 and 24 hour time formats may not be mixed.
3767 An illegal date format has been supplied.
3768 An illegal day range has been supplied.
3769 An illegal time range has been supplied.
3770 Arguments to NET USER are invalid. Check the minimum password length and/or arguments supplied.
3771 The value for ENABLESCRIPT must be YES.
3773 An illegal country code has been supplied.
3774 The user was successfully created but could not be added to the USERS local group.
3775 The user context supplied is invalid.
3777 Sending files is no longer supported.
3778 You may not specify paths for ADMIN$ and IPC$ shares.
3784 Only disk shares can be marked as cacheable
3802 This schedule date is invalid.
3803 The LANMAN root directory is unavailable.
3804 The SCHED.LOG file could not be opened.
3805 The Server service has not been started.
3806 The AT job ID does not exist.
3807 The AT schedule file is corrupted.
3808 The delete failed due to a problem with the AT schedule file.
3809 The command line cannot exceed 259 characters.
3810 The AT schedule file could not be updated because the disk is full.
3812 The AT schedule file is invalid. Please delete the file and create a new one.
3813 The AT schedule file was deleted.
3814 The syntax of this command is: AT [id] [/DELETE] AT time [/EVERY:date | /NEXT:date] command The AT command schedules a program command to run at a later date and time on a server. It also displays the list of programs and commands scheduled to be run.
3815 The AT command has timed-out. Please try again later.
3816 The minimum password age for user accounts cannot be greater than the maximum password age.
3817 You have specified a value that is incompatible with servers with down-level software. Please specify a lower value.
3901 ****
3902 **** unexpected end of message ****
3905 Press ESC to exit
3906 ...
3912 Could not locate a time-server.
3915 The user's home directory could not be determined.
3916 The user's home directory has not been specified.
3920 There are no available drive letters left.
3936 This computer is not currently configured to use a specific SNTP server.
3953 The syntax is incorrect.
3960 You specified an invalid file number.
3961 You specified an invalid print job number.
3963 The user or group account specified cannot be found.
3965 The user was added but could not be enabled for File and Print Services for NetWare.
3966 File and Print Services for NetWare is not installed.
3967 Cannot set user properties for File and Print Services for NetWare.
3969 NetWare compatible logon
4000 WINS encountered an error while processing the command.
4001 The local WINS can not be deleted.
4002 The importation from the file failed.
4003 The backup failed. Was a full backup done before?
4004 The backup failed. Check the directory to which you are backing the database.
4005 The name does not exist in the WINS database.
4006 Replication with a nonconfigured partner is not allowed.
4100 The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.
4200 The GUID passed was not recognized as valid by a WMI data provider.
4201 The instance name passed was not recognized as valid by a WMI data provider.
4202 The data item ID passed was not recognized as valid by a WMI data provider.
4203 The WMI request could not be completed and should be retried.
4204 The WMI data provider could not be located.
4205 The WMI data provider references an instance set that has not been registered.
4206 The WMI data block or event notification has already been enabled.
4207 The WMI data block is no longer available.
4208 The WMI data service is not available.
4209 The WMI data provider failed to carry out the request.
4210 The WMI MOF information is not valid.
4211 The WMI registration information is not valid.
4212 The WMI data block or event notification has already been disabled.
4213 The WMI data item or data block is read only.
4214 The WMI data item or data block could not be changed.
4300 The media identifier does not represent a valid medium.
4301 The library identifier does not represent a valid library.
4302 The media pool identifier does not represent a valid media pool.
4303 The drive and medium are not compatible or exist in different libraries.
4304 The medium currently exists in an offline library and must be online to perform this operation.
4305 The operation cannot be performed on an offline library.
4306 The library, drive, or media pool is empty.
4307 The library, drive, or media pool must be empty to perform this operation.
4308 No media is currently available in this media pool or library.
4309 A resource required for this operation is disabled.
4310 The media identifier does not represent a valid cleaner.
4311 The drive cannot be cleaned or does not support cleaning.
4312 The object identifier does not represent a valid object.
4313 Unable to read from or write to the database.
4314 The database is full.
4315 The medium is not compatible with the device or media pool.
4316 The resource required for this operation does not exist.
4317 The operation identifier is not valid.
4318 The media is not mounted or ready for use.
4319 The device is not ready for use.
4320 The operator or administrator has refused the request.
4321 The drive identifier does not represent a valid drive.
4322 Library is full. No slot is available for use.
4323 The transport cannot access the medium.
4324 Unable to load the medium into the drive.
4325 Unable to retrieve the drive status.
4326 Unable to retrieve the slot status.
4327 Unable to retrieve status about the transport.
4328 Cannot use the transport because it is already in use.
4329 Unable to open or close the inject/eject port.
4330 Unable to eject the medium because it is in a drive.
4331 A cleaner slot is already reserved.
4332 A cleaner slot is not reserved.
4333 The cleaner cartridge has performed the maximum number of drive cleanings.
4334 Unexpected on-medium identifier.
4335 The last remaining item in this group or resource cannot be deleted.
4336 The message provided exceeds the maximum size allowed for this parameter.
4337 The volume contains system or paging files.
4338 The media type cannot be removed from this library since at least one drive in the library reports it can support this media type.
4339 This offline media cannot be mounted on this system since no enabled drives are present which can be used.
4340 (Y/N) [Y]
4341 (Y/N) [N]
4342 Error
4343 OK
4344 Y
4345 N
4346 Any
4347 A
4348 P
4349 (not found)
4350 The remote storage service was not able to recall the file.
4351 The remote storage service is not operational at this time.
4352 The remote storage service encountered a media error.
4354 Please type the password:
4358 Type a password for the user:
4359 Type the password for the shared resource:
4360 Type your password:
4361 Retype the password to confirm:
4362 Type the user's old password:
4363 Type the user's new password:
4364 Type your new password:
4365 Type the Replicator service password:
4368 Type your user name:
4372 Print job detail
4378 The following running services can be controlled:
4379 Statistics are available for the following running services:
4381 The syntax of this command is:
4382 The options of this command are:
4383 Please enter the name of the Primary Domain Controller:
4385 Sunday
4386 Monday
4387 Tuesday
4388 Wednesday
4389 Thursday
4390 The file or directory is not a reparse point.
4391 The reparse point attribute cannot be set because it conflicts with an existing attribute.
4392 The data present in the reparse point buffer is invalid.
4393 The tag present in the reparse point buffer is invalid.
4394 There is a mismatch between the tag specified in the request and the tag present in the reparse point.
4395 W
4396 Th
4397 F
4398 S
4399 Sa
4401 Group name
4402 Comment
4403 Members
4406 Alias name
4407 Comment
4408 Members
4411 User name
4412 Full Name
4413 Comment
4414 User's comment
4415 Parameters
4416 Country code
4417 Privilege level
4418 Operator privileges
4419 Account active
4420 Account expires
4421 Password last set
4422 Password expires
4423 Password changeable
4424 Workstations allowed
4425 Maximum disk space
4426 Unlimited
4427 Local Group Memberships
4428 Domain controller
4429 Logon script
4430 Last logon
4431 Global Group memberships
4432 Logon hours allowed
4433 All
4434 None
4436 Home directory
4437 Password required
4438 User may change password
4439 User profile
4440 Locked
4450 Computer name
4451 User name
4452 Software version
4453 Workstation active on
4454 Windows NT root directory
4455 Workstation domain
4456 Logon domain
4457 Other domain(s)
4458 COM Open Timeout (sec)
4459 COM Send Count (byte)
4460 COM Send Timeout (msec)
4461 DOS session print time-out (sec)
4462 Maximum error log size 
4463 Maximum cache memory 
4464 Number of network buffers
4465 Number of character buffers
4466 Size of network buffers
4467 Size of character buffers
4468 Full Computer name
4469 Workstation Domain DNS Name
4470 Windows 2000
4481 Server Name
4482 Server Comment
4483 Send administrative alerts to
4484 Software version
4485 Peer Server
4486 Windows NT
4487 Server Level
4488 Windows NT Server
4489 Server is active on
4492 Server hidden
4500 Single Instance Storage is not available on this volume.
4506 Maximum Logged On Users
4507 Maximum concurrent administrators
4508 Maximum resources shared
4509 Maximum connections to resources
4510 Maximum open files on server
4511 Maximum open files per session
4512 Maximum file locks
4520 Idle session time (min)
4526 Share-level
4527 User-level
4530 Unlimited Server
4570 Force user logoff how long after time expires?:
4571 Lock out account after how many bad passwords?:
4572 Minimum password age (days):
4573 Maximum password age (days):
4574 Minimum password length:
4575 Length of password history maintained:
4576 Computer role:
4577 Primary Domain controller for workstation domain:
4578 Lockout threshold:
4579 Lockout duration (minutes):
4580 Lockout observation window (minutes):
4600 Statistics since
4601 Sessions accepted
4602 Sessions timed-out
4603 Sessions errored-out
4604 Kilobytes sent
4605 Kilobytes received
4606 Mean response time (msec)
4607 Network errors
4608 Files accessed
4609 Print jobs spooled
4610 System errors
4611 Password violations
4612 Permission violations
4613 Communication devices accessed
4614 Sessions started
4615 Sessions reconnected
4616 Sessions starts failed
4617 Sessions disconnected
4618 Network I/O's performed
4619 Files and pipes accessed
4620 Times buffers exhausted
4621 Big buffers
4622 Request buffers
4626 Connections made
4627 Connections failed
4630 Bytes received
4631 Server Message Blocks (SMBs) received
4632 Bytes transmitted
4633 Server Message Blocks (SMBs) transmitted
4634 Read operations
4635 Write operations
4636 Raw reads denied
4637 Raw writes denied
4638 Network errors
4639 Connections made
4640 Reconnections made
4641 Server disconnects
4642 Sessions started
4643 Hung sessions
4644 Failed sessions
4645 Failed operations
4646 Use count
4647 Failed use count
4655 The message name forwarding was successfully canceled.
4661 The password was changed successfully.
4664 The message was successfully sent to all users of the network.
4666 The message was successfully sent to all users of this server.
4696 Windows NT Server
4697 Windows NT Workstation
4698 MS-DOS Enhanced Workstation
4700 Server Name Remark
4701 Share name Type Used as Comment
4702 (UNC)
4703 ...
4704 Domain
4706 Other available networks are:
4710 Disk
4711 Print
4712 Comm
4713 IPC
4714 Status Local Remote Network
4715 OK
4716 Dormant
4717 Paused
4718 Disconnected
4719 Error
4720 Connecting
4721 Reconnecting
4722 Status
4723 Local name
4724 Remote name
4725 Resource type
4726 # Opens
4727 # Connections
4728 Unavailable
4730 Share name Resource Remark
4731 Share name
4732 Resource
4733 Spooled
4734 Permission
4735 Maximum users
4736 No limit
4737 Users
4740 ID Path User name # Locks
4741 File ID
4742 Locks
4743 Permissions
4750 Computer User name Client Type Opens Idle time
4751 Computer
4752 Sess time
4753 Idle time
4754 Share name Type # Opens
4755 Client type
4756 Guest logon
4770 Offline cache enabled: manual restore
4771 Offline cache enabled: automatic restore
4772 Offline cache enabled: no sharing among users
4773 Offline cache disabled
4774 Automatic
4775 Manual
4800 Name
4801 Forwarded to
4802 Forwarded to you from
4803 Users of this server
4804 Net Send has been interrupted by a Ctrl+Break from the user.
4810 Name Job # Size Status
4811 jobs
4812 Print
4813 Name
4814 Job #
4815 Size
4816 Status
4817 Separator file
4818 Comment
4819 Priority
4820 Print after
4821 Print until
4822 Print processor
4823 Additional info
4824 Parameters
4825 Print Devices
4826 Printer Active
4827 Printer held
4828 Printer error
4829 Printer being deleted
4830 Printer status unknown
4841 Job #
4842 Submitting user
4843 Notify
4844 Job data type
4845 Job parameters
4846 Waiting
4847 Held in queue
4848 Spooling
4849 Paused
4850 Offline
4851 Error
4852 Out of paper
4853 Intervention required
4854 Printing
4855 on
4862 Driver
4930 User name Type Date
4931 Lockout
4932 Service
4933 Server
4934 Server started
4935 Server paused
4936 Server continued
4937 Server stopped
4938 Session
4939 Logon Guest
4940 Logon User
4941 Logon Administrator
4942 Logoff normal
4943 Logon
4944 Logoff error
4945 Logoff auto-disconnect
4946 Logoff administrator-disconnect
4947 Logoff forced by logon restrictions
4948 Service
4957 Account
4964 Account system settings were modified
4965 Logon restriction
4966 Limit exceeded: UNKNOWN
4967 Limit exceeded: Logon hours
4968 Limit exceeded: Account expired
4969 Limit exceeded: Workstation ID invalid
4970 Limit exceeded: Account disabled
4971 Limit exceeded: Account deleted
4972 Share
4978 Bad password
4979 Administrator privilege required
4980 Access
4984 Access denied
4985 Unknown
4986 Other
4987 Duration:
4988 Duration: Not available
4989 Duration: Less than one second
4990 (none)
4994 Access ended
4995 Log on to network
4996 Logon denied
4997 Program Message Time
4999 Account unlocked by administrator
5000 Log off network
5001 The cluster resource cannot be moved to another group because other resources are dependent on it.
5002 The cluster resource dependency cannot be found.
5003 The cluster resource cannot be made dependent on the specified resource because it is already dependent.
5004 The cluster resource is not online.
5005 A cluster node is not available for this operation.
5006 The cluster resource is not available.
5007 The cluster resource could not be found.
5008 The cluster is being shut down.
5009 A cluster node cannot be evicted from the cluster while it is online.
5010 The object already exists.
5011 The object is already in the list.
5012 The cluster group is not available for any new requests.
5013 The cluster group could not be found.
5014 The operation could not be completed because the cluster group is not online.
5015 The cluster node is not the owner of the resource.
5016 The cluster node is not the owner of the group.
5017 The cluster resource could not be created in the specified resource monitor.
5018 The cluster resource could not be brought online by the resource monitor.
5019 The operation could not be completed because the cluster resource is online.
5020 The cluster resource could not be deleted or brought offline because it is the quorum resource.
5021 The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.
5022 The cluster software is shutting down.
5023 The group or resource is not in the correct state to perform the requested operation.
5024 The properties were stored but not all changes will take effect until the next time the resource is brought online.
5025 The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.
5026 The cluster resource could not be deleted since it is a core resource.
5027 The quorum resource failed to come online.
5028 The quorum log could not be created or mounted successfully.
5029 The cluster log is corrupt.
5030 The record could not be written to the cluster log since it exceeds the maximum size.
5031 The cluster log exceeds its maximum size.
5032 No checkpoint record was found in the cluster log.
5033 The minimum required disk space needed for logging is not available.
5034 The cluster node failed to take control of the quorum resource because the resource is owned by another active node.
5035 A cluster network is not available for this operation.
5036 A cluster node is not available for this operation.
5037 All cluster nodes must be running to perform this operation.
5038 A cluster resource failed.
5039 The cluster node is not valid.
5040 The cluster node already exists.
5041 A node is in the process of joining the cluster.
5042 The cluster node was not found.
5043 The cluster local node information was not found.
5044 The cluster network already exists.
5045 The cluster network was not found.
5046 The cluster network interface already exists.
5047 The cluster network interface was not found.
5048 The cluster request is not valid for this object.
5049 The cluster network provider is not valid.
5050 The cluster node is down.
5051 The cluster node is not reachable.
5052 The cluster node is not a member of the cluster.
5053 A cluster join operation is not in progress.
5054 The cluster network is not valid.
5055 Mar
5056 The cluster node is up.
5057 The cluster IP address is already in use.
5058 The cluster node is not paused.
5059 No cluster security context is available.
5060 The cluster network is not configured for internal cluster communication.
5061 The cluster node is already up.
5062 The cluster node is already down.
5063 The cluster network is already online.
5064 The cluster network is already offline.
5065 The cluster node is already a member of the cluster.
5066 The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.
5067 One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
5068 This operation cannot be performed on the cluster resource as it the quorum resource. You may not bring the quorum resource offline or modify its possible owners list.
5069 The cluster quorum resource is not allowed to have any dependencies.
5070 The cluster node is paused.
5071 The cluster resource cannot be brought online. The owner node cannot run this resource.
5072 The cluster node is not ready to perform the requested operation.
5073 The cluster node is shutting down.
5074 The cluster join operation was aborted.
5075 The cluster join operation failed due to incompatible software versions between the joining node and its sponsor.
5076 This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.
5077 The system configuration changed during the cluster join or form operation. The join or form operation was aborted.
5078 The specified resource type was not found.
5079 The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
5080 The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.
5081 No authentication package could be registered with the RPC server.
5082 You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.
5083 The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.
5084 The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.
5085 A non locker code got a request to reserve the lock for making global updates.
5086 The quorum disk could not be located by the cluster service.
5087 The backed up cluster database is possibly corrupt.
5088 A DFS root already exists in this cluster node.
5089 An attempt to modify a resource property failed because it conflicts with another existing property.
5090 Spain
5091 Denmark
5092 Sweden
5093 Norway
5094 Germany
5095 Australia
5096 Japan
5097 Korea
5098 China (PRC)
5099 Taiwan
5100 Asia
5101 Portugal
5102 Finland
5103 Arabic
5104 Hebrew
5153 The UPS service is about to perform final shut down.
5170 The Workstation must be started with the NET START command.
5175 Remote IPC
5176 Remote Admin
5177 Default share
5291 Never
5292 Never
5293 Never
5295 NET.HLP
5296 NET.HLP
5300 The network control block (NCB) request completed successfully. The NCB is the data.
5301 Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS. The NCB is the data.
5302 The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the data.
5303 The command specified in the network control block (NCB) is illegal. The NCB is the data.
5304 The message correlator specified in the network control block (NCB) is invalid. The NCB is the data.
5305 A network control block (NCB) command timed-out. The session may have terminated abnormally. The NCB is the data.
5306 An incomplete network control block (NCB) message was received. The NCB is the data.
5307 The buffer address specified in the network control block (NCB) is illegal. The NCB is the data.
5308 The session number specified in the network control block (NCB) is not active. The NCB is the data.
5309 No resource was available in the network adapter. The network control block (NCB) request was refused. The NCB is the data.
5310 The session specified in the network control block (NCB) was closed. The NCB is the data.
5311 The network control block (NCB) command was canceled. The NCB is the data.
5312 The message segment specified in the network control block (NCB) is illogical. The NCB is the data.
5313 The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is the data.
5314 The network adapter name table is full. The network control block (NCB) request was refused. The NCB is the data.
5315 The network name has active sessions and is now de-registered. The network control block (NCB) command completed. The NCB is the data.
5316 A previously issued Receive Lookahead command is active for this session. The network control block (NCB) command was rejected. The NCB is the data.
5317 The local session table is full. The network control block (NCB) request was refused. The NCB is the data.
5318 A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the data.
5319 The name number specified in the network control block (NCB) is illegal. The NCB is the data.
5320 The call name specified in the network control block (NCB) cannot be found or did not answer. The NCB is the data.
5321 The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the data.
5322 The name specified in the network control block (NCB) is in use on a remote adapter. The NCB is the data.
5323 The name specified in the network control block (NCB) has been deleted. The NCB is the data.
5324 The session specified in the network control block (NCB) ended abnormally. The NCB is the data.
5325 The network protocol has detected two or more identical names on the network. The network control block (NCB) is the data.
5326 An unexpected protocol packet was received. There may be an incompatible remote device. The network control block (NCB) is the data.



5333 The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB is the data.
5334 There are too many network control block (NCB) commands outstanding. The NCB request was refused. The NCB is the data.
5335 The adapter number specified in the network control block (NCB) is illegal. The NCB is the data.
5336 The network control block (NCB) command completed while a cancel was occurring. The NCB is the data.
5337 The name specified in the network control block (NCB) is reserved. The NCB is the data.
5338 The network control block (NCB) command is not valid to cancel. The NCB is the data.
5351 There are multiple network control block (NCB) requests for the same session. The NCB request was refused. The NCB is the data.
5352 There has been a network adapter error. The only NetBIOS command that may be issued is an NCB RESET. The network control block (NCB) is the data.
5354 The maximum number of applications was exceeded. The network control block (NCB) request was refused. The NCB is the data.
5356 The requested resources are not available. The network control block (NCB) request was refused. The NCB is the data.
5364 A system error has occurred. The network control block (NCB) request was refused. The NCB is the data.
5365 A ROM checksum failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5366 A RAM test failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5367 A digital loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5368 An analog loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5369 An interface failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5370 An unrecognized network control block (NCB) return code was received. The NCB is the data.
5380 A network adapter malfunction has occurred. The network control block (NCB) request was refused. The NCB is the data.
5381 The network control block (NCB) command is still pending. The NCB is the data.
5509 Windows 2000 could not be started as configured. A previous working configuration was used instead.
5600 Could not share the User or Script path.
5601 The password for this computer is not found in the local security database.
5602 An internal error occurred while accessing the computer's local or network security database.
5705 The change log cache maintained by the Netlogon service for database changes is corrupted. The Netlogon service is resetting the change log.
5728 Could not load any transport.
5739 This domain has more global groups than can be replicated to a LanMan BDC. Either delete some of your global groups or remove the LanMan BDCs from the domain.
5742 Service failed to retrieve messages needed to boot remote boot clients.
5743 Service experienced a severe error and can no longer provide remote boot for 3Com 3Start remote boot clients.
5744 Service experienced a severe system error and will shut itself down.
5760 Service experienced error evaluating RPL configurations.
5761 Service experienced error creating RPL profiles for all configurations.
5762 Service experienced error accessing registry.
5763 Service experienced error replacing possibly outdated RPLDISK.SYS.
5764 Service experienced error adding security accounts or setting file permissions. These accounts are the RPLUSER local group and the user accounts for the individual RPL workstations.
5765 Service failed to back up its database.
5766 Service failed to initialize from its database. The database may be missing or corrupted. Service will attempt restoring the database from the backup.
5767 Service failed to restore its database from the backup. Service will not start.
5768 Service sucessfully restored its database from the backup.
5769 Service failed to initialize from its restored database. Service will not start.
5771 The Remoteboot database was in NT 3.5 / NT 3.51 format and NT is attempting to convert it to NT 4.0 format. The JETCONV converter will write to the Application event log when it is finished.
5773 The DNS server for this DC does not support dynamic DNS. Add the DNS records from the file 'SystemRoot\System32\Config\netlogon.dns' to the DNS server serving the domain referenced in that file.
5781 Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.
6000 The specified file could not be encrypted.
6001 The specified file could not be decrypted.
6002 The specified file is encrypted and the user does not have the ability to decrypt it.
6003 There is no valid encryption recovery policy configured for this system.
6004 The required encryption driver is not loaded for this system.
6005 The file was encrypted with a different encryption driver than is currently loaded.
6006 There are no EFS keys defined for the user.
6007 The specified file is not encrypted.
6008 The specified file is not in the defined EFS export format.
6009 The specified file is read only.
6010 The directory has been disabled for encryption.
6011 The server is not trusted for remote encryption operation.
6118 The list of servers for this workgroup is not currently available
6200 The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts.
7001 The specified session name is invalid.
7002 The specified protocol driver is invalid.
7003 The specified protocol driver was not found in the system path.
7004 The specified terminal connection driver was not found in the system path.
7005 A registry key for event logging could not be created for this session.
7006 A service with the same name already exists on the system.
7007 A close operation is pending on the session.
7008 There are no free output buffers available.
7009 The MODEM.INF file was not found.
7010 The modem name was not found in MODEM.INF.
7011 The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.
7012 The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.
7013 Carrier detect has failed or carrier has been dropped due to disconnect.
7014 Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.
7015 Busy signal detected at remote site on callback.
7016 Voice detected at remote site on callback.
7017 Transport driver error
7022 The specified session cannot be found.
7023 The specified session name is already in use.
7024 The requested operation cannot be completed because the terminal connection is currently busy processing a connect, disconnect, reset, or delete operation.
7025 An attempt has been made to connect to a session whose video mode is not supported by the current client.
7035 The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.
7037 Your interactive logon privilege has been disabled. Please contact your administrator.
7038 The requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access.
7040 The client failed to respond to the server connect message.
7041 Disconnecting the console session is not supported.
7042 Reconnecting a disconnected session to the console is not supported.
7044 The request to control another session remotely was denied.
7045 The requested session access is denied.
7049 The specified terminal connection driver is invalid.
7050 The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on. Also, you cannot control a session remotely from the system console or control the system console remotely. A
7051 The requested session is not configured to allow remote control.
7052 Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a new copy of the Terminal Server client with a valid, u
7053 Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please call your system administrator for help in entering a valid, unique lice
7054 The system has reached its licensed logon limit. Please try again later.
7055 The client you are using is not licensed to use this system. Your logon request is denied.
7056 The system license has expired. Your logon request is denied.
8001 The file replication service API was called incorrectly.
8002 The file replication service cannot be started.
8003 The file replication service cannot be stopped.
8004 The file replication service API terminated the request. The event log may have more information.
8005 The file replication service terminated the request. The event log may have more information.
8006 The file replication service cannot be contacted. The event log may have more information.
8007 The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information.
8008 The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.
8009 The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information.
8010 The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information.
8011 The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information.
8012 The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information.
8013 The file replication service cannot populate the system volume because of an internal error. The event log may have more information.
8014 The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information.
8015 The file replication service cannot process the request. The system volume is busy with a previous request.
8016 The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information.
8017 The file replication service detected an invalid parameter.
8200 An error occurred while installing the directory service. For more information, see the event log.
8201 The directory service evaluated group memberships locally.
8202 The specified directory service attribute or value does not exist.
8203 The attribute syntax specified to the directory service is invalid.
8204 The attribute type specified to the directory service is not defined.
8205 The specified directory service attribute or value already exists.
8206 The directory service is busy.
8207 The directory service is unavailable.
8208 The directory service was unable to allocate a relative identifier.
8209 The directory service has exhausted the pool of relative identifiers.
8210 The requested operation could not be performed because the directory service is not the master for that type of operation.
8211 The directory service was unable to initialize the subsystem that allocates relative identifiers.
8212 The requested operation did not satisfy one or more constraints associated with the class of the object.
8213 The directory service can perform the requested operation only on a leaf object.
8214 The directory service cannot perform the requested operation on the RDN attribute of an object.
8215 The directory service detected an attempt to modify the object class of an object.
8216 The requested cross-domain move operation could not be performed.
8217 Unable to contact the global catalog server.
8218 The policy object is shared and can only be modified at the root.
8219 The policy object does not exist.
8220 The requested policy information is only in the directory service.
8221 A domain controller promotion is currently active.
8222 A domain controller promotion is not currently active
8224 An operations error occurred.
8225 A protocol error occurred.
8226 The time limit for this request was exceeded.
8227 The size limit for this request was exceeded.
8228 The administrative limit for this request was exceeded.
8229 The compare response was false.
8230 The compare response was true.
8231 The requested authentication method is not supported by the server.
8232 A more secure authentication method is required for this server.
8233 Inappropriate authentication.
8234 The authentication mechanism is unknown.
8235 A referral was returned from the server.
8236 The server does not support the requested critical extension.
8237 This request requires a secure connection.
8238 Inappropriate matching.
8239 A constraint violation occurred.
8240 There is no such object on the server.
8241 There is an alias problem.
8242 An invalid dn syntax has been specified.
8243 The object is a leaf object.
8244 There is an alias dereferencing problem.
8245 The server is unwilling to process the request.
8246 A loop has been detected.
8247 There is a naming violation.
8248 The result set is too large.
8249 The operation affects multiple DSAs
8250 The server is not operational.
8251 A local error has occurred.
8252 An encoding error has occurred.
8253 A decoding error has occurred.
8254 The search filter cannot be recognized.
8255 One or more parameters are illegal.
8256 The specified method is not supported.
8257 No results were returned.
8258 The specified control is not supported by the server.
8259 A referral loop was detected by the client.
8260 The preset referral limit was exceeded.
8301 The root object must be the head of a naming context. The root object cannot have an instantiated parent.
8302 The add replica operation cannot be performed. The naming context must be writable in order to create the replica.
8303 A reference to an attribute that is not defined in the schema occurred.
8304 The maximum size of an object has been exceeded.
8305 An attempt was made to add an object to the directory with a name that is already in use.
8306 An attempt was made to add an object of a class that does not have an RDN defined in the schema.
8307 An attempt was made to add an object using an RDN that is not the RDN defined in the schema.
8308 None of the requested attributes were found on the objects.
8309 The user buffer is too small.
8310 The attribute specified in the operation is not present on the object.
8311 Illegal modify operation. Some aspect of the modification is not permitted.
8312 The specified object is too large.
8313 The specified instance type is not valid.
8314 The operation must be performed at a master DSA.
8315 The object class attribute must be specified.
8316 A required attribute is missing.
8317 An attempt was made to modify an object to include an attribute that is not legal for its class.
8318 The specified attribute is already present on the object.
8320 The specified attribute is not present, or has no values.
8321 Mutliple values were specified for an attribute that can have only one value.
8322 A value for the attribute was not in the acceptable range of values.
8323 The specified value already exists.
8324 The attribute cannot be removed because it is not present on the object.
8325 The attribute value cannot be removed because it is not present on the object.
8326 The specified root object cannot be a subref.
8327 Chaining is not permitted.
8328 Chained evaluation is not permitted.
8329 The operation could not be performed because the object's parent is either uninstantiated or deleted.
8330 Having a parent that is an alias is not permitted. Aliases are leaf objects.
8331 The object and parent must be of the same type, either both masters or both replicas.
8332 The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object.
8333 Directory object not found.
8334 The aliased object is missing.
8335 The object name has bad syntax.
8336 It is not permitted for an alias to refer to another alias.
8337 The alias cannot be dereferenced.
8338 The operation is out of scope.
8340 The DSA object cannot be deleted.
8341 A directory service error has occurred.
8342 The operation can only be performed on an internal master DSA object.
8343 The object must be of class DSA.
8344 Insufficient access rights to perform the operation.
8345 The object cannot be added because the parent is not on the list of possible superiors.
8346 Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM).
8347 The name has too many parts.
8348 The name is too long.
8349 The name value is too long.
8350 The directory service encountered an error parsing a name.
8351 The directory service cannot get the attribute type for a name.
8352 The name does not identify an object; the name identifies a phantom.
8353 The security descriptor is too short.
8354 The security descriptor is invalid.
8355 Failed to create name for deleted object.
8356 The parent of a new subref must exist.
8357 The object must be a naming context.
8358 It is not permitted to add an attribute which is owned by the system.
8359 The class of the object must be structural; you cannot instantiate an abstract class.
8360 The schema object could not be found.
8361 A local object with this GUID (dead or alive) already exists.
8362 The operation cannot be performed on a back link.
8363 The cross reference for the specified naming context could not be found.
8364 The operation could not be performed because the directory service is shutting down.
8365 The directory service request is invalid.
8366 The role owner attribute could not be read.
8367 The requested FSMO operation failed. The current FSMO holder could not be contacted.
8368 Modification of a DN across a naming context is not permitted.
8369 The attribute cannot be modified because it is owned by the system.
8370 Only the replicator can perform this function.
8371 The specified class is not defined.
8372 The specified class is not a subclass.
8373 The name reference is invalid.
8374 A cross reference already exists.
8375 It is not permitted to delete a master cross reference.
8376 Subtree notifications are only supported on NC heads.
8377 Notification filter is too complex.
8378 Schema update failed: duplicate RDN.
8379 Schema update failed: duplicate OID.
8380 Schema update failed: duplicate MAPI identifier.
8381 Schema update failed: duplicate schema-id GUID.
8382 Schema update failed: duplicate LDAP display name.
8383 Schema update failed: range-lower less than range upper.
8384 Schema update failed: syntax mismatch.
8385 Schema deletion failed: attribute is used in must-contain.
8386 Schema deletion failed: attribute is used in may-contain.
8387 Schema update failed: attribute in may-contain does not exist.
8388 Schema update failed: attribute in must-contain does not exist.
8389 Schema update failed: class in aux-class list does not exist or is not an auxiliary class.
8390 Schema update failed: class in poss-superiors does not exist.
8391 Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules.
8392 Schema update failed: Rdn-Att-Id has wrong syntax.
8393 Schema deletion failed: class is used as auxiliary class.
8394 Schema deletion failed: class is used as sub class.
8395 Schema deletion failed: class is used as poss superior.
8396 Schema update failed in recalculating validation cache.
8397 The tree deletion is not finished. The request must be made again to continue deleting the tree.
8398 The requested delete operation could not be performed.
8399 Cannot read the governs class identifier for the schema record.
8400 The attribute schema has bad syntax.
8401 The attribute could not be cached.
8402 The class could not be cached.
8403 The attribute could not be removed from the cache.
8404 The class could not be removed from the cache.
8405 The distinguished name attribute could not be read.
8406 A required subref is missing.
8407 The instance type attribute could not be retrieved.
8408 An internal error has occurred.
8409 A database error has occurred.
8410 The attribute GOVERNSID is missing.
8411 An expected attribute is missing.
8412 The specified naming context is missing a cross reference.
8413 A security checking error has occurred.
8414 The schema is not loaded.
8415 Schema allocation failed. Please check if the machine is running low on memory.
8416 Failed to obtain the required syntax for the attribute schema.
8417 The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.
8418 The replication operation failed because of a schema mismatch between the servers involved.
8419 The DSA object could not be found.
8420 The naming context could not be found.
8421 The naming context could not be found in the cache.
8422 The child object could not be retrieved.
8423 The modification was not permitted for security reasons.
8424 The operation cannot replace the hidden record.
8425 The hierarchy file is invalid.
8426 The attempt to build the hierarchy table failed.
8427 The directory configuration parameter is missing from the registry.
8428 The attempt to count the address book indices failed.
8429 The allocation of the hierarchy table failed.
8430 The directory service encountered an internal failure.
8431 The directory service encountered an unknown failure.
8432 A root object requires a class of 'top'.
8433 This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.
8434 The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.
8435 The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.
8436 The replication operation failed.
8437 An invalid parameter was specified for this replication operation.
8438 The directory service is too busy to complete the replication operation at this time.
8439 The distinguished name specified for this replication operation is invalid.
8440 The naming context specified for this replication operation is invalid.
8441 The distinguished name specified for this replication operation already exists.
8442 The replication system encountered an internal error.
8443 The replication operation encountered a database inconsistency.
8444 The server specified for this replication operation could not be contacted.
8445 The replication operation encountered an object with an invalid instance type.
8446 The replication operation failed to allocate memory.
8447 The replication operation encountered an error with the mail system.
8448 The replication reference information for the target server already exists.
8449 The replication reference information for the target server does not exist.
8450 The naming context cannot be removed because it is replicated to another server.
8451 The replication operation encountered a database error.
8452 The naming context is in the process of being removed or is not replicated from the specified server.
8453 Replication access was denied.
8454 The requested operation is not supported by this version of the directory service.
8455 The replication remote procedure call was cancelled.
8456 The source server is currently rejecting replication requests.
8457 The destination server is currently rejecting replication requests.
8458 The replication operation failed due to a collision of object names.
8459 The replication source has been reinstalled.
8460 The replication operation failed because a required parent object is missing.
8461 The replication operation was preempted.
8462 The replication synchronization attempt was abandoned because of a lack of updates.
8463 The replication operation was terminated because the system is shutting down.
8464 The replication synchronization attempt failed as the destination partial attribute set is not a subset of source partial attribute set.
8465 The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.
8466 The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.
8467 A schema mismatch is detected between the source and the build used during a replica install. The replica cannot be installed.
8468 Schema update failed: An attribute with the same link identifier already exists.
8469 Name translation: Generic processing error.
8470 Name translation: Could not find the name or insufficient right to see name.
8471 Name translation: Input name mapped to more than one output name.
8472 Name translation: Input name found, but not the associated output format.
8473 Name translation: Unable to resolve completely, only the domain was found.
8474 Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.
8475 Modification of a constructed att is not allowed.
8476 The OM-Object-Class specified is incorrect for an attribute with the specified syntax.
8477 The replication request has been posted; waiting for reply.
8478 The requested operation requires a directory service, and none was available.
8479 The LDAP display name of the class or attribute contains non-ASCII characters.
8480 The requested search operation is only supported for base searches.
8481 The search failed to retrieve attributes from the database.
8482 The schema update operation tried to add a backward link attribute that has no corresponding forward link.
8483 Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object.
8484 Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object.
8485 Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.
8486 Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container.
8487 Destination of a cross-domain move is not authoritative for the destination naming context.
8488 Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object.
8489 Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object.
8490 Another operation which requires exclusive access to the PDC FSMO is already in progress.
8491 A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.
8492 This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, eg: trust account or restricted RID, which prevent its move.
8493 Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry.
8494 A naming context head must be the immediate child of another naming context head, not of an interior node.
8495 The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global
8496 Destination domain must be in native mode.
8497 The operation can not be performed because the server does not have an infrastructure container in the domain of interest.
8498 Cross-domain move of account groups is not allowed.
8499 Cross-domain move of resource groups is not allowed.
8500 The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.
8501 Tree deletions starting at an object which has an NC head as a descendant are not allowed.
8502 The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.
8503 The directory service failed to identify the list of objects to delete while attempting a tree deletion.
8505 Only an administrator can modify the membership list of an administrative group.
8506 Cannot change the primary group ID of a domain controller account.
8507 An attempt is made to modify the base schema.
8508 Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by addin
8509 Schema update is not allowed on this DC. Either the registry key is not set or the DC is not the schema FSMO Role Owner.
8510 An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container.
8511 The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it.
8512 The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.
8513 The specified group type is invalid.
8514 You cannot nest global groups in a mixed domain if the group is security-enabled.
8515 You cannot nest local groups in a mixed domain if the group is security-enabled.
8516 A global group cannot have a local group as a member.
8517 A global group cannot have a universal group as a member.
8518 A universal group cannot have a local group as a member.
8519 A global group cannot have a cross-domain member.
8520 A local group cannot have another cross domain local group as a member.
8521 A group with primary members cannot change to a security-disabled group.
8522 The schema cache load failed to convert the string default SD on a class-schema object.
8523 Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role.
8524 The DSA operation is unable to proceed because of a DNS lookup failure.
8525 While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.
8526 The Security Descriptor attribute could not be read.
8527 The object requested was not found, but an object with that key was found.
8528 The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1
8529 Security Account Manager needs to get the boot password.
8530 Security Account Manager needs to get the boot key from floppy disk.
8531 Directory Service cannot start.
8532 Directory Services could not start.
8533 The connection between client and server requires packet privacy or better.
8534 The source domain may not be in the same forest as destination.
8535 The destination domain must be in the forest.
8536 The operation requires that destination domain auditing be enabled.
8537 The operation couldn't locate a DC for the source domain.
8538 The source object must be a group or user.
8539 The source object's SID already exists in destination forest.
8540 The source and destination object must be of the same type.
8542 Schema information could not be included in the replication request.
8543 The replication operation could not be completed due to a schema incompatibility.
8544 The replication operation could not be completed due to a previous schema incompatibility.
8545 The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation.
8546 The requested domain could not be deleted because there exist domain controllers that still host this domain.
8547 The requested operation can be performed only on a global catalog server.
8548 A local group can only be a member of other local groups in the same domain.
8549 Foreign security principals cannot be members of universal groups.
8550 The attribute is not allowed to be replicated to the GC because of security reasons.
8551 The checkpoint with the PDC could not be taken because there too many modifications being processed currently.
8552 The operation requires that source domain auditing be enabled.
8553 Security principal objects can only be created inside domain naming contexts.
8554 A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.
8555 A Filter was passed that uses constructed attributes.
8556 The unicodePwd attribute value must be enclosed in double quotes.
8557 Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.
8558 For security reasons, the operation must be run on the destination DC.
8559 For security reasons, the source DC must be Service Pack 4 or greater.
8560 Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.
9001 DNS server unable to interpret format.
9002 DNS server failure.
9003 DNS name does not exist.
9004 DNS request not supported by name server.
9005 DNS operation refused.
9006 DNS name that ought not exist, does exist.
9007 DNS RR set that ought not exist, does exist.
9008 DNS RR set that ought to exist, does not exist.
9009 DNS server not authoritative for zone.
9010 DNS name in update or prereq is not in zone.
9016 DNS signature failed to verify.
9017 DNS bad key.
9018 DNS signature validity expired.
9501 No records found for given DNS query.
9502 Bad DNS packet.
9503 No DNS packet.
9504 DNS error, check rcode.
9505 Unsecured DNS packet.
9551 Invalid DNS type.
9552 Invalid IP address.
9553 Invalid property.
9554 Try DNS operation again later.
9555 Record for given name and type is not unique.
9556 DNS name does not comply with RFC specifications.
9557 DNS name is a fully-qualified DNS name.
9558 DNS name is dotted (multi-label).
9559 DNS name is a single-part name.
9560 DNS name contains an invalid character.
9561 DNS name is entirely numeric.
9601 DNS zone does not exist.
9602 DNS zone information not available.
9603 Invalid operation for DNS zone.
9604 Invalid DNS zone configuration.
9605 DNS zone has no start of authority (SOA) record.
9606 DNS zone has no Name Server (NS) record.
9607 DNS zone is locked.
9608 DNS zone creation failed.
9609 DNS zone already exists.
9610 DNS automatic zone already exists.
9611 Invalid DNS zone type.
9612 Secondary DNS zone requires master IP address.
9613 DNS zone not secondary.
9614 Need secondary IP address.
9615 WINS initialization failed.
9616 Need WINS servers.
9617 NBTSTAT initialization call failed.
9618 Invalid delete of start of authority (SOA)
9651 Primary DNS zone requires datafile.
9652 Invalid datafile name for DNS zone.
9653 Failed to open datafile for DNS zone.
9654 Failed to write datafile for DNS zone.
9655 Failure while reading datafile for DNS zone.
9701 DNS record does not exist.
9702 DNS record format error.
9703 Node creation failure in DNS.
9704 Unknown DNS record type.
9705 DNS record timed out.
9706 Name not in DNS zone.
9707 CNAME loop detected.
9708 Node is a CNAME DNS record.
9709 A CNAME record already exists for given name.
9710 Record only at DNS zone root.
9711 DNS record already exists.
9712 Secondary DNS zone data error.
9713 Could not create DNS cache data.
9714 DNS name does not exist.
9715 Could not create pointer (PTR) record.
9716 DNS domain was undeleted.
9717 The directory service is unavailable.
9718 DNS zone already exists in the directory service.
9719 DNS server not creating or reading the boot file for the directory service integrated DNS zone.
9751 DNS AXFR (zone transfer) complete.
9752 DNS zone transfer failed.
9753 Added local WINS server.
9801 Secure update call needs to continue update request.
9851 TCP/IP network protocol not installed.
9852 No DNS servers configured for local system.
10004 A blocking operation was interrupted by a call to WSACancelBlockingCall.
10009 The file handle supplied is not valid.
10013 An attempt was made to access a socket in a way forbidden by its access permissions.
10014 The system detected an invalid pointer address in attempting to use a pointer argument in a call.
10022 An invalid argument was supplied.
10024 Too many open sockets.
10035 A non-blocking socket operation could not be completed immediately.
10036 A blocking operation is currently executing.
10037 An operation was attempted on a non-blocking socket that already had an operation in progress.
10038 An operation was attempted on something that is not a socket.
10039 A required address was omitted from an operation on a socket.
10040 A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
10041 A protocol was specified in the socket function call that does not support the semantics of the socket type requested.
10042 An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call.
10043 The requested protocol has not been configured into the system, or no implementation for it exists.
10044 The support for the specified socket type does not exist in this address family.
10045 The attempted operation is not supported for the type of object referenced.
10046 The protocol family has not been configured into the system or no implementation for it exists.
10047 An address incompatible with the requested protocol was used.
10048 Only one usage of each socket address (protocol/network address/port) is normally permitted.
10049 The requested address is not valid in its context.
10050 A socket operation encountered a dead network.
10051 A socket operation was attempted to an unreachable network.
10052 The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
10053 An established connection was aborted by the software in your host machine.
10054 An existing connection was forcibly closed by the remote host.
10055 An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
10056 A connect request was made on an already connected socket.
10057 A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.
10058 A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.
10059 Too many references to some kernel object.
10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
10061 No connection could be made because the target machine actively refused it.
10062 Cannot translate name.
10063 Name component or name was too long.
10064 A socket operation failed because the destination host was down.
10065 A socket operation was attempted to an unreachable host.
10066 Cannot remove a directory that is not empty.
10067 A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously.
10068 Ran out of quota.
10069 Ran out of disk quota.
10070 File handle reference is no longer available.
10071 Item is not available locally.
10091 WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.
10092 The Windows Sockets version requested is not supported.
10093 Either the application has not called WSAStartup, or WSAStartup failed.
10101 Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.
10102 No more results can be returned by WSALookupServiceNext.
10103 A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
10104 The procedure call table is invalid.
10105 The requested service provider is invalid.
10106 The requested service provider could not be loaded or initialized.
10107 A system call that should never fail has failed.
10108 No such service is known. The service cannot be found in the specified name space.
10109 The specified class was not found.
10110 No more results can be returned by WSALookupServiceNext.
10111 A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
10112 A database query failed because it was actively refused

Share it Please

Tweet

Saurabh Gupta

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation.