|
|
You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747
|
|
|
Device's command support detection is in progress.
|
|
|
This file is checked out or locked for editing by another user.
|
|
|
The file must be checked out before saving changes.
|
|
|
The file type being saved or retrieved has been blocked.
|
|
|
The file size exceeds the limit allowed and cannot be saved.
|
|
|
Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically.
|
|
|
Operation did not complete successfully because the file contains a virus or potentially unwanted software.
|
|
|
This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location.
|
|
|
The pipe is local.
|
|
|
The action requested resulted in no work being done. Error-style clean-up has been performed.
|
|
|
Short name settings may not be changed on this volume due to the global registry setting.
|
|
|
Short names are not enabled on this volume.
|
|
|
The security stream for the given volume is in an inconsistent state. Please run CHKDSK on the volume.
|
|
|
A requested file lock operation cannot be processed due to an invalid byte range.
|
|
|
The subsystem needed to support the image type is not present.
|
|
|
The specified file already has a notification GUID associated with it.
|
|
|
An invalid exception handler routine has been detected.
|
|
|
Duplicate privileges were specified for the token.
|
|
|
No ranges for the specified operation were able to be processed.
|
|
|
Operation is not allowed on a file system internal file.
|
|
|
The physical resources of this disk have been exhausted.
|
|
|
The token representing the data is invalid.
|
|
|
The device does not support the command feature.
|
|
|
The scope specified was not found.
|
|
|
The Central Access Policy specified is not defined on the target machine.
|
|
|
The Central Access Policy obtained from Active Directory is invalid.
|
|
|
The device is unreachable.
|
|
|
The target device has insufficient resources to complete the operation.
|
|
|
A data integrity checksum error occurred. Data in the file stream is corrupt.
|
|
|
An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation.
|
|
|
Device does not support file-level TRIM.
|
|
|
The command specified a data offset that does not align to the device's granularity/alignment.
|
|
|
The command specified an invalid field in its parameter list.
|
|
|
An operation is currently in progress with the device.
|
|
|
An attempt was made to send down the command via an invalid path to the target device.
|
|
|
The command specified a number of descriptors that exceeded the maximum supported by the device.
|
|
|
Scrub is disabled on the specified file.
|
|
|
The storage device does not provide redundancy.
|
|
|
An operation is not supported on a resident file.
|
|
|
An operation is not supported on a compressed file.
|
|
|
An operation is not supported on a directory.
|
|
|
The specified copy of the requested data could not be read.
|
|
|
The specified data could not be written to any of the copies.
|
|
|
One or more copies of data on this device may be out of sync. No writes may be performed until a data integrity scan is completed.
|
|
|
The supplied kernel information version is invalid.
|
|
|
The supplied PEP information version is invalid.
|
|
|
This object is not externally backed by any provider.
|
|
|
The external backing provider is not recognized.
|
|
|
Compressing this object would not save space.
|
|
|
The request failed due to a storage topology ID mismatch.
|
|
|
The operation was blocked by parental controls.
|
|
|
A file system block being referenced has already reached the maximum reference count and can't be referenced any further.
|
|
|
The requested operation failed because the file stream is marked to disallow writes.
|
|
|
The requested operation failed with an architecture-specific failure code.
|
|
|
No action was taken as a system reboot is required.
|
|
|
The shutdown operation failed.
|
|
|
The restart operation failed.
|
|
|
The maximum number of sessions has been reached.
|
|
|
Windows Information Protection policy does not allow access to this network resource.
|
|
|
The device hint name buffer is too small to receive the remaining name.
|
|
|
The requested operation was blocked by Windows Information Protection policy. For more information, contact your system administrator.
|
|
|
The requested operation cannot be performed because hardware or software configuration of the device does not comply with Windows Information Protection under Lock policy. Please, verify that user PIN has been created. For more information, contact your system administrator.
|
|
|
The cloud sync root metadata is corrupted.
|
|
|
The device is in maintenance mode.
|
|
|
This operation is not supported on a DAX volume.
|
|
|
The volume has active DAX mappings.
|
|
|
The cloud file provider is not running.
|
|
|
The cloud file metadata is corrupt and unreadable.
|
|
|
The cloud file metadata is too large.
|
|
|
The cloud file property is too large.
|
|
|
The cloud file property is possibly corrupt. The on-disk checksum does not match the computed checksum.
|
|
|
The process creation has been blocked.
|
|
|
The storage device has lost data or persistence.
|
|
|
The provider that supports file system virtualization is temporarily unavailable.
|
|
|
The metadata for file system virtualization is corrupt and unreadable.
|
|
|
The provider that supports file system virtualization is too busy to complete this operation.
|
|
|
The provider that supports file system virtualization is unknown.
|
|
|
GDI handles were potentially leaked by the application.
|
|
|
The maximum number of cloud file properties has been reached.
|
|
|
The version of the cloud file property store is not supported.
|
|
|
The file is not a cloud file.
|
|
|
The file is not in sync with the cloud.
|
|
|
The cloud sync root is already connected with another cloud sync provider.
|
|
|
The operation is not supported by the cloud sync provider.
|
|
|
The cloud operation is invalid.
|
|
|
The cloud operation is not supported on a read-only volume.
|
|
|
The operation is reserved for a connected cloud sync provider.
|
|
|
The cloud sync provider failed to validate the downloaded data.
|
|
|
The virtualization operation is not allowed on the file in its current state.
|
|
|
The cloud sync provider failed user authentication.
|
|
|
The cloud sync provider failed to perform the operation due to low system resources.
|
|
|
The cloud sync provider failed to perform the operation due to network being unavailable.
|
|
|
The cloud operation was unsuccessful.
|
|
|
The operation is only supported on files under a cloud sync root.
|
|
|
The operation cannot be performed on cloud files in use.
|
|
|
The operation cannot be performed on pinned cloud files.
|
|
|
The cloud operation was aborted.
|
|
|
The cloud file's property store is corrupt.
|
|
|
Access to the cloud file is denied.
|
|
|
The cloud operation cannot be performed on a file with incompatible hardlinks.
|
|
|
The operation failed due to a conflicting cloud file property lock.
|
|
|
The cloud operation was canceled by user.
|
|
|
An externally encrypted syskey has been configured, but the system no longer supports this feature. Please see https://go.microsoft.com/fwlink/?linkid=851152 for more information.
|
|
|
The thread is already in background processing mode.
|
|
|
The thread is not in background processing mode.
|
|
|
The process is already in background processing mode.
|
|
|
The process is not in background processing mode.
|
|
|
The cloud file provider exited unexpectedly.
|
|
|
The file is not a cloud sync root.
|
|
|
The read or write operation to an encrypted file could not be completed because the file can only be accessed when the device is unlocked.
|
|
|
The volume is not cluster aligned on the disk.
|
|
|
No physically aligned free space was found on the volume.
|
|
|
The APPX file can not be accessed because it is not encrypted as expected.
|
|
|
A read or write of raw encrypted data cannot be performed because the file is not encrypted.
|
|
|
An invalid file offset in the encrypted data info block was passed for read or write operation of file's raw encrypted data.
|
|
|
An invalid offset and length combination in the encrypted data info block was passed for read or write operation of file's raw encrypted data.
|
|
|
An invalid parameter in the encrypted data info block was passed for read or write operation of file's raw encrypted data.
|
|
|
The Windows Subsystem for Linux has not been enabled.
|
|
|
The specified data could not be read from any of the copies.
|
|
|
The specified storage reserve ID is invalid.
|
|
|
The specified storage reserve does not exist.
|
|
|
The specified storage reserve already exists.
|
|
|
The specified storage reserve is not empty.
|
|
|
This operation requires a DAX volume.
|
|
|
This stream is not DAX mappable.
|
|
|
Operation cannot be performed on a time critical thread.
|
|
|
User data protection is not supported for the current or provided user.
|
|
|
This directory contains entries whose names differ only in case.
|
|
|
The file cannot be safely opened because it is not supported by this version of Windows.
|
|
|
The cloud operation was not completed before the time-out period expired.
|
|
|
A task queue is required for this operation but none is available.
|
|
|
Failed loading a valid version of srcsrv.dll.
|
|
|
This operation is not supported with BTT enabled.
|
|
|
This operation cannot be performed because encryption is currently disabled.
|
|
|
This encryption operation cannot be performed on filesystem metadata.
|
|
|
Encryption cannot be cleared on this file/directory because it still has an encrypted attribute.
|
|
|
A device which does not exist was specified.
|
|
|
Neither developer unlocked mode nor side loading mode is enabled on the device.
|
|
|
Can not change application type during upgrade or re-provision.
|
|
|
The application has not been provisioned.
|
|
|
The requested capability can not be authorized for this application.
|
|
|
There is no capability authorization policy on the device.
|
|
|
The capability authorization database has been corrupted.
|
|
|
The custom capability's SCCD has an invalid catalog.
|
|
|
None of the authorized entity elements in the SCCD matched the app being installed; either the PFNs don't match, or the element's signature hash doesn't validate.
|
|
|
The custom capability's SCCD failed to parse.
|
|
|
The custom capability's SCCD requires developer mode.
|
|
|
There not all declared custom capabilities are found in the SCCD.
|
|
|
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in its device stack. The system may need to be rebooted to complete the request.
|
|
|
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of a related device. The system may need to be rebooted to complete the operation.
|
|
|
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of an unrelated device. The system may need to be rebooted to complete the operation.
|
|
|
The request failed due to a fatal device hardware error.
|
|
|
User profile cannot be loaded.
|
|
|
Application verifier has found an error in the current process.
|
|
|
An error occurred in the ABIOS subsystem.
|
|
|
A warning occurred in the WX86 subsystem.
|
|
|
An error occurred in the WX86 subsystem.
|
|
|
An attempt was made to cancel or set a timer that has an associated APC and the subject thread is not the thread that originally set the timer with an associated APC routine.
|
|
|
Unwind exception code.
|
|
|
An invalid or unaligned stack was encountered during an unwind operation.
|
|
|
An invalid unwind target was encountered during an unwind operation.
|
|
|
Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort
|
|
|
Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port.
|
|
|
An attempt was made to lower a quota limit below the current usage.
|
|
|
An attempt was made to attach to a device that was already attached to another device.
|
|
|
An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references.
|
|
|
Profiling not started.
|
|
|
Profiling not stopped.
|
|
|
The passed ACL did not contain the minimum required information.
|
|
|
The number of active profiling objects is at the maximum and no more may be started.
|
|
|
Used to indicate that an operation cannot continue without blocking for I/O.
|
|
|
Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process.
|
|
|
If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception.
|
|
|
If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception.
|
|
|
If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception.
|
|
|
A malformed function table was encountered during an unwind operation.
|
|
|
Indicates that an attempt was made to assign protection to a file system file or directory and one of the SIDs in the security descriptor could not be translated into a GUID that could be stored by the file system. This causes the protection attempt to fail, which may cause a file creation attempt to fail.
|
|
|
Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors.
|
|
|
Indicates that the starting value for the LDT information was not an integral multiple of the selector size.
|
|
|
Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors.
|
|
|
Indicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads.
|
|
|
An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified.
|
|
|
Page file quota was exceeded.
|
|
|
The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role.
|
|
|
The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required.
|
|
|
The NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines.
|
|
|
{Privilege Failed} The I/O permissions for the process could not be changed.
|
|
|
{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C.
|
|
|
{Missing System File} The required system file hs is bad or missing.
|
|
|
{Application Error} The exception s (0x
|
|
|
{Application Error} The application was unable to start correctly (0xlx). Click OK to close the application.
|
|
|
{Unable to Create Paging File} The creation of the paging file hs failed (lx). The requested size was ld.
|
|
|
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
|
|
|
{No Paging File Specified} No paging file was specified in the system configuration.
|
|
|
{EXCEPTION} A real-mode application issued a floating-point instruction and floating-point hardware is not present.
|
|
|
An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread.
|
|
|
A Windows Server has an incorrect configuration.
|
|
|
An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.
|
|
|
The Unicode character is not defined in the Unicode character set installed on the system.
|
|
|
The paging file cannot be created on a floppy diskette.
|
|
|
The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected.
|
|
|
This operation is only allowed for the Primary Domain Controller of the domain.
|
|
|
An attempt was made to acquire a mutant such that its maximum count would have been exceeded.
|
|
|
A volume has been accessed for which a file system driver is required that has not yet been loaded.
|
|
|
{Registry File Failure} The registry cannot load the hive (file): hs or its log or alternate. It is corrupt, absent, or not writable.
|
|
|
{Unexpected Failure in DebugActiveProcess} An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error.
|
|
|
{Fatal System Error} The hs system process terminated unexpectedly with a status of 0x
|
|
|
{Data Not Accepted} The TDI client could not handle the data received during an indication.
|
|
|
NTVDM encountered a hard error.
|
|
|
{Cancel Timeout} The driver hs failed to complete a cancelled I/O request in the allotted time.
|
|
|
{Reply Message Mismatch} An attempt was made to reply to an LPC message, but the thread specified by the client ID in the message was not waiting on that message.
|
|
|
{Delayed Write Failed} Windows was unable to save all the data for the file hs. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
|
|
|
The parameter(s) passed to the server in the client/server shared memory window were invalid. Too much data may have been put in the shared memory window.
|
|
|
The stream is not a tiny stream.
|
|
|
The request must be handled by the stack overflow code.
|
|
|
Internal OFS status codes indicating how an allocation operation is handled. Either it is retried after the containing onode is moved or the extent stream is converted to a large stream.
|
|
|
The attempt to find the object found an object matching by ID on the volume but it is out of the scope of the handle used for the operation.
|
|
|
The bucket array must be grown. Retry transaction after doing so.
|
|
|
The user/kernel marshalling buffer has overflowed.
|
|
|
The supplied variant structure contains invalid data.
|
|
|
The specified buffer contains ill-formed data.
|
|
|
{Audit Failed} An attempt to generate a security audit failed.
|
|
|
The timer resolution was not previously set by the current process.
|
|
|
There is insufficient account information to log you on.
|
|
|
{Invalid DLL Entrypoint} The dynamic link library hs is not written correctly. The stack pointer has been left in an inconsistent state. The entrypoint should be declared as WINAPI or STDCALL. Select YES to fail the DLL load. Select NO to continue execution. Selecting NO may cause the application to operate incorrectly.
|
|
|
{Invalid Service Callback Entrypoint} The hs service is not written correctly. The stack pointer has been left in an inconsistent state. The callback entrypoint should be declared as WINAPI or STDCALL. Selecting OK will cause the service to continue operation. However, the service process may operate incorrectly.
|
|
|
There is an IP address conflict with another system on the network
|
|
|
There is an IP address conflict with another system on the network
|
|
|
{Low On Registry Space} The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored.
|
|
|
A callback return system service cannot be executed when no callback is active.
|
|
|
The password provided is too short to meet the policy of your user account. Please choose a longer password.
|
|
|
The policy of your user account does not allow you to change passwords too frequently. This is done to prevent users from changing back to a familiar, but potentially discovered, password. If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned.
|
|
|
You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used.
|
|
|
The specified compression format is unsupported.
|
|
|
The specified hardware profile configuration is invalid.
|
|
|
The specified Plug and Play registry device path is invalid.
|
|
|
The specified quota list is internally inconsistent with its descriptor.
|
|
|
{Windows Evaluation Notification} The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product.
|
|
|
{Illegal System DLL Relocation} The system DLL hs was relocated in memory. The application will not run properly. The relocation occurred because the DLL hs occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL.
|
|
|
{DLL Initialization Failed} The application failed to initialize because the window station is shutting down.
|
|
|
The validation process needs to continue on to the next step.
|
|
|
There are no more matches for the current index enumeration.
|
|
|
The range could not be added to the range list because of a conflict.
|
|
|
The server process is running under a SID different than that required by client.
|
|
|
A group marked use for deny only cannot be enabled.
|
|
|
{EXCEPTION} Multiple floating point faults.
|
|
|
{EXCEPTION} Multiple floating point traps.
|
|
|
The requested interface is not supported.
|
|
|
{System Standby Failed} The driver hs does not support standby mode. Updating this driver may allow the system to go to standby mode.
|
|
|
{Virtual Memory Minimum Too Low} Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help.
|
|
|
A device was removed so enumeration must be restarted.
|
|
|
{Fatal System Error} The system image s is not properly signed. The file has been replaced with the signed file. The system has been shut down.
|
|
|
Device will not start without a reboot.
|
|
|
There is not enough power to complete the requested operation.
|
|
|
ERROR_MULTIPLE_FAULT_VIOLATION
|
|
|
The system is in the process of shutting down.
|
|
|
An attempt to remove a processes DebugPort was made, but a port was not already associated with the process.
|
|
|
This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller.
|
|
|
The specified range could not be found in the range list.
|
|
|
The driver was not loaded because the system is booting into safe mode.
|
|
|
The driver was not loaded because it failed its initialization call.
|
|
|
The "hs" encountered an error while applying power or reading the device configuration. This may be caused by a failure of your hardware or by a poor connection.
|
|
|
The create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached.
|
|
|
The device object parameter is either not a valid device object or is not attached to the volume specified by the file name.
|
|
|
A Machine Check Error has occurred. Please check the system eventlog for additional information.
|
|
|
System hive size has exceeded its limit.
|
|
|
The driver could not be loaded because a previous version of the driver is still in memory.
|
|
|
{Volume Shadow Copy Service} Please wait while the Volume Shadow Copy Service prepares volume hs for hibernation.
|
|
|
The system has failed to hibernate (The error code is hs). Hibernation will be disabled until the system is restarted.
|
|
|
The password provided is too long to meet the policy of your user account. Please choose a shorter password.
|
|
|
The requested operation could not be completed due to a file system limitation
|
|
|
An assertion failure has occurred.
|
|
|
An error occurred in the ACPI subsystem.
|
|
|
WOW Assertion Error.
|
|
|
A device is missing in the system BIOS MPS table. This device will not be used. Please contact your system vendor for system BIOS update.
|
|
|
A translator failed to translate resources.
|
|
|
A IRQ translator failed to translate resources.
|
|
|
{Kernel Debugger Awakened} the system debugger was awakened by an interrupt.
|
|
|
{Handles Closed} Handles to objects have been automatically closed as a result of the requested operation.
|
|
|
{Too Much Information} The specified access control list (ACL) contained more information than was expected.
|
|
|
This warning level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has NOT been completed, but has not been rolled back either (so it may still be committed if desired).
|
|
|
{Media Changed} The media may have changed.
|
|
|
{GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended.
|
|
|
The create operation stopped after reaching a symbolic link
|
|
|
A long jump has been executed.
|
|
|
The Plug and Play query operation was not successful.
|
|
|
A frame consolidation has been executed.
|
|
|
{Registry Hive Recovered} Registry hive (file): hs was corrupted and it has been recovered. Some data might have been lost.
|
|
|
The application is attempting to run executable code from the module hs. This may be insecure. An alternative, hs, is available. Should the application use the secure module hs?
|
|
|
The application is loading executable code from the module hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, hs, is available. Should the application use the secure module hs?
|
|
|
Debugger did not handle the exception.
|
|
|
Debugger will reply later.
|
|
|
Debugger cannot provide handle.
|
|
|
Debugger terminated thread.
|
|
|
Debugger terminated process.
|
|
|
Debugger got control C.
|
|
|
Debugger printed exception on control C.
|
|
|
Debugger received RIP exception.
|
|
|
Debugger received control break.
|
|
|
Debugger command communication exception.
|
|
|
{Object Exists} An attempt was made to create an object and the object name already existed.
|
|
|
{Thread Suspended} A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded.
|
|
|
{Image Relocated} An image file could not be mapped at the address specified in the image file. Local fixups must be performed on this image.
|
|
|
This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created.
|
|
|
{Segment Load} A virtual DOS machine (VDM) is loading, unloading, or moving an MS-DOS or Win16 program segment image. An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments.
|
|
|
{Invalid Current Directory} The process cannot switch to the startup current directory hs. Select OK to set current directory to hs, or select CANCEL to exit.
|
|
|
{Redundant Read} To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device.
|
|
|
{Redundant Write} To satisfy a write request, the NT fault-tolerant file system successfully wrote a redundant copy of the information. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was not able to reassign the failing area of the device.
|
|
|
{Machine Type Mismatch} The image file hs is valid, but is for a machine type other than the current machine. Select OK to continue, or CANCEL to fail the DLL load.
|
|
|
{Partial Data Received} The network transport returned partial data to its client. The remaining data will be sent later.
|
|
|
{Expedited Data Received} The network transport returned data to its client that was marked as expedited by the remote system.
|
|
|
{Partial Expedited Data Received} The network transport returned partial data to its client and this data was marked as expedited by the remote system. The remaining data will be sent later.
|
|
|
{TDI Event Done} The TDI indication has completed successfully.
|
|
|
{TDI Event Pending} The TDI indication has entered the pending state.
|
|
|
Checking file system on wZ
|
|
|
{Fatal Application Exit} hs
|
|
|
The specified registry key is referenced by a predefined handle.
|
|
|
{Page Unlocked} The page protection of a locked page was changed to 'No Access' and the page was unlocked from memory and from the process.
|
|
|
hs
|
|
|
{Page Locked} One of the pages to lock was already locked.
|
|
|
ERROR_ALREADY_WIN32
|
|
|
{Machine Type Mismatch} The image file hs is valid, but is for a machine type other than the current machine.
|
|
|
A yield execution was performed and no thread was available to run.
|
|
|
The resumable flag to a timer API was ignored.
|
|
|
The arbiter has deferred arbitration of these resources to its parent
|
|
|
The inserted CardBus device cannot be started because of a configuration error on "hs".
|
|
|
The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported.
|
|
|
The system was put into hibernation.
|
|
|
The system was resumed from hibernation.
|
|
|
A device driver is leaking locked I/O pages causing system degradation. The system has automatically enabled tracking code in order to try and catch the culprit.
|
|
|
The system has awoken
|
|
|
ERROR_WAIT_1
|
|
|
ERROR_WAIT_2
|
|
|
ERROR_WAIT_3
|
|
|
ERROR_WAIT_63
|
|
|
ERROR_ABANDONED_WAIT_0
|
|
|
ERROR_ABANDONED_WAIT_63
|
|
|
ERROR_USER_APC
|
|
|
ERROR_KERNEL_APC
|
|
|
ERROR_ALERTED
|
|
|
The requested operation requires elevation.
|
|
|
A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link.
|
|
|
An open/create operation completed while an oplock break is underway.
|
|
|
A new volume has been mounted by a file system.
|
|
|
This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has now been completed.
|
|
|
This indicates that a notify change request has been completed due to closing the handle which made the notify change request.
|
|
|
{Connect Failure on Primary Transport} An attempt was made to connect to the remote server hs on the primary transport, but the connection failed. The computer WAS able to connect on a secondary transport.
|
|
|
Page fault was a transition fault.
|
|
|
Page fault was a demand zero fault.
|
|
|
Page fault was a demand zero fault.
|
|
|
Page fault was a demand zero fault.
|
|
|
Page fault was satisfied by reading from a secondary storage device.
|
|
|
Cached page was locked during operation.
|
|
|
Crash dump exists in paging file.
|
|
|
Specified buffer contains all zeros.
|
|
|
A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link.
|
|
|
The device has succeeded a query-stop and its resource requirements have changed.
|
|
|
The translator has translated these resources into the global space and no further translations should be performed.
|
|
|
A process being terminated has no threads to terminate.
|
|
|
The specified process is not part of a job.
|
|
|
The specified process is part of a job.
|
|
|
{Volume Shadow Copy Service} The system is now ready for hibernation.
|
|
|
A file system or file system filter driver has successfully completed an FsFilter operation.
|
|
|
The specified interrupt vector was already connected.
|
|
|
The specified interrupt vector is still connected.
|
|
|
An operation is blocked waiting for an oplock.
|
|
|
Debugger handled exception
|
|
|
Debugger continued
|
|
|
An exception occurred in a user mode callback and the kernel callback frame should be removed.
|
|
|
Compression is disabled for this volume.
|
|
|
The data provider cannot fetch backwards through a result set.
|
|
|
The data provider cannot scroll backwards through a result set.
|
|
|
The data provider requires that previously fetched data is released before asking for more data.
|
|
|
The data provider was not able to interpret the flags set for a column binding in an accessor.
|
|
|
One or more errors occurred while processing the request.
|
|
|
The implementation is not capable of performing the request.
|
|
|
The client of a component requested an operation which is not valid given the state of the component instance.
|
|
|
A version number could not be parsed.
|
|
|
The iterator's start position is invalid.
|
|
|
The hardware has reported an uncorrectable memory error.
|
|
|
The attempted operation required self healing to be enabled.
|
|
|
The Desktop heap encountered an error while allocating session memory. There is more information in the system event log.
|
|
|
A thread is getting dispatched with MCA EXCEPTION because of MCA.
|
|
|
A valid hibernation file has been invalidated and should be abandoned.
|
|
|
{Delayed Write Failed} Windows was unable to save all the data for the file hs; the data has been lost. This error may be caused by network connectivity issues. Please try to save this file elsewhere.
|
|
|
{Delayed Write Failed} Windows was unable to save all the data for the file hs; the data has been lost. This error was returned by the server on which the file exists. Please try to save this file elsewhere.
|
|
|
{Delayed Write Failed} Windows was unable to save all the data for the file hs; the data has been lost. This error may be caused if the device has been removed or the media is write-protected.
|
|
|
The resources required for this device conflict with the MCFG table.
|
|
|
The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be repaired.
|
|
|
The volume repair was not successful.
|
|
|
One of the volume corruption logs is full. Further corruptions that may be detected won't be logged.
|
|
|
One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned.
|
|
|
One of the volume corruption logs is unavailable for being operated on.
|
|
|
One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned.
|
|
|
One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions.
|
|
|
Orphaned files exist on the volume but could not be recovered because no more new names could be created in the recovery directory. Files must be moved from the recovery directory.
|
|
|
The oplock that was associated with this handle is now associated with a different handle.
|
|
|
An oplock of the requested level cannot be granted. An oplock of a lower level may be available.
|
|
|
The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken.
|
|
|
The handle with which this oplock was associated has been closed. The oplock is now broken.
|
|
|
The specified access control entry (ACE) does not contain a condition.
|
|
|
The specified access control entry (ACE) contains an invalid condition.
|
|
|
Access to the specified file handle has been revoked.
|
|
|
{Image Relocated} An image file was mapped at a different address from the one specified in the image file but fixups will still be automatically performed on the image.
|
|
|
The read or write operation to an encrypted file could not be completed because the file has not been opened for data access.
|
|
|
File metadata optimization is already in progress.
|
|
|
The requested operation failed due to quota operation is still in progress.
|
|
|
Access to the specified handle has been revoked.
|
|
|
The callback function must be invoked inline.
|
|
|
The specified CPU Set IDs are invalid.
|
|
|
The specified enclave has not yet been terminated.
|
|
|
An attempt was made to access protected memory in violation of its secure access policy.
|
|
|
Driver Verifier Volatile settings cannot be set when CFG is enabled.
|
|
|
An attempt was made to access a partition that has begun termination.
|
|
|
A system shutdown has already been scheduled.
|
|
|
The system shutdown cannot be initiated because there are other users logged on to the computer.
|
|
|
You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
|
|
|
Windows cannot open this program since it has been disabled.
|
|
|
Windows cannot open this program because the license enforcement system has been tampered with or become corrupted.
|
|
|
A transaction recover failed.
|
|
|
The current thread has already been converted to a fiber.
|
|
|
The current thread has already been converted from a fiber.
|
|
|
The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
|
|
|
Data present in one of the parameters is more than the function can operate on.
|
|
|
An attempt to do an operation on a debug object failed because the object is in the process of being deleted.
|
|
|
An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed.
|
|
|
Insufficient information exists to identify the cause of failure.
|
|
|
The parameter passed to a C runtime function is incorrect.
|
|
|
The operation occurred beyond the valid data length of the file.
|
|
|
The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service.
|
|
|
The process hosting the driver for this device has been terminated.
|
|
|
An operation attempted to exceed an implementation-defined limit.
|
|
|
Either the target process, or the target thread's containing process, is a protected process.
|
|
|
The service notification client is lagging too far behind the current state of services in the machine.
|
|
|
The requested file operation failed because the storage quota was exceeded. To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator.
|
|
|
The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator.
|
|
|
A privilege that the service requires to function properly does not exist in the service account configuration. You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration.
|
|
|
A thread involved in this operation appears to be unresponsive.
|
|
|
Indicates a particular Security ID may not be assigned as the label of an object.
|
|
|
Incorrect size argument.
|
|
|
The symbolic link cannot be followed because its type is disabled.
|
|
|
This application does not support the current operation on symbolic links.
|
|
|
Windows was unable to parse the requested XML data.
|
|
|
An error was encountered while processing an XML digital signature.
|
|
|
This application must be restarted.
|
|
|
The caller made the connection request in the wrong routing compartment.
|
|
|
There was an AuthIP failure when attempting to connect to the remote host.
|
|
|
Insufficient NVRAM resources exist to complete the requested service. A reboot might be required.
|
|
|
Unable to finish the requested operation because the specified process is not a GUI process.
|
|
|
The specified Job already has a container assigned to it.
|
|
|
The specified Job does not have a container assigned to it.
|
|
|
The specified task name is invalid.
|
|
|
The specified task index is invalid.
|
|
|
The specified thread is already joining a task.
|
|
|
The Windows Installer does not permit installation from a Remote Desktop Connection.
|
|
|
Uninstallation of the update package is not supported.
|
|
|
The update is not applied to this product.
|
|
|
No valid sequence could be found for the set of updates.
|
|
|
Update removal was disallowed by policy.
|
|
|
The XML update data is invalid.
|
|
|
Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update.
|
|
|
The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state.
|
|
|
A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately.
|
|
|
The app that you are trying to run is not supported on this version of Windows.
|
|
|
The operation was blocked as the process prohibits dynamic code generation.
|
|
|
The objects are not identical.
|
|
|
The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard.
|
|
|
The thread context could not be updated because this has been restricted for the process.
|
|
|
An invalid cross-partition private file/section access was attempted.
|
|
|
Access to the HTTP proxy is denied.
|
|
|
HTTP proxy server rejected the connection because the cookie authentication failed.
|
|
|
The RPC server is suspended, and could not be resumed for this request. The call did not execute.
|
|
|
The RPC call contains too many handles to be transmitted in a single request.
|
|
|
The RPC call contains a handle that differs from the declared handle type.
|
|
|
The current user's delegated trust creation quota has been exceeded.
|
|
|
The total delegated trust creation quota has been exceeded.
|
|
|
The current user's delegated trust deletion quota has been exceeded.
|
|
|
The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer.
|
|
|
Remote connections to the Print Spooler are blocked by a policy set on your machine.
|
|
|
Authentication failed because NTLM authentication has been disabled.
|
|
|
Logon Failure: EAS policy requires that the user change their password before this operation can be performed.
|
|
|
An administrator has restricted sign in. To sign in, make sure your device is connected to the Internet, and have your administrator sign in first.
|
|
|
The specified profile is intended for a device of a different type than the specified device.
|
|
|
The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified.
|
|
|
The network connection was made successfully using default credentials.
|
|
|
The user name may not be same as computer name.
|
|
|
An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting, see Windows Help.
|
|
|
This device is joined to Azure AD. To join an Active Directory domain, you must first go to settings and choose to disconnect your device from your work or school.
|
|
|
Password must change at next logon
|
|
|
Account is locked out
|
|
|
Password is too long
|
|
|
Password doesn't meet the complexity policy
|
|
|
Password doesn't meet the requirements of the filter dll's
|
|
|
Offline join completion information was not found.
|
|
|
The offline join completion information was bad.
|
|
|
Unable to create offline join information. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required.
|
|
|
The domain join info being saved was incomplete or bad.
|
|
|
Offline join operation successfully completed but a restart is needed.
|
|
|
There was no offline join operation pending.
|
|
|
Unable to set one or more requested machine or domain name values on the local computer.
|
|
|
Could not verify the current machine's hostname against the saved value in the join completion information.
|
|
|
Unable to load the specified offline registry hive. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required.
|
|
|
The minimum session security requirements for this operation were not met.
|
|
|
Computer account provisioning blob version is not supported.
|
|
|
The specified domain controller does not meet the version requirement for this operation. Please select a domain controller capable of issuing claims.
|
|
|
This operation requires a domain controller which supports LDAP. Please select an LDAP-capable domain controller.
|
|
|
A domain controller which meets the version requirement for this operation could not be located. Please ensure that a domain controller capable of issuing claims is available.
|
|
|
The Windows version of the specified image does not support provisioning.
|
|
|
The machine name is blocked from joining the domain.
|
|
|
The domain controller does not meet the version requirement for this operation. See http://go.microsoft.com/fwlink/?LinkId=294288 for more information.
|
|
|
The local machine does not allow querying of LSA secrets in plain-text.
|
|
|
Unable to leave the Azure AD domain that this machine is joined to. Check the event log for detailed error information.
|
|
|
The specified printer driver package is currently in use.
|
|
|
Unable to find a core driver package that is required by the printer driver package.
|
|
|
The requested operation failed. A system reboot is required to roll back changes made.
|
|
|
The requested operation failed. A system reboot has been initiated to roll back changes made.
|
|
|
The specified printer driver was not found on the system and needs to be downloaded.
|
|
|
The operation was not completed because a required resource donor was not found for the host.
|
|
|
The operation was not completed because an unexpected host ID was encountered.
|
|
|
The operation was not completed because the specified user was not known to the service.
|
|
|
Reissue the given operation as a cached IO operation
|
|
|
The version of the supplied content information is not supported.
|
|
|
The supplied content information is malformed.
|
|
|
The requested data cannot be found in local or peer caches.
|
|
|
No more data is available or required.
|
|
|
The supplied object has not been initialized.
|
|
|
The supplied object has already been initialized.
|
|
|
A shutdown operation is already in progress.
|
|
|
The supplied object has already been invalidated.
|
|
|
An element already exists and was not replaced.
|
|
|
Can not cancel the requested operation as it has already been completed.
|
|
|
Can not perform the requested operation because it has already been carried out.
|
|
|
An operation accessed data beyond the bounds of valid data.
|
|
|
The requested version is not supported.
|
|
|
A configuration value is invalid.
|
|
|
The SKU is not licensed.
|
|
|
PeerDist Service is still initializing and will be available shortly.
|
|
|
Communication with one or more computers will be temporarily blocked due to recent errors.
|
|
|
This operation is only valid in the context of an app container.
|
|
|
This application can only run in the context of an app container.
|
|
|
This functionality is not supported in the context of an app container.
|
|
|
The length of the SID supplied is not a valid length for app container SIDs.
|
|
|
Read
|
|
|
Full
|
|
|
Please type the password:
|
|
|
Fast Cache has been ReArmed and requires a reboot until it can be updated.
|
|
|
The copy offload write operation is not supported by a filter.
|
|
|
The copy offload read operation is not supported for the file.
|
|
|
The copy offload write operation is not supported for the file.
|
|
|
This file is currently associated with a different stream id.
|
|
|
The volume must undergo garbage collection.
|
|
|
The WOF driver encountered a corruption in WIM image's Header.
|
|
|
The WOF driver encountered a corruption in WIM image's Resource Table.
|
|
|
The WOF driver encountered a corruption in the compressed file's Resource Table.
|
|
|
System Integrity detected that policy rollback has been attempted.
|
|
|
Your organization used Device Guard to block this app. Contact your support person for more info.
|
|
|
The System Integrity policy is invalid.
|
|
|
The System Integrity policy is either not signed or is signed by a non-trusted signer.
|
|
|
The number of System Integrity policies is out of limit.
|
|
|
The Code Integrity supplemental policy is not authorized by a Code Integrity base policy.
|
|
|
Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled.
|
|
|
The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS.
|
|
|
Cannot enumerate servers in non-default compartment.
|
|
|
BranchCache
|
|
|
None
|
|
|
Dynamic DNS updates have been manually disabled on this domain controller.
|
|
|
The cluster configuration action has already been committed.
|
|
|
The cluster configuration action could not be rolled back.
|
|
|
The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node.
|
|
|
One or more nodes in the cluster are running a version of Windows that does not support this operation.
|
|
|
The name of the corresponding computer account doesn't match the Network Name for this resource.
|
|
|
No network adapters are available.
|
|
|
The cluster node has been poisoned.
|
|
|
The group is unable to accept the request since it is moving to another node.
|
|
|
The resource type cannot accept the request since is too busy performing another operation.
|
|
|
The call to the cluster resource DLL timed out.
|
|
|
The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted.
|
|
|
An internal cluster error occurred. A call to an invalid function was attempted.
|
|
|
A parameter value is out of acceptable range.
|
|
|
A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required.
|
|
|
An invalid cluster registry operation was attempted.
|
|
|
An input string of characters is not properly terminated.
|
|
|
An input string of characters is not in a valid format for the data it represents.
|
|
|
An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress.
|
|
|
An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress.
|
|
|
An internal cluster error occurred. Data was not properly initialized.
|
|
|
An error occurred while reading from a stream of data. An unexpected number of bytes was returned.
|
|
|
An error occurred while writing to a stream of data. The required number of bytes could not be written.
|
|
|
An error occurred while deserializing a stream of cluster data.
|
|
|
One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s).
|
|
|
A quorum of cluster nodes was not present to form a cluster.
|
|
|
The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address.
|
|
|
The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends.
|
|
|
Quorum resource cannot reside in the Available Storage group.
|
|
|
The dependencies for this resource are nested too deeply.
|
|
|
The call into the resource DLL raised an unhandled exception.
|
|
|
The RHS process failed to initialize.
|
|
|
The Failover Clustering feature is not installed on this node.
|
|
|
The resources must be online on the same node for this operation
|
|
|
A new node can not be added since this cluster is already at its maximum number of nodes.
|
|
|
This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit.
|
|
|
An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain.
|
|
|
This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed.
|
|
|
File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes.
|
|
|
Eviction of this node is invalid at this time. Due to quorum requirements node eviction will result in cluster shutdown. If it is the last node in the cluster, destroy cluster command should be used.
|
|
|
Only one instance of this resource type is allowed in the cluster.
|
|
|
Only one instance of this resource type is allowed per resource group.
|
|
|
The resource failed to come online due to the failure of one or more provider resources.
|
|
|
The resource has indicated that it cannot come online on any node.
|
|
|
The current operation cannot be performed on this group at this time.
|
|
|
The directory or file is not located on a cluster shared volume.
|
|
|
The Security Descriptor does not meet the requirements for a cluster.
|
|
|
There is one or more shared volumes resources configured in the cluster. Those resources must be moved to available storage in order for operation to succeed.
|
|
|
This group or resource cannot be directly manipulated. Use shared volume APIs to perform desired operation.
|
|
|
Back up is in progress. Please wait for backup completion before trying this operation again.
|
|
|
The path does not belong to a cluster shared volume.
|
|
|
The cluster shared volume is not locally mounted on this node.
|
|
|
The cluster watchdog is terminating.
|
|
|
A resource vetoed a move between two nodes because they are incompatible.
|
|
|
The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements.
|
|
|
The resource vetoed the call.
|
|
|
Resource could not start or run because it could not reserve sufficient system resources.
|
|
|
A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation.
|
|
|
A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation.
|
|
|
The requested operation can not be completed because the group is queued for an operation.
|
|
|
The requested operation can not be completed because a resource has locked status.
|
|
|
The resource cannot move to another node because a cluster shared volume vetoed the operation.
|
|
|
A node drain is already in progress.
|
|
|
Clustered storage is not connected to the node.
|
|
|
The disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS or REFS.
|
|
|
The resource must be part of the Available Storage group to complete this action.
|
|
|
CSVFS failed operation as volume is in redirected mode.
|
|
|
CSVFS failed operation as volume is not in redirected mode.
|
|
|
Cluster properties cannot be returned at this time.
|
|
|
The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes.
|
|
|
The operation cannot be completed because the resource is in maintenance mode.
|
|
|
The operation cannot be completed because of cluster affinity conflicts
|
|
|
The operation cannot be completed because the resource is a replica virtual machine.
|
|
|
The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version.
|
|
|
Updating the cluster functional level failed because the cluster is running in fix quorum mode. Start additional nodes which are members of the cluster until the cluster reaches quorum and the cluster will automatically switch out of fix quorum mode, or stop and restart the cluster without the FixQuorum switch. Once the cluster is out of fix quorum mode retry the Update-ClusterFunctionalLevel PowerShell cmdlet to update the cluster functional level.
|
|
|
The cluster functional level has been successfully updated but not all features are available yet. Restart the cluster by using the Stop-Cluster PowerShell cmdlet followed by the Start-Cluster PowerShell cmdlet and all cluster features will be available.
|
|
|
The cluster is currently performing a version upgrade.
|
|
|
The cluster did not successfully complete the version upgrade.
|
|
|
The cluster node is in grace period.
|
|
|
The operation has failed because CSV volume was not able to recover in time specified on this file object.
|
|
|
The operation failed because the requested node is not currently part of active cluster membership.
|
|
|
The operation failed because the requested cluster resource is currently unmonitored.
|
|
|
The operation failed because a resource does not support running in an unmonitored state.
|
|
|
The operation cannot be completed because a resource participates in replication.
|
|
|
The operation failed because the requested cluster node has been isolated
|
|
|
The operation failed because the requested cluster node has been quarantined
|
|
|
The operation failed because the specified database update condition was not met
|
|
|
A clustered space is in a degraded condition and the requested action cannot be completed at this time.
|
|
|
The operation failed because token delegation for this control is not supported.
|
|
|
The operation has failed because CSV has invalidated this file object.
|
|
|
This operation is supported only on the CSV coordinator node.
|
|
|
The cluster group set is not available for any further requests.
|
|
|
The cluster group set could not be found.
|
|
|
The action cannot be completed at this time because the cluster group set would fall below quorum and not be able to act as a provider.
|
|
|
The specified parent fault domain is not found.
|
|
|
The fault domain cannot be a child of the parent specified.
|
|
|
Storage Spaces Direct has rejected the proposed fault domain changes because it impacts the fault tolerance of the storage.
|
|
|
Storage Spaces Direct has rejected the proposed fault domain changes because it reduces the storage connected to the system.
|
|
|
Cluster infrastructure file server creation failed because a valid non-empty file server name was not provided.
|
|
|
The action cannot be completed because the cluster set management cluster is unreachable.
|
|
|
The remote server sent an invalid response for a file being opened with Client Side Encryption.
|
|
|
Client Side Encryption is not supported by the remote server even though it claims to support it.
|
|
|
File is encrypted and should be opened in Client Side Encryption mode.
|
|
|
A new encrypted file is being created and a $EFS needs to be provided.
|
|
|
The SMB client requested a CSE FSCTL on a non-CSE file.
|
|
|
The requested operation was blocked by policy. For more information, contact your system administrator.
|
|
|
The specified file could not be encrypted with Windows Information Protection.
|
|
|
Log service encountered an invalid log sector.
|
|
|
Log service encountered a log sector with invalid block parity.
|
|
|
Log service encountered a remapped log sector.
|
|
|
Log service encountered a partial or incomplete log block.
|
|
|
Log service encountered an attempt access data outside the active log range.
|
|
|
Log service user marshalling buffers are exhausted.
|
|
|
Log service encountered an attempt read from a marshalling area with an invalid read context.
|
|
|
Log service encountered an invalid log restart area.
|
|
|
Log service encountered an invalid log block version.
|
|
|
Log service encountered an invalid log block.
|
|
|
Log service encountered an attempt to read the log with an invalid read mode.
|
|
|
Log service encountered a log stream with no restart area.
|
|
|
Log service encountered a corrupted metadata file.
|
|
|
Log service encountered a metadata file that could not be created by the log file system.
|
|
|
Log service encountered a metadata file with inconsistent data.
|
|
|
Log service encountered an attempt to erroneous allocate or dispose reservation space.
|
|
|
Log service cannot delete log file or file system container.
|
|
|
Log service has reached the maximum allowable containers allocated to a log file.
|
|
|
Log service has attempted to read or write backward past the start of the log.
|
|
|
Log policy could not be installed because a policy of the same type is already present.
|
|
|
Log policy in question was not installed at the time of the request.
|
|
|
The installed set of policies on the log is invalid.
|
|
|
A policy on the log in question prevented the operation from completing.
|
|
|
Log space cannot be reclaimed because the log is pinned by the archive tail.
|
|
|
Log record is not a record in the log file.
|
|
|
Number of reserved log records or the adjustment of the number of reserved log records is invalid.
|
|
|
Reserved log space or the adjustment of the log space is invalid.
|
|
|
An new or existing archive tail or base of the active log is invalid.
|
|
|
Log space is exhausted.
|
|
|
The log could not be set to the requested size.
|
|
|
Log is multiplexed, no direct writes to the physical log is allowed.
|
|
|
The operation failed because the log is a dedicated log.
|
|
|
The operation requires an archive context.
|
|
|
Log archival is in progress.
|
|
|
The operation requires a non-ephemeral log, but the log is ephemeral.
|
|
|
The log must have at least two containers before it can be read from or written to.
|
|
|
A log client has already registered on the stream.
|
|
|
A log client has not been registered on the stream.
|
|
|
A request has already been made to handle the log full condition.
|
|
|
Log service encountered an error when attempting to read from a log container.
|
|
|
Log service encountered an error when attempting to write to a log container.
|
|
|
Log service encountered an error when attempting open a log container.
|
|
|
Log service encountered an invalid container state when attempting a requested action.
|
|
|
Log service is not in the correct state to perform a requested action.
|
|
|
Log space cannot be reclaimed because the log is pinned.
|
|
|
Log metadata flush failed.
|
|
|
Security on the log and its containers is inconsistent.
|
|
|
Records were appended to the log or reservation changes were made, but the log could not be flushed.
|
|
|
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.
|
|
|
The transaction handle associated with this operation is not valid.
|
|
|
The requested operation was made in the context of a transaction that is no longer active.
|
|
|
The requested operation is not valid on the Transaction object in its current state.
|
|
|
The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller.
|
|
|
It is too late to perform the requested operation, since the Transaction has already been aborted.
|
|
|
It is too late to perform the requested operation, since the Transaction has already been committed.
|
|
|
The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.
|
|
|
The specified ResourceManager made no changes or updates to the resource under this transaction.
|
|
|
The resource manager has attempted to prepare a transaction that it has not successfully joined.
|
|
|
The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow.
|
|
|
The RM tried to register a protocol that already exists.
|
|
|
The attempt to propagate the Transaction failed.
|
|
|
The requested propagation protocol was not registered as a CRM.
|
|
|
The buffer passed in to PushTransaction or PullTransaction is not in a valid format.
|
|
|
The current transaction context associated with the thread is not a valid handle to a transaction object.
|
|
|
The specified Transaction object could not be opened, because it was not found.
|
|
|
The specified ResourceManager object could not be opened, because it was not found.
|
|
|
The specified Enlistment object could not be opened, because it was not found.
|
|
|
The specified TransactionManager object could not be opened, because it was not found.
|
|
|
The object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline.
|
|
|
The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.
|
|
|
The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior.
|
|
|
Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.
|
|
|
The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask.
|
|
|
The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.
|
|
|
Implicit transaction are not supported.
|
|
|
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.
|
|
|
The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file.
|
|
|
This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.
|
|
|
The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed.
|
|
|
The transaction does not have a superior enlistment.
|
|
|
The attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data.
|
|
|
The function attempted to use a name that is reserved for use by another transaction.
|
|
|
Transaction support within the specified resource manager is not started or was shut down due to an error.
|
|
|
The metadata of the RM has been corrupted. The RM will not function.
|
|
|
The specified directory does not contain a resource manager.
|
|
|
The remote server or share does not support transacted file operations.
|
|
|
The requested log size is invalid.
|
|
|
The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.
|
|
|
The specified file miniversion was not found for this transacted file open.
|
|
|
The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.
|
|
|
A miniversion may only be opened in the context of the transaction that created it.
|
|
|
It is not possible to open a miniversion with modify access.
|
|
|
It is not possible to create any more miniversions for this stream.
|
|
|
The remote server sent mismatching version number or Fid for a file opened with transactions.
|
|
|
The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint.
|
|
|
There is no transaction metadata on the file.
|
|
|
The log data is corrupt.
|
|
|
The file can't be recovered because there is a handle still open on it.
|
|
|
The transaction outcome is unavailable because the resource manager responsible for it has disconnected.
|
|
|
The request was rejected because the enlistment in question is not a superior enlistment.
|
|
|
The transactional resource manager is already consistent. Recovery is not needed.
|
|
|
The transactional resource manager has already been started.
|
|
|
The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.
|
|
|
The operation cannot be performed because another transaction is depending on the fact that this property will not change.
|
|
|
The operation would involve a single file with two transactional resource managers and is therefore not allowed.
|
|
|
The $Txf directory must be empty for this operation to succeed.
|
|
|
The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.
|
|
|
The operation could not be completed because the transaction manager does not have a log.
|
|
|
A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.
|
|
|
The transactional metadata attribute on the file or directory is corrupt and unreadable.
|
|
|
The encryption operation could not be completed because a transaction is active.
|
|
|
This object is not allowed to be opened in a transaction.
|
|
|
An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.
|
|
|
Memory mapping (creating a mapped section) a remote file under a transaction is not supported.
|
|
|
Transaction metadata is already present on this file and cannot be superseded.
|
|
|
A transaction scope could not be entered because the scope handler has not been initialized.
|
|
|
Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.
|
|
|
This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.
|
|
|
The request to thaw frozen transactions was ignored because transactions had not previously been frozen.
|
|
|
Transactions cannot be frozen because a freeze is already in progress.
|
|
|
The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.
|
|
|
The savepoint operation failed because files are open on the transaction. This is not permitted.
|
|
|
Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.
|
|
|
The sparse operation could not be completed because a transaction is active on the file.
|
|
|
The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument.
|
|
|
I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.
|
|
|
The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.
|
|
|
The transactional resource manager had too many transactions outstanding that could not be aborted. The transactional resource manger has been shut down.
|
|
|
The operation could not be completed due to bad clusters on disk.
|
|
|
The compression operation could not be completed because a transaction is active on the file.
|
|
|
The operation could not be completed because the volume is dirty. Please run chkdsk and try again.
|
|
|
The link tracking operation could not be completed because a transaction is active.
|
|
|
This operation cannot be performed in a transaction.
|
|
|
The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one.
|
|
|
The specified operation could not be performed because the resource manager is not enlisted in the transaction.
|
|
|
Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared.
|
|
|
Remote logins are currently disabled.
|
|
|
You do not have the proper encryption level to access this Session.
|
|
|
The user s\\s is currently logged on to this computer. Only the current user or an administrator can log on to this computer.
|
|
|
The user s\\s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact s\\s and have them log off.
|
|
|
Unable to log you on because of an account restriction.
|
|
|
The Client Drive Mapping Service Has Connected on Terminal Connection.
|
|
|
The Client Drive Mapping Service Has Disconnected on Terminal Connection.
|
|
|
The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.
|
|
|
The target session is incompatible with the current session.
|
|
|
Windows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later, or contact the server administrator for assistance.
|
|
|
The directory service detected the subsystem that allocates relative identifiers is disabled. This can occur as a protective mechanism when the system determines a significant portion of relative identifiers (RIDs) have been exhausted. Please see http://go.microsoft.com/fwlink/?LinkId=228610 for recommended diagnostic steps and the procedure to re-enable account creation.
|
|
|
A cross reference is in use locally with the same name.
|
|
|
The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest.
|
|
|
Writeable NCs prevent this DC from demoting.
|
|
|
The requested object has a non-unique identifier and cannot be retrieved.
|
|
|
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
|
|
|
The group cannot be converted due to attribute restrictions on the requested group type.
|
|
|
Cross-domain move of non-empty basic application groups is not allowed.
|
|
|
Cross-domain move of non-empty query based application groups is not allowed.
|
|
|
The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
|
|
|
The target container for a redirection of a well known object container cannot already be a special container.
|
|
|
The Directory Service cannot perform the requested operation because a domain rename operation is in progress.
|
|
|
The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method.
|
|
|
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
|
|
|
The requested operation is not allowed on an object under the system container.
|
|
|
The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected.
|
|
|
The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency.
|
|
|
At this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies.
|
|
|
The site settings object for the specified site does not exist.
|
|
|
The local account store does not contain secret material for the specified account.
|
|
|
Could not find a writable domain controller in the domain.
|
|
|
The server object for the domain controller does not exist.
|
|
|
The NTDS Settings object for the domain controller does not exist.
|
|
|
The requested search operation is not supported for ASQ searches.
|
|
|
A required audit event could not be generated for the operation.
|
|
|
The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes.
|
|
|
The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings.
|
|
|
The address books are nested too deeply. Failed to build the hierarchy table.
|
|
|
The specified up-to-date-ness vector is corrupt.
|
|
|
The request to replicate secrets is denied.
|
|
|
Schema update failed: The MAPI identifier is reserved.
|
|
|
Schema update failed: There are no MAPI identifiers available.
|
|
|
The replication operation failed because the required attributes of the local krbtgt object are missing.
|
|
|
The domain name of the trusted domain already exists in the forest.
|
|
|
The flat name of the trusted domain already exists in the forest.
|
|
|
The User Principal Name (UPN) is invalid.
|
|
|
OID mapped groups cannot have members.
|
|
|
The specified OID cannot be found.
|
|
|
The replication operation failed because the target object referred by a link value is recycled.
|
|
|
The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller.
|
|
|
The functional level of the AD LDS configuration set cannot be lowered to the requested value.
|
|
|
The functional level of the domain (or forest) cannot be lowered to the requested value.
|
|
|
The functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level.
|
|
|
The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information.
|
|
|
The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object.
|
|
|
The system is not authoritative for the specified account and therefore cannot complete the operation. Please retry the operation using the provider associated with this account. If this is an online provider please use the provider's online site.
|
|
|
The operation failed because SPN value provided for addition/modification is not unique forest-wide.
|
|
|
The operation failed because UPN value provided for addition/modification is not unique forest-wide.
|
|
|
The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present.
|
|
|
The link value specified was not found, but a link value with that key was found.
|
|
|
Only the DNS server acting as the key master for the zone may perform this operation.
|
|
|
This operation is not allowed on a zone that is signed or has signing keys.
|
|
|
NSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC.
|
|
|
The zone does not have enough signing keys. There must be at least one key signing key (KSK) and at least one zone signing key (ZSK).
|
|
|
The specified algorithm is not supported.
|
|
|
The specified key size is not supported.
|
|
|
One or more of the signing keys for a zone are not accessible to the DNS server. Zone signing will not be operational until this error is resolved.
|
|
|
The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved.
|
|
|
An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved.
|
|
|
An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved.
|
|
|
The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved.
|
|
|
The specified key service provider cannot be opened by the DNS server.
|
|
|
The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone.
|
|
|
The specified rollover period is invalid.
|
|
|
The specified initial rollover offset is invalid.
|
|
|
The specified signing key is already in process of rolling over keys.
|
|
|
The specified signing key does not have a standby key to revoke.
|
|
|
This operation is not allowed on a zone signing key (ZSK).
|
|
|
This operation is not allowed on an active signing key.
|
|
|
The specified signing key is already queued for rollover.
|
|
|
This operation is not allowed on an unsigned zone.
|
|
|
This operation could not be completed because the DNS server listed as the current key master for this zone is down or misconfigured. Resolve the problem on the current key master for this zone or use another DNS server to seize the key master role.
|
|
|
The specified signature validity period is invalid.
|
|
|
The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone.
|
|
|
This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server.
|
|
|
This operation could not be completed because the XML stream received is empty or syntactically invalid.
|
|
|
This operation completed, but no trust anchors were added because all of the trust anchors received were either invalid, unsupported, expired, or would not become valid in less than 30 days.
|
|
|
The specified signing key is not waiting for parental DS update.
|
|
|
Hash collision detected during NSEC3 signing. Specify a different user-provided salt, or use a randomly generated salt, and attempt to sign the zone again.
|
|
|
NSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3.
|
|
|
DNS query request is pending.
|
|
|
The record could not be created because this part of the DNS namespace has been delegated to another server.
|
|
|
The DNS server could not find a set of root hints.
|
|
|
The DNS server found root hints but they were not consistent across all adapters.
|
|
|
The specified value is too small for this parameter.
|
|
|
The specified value is too large for this parameter.
|
|
|
This operation is not allowed while the DNS server is loading zones in the background. Please try again later.
|
|
|
The operation requested is not permitted on against a DNS server running on a read-only DC.
|
|
|
No data is allowed to exist underneath a DNAME record.
|
|
|
This operation requires credentials delegation.
|
|
|
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator.
|
|
|
Not allowed to remove all addresses.
|
|
|
This operation cannot be performed because the zone is currently being signed. Please try again later.
|
|
|
Node is a DNAME DNS record.
|
|
|
A DNAME record already exists for given name.
|
|
|
An alias loop has been detected with either CNAME or DNAME records.
|
|
|
The directory partition is not available at this time. Please wait a few minutes and try again.
|
|
|
The operation failed because the domain naming master FSMO role could not be reached. The domain controller holding the domain naming master FSMO role is down or unable to service the request or is not running Windows Server 2003 or later.
|
|
|
The RRL is not enabled.
|
|
|
The window size parameter is invalid. It should be greater than or equal to 1.
|
|
|
The IPv4 prefix length parameter is invalid. It should be less than or equal to 32.
|
|
|
The IPv6 prefix length parameter is invalid. It should be less than or equal to 128.
|
|
|
The TC Rate parameter is invalid. It should be less than 10.
|
|
|
The Leak Rate parameter is invalid. It should be either 0, or between 2 and 10.
|
|
|
The Leak Rate or TC Rate parameter is invalid. Leak Rate should be greater than TC Rate.
|
|
|
The virtualization instance already exists.
|
|
|
The virtualization instance does not exist.
|
|
|
The virtualization tree is locked.
|
|
|
Invalid virtualization instance name.
|
|
|
The default virtualization instance cannot be added, removed or modified.
|
|
|
The scope already exists for the zone.
|
|
|
The scope does not exist for the zone.
|
|
|
The scope is the same as the default zone scope.
|
|
|
The scope name contains invalid characters.
|
|
|
Operation not allowed when the zone has scopes.
|
|
|
Failed to load zone scope.
|
|
|
Failed to write data file for DNS zone scope. Please verify the file exists and is writable.
|
|
|
The scope name contains invalid characters.
|
|
|
The scope does not exist.
|
|
|
The scope is the same as the default scope.
|
|
|
The operation is invalid on the scope.
|
|
|
The scope is locked.
|
|
|
The scope already exists.
|
|
|
A policy with the same name already exists on this level (server level or zone level) on the DNS server.
|
|
|
No policy with this name exists on this level (server level or zone level) on the DNS server.
|
|
|
The criteria provided in the policy are invalid.
|
|
|
At least one of the settings of this policy is invalid.
|
|
|
The client subnet cannot be deleted while it is being accessed by a policy.
|
|
|
The client subnet does not exist on the DNS server.
|
|
|
A client subnet with this name already exists on the DNS server.
|
|
|
The IP subnet specified does not exist in the client subnet.
|
|
|
The IP subnet that is being added, already exists in the client subnet.
|
|
|
The policy is locked.
|
|
|
The weight of the scope in the policy is invalid.
|
|
|
The DNS policy name is invalid.
|
|
|
The policy is missing criteria.
|
|
|
The name of the the client subnet record is invalid.
|
|
|
Invalid policy processing order.
|
|
|
The scope information has not been provided for a policy that requires it.
|
|
|
The scope information has been provided for a policy that does not require it.
|
|
|
The server scope cannot be deleted because it is referenced by a DNS Policy.
|
|
|
The zone scope cannot be deleted because it is referenced by a DNS Policy.
|
|
|
The criterion client subnet provided in the policy is invalid.
|
|
|
The criterion transport protocol provided in the policy is invalid.
|
|
|
The criterion network protocol provided in the policy is invalid.
|
|
|
The criterion interface provided in the policy is invalid.
|
|
|
The criterion FQDN provided in the policy is invalid.
|
|
|
The criterion query type provided in the policy is invalid.
|
|
|
The criterion time of day provided in the policy is invalid.
|
|
|
No such host is known securely.
|
|
|
Name based IPSEC policy could not be added.
|
|
|
The Main Mode policy was successfully added, but some of the requested offers are not supported.
|
|
|
The Quick Mode policy was successfully added, but some of the requested offers are not supported.
|
|
|
Simultaneous rekeys were detected.
|
|
|
Don't know how to process critical payload
|
|
|
The recipient cannot handle version of IKE specified in the header.
|
|
|
Main mode SA lifetime expired or peer sent a main mode delete.
|
|
|
Main mode SA assumed to be invalid because peer stopped responding.
|
|
|
Certificate doesn't chain to a trusted root in IPsec policy.
|
|
|
Received unexpected message ID.
|
|
|
Received invalid authentication offers.
|
|
|
Sent DoS cookie notify to initiator.
|
|
|
IKE service is shutting down.
|
|
|
Could not verify binding between CGA address and certificate.
|
|
|
Error processing NatOA payload.
|
|
|
Parameters of the main mode are invalid for this quick mode.
|
|
|
Quick mode SA was expired by IPsec driver.
|
|
|
Too many dynamically added IKEEXT filters were detected.
|
|
|
ERROR_IPSEC_IKE_NEG_STATUS_END
|
|
|
NAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel.
|
|
|
Error in assigning inner IP address to initiator in tunnel mode.
|
|
|
Require configuration payload missing.
|
|
|
A negotiation running as the security principle who issued the connection is in progress
|
|
|
SA was deleted due to IKEv1/AuthIP co-existence suppress check.
|
|
|
Incoming SA request was dropped due to peer IP address rate limiting.
|
|
|
Peer does not support MOBIKE.
|
|
|
SA establishment is not authorized.
|
|
|
SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential.
|
|
|
SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard.
|
|
|
SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This might be related to certificate-to-account mapping failure for the SA.
|
|
|
ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END
|
|
|
The SPI in the packet does not match a valid IPsec SA.
|
|
|
Packet was received on an IPsec SA whose lifetime has expired.
|
|
|
Packet was received on an IPsec SA that does not match the packet characteristics.
|
|
|
Packet sequence number replay check failed.
|
|
|
IPsec header and/or trailer in the packet is invalid.
|
|
|
IPsec integrity check failed.
|
|
|
IPsec dropped a clear text packet.
|
|
|
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.
|
|
|
IPsec dropped a packet due to DoS throttling.
|
|
|
IPsec DoS Protection matched an explicit block rule.
|
|
|
IPsec DoS Protection received an IPsec specific multicast packet which is not allowed.
|
|
|
IPsec DoS Protection received an incorrectly formatted packet.
|
|
|
IPsec DoS Protection failed to look up state.
|
|
|
IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached.
|
|
|
IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.
|
|
|
IPsec DoS Protection has not been enabled.
|
|
|
IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached.
|
|
|
The referenced assembly could not be found.
|
|
|
The activation context activation stack for the running thread of execution is corrupt.
|
|
|
The application isolation metadata for this process or thread has become corrupt.
|
|
|
The activation context being deactivated is not the most recently activated one.
|
|
|
The activation context being deactivated is not active for the current thread of execution.
|
|
|
The activation context being deactivated has already been deactivated.
|
|
|
A component used by the isolation facility has requested to terminate the process.
|
|
|
A kernel mode component is releasing a reference on an activation context.
|
|
|
The activation context of system default assembly could not be generated.
|
|
|
The value of an attribute in an identity is not within the legal range.
|
|
|
The name of an attribute in an identity is not within the legal range.
|
|
|
An identity contains two definitions for the same attribute.
|
|
|
The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.
|
|
|
A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found.
|
|
|
The public key token does not correspond to the public key specified.
|
|
|
A substitution string had no mapping.
|
|
|
The component must be locked before making the request.
|
|
|
The component store has been corrupted.
|
|
|
An advanced installer failed during setup or servicing.
|
|
|
The character encoding in the XML declaration did not match the encoding used in the document.
|
|
|
The identities of the manifests are identical but their contents are different.
|
|
|
The component identities are different.
|
|
|
The assembly is not a deployment.
|
|
|
The file is not a part of the assembly.
|
|
|
The size of the manifest exceeds the maximum allowed.
|
|
|
The setting is not registered.
|
|
|
One or more required members of the transaction are not present.
|
|
|
The SMI primitive installer failed during setup or servicing.
|
|
|
A generic command executable returned a result that indicates failure.
|
|
|
A component is missing file verification information in its manifest.
|
|
|
Two or more components referenced directly or indirectly by the application manifest have the same WinRT ActivatableClass IDs.
|
|
|
The specified channel path is invalid.
|
|
|
The specified query is invalid.
|
|
|
The publisher metadata cannot be found in the resource.
|
|
|
The specified publisher name is invalid.
|
|
|
The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest.
|
|
|
The specified channel could not be found.
|
|
|
The specified XML text was not well-formed. See Extended Error for more details.
|
|
|
The events for a direct channel go directly to a log file and cannot be subscribed to.
|
|
|
Configuration error.
|
|
|
The query result is stale or invalid and must be recreated. This may be due to the log being cleared or rolling over after the query result was created.
|
|
|
The query result is currently at an invalid position.
|
|
|
Registered MSXML doesn't support validation.
|
|
|
An expression can only be followed by a change-of-scope operation if the expression evaluates to a node set and is not already part of another change-of-scope operation.
|
|
|
Cannot perform a step operation from a term that does not represent an element set.
|
|
|
Left-hand side arguments to binary operators must be either attributes, nodes or variables. Right-hand side arguments must be constants.
|
|
|
A step operation must involve a node test or, in the case of a predicate, an algebraic expression against which to test each node in the preceeding node set.
|
|
|
This data type is currently unsupported.
|
|
|
This operator is unsupported by this implementation of the filter.
|
|
|
An unexpected token was encountered.
|
|
|
The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled.
|
|
|
The channel failed to activate.
|
|
|
The XPath expression exceeded the supported complexity. Simplify the expression or split it into multiple expressions.
|
|
|
The message resource is present but the message was not found in the message table.
|
|
|
The message ID for the desired message could not be found.
|
|
|
The maximum number of replacements has been reached.
|
|
|
The locale specific resource for the desired message is not present.
|
|
|
The resource is too old and is not supported.
|
|
|
The resource is too new and is not supported.
|
|
|
The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded.
|
|
|
Attempted to create a numeric type that is outside of its valid range.
|
|
|
The subscription fails to activate.
|
|
|
The log of the subscription is in disabled state, and can not be used to forward events to. The log must first be enabled before the subscription can be activated.
|
|
|
When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription.
|
|
|
The credential store that is used to save credentials is full.
|
|
|
The credential used by this subscription can't be found in credential store.
|
|
|
No active channel is found for the query.
|
|
|
The resource loader failed to find MUI file.
|
|
|
The resource loader failed to load MUI file because the file fail to pass validation.
|
|
|
The RC Manifest is corrupted with garbage data or unsupported version or missing required item.
|
|
|
The RC Manifest has invalid culture name.
|
|
|
The RC Manifest has invalid ultimatefallback name.
|
|
|
The resource loader cache doesn't have loaded MUI entry.
|
|
|
User stopped resource enumeration.
|
|
|
UI language installation failed.
|
|
|
Locale installation failed.
|
|
|
A resource does not have default or neutral value.
|
|
|
Invalid PRI config file.
|
|
|
Invalid file type.
|
|
|
Unknown qualifier.
|
|
|
Invalid qualifier value.
|
|
|
No Candidate found.
|
|
|
The ResourceMap or NamedResource has an item that does not have default or neutral resource..
|
|
|
Invalid ResourceCandidate type.
|
|
|
Duplicate Resource Map.
|
|
|
Duplicate Entry.
|
|
|
Invalid Resource Identifier.
|
|
|
Filepath too long.
|
|
|
Unsupported directory type.
|
|
|
Invalid PRI File.
|
|
|
NamedResource Not Found.
|
|
|
ResourceMap Not Found.
|
|
|
Unsupported MRT profile type.
|
|
|
Invalid qualifier operator.
|
|
|
Unable to determine qualifier value or qualifier value has not been set.
|
|
|
Automerge is enabled in the PRI file.
|
|
|
Too many resources defined for package.
|
|
|
Resource File can not be used for merge operation.
|
|
|
Load/UnloadPriFiles cannot be used with resource packages.
|
|
|
Resource Contexts may not be created on threads that do not have a CoreWindow.
|
|
|
The singleton Resource Manager with different profile is already created.
|
|
|
The system component cannot operate given API operation
|
|
|
The resource is a direct reference to a non-default resource candidate.
|
|
|
Resource Map has been re-generated and the query string is not valid anymore.
|
|
|
The PRI files to be merged have incompatible versions.
|
|
|
The primary PRI files to be merged does not contain a schema.
|
|
|
Unable to load one of the PRI files to be merged.
|
|
|
Unable to add one of the PRI files to the merged file.
|
|
|
Unable to create the merged PRI file.
|
|
|
Packages for a PRI file merge must all be from the same package family.
|
|
|
Packages for a PRI file merge must not include multiple main packages.
|
|
|
Packages for a PRI file merge must not include bundle packages.
|
|
|
Packages for a PRI file merge must include one main package.
|
|
|
Packages for a PRI file merge must include at least one resource package.
|
|
|
Invalid name supplied for a canonical merged PRI file.
|
|
|
Unable to find the specified package.
|
|
|
No default value for language was specified.
|
|
|
The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or MCCS 2 Revision 1 specification.
|
|
|
The monitor's VCP Version (0xDF) VCP code returned an invalid version value.
|
|
|
The monitor does not comply with the MCCS specification it claims to support.
|
|
|
The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.
|
|
|
The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.
|
|
|
An internal Monitor Configuration API error occurred.
|
|
|
The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
|
|
|
The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
|
|
|
The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.
|
|
|
The requested system device cannot be found.
|
|
|
Hash generation for the specified hash version and hash type is not enabled on the server.
|
|
|
The hash requested from the server is not available or no longer valid.
|
|
|
The secondary interrupt controller instance that manages the specified interrupt is not registered.
|
|
|
The information supplied by the GPIO client driver is invalid.
|
|
|
The version specified by the GPIO client driver is not supported.
|
|
|
The registration packet supplied by the GPIO client driver is not valid.
|
|
|
The requested operation is not supported for the specified handle.
|
|
|
The requested connect mode conflicts with an existing mode on one or more of the specified pins.
|
|
|
The interrupt requested to be unmasked is not masked.
|
|
|
The requested run level switch cannot be completed successfully.
|
|
|
The service has an invalid run level setting. The run level for a service must not be higher than the run level of its dependent services.
|
|
|
The requested run level switch cannot be completed successfully since one or more services will not stop or restart within the specified timeout.
|
|
|
A run level switch agent did not respond within the specified timeout.
|
|
|
A run level switch is currently in progress.
|
|
|
One or more services failed to start during the service startup phase of a run level switch.
|
|
|
The task stop request cannot be completed immediately since task needs more time to shutdown.
|
|
|
Package could not be opened.
|
|
|
Package was not found.
|
|
|
Package data is invalid.
|
|
|
Package failed updates, dependency or conflict validation.
|
|
|
There is not enough disk space on your computer. Please free up some space and try again.
|
|
|
There was a problem downloading your product.
|
|
|
Package could not be registered.
|
|
|
Package could not be unregistered.
|
|
|
User cancelled the install request.
|
|
|
Install failed. Please contact your software vendor.
|
|
|
Removal failed. Please contact your software vendor.
|
|
|
The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details.
|
|
|
The application cannot be started. Try reinstalling the application to fix the problem.
|
|
|
A Prerequisite for an install could not be satisfied.
|
|
|
The package repository is corrupted.
|
|
|
To install this application you need either a Windows developer license or a sideloading-enabled system.
|
|
|
The application cannot be started because it is currently updating.
|
|
|
The package deployment operation is blocked by policy. Please contact your system administrator.
|
|
|
The package could not be installed because resources it modifies are currently in use.
|
|
|
The package could not be recovered because necessary data for recovery have been corrupted.
|
|
|
The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present.
|
|
|
An error occurred while deleting the package's previously existing application data.
|
|
|
The package could not be installed because a higher version of this package is already installed.
|
|
|
An error in a system binary was detected. Try refreshing the PC to fix the problem.
|
|
|
A corrupted CLR NGEN binary was detected on the system.
|
|
|
The operation could not be resumed because necessary data for recovery have been corrupted.
|
|
|
The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again.
|
|
|
Package move failed.
|
|
|
The deployment operation failed because the volume is not empty.
|
|
|
The deployment operation failed because the volume is offline.
|
|
|
The deployment operation failed because the specified volume is corrupt.
|
|
|
The deployment operation failed because the specified application needs to be registered first.
|
|
|
The deployment operation failed because the package targets the wrong processor architecture.
|
|
|
You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again.
|
|
|
A main app package is required to install this optional package. Install the main package first and try again.
|
|
|
This app package type is not supported on this filesystem
|
|
|
Package move operation is blocked until the application has finished streaming
|
|
|
A main or another optional app package has the same application ID as this optional package. Change the application ID for the optional package to avoid conflicts.
|
|
|
This staging session has been held to allow another staging operation to be prioritized.
|
|
|
A related set cannot be updated because the updated set is invalid. All packages in the related set must be updated at the same time.
|
|
|
An optional package with a FullTrust entry point requires the main package to have the runFullTrust capability.
|
|
|
An error occurred because a user was logged off.
|
|
|
An optional package provision requires the dependency main package to also be provisioned.
|
|
|
The packages failed the SmartScreen reputation check.
|
|
|
The SmartScreen reputation check operation timed out.
|
|
|
The current deployment option is not supported.
|
|
|
Activation is blocked due to the .appinstaller update settings for this app.
|
|
|
Remote drives are not supported; use \\server\share to register a remote package.
|
|
|
Failed to process and write downloaded APPX package data to disk.
|
|
|
The deployment operation was blocked due to a per-package-family policy restricting deployments on a non-system volume. Per policy, this app must be installed to the system drive, but that's not set as the default. In Storage Settings, make the system drive the default location to save new content, then retry the install.
|
|
|
The deployment operation was blocked due to a machine-wide policy restricting deployments on a non-system volume. Per policy, this app must be installed to the system drive, but that's not set as the default. In Storage Settings, make the system drive the default location to save new content, then retry the install.
|
|
|
The deployment operation was blocked because Special profile deployment is not allowed. Please try logging into an account that is not a Special profile. You can try logging out and logging back into the current account, or try logging into a different account.
|
|
|
The deployment operation failed due to a conflicting package's mutable package directory. To install this package remove the existing package with the conflicting mutable package directory.
|
|
|
The package installation failed because a singleton resource was specified and another user with that package installed is logged in. Please make sure that all active users with the package installed are logged out and retry installation.
|
|
|
The package installation failed because a different version of the service is installed. Try installing a newer version of the package.
|
|
|
The package installation failed because a version of the service exists outside of APPX packaging. Please contact your software vendor.
|
|
|
The package installation failed because administrator privileges are required. Please contact an administrator to install this package.
|
|
|
The process has no package identity.
|
|
|
The package runtime information is corrupted.
|
|
|
The package identity is corrupted.
|
|
|
The process has no application identity.
|
|
|
One or more AppModel Runtime group policy values could not be read. Please contact your system administrator with the contents of your AppModel Runtime event log.
|
|
|
One or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log.
|
|
|
The package is currently not available.
|
|
|
The package does not have a mutable directory.
|
|
|
Loading the state store failed.
|
|
|
Retrieving the state version for the application failed.
|
|
|
Setting the state version for the application failed.
|
|
|
Resetting the structured state of the application failed.
|
|
|
State Manager failed to open the container.
|
|
|
State Manager failed to create the container.
|
|
|
State Manager failed to delete the container.
|
|
|
State Manager failed to read the setting.
|
|
|
State Manager failed to write the setting.
|
|
|
State Manager failed to delete the setting.
|
|
|
State Manager failed to query the setting.
|
|
|
State Manager failed to read the composite setting.
|
|
|
State Manager failed to write the composite setting.
|
|
|
State Manager failed to enumerate the containers.
|
|
|
State Manager failed to enumerate the settings.
|
|
|
The size of the state manager composite setting value has exceeded the limit.
|
|
|
The size of the state manager setting value has exceeded the limit.
|
|
|
The length of the state manager setting name has exceeded the limit.
|
|
|
The length of the state manager container name has exceeded the limit.
|
|
|
This API cannot be used in the context of the caller's application type.
|
|
|
This PC does not have a valid license for the application or product.
|
|
|
The authenticated user does not have a valid license for the application or product.
|
|
|
The commerce transaction associated with this license is still pending verification.
|
|
|
The license has been revoked for this user.
|
|
|
The operation completed successfully.
|
|
|
Incorrect function.
|
|
|
The system cannot find the file specified.
|
|
|
The system cannot find the path specified.
|
|
|
The system cannot open the file.
|
|
|
Access is denied.
|
|
|
The handle is invalid.
|
|
|
The storage control blocks were destroyed.
|
|
|
Not enough memory resources are available to process this command.
|
|
|
The storage control block address is invalid.
|
|
|
The environment is incorrect.
|
|
|
An attempt was made to load a program with an incorrect format.
|
|
|
The access code is invalid.
|
|
|
The data is invalid.
|
|
|
Not enough memory resources are available to complete this operation.
|
|
|
The system cannot find the drive specified.
|
|
|
The directory cannot be removed.
|
|
|
The system cannot move the file to a different disk drive.
|
|
|
There are no more files.
|
|
|
The media is write protected.
|
|
|
The system cannot find the device specified.
|
|
|
The device is not ready.
|
|
|
The device does not recognize the command.
|
|
|
Data error (cyclic redundancy check).
|
|
|
The program issued a command but the command length is incorrect.
|
|
|
The drive cannot locate a specific area or track on the disk.
|
|
|
The specified disk or diskette cannot be accessed.
|
|
|
The drive cannot find the sector requested.
|
|
|
The printer is out of paper.
|
|
|
The system cannot write to the specified device.
|
|
|
The system cannot read from the specified device.
|
|
|
A device attached to the system is not functioning.
|
|
|
The process cannot access the file because it is being used by another process.
|
|
|
The process cannot access the file because another process has locked a portion of the file.
|
|
|
Too many files opened for sharing.
|
|
|
Reached the end of the file.
|
|
|
The disk is full.
|
|
|
The request is not supported.
|
|
|
Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator.
|
|
|
You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.
|
|
|
The network path was not found.
|
|
|
The network is busy.
|
|
|
The specified network resource or device is no longer available.
|
|
|
The network BIOS command limit has been reached.
|
|
|
A network adapter hardware error occurred.
|
|
|
The specified server cannot perform the requested operation.
|
|
|
An unexpected network error occurred.
|
|
|
The remote adapter is not compatible.
|
|
|
The printer queue is full.
|
|
|
Space to store the file waiting to be printed is not available on the server.
|
|
|
Your file waiting to be printed was deleted.
|
|
|
The specified network name is no longer available.
|
|
|
Network access is denied.
|
|
|
The network resource type is not correct.
|
|
|
The network name cannot be found.
|
|
|
The name limit for the local computer network adapter card was exceeded.
|
|
|
The network BIOS session limit was exceeded.
|
|
|
The remote server has been paused or is in the process of being started.
|
|
|
No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.
|
|
|
The specified printer or disk device has been paused.
|
|
|
The file exists.
|
|
|
The directory or file cannot be created.
|
|
|
Fail on INT 24.
|
|
|
Storage to process this request is not available.
|
|
|
The local device name is already in use.
|
|
|
The specified network password is not correct.
|
|
|
The parameter is incorrect.
|
|
|
A write fault occurred on the network.
|
|
|
The system cannot start another process at this time.
|
|
|
Cannot create another system semaphore.
|
|
|
The exclusive semaphore is owned by another process.
|
|
|
The semaphore is set and cannot be closed.
|
|
|
The semaphore cannot be set again.
|
|
|
Cannot request exclusive semaphores at interrupt time.
|
|
|
The previous ownership of this semaphore has ended.
|
|
|
The program stopped because an alternate diskette was not inserted.
|
|
|
The disk is in use or locked by another process.
|
|
|
The pipe has been ended.
|
|
|
The system cannot open the device or file specified.
|
|
|
The file name is too long.
|
|
|
There is not enough space on the disk.
|
|
|
No more internal file identifiers available.
|
|
|
The target internal file identifier is incorrect.
|
|
|
The IOCTL call made by the application program is not correct.
|
|
|
The verify-on-write switch parameter value is not correct.
|
|
|
The system does not support the command requested.
|
|
|
This function is not supported on this system.
|
|
|
The semaphore timeout period has expired.
|
|
|
The data area passed to a system call is too small.
|
|
|
The filename, directory name, or volume label syntax is incorrect.
|
|
|
The system call level is not correct.
|
|
|
The disk has no volume label.
|
|
|
The specified module could not be found.
|
|
|
The specified procedure could not be found.
|
|
|
There are no child processes to wait for.
|
|
|
Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O.
|
|
|
An attempt was made to move the file pointer before the beginning of the file.
|
|
|
The file pointer cannot be set on the specified device or file.
|
|
|
A JOIN or SUBST command cannot be used for a drive that contains previously joined drives.
|
|
|
An attempt was made to use a JOIN or SUBST command on a drive that has already been joined.
|
|
|
An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted.
|
|
|
The system tried to delete the JOIN of a drive that is not joined.
|
|
|
The system tried to delete the substitution of a drive that is not substituted.
|
|
|
The system tried to join a drive to a directory on a joined drive.
|
|
|
The system tried to substitute a drive to a directory on a substituted drive.
|
|
|
The system tried to join a drive to a directory on a substituted drive.
|
|
|
The system tried to SUBST a drive to a directory on a joined drive.
|
|
|
The system cannot perform a JOIN or SUBST at this time.
|
|
|
The system cannot join or substitute a drive to or for a directory on the same drive.
|
|
|
The directory is not a subdirectory of the root directory.
|
|
|
The directory is not empty.
|
|
|
The path specified is being used in a substitute.
|
|
|
Not enough resources are available to process this command.
|
|
|
The path specified cannot be used at this time.
|
|
|
An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute.
|
|
|
System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.
|
|
|
The number of specified semaphore events for DosMuxSemWait is not correct.
|
|
|
DosMuxSemWait did not execute; too many semaphores are already set.
|
|
|
The DosMuxSemWait list is not correct.
|
|
|
The volume label you entered exceeds the label character limit of the target file system.
|
|
|
Cannot create another thread.
|
|
|
The recipient process has refused the signal.
|
|
|
The segment is already discarded and cannot be locked.
|
|
|
The segment is already unlocked.
|
|
|
The address for the thread ID is not correct.
|
|
|
One or more arguments are not correct.
|
|
|
The specified path is invalid.
|
|
|
A signal is already pending.
|
|
|
No more threads can be created in the system.
|
|
|
Unable to lock a region of a file.
|
|
|
The requested resource is in use.
|
|
|
A lock request was not outstanding for the supplied cancel region.
|
|
|
The file system does not support atomic changes to the lock type.
|
|
|
The system detected a segment number that was not correct.
|
|
|
Cannot create a file when that file already exists.
|
|
|
The flag passed is not correct.
|
|
|
The specified system semaphore name was not found.
|
|
|
The operating system cannot run this application program.
|
|
|
The operating system is not presently configured to run this application.
|
|
|
The operating system cannot run this application program.
|
|
|
The code segment cannot be greater than or equal to 64K.
|
|
|
The system could not find the environment option that was entered.
|
|
|
No process in the command subtree has a signal handler.
|
|
|
The filename or extension is too long.
|
|
|
The ring 2 stack is in use.
|
|
|
The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.
|
|
|
The signal being posted is not correct.
|
|
|
The signal handler cannot be set.
|
|
|
The segment is locked and cannot be reallocated.
|
|
|
Too many dynamic-link modules are attached to this program or dynamic-link module.
|
|
|
Cannot nest calls to LoadModule.
|
|
|
The pipe state is invalid.
|
|
|
All pipe instances are busy.
|
|
|
The pipe is being closed.
|
|
|
No process is on the other end of the pipe.
|
|
|
More data is available.
|
|
|
The session was canceled.
|
|
|
The specified extended attribute name was invalid.
|
|
|
The extended attributes are inconsistent.
|
|
|
The wait operation timed out.
|
|
|
No more data is available.
|
|
|
The copy functions cannot be used.
|
|
|
The directory name is invalid.
|
|
|
The extended attributes did not fit in the buffer.
|
|
|
The extended attribute file on the mounted file system is corrupt.
|
|
|
The extended attribute table file is full.
|
|
|
The specified extended attribute handle is invalid.
|
|
|
The mounted file system does not support extended attributes.
|
|
|
Attempt to release mutex not owned by caller.
|
|
|
Too many posts were made to a semaphore.
|
|
|
Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
|
|
|
The oplock request is denied.
|
|
|
An invalid oplock acknowledgment was received by the system.
|
|
|
The volume is too fragmented to complete this operation.
|
|
|
The file cannot be opened because it is in the process of being deleted.
|
|
|
Attempt to access invalid address.
|
|
|
Arithmetic result exceeded 32 bits.
|
|
|
There is a process on other end of the pipe.
|
|
|
Waiting for a process to open the other end of the pipe.
|
|
|
Access to the extended attribute was denied.
|
|
|
The I/O operation has been aborted because of either a thread exit or an application request.
|
|
|
Overlapped I/O event is not in a signaled state.
|
|
|
Overlapped I/O operation is in progress.
|
|
|
Invalid access to memory location.
|
|
|
Error performing inpage operation.
|
|
|
Recursion too deep; the stack overflowed.
|
|
|
The window cannot act on the sent message.
|
|
|
Cannot complete this function.
|
|
|
Invalid flags.
|
|
|
The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted.
|
|
|
The volume for a file has been externally altered so that the opened file is no longer valid.
|
|
|
The requested operation cannot be performed in full-screen mode.
|
|
|
An attempt was made to reference a token that does not exist.
|
|
|
The configuration registry database is corrupt.
|
|
|
The configuration registry key is invalid.
|
|
|
The configuration registry key could not be opened.
|
|
|
The configuration registry key could not be read.
|
|
|
The configuration registry key could not be written.
|
|
|
One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.
|
|
|
The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted.
|
|
|
An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.
|
|
|
The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.
|
|
|
Illegal operation attempted on a registry key that has been marked for deletion.
|
|
|
System could not allocate the required space in a registry log.
|
|
|
Cannot create a symbolic link in a registry key that already has subkeys or values.
|
|
|
Cannot create a stable subkey under a volatile parent key.
|
|
|
A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes.
|
|
|
A stop control has been sent to a service that other running services are dependent on.
|
|
|
The requested control is not valid for this service.
|
|
|
The service did not respond to the start or control request in a timely fashion.
|
|
|
A thread could not be created for the service.
|
|
|
The service database is locked.
|
|
|
An instance of the service is already running.
|
|
|
The account name is invalid or does not exist, or the password is invalid for the account name specified.
|
|
|
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
|
|
|
Circular service dependency was specified.
|
|
|
The specified service does not exist as an installed service.
|
|
|
The service cannot accept control messages at this time.
|
|
|
The service has not been started.
|
|
|
The service process could not connect to the service controller.
|
|
|
An exception occurred in the service when handling the control request.
|
|
|
The database specified does not exist.
|
|
|
The service has returned a service-specific error code.
|
|
|
The process terminated unexpectedly.
|
|
|
The dependency service or group failed to start.
|
|
|
The service did not start due to a logon failure.
|
|
|
After starting, the service hung in a start-pending state.
|
|
|
The specified service database lock is invalid.
|
|
|
The specified service has been marked for deletion.
|
|
|
The specified service already exists.
|
|
|
The system is currently running with the last-known-good configuration.
|
|
|
The dependency service does not exist or has been marked for deletion.
|
|
|
The current boot has already been accepted for use as the last-known-good control set.
|
|
|
No attempts to start the service have been made since the last boot.
|
|
|
The name is already in use as either a service name or a service display name.
|
|
|
The account specified for this service is different from the account specified for other services running in the same process.
|
|
|
Failure actions can only be set for Win32 services, not for drivers.
|
|
|
This service runs in the same process as the service control manager. Therefore, the service control manager cannot take action if this service's process terminates unexpectedly.
|
|
|
No recovery program has been configured for this service.
|
|
|
The executable program that this service is configured to run in does not implement the service.
|
|
|
This service cannot be started in Safe Mode
|
|
|
The physical end of the tape has been reached.
|
|
|
A tape access reached a filemark.
|
|
|
The beginning of the tape or a partition was encountered.
|
|
|
A tape access reached the end of a set of files.
|
|
|
No more data is on the tape.
|
|
|
Tape could not be partitioned.
|
|
|
When accessing a new tape of a multivolume partition, the current block size is incorrect.
|
|
|
Tape partition information could not be found when loading a tape.
|
|
|
Unable to lock the media eject mechanism.
|
|
|
Unable to unload the media.
|
|
|
The media in the drive may have changed.
|
|
|
The I/O bus was reset.
|
|
|
No media in drive.
|
|
|
No mapping for the Unicode character exists in the target multi-byte code page.
|
|
|
A dynamic link library (DLL) initialization routine failed.
|
|
|
A system shutdown is in progress.
|
|
|
Unable to abort the system shutdown because no shutdown was in progress.
|
|
|
The request could not be performed because of an I/O device error.
|
|
|
No serial device was successfully initialized. The serial driver will unload.
|
|
|
Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened.
|
|
|
A serial I/O operation was completed by another write to the serial port. (The IOCTL_SERIAL_XOFF_COUNTER reached zero.)
|
|
|
A serial I/O operation completed because the timeout period expired. (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)
|
|
|
No ID address mark was found on the floppy disk.
|
|
|
Mismatch between the floppy disk sector ID field and the floppy disk controller track address.
|
|
|
The floppy disk controller reported an error that is not recognized by the floppy disk driver.
|
|
|
The floppy disk controller returned inconsistent results in its registers.
|
|
|
While accessing the hard disk, a recalibrate operation failed, even after retries.
|
|
|
While accessing the hard disk, a disk operation failed even after retries.
|
|
|
While accessing the hard disk, a disk controller reset was needed, but even that failed.
|
|
|
Physical end of tape encountered.
|
|
|
Not enough server memory resources are available to process this command.
|
|
|
A potential deadlock condition has been detected.
|
|
|
The base address or the file offset specified does not have the proper alignment.
|
|
|
An attempt to change the system power state was vetoed by another application or driver.
|
|
|
The system BIOS failed an attempt to change the system power state.
|
|
|
An attempt was made to create more links on a file than the file system supports.
|
|
|
The specified program requires a newer version of Windows.
|
|
|
The specified program is not a Windows or MS-DOS program.
|
|
|
Cannot start more than one instance of the specified program.
|
|
|
The specified program was written for an earlier version of Windows.
|
|
|
One of the library files needed to run this application is damaged.
|
|
|
No application is associated with the specified file for this operation.
|
|
|
An error occurred in sending the command to the application.
|
|
|
One of the library files needed to run this application cannot be found.
|
|
|
The current process has used all of its system allowance of handles for Window Manager objects.
|
|
|
The message can be used only with synchronous operations.
|
|
|
The indicated source element has no media.
|
|
|
The indicated destination element already contains media.
|
|
|
The indicated element does not exist.
|
|
|
The indicated element is part of a magazine that is not present.
|
|
|
The indicated device requires reinitialization due to hardware errors.
|
|
|
The device has indicated that cleaning is required before further operations are attempted.
|
|
|
The device has indicated that its door is open.
|
|
|
The device is not connected.
|
|
|
Element not found.
|
|
|
There was no match for the specified key in the index.
|
|
|
The property set specified does not exist on the object.
|
|
|
The point passed to GetMouseMovePoints is not in the buffer.
|
|
|
The tracking (workstation) service is not running.
|
|
|
The Volume ID could not be found.
|
|
|
Unable to remove the file to be replaced.
|
|
|
Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name.
|
|
|
Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name.
|
|
|
The volume change journal is being deleted.
|
|
|
The volume change journal is not active.
|
|
|
A file was found, but it may not be the correct file.
|
|
|
The journal entry has been deleted from the journal.
|
|
|
The specified device name is invalid.
|
|
|
The device is not currently connected but it is a remembered connection.
|
|
|
The local device name has a remembered connection to another network resource.
|
|
|
The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.
|
|
|
The specified network provider name is invalid.
|
|
|
Unable to open the network connection profile.
|
|
|
The network connection profile is corrupted.
|
|
|
Cannot enumerate a noncontainer.
|
|
|
An extended error has occurred.
|
|
|
The format of the specified group name is invalid.
|
|
|
The format of the specified computer name is invalid.
|
|
|
The format of the specified event name is invalid.
|
|
|
The format of the specified domain name is invalid.
|
|
|
The format of the specified service name is invalid.
|
|
|
The format of the specified network name is invalid.
|
|
|
The format of the specified share name is invalid.
|
|
|
The format of the specified password is invalid.
|
|
|
The format of the specified message name is invalid.
|
|
|
The format of the specified message destination is invalid.
|
|
|
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
|
|
|
An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.
|
|
|
The workgroup or domain name is already in use by another computer on the network.
|
|
|
The network is not present or not started.
|
|
|
The operation was canceled by the user.
|
|
|
The requested operation cannot be performed on a file with a user-mapped section open.
|
|
|
The remote computer refused the network connection.
|
|
|
The network connection was gracefully closed.
|
|
|
The network transport endpoint already has an address associated with it.
|
|
|
An address has not yet been associated with the network endpoint.
|
|
|
An operation was attempted on a nonexistent network connection.
|
|
|
An invalid operation was attempted on an active network connection.
|
|
|
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
|
|
|
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
|
|
|
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
|
|
|
No service is operating at the destination network endpoint on the remote system.
|
|
|
The request was aborted.
|
|
|
The network connection was aborted by the local system.
|
|
|
The operation could not be completed. A retry should be performed.
|
|
|
A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached.
|
|
|
Attempting to log in during an unauthorized time of day for this account.
|
|
|
The account is not authorized to log in from this station.
|
|
|
The network address could not be used for the operation requested.
|
|
|
The service is already registered.
|
|
|
The specified service does not exist.
|
|
|
The operation being requested was not performed because the user has not been authenticated.
|
|
|
The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist.
|
|
|
Continue with work in progress.
|
|
|
An attempt was made to perform an initialization operation when initialization has already been completed.
|
|
|
No more local devices.
|
|
|
The specified site does not exist.
|
|
|
A domain controller with the specified name already exists.
|
|
|
This operation is supported only when you are connected to the server.
|
|
|
The group policy framework should call the extension even if there are no changes.
|
|
|
The specified user does not have a valid profile.
|
|
|
This operation is not supported on a computer running Windows Server 2003 for Small Business Server
|
|
|
The server machine is shutting down.
|
|
|
The remote system is not available. For information about network troubleshooting, see Windows Help.
|
|
|
The security identifier provided is not from an account domain.
|
|
|
The security identifier provided does not have a domain component.
|
|
|
AppHelp dialog canceled thus preventing the application from starting.
|
|
|
This program is blocked by group policy. For more information, contact your system administrator.
|
|
|
A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific.
|
|
|
The share is currently offline or does not exist.
|
|
|
The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log.
|
|
|
The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem.
|
|
|
The system cannot contact a domain controller to service the authentication request. Please try again later.
|
|
|
The smartcard certificate used for authentication has been revoked.
Please contact your system administrator. There may be additional information in the
event log.
|
|
|
An untrusted certificate authority was detected While processing the
smartcard certificate used for authentication. Please contact your system
administrator.
|
|
|
The revocation status of the smartcard certificate used for
authentication could not be determined. Please contact your system administrator.
|
|
|
The smartcard certificate used for authentication was not trusted. Please
contact your system administrator.
|
|
|
The smartcard certificate used for authentication has expired. Please
contact your system administrator.
|
|
|
The machine is locked and cannot be shut down without the force option.
|
|
|
An application-defined callback gave invalid data when called.
|
|
|
The group policy framework should call the extension in the synchronous foreground policy refresh.
|
|
|
This driver has been blocked from loading
|
|
|
A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image.
|
|
|
Not all privileges or groups referenced are assigned to the caller.
|
|
|
Some mapping between account names and security IDs was not done.
|
|
|
No system quota limits are specifically set for this account.
|
|
|
No encryption key is available. A well-known encryption key was returned.
|
|
|
The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.
|
|
|
The revision level is unknown.
|
|
|
Indicates two revision levels are incompatible.
|
|
|
This security ID may not be assigned as the owner of this object.
|
|
|
This security ID may not be assigned as the primary group of an object.
|
|
|
An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
|
|
|
The group may not be disabled.
|
|
|
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.
|
|
|
A specified logon session does not exist. It may already have been terminated.
|
|
|
A specified privilege does not exist.
|
|
|
A required privilege is not held by the client.
|
|
|
The name provided is not a properly formed account name.
|
|
|
The specified account already exists.
|
|
|
The specified account does not exist.
|
|
|
The specified group already exists.
|
|
|
The specified group does not exist.
|
|
|
Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member.
|
|
|
The specified user account is not a member of the specified group account.
|
|
|
This operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon.
|
|
|
Unable to update the password. The value provided as the current password is incorrect.
|
|
|
Unable to update the password. The value provided for the new password contains values that are not allowed in passwords.
|
|
|
Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain.
|
|
|
The user name or password is incorrect.
|
|
|
Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.
|
|
|
Your account has time restrictions that keep you from signing in right now.
|
|
|
This user isn't allowed to sign in to this computer.
|
|
|
The password for this account has expired.
|
|
|
This user can't sign in because this account is currently disabled.
|
|
|
No mapping between account names and security IDs was done.
|
|
|
Too many local user identifiers (LUIDs) were requested at one time.
|
|
|
No more local user identifiers (LUIDs) are available.
|
|
|
The subauthority part of a security ID is invalid for this particular use.
|
|
|
The access control list (ACL) structure is invalid.
|
|
|
The security ID structure is invalid.
|
|
|
The security descriptor structure is invalid.
|
|
|
The inherited access control list (ACL) or access control entry (ACE) could not be built.
|
|
|
The server is currently disabled.
|
|
|
The server is currently enabled.
|
|
|
The value provided was an invalid value for an identifier authority.
|
|
|
No more memory is available for security information updates.
|
|
|
The specified attributes are invalid, or incompatible with the attributes for the group as a whole.
|
|
|
Either a required impersonation level was not provided, or the provided impersonation level is invalid.
|
|
|
Cannot open an anonymous level security token.
|
|
|
The validation information class requested was invalid.
|
|
|
The type of the token is inappropriate for its attempted use.
|
|
|
Unable to perform a security operation on an object that has no associated security.
|
|
|
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.
|
|
|
The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.
|
|
|
The domain was in the wrong state to perform the security operation.
|
|
|
This operation is only allowed for the Primary Domain Controller of the domain.
|
|
|
The specified domain either does not exist or could not be contacted.
|
|
|
The specified domain already exists.
|
|
|
An attempt was made to exceed the limit on the number of domains per server.
|
|
|
Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.
|
|
|
An internal error occurred.
|
|
|
Generic access types were contained in an access mask which should already be mapped to nongeneric types.
|
|
|
A security descriptor is not in the right format (absolute or self-relative).
|
|
|
The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process.
|
|
|
Cannot start a new logon session with an ID that is already in use.
|
|
|
A specified authentication package is unknown.
|
|
|
The logon session is not in a state that is consistent with the requested operation.
|
|
|
The logon session ID is already in use.
|
|
|
A logon request contained an invalid logon type value.
|
|
|
Unable to impersonate using a named pipe until data has been read from that pipe.
|
|
|
The transaction state of a registry subtree is incompatible with the requested operation.
|
|
|
An internal security database corruption has been encountered.
|
|
|
Cannot perform this operation on built-in accounts.
|
|
|
Cannot perform this operation on this built-in special group.
|
|
|
Cannot perform this operation on this built-in special user.
|
|
|
The user cannot be removed from a group because the group is currently the user's primary group.
|
|
|
The token is already in use as a primary token.
|
|
|
The specified local group does not exist.
|
|
|
The specified account name is not a member of the group.
|
|
|
The specified account name is already a member of the group.
|
|
|
The specified local group already exists.
|
|
|
Logon failure: the user has not been granted the requested logon type at this computer.
|
|
|
The maximum number of secrets that may be stored in a single system has been exceeded.
|
|
|
The length of a secret exceeds the maximum length allowed.
|
|
|
The local security authority database contains an internal inconsistency.
|
|
|
During a logon attempt, the user's security context accumulated too many security IDs.
|
|
|
Logon failure: the user has not been granted the requested logon type at this computer.
|
|
|
A cross-encrypted password is necessary to change a user password.
|
|
|
A member could not be added to or removed from the local group because the member does not exist.
|
|
|
A new member could not be added to a local group because the member has the wrong account type.
|
|
|
Too many security IDs have been specified.
|
|
|
A cross-encrypted password is necessary to change this user password.
|
|
|
Indicates an ACL contains no inheritable components.
|
|
|
The file or directory is corrupted and unreadable.
|
|
|
The disk structure is corrupted and unreadable.
|
|
|
There is no user session key for the specified logon session.
|
|
|
The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.
|
|
|
The target account name is incorrect.
|
|
|
Mutual Authentication failed. The server's password is out of date at the domain controller.
|
|
|
There is a time and/or date difference between the client and server.
|
|
|
This operation cannot be performed on the current domain.
|
|
|
Invalid window handle.
|
|
|
Invalid menu handle.
|
|
|
Invalid cursor handle.
|
|
|
Invalid accelerator table handle.
|
|
|
Invalid hook handle.
|
|
|
Invalid handle to a multiple-window position structure.
|
|
|
Cannot create a top-level child window.
|
|
|
Cannot find window class.
|
|
|
Invalid window; it belongs to other thread.
|
|
|
Hot key is already registered.
|
|
|
Class already exists.
|
|
|
Class does not exist.
|
|
|
Class still has open windows.
|
|
|
Invalid index.
|
|
|
Invalid icon handle.
|
|
|
Using private DIALOG window words.
|
|
|
The list box identifier was not found.
|
|
|
No wildcards were found.
|
|
|
Thread does not have a clipboard open.
|
|
|
Hot key is not registered.
|
|
|
The window is not a valid dialog window.
|
|
|
Control ID not found.
|
|
|
Invalid message for a combo box because it does not have an edit control.
|
|
|
The window is not a combo box.
|
|
|
Height must be less than 256.
|
|
|
Invalid device context (DC) handle.
|
|
|
Invalid hook procedure type.
|
|
|
Invalid hook procedure.
|
|
|
Cannot set nonlocal hook without a module handle.
|
|
|
This hook procedure can only be set globally.
|
|
|
The journal hook procedure is already installed.
|
|
|
The hook procedure is not installed.
|
|
|
Invalid message for single-selection list box.
|
|
|
LB_SETCOUNT sent to non-lazy list box.
|
|
|
This list box does not support tab stops.
|
|
|
Cannot destroy object created by another thread.
|
|
|
Child windows cannot have menus.
|
|
|
The window does not have a system menu.
|
|
|
Invalid message box style.
|
|
|
Invalid system-wide (SPI_*) parameter.
|
|
|
Screen already locked.
|
|
|
All handles to windows in a multiple-window position structure must have the same parent.
|
|
|
The window is not a child window.
|
|
|
Invalid GW_* command.
|
|
|
Invalid thread identifier.
|
|
|
Cannot process a message from a window that is not a multiple document interface (MDI) window.
|
|
|
Popup menu already active.
|
|
|
The window does not have scroll bars.
|
|
|
Scroll bar range cannot be greater than MAXLONG.
|
|
|
Cannot show or remove the window in the way specified.
|
|
|
Insufficient system resources exist to complete the requested service.
|
|
|
Insufficient system resources exist to complete the requested service.
|
|
|
Insufficient system resources exist to complete the requested service.
|
|
|
Insufficient quota to complete the requested service.
|
|
|
Insufficient quota to complete the requested service.
|
|
|
The paging file is too small for this operation to complete.
|
|
|
A menu item was not found.
|
|
|
Invalid keyboard layout handle.
|
|
|
Hook type not allowed.
|
|
|
This operation requires an interactive window station.
|
|
|
This operation returned because the timeout period expired.
|
|
|
Invalid monitor handle.
|
|
|
The event log file is corrupted.
|
|
|
No event log file could be opened, so the event logging service did not start.
|
|
|
The event log file is full.
|
|
|
The event log file has changed between read operations.
|
|
|
The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
|
|
|
User cancelled installation.
|
|
|
Fatal error during installation.
|
|
|
Installation suspended, incomplete.
|
|
|
This action is only valid for products that are currently installed.
|
|
|
Feature ID not registered.
|
|
|
Component ID not registered.
|
|
|
Unknown property.
|
|
|
Handle is in an invalid state.
|
|
|
The configuration data for this product is corrupt. Contact your support personnel.
|
|
|
Component qualifier not present.
|
|
|
The installation source for this product is not available. Verify that the source exists and that you can access it.
|
|
|
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
|
|
|
Product is uninstalled.
|
|
|
SQL query syntax invalid or unsupported.
|
|
|
Record field does not exist.
|
|
|
The device has been removed.
|
|
|
Another installation is already in progress. Complete that installation before proceeding with this install.
|
|
|
This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.
|
|
|
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
|
|
|
There was an error starting the Windows Installer service user interface. Contact your support personnel.
|
|
|
Error opening installation log file. Verify that the specified log file location exists and that you can write to it.
|
|
|
The language of this installation package is not supported by your system.
|
|
|
Error applying transforms. Verify that the specified transform paths are valid.
|
|
|
This installation is forbidden by system policy. Contact your system administrator.
|
|
|
Function could not be executed.
|
|
|
Function failed during execution.
|
|
|
Invalid or unknown table specified.
|
|
|
Data supplied is of wrong type.
|
|
|
Data of this type is not supported.
|
|
|
The Windows Installer service failed to start. Contact your support personnel.
|
|
|
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder.
|
|
|
This installation package is not supported by this processor type. Contact your product vendor.
|
|
|
Component not used on this computer.
|
|
|
This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
|
|
|
This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package.
|
|
|
This update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
|
|
|
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
|
|
|
Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
|
|
|
Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator.
|
|
|
The requested operation completed successfully. The system will be restarted so the changes can take effect.
|
|
|
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
|
|
|
The update package is not permitted by software restriction policy.
|
|
|
One or more customizations are not permitted by software restriction policy.
|
|
|
The string binding is invalid.
|
|
|
The binding handle is not the correct type.
|
|
|
The binding handle is invalid.
|
|
|
The RPC protocol sequence is not supported.
|
|
|
The RPC protocol sequence is invalid.
|
|
|
The string universal unique identifier (UUID) is invalid.
|
|
|
The endpoint format is invalid.
|
|
|
The network address is invalid.
|
|
|
No endpoint was found.
|
|
|
The timeout value is invalid.
|
|
|
The object universal unique identifier (UUID) was not found.
|
|
|
The object universal unique identifier (UUID) has already been registered.
|
|
|
The type universal unique identifier (UUID) has already been registered.
|
|
|
The RPC server is already listening.
|
|
|
No protocol sequences have been registered.
|
|
|
The RPC server is not listening.
|
|
|
The manager type is unknown.
|
|
|
The interface is unknown.
|
|
|
There are no bindings.
|
|
|
There are no protocol sequences.
|
|
|
The endpoint cannot be created.
|
|
|
Not enough resources are available to complete this operation.
|
|
|
The RPC server is unavailable.
|
|
|
The RPC server is too busy to complete this operation.
|
|
|
The network options are invalid.
|
|
|
There are no remote procedure calls active on this thread.
|
|
|
The remote procedure call failed.
|
|
|
The remote procedure call failed and did not execute.
|
|
|
A remote procedure call (RPC) protocol error occurred.
|
|
|
The transfer syntax is not supported by the RPC server.
|
|
|
The universal unique identifier (UUID) type is not supported.
|
|
|
The tag is invalid.
|
|
|
The array bounds are invalid.
|
|
|
The binding does not contain an entry name.
|
|
|
The name syntax is invalid.
|
|
|
The name syntax is not supported.
|
|
|
No network address is available to use to construct a universal unique identifier (UUID).
|
|
|
The endpoint is a duplicate.
|
|
|
The authentication type is unknown.
|
|
|
The maximum number of calls is too small.
|
|
|
The string is too long.
|
|
|
The RPC protocol sequence was not found.
|
|
|
The procedure number is out of range.
|
|
|
The binding does not contain any authentication information.
|
|
|
The authentication service is unknown.
|
|
|
The authentication level is unknown.
|
|
|
The security context is invalid.
|
|
|
The authorization service is unknown.
|
|
|
The entry is invalid.
|
|
|
The server endpoint cannot perform the operation.
|
|
|
There are no more endpoints available from the endpoint mapper.
|
|
|
No interfaces have been exported.
|
|
|
The entry name is incomplete.
|
|
|
The version option is invalid.
|
|
|
There are no more members.
|
|
|
There is nothing to unexport.
|
|
|
The interface was not found.
|
|
|
The entry already exists.
|
|
|
The entry is not found.
|
|
|
The name service is unavailable.
|
|
|
The network address family is invalid.
|
|
|
The requested operation is not supported.
|
|
|
No security context is available to allow impersonation.
|
|
|
An internal error occurred in a remote procedure call (RPC).
|
|
|
The RPC server attempted an integer division by zero.
|
|
|
An addressing error occurred in the RPC server.
|
|
|
A floating-point operation at the RPC server caused a division by zero.
|
|
|
A floating-point underflow occurred at the RPC server.
|
|
|
A floating-point overflow occurred at the RPC server.
|
|
|
The list of RPC servers available for the binding of auto handles has been exhausted.
|
|
|
Unable to open the character translation table file.
|
|
|
The file containing the character translation table has fewer than 512 bytes.
|
|
|
A null context handle was passed from the client to the host during a remote procedure call.
|
|
|
The context handle changed during a remote procedure call.
|
|
|
The binding handles passed to a remote procedure call do not match.
|
|
|
The stub is unable to get the remote procedure call handle.
|
|
|
A null reference pointer was passed to the stub.
|
|
|
The enumeration value is out of range.
|
|
|
The byte count is too small.
|
|
|
The stub received bad data.
|
|
|
The supplied user buffer is not valid for the requested operation.
|
|
|
The disk media is not recognized. It may not be formatted.
|
|
|
The workstation does not have a trust secret.
|
|
|
The security database on the server does not have a computer account for this workstation trust relationship.
|
|
|
The trust relationship between the primary domain and the trusted domain failed.
|
|
|
The trust relationship between this workstation and the primary domain failed.
|
|
|
The network logon failed.
|
|
|
A remote procedure call is already in progress for this thread.
|
|
|
An attempt was made to logon, but the network logon service was not started.
|
|
|
The user's account has expired.
|
|
|
The redirector is in use and cannot be unloaded.
|
|
|
The specified printer driver is already installed.
|
|
|
The specified port is unknown.
|
|
|
The printer driver is unknown.
|
|
|
The print processor is unknown.
|
|
|
The specified separator file is invalid.
|
|
|
The specified priority is invalid.
|
|
|
The printer name is invalid.
|
|
|
The printer already exists.
|
|
|
The printer command is invalid.
|
|
|
The specified datatype is invalid.
|
|
|
The environment specified is invalid.
|
|
|
There are no more bindings.
|
|
|
The account used is an interdomain trust account. Use your global user account or local user account to access this server.
|
|
|
The account used is a computer account. Use your global user account or local user account to access this server.
|
|
|
The account used is a server trust account. Use your global user account or local user account to access this server.
|
|
|
The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.
|
|
|
The server is in use and cannot be unloaded.
|
|
|
The specified image file did not contain a resource section.
|
|
|
The specified resource type cannot be found in the image file.
|
|
|
The specified resource name cannot be found in the image file.
|
|
|
The specified resource language ID cannot be found in the image file.
|
|
|
Not enough quota is available to process this command.
|
|
|
No interfaces have been registered.
|
|
|
The remote procedure call was cancelled.
|
|
|
The binding handle does not contain all required information.
|
|
|
A communications failure occurred during a remote procedure call.
|
|
|
The requested authentication level is not supported.
|
|
|
No principal name registered.
|
|
|
The error specified is not a valid Windows RPC error code.
|
|
|
A UUID that is valid only on this computer has been allocated.
|
|
|
A security package specific error occurred.
|
|
|
Thread is not canceled.
|
|
|
Invalid operation on the encoding/decoding handle.
|
|
|
Incompatible version of the serializing package.
|
|
|
Incompatible version of the RPC stub.
|
|
|
The RPC pipe object is invalid or corrupted.
|
|
|
An invalid operation was attempted on an RPC pipe object.
|
|
|
Unsupported RPC pipe version.
|
|
|
The group member was not found.
|
|
|
The endpoint mapper database entry could not be created.
|
|
|
The object universal unique identifier (UUID) is the nil UUID.
|
|
|
The specified time is invalid.
|
|
|
The specified form name is invalid.
|
|
|
The specified form size is invalid.
|
|
|
The specified printer handle is already being waited on
|
|
|
The specified printer has been deleted.
|
|
|
The state of the printer is invalid.
|
|
|
The user's password must be changed before signing in.
|
|
|
Could not find the domain controller for this domain.
|
|
|
The referenced account is currently locked out and may not be logged on to.
|
|
|
The object exporter specified was not found.
|
|
|
The object specified was not found.
|
|
|
The object resolver set specified was not found.
|
|
|
Some data remains to be sent in the request buffer.
|
|
|
Invalid asynchronous remote procedure call handle.
|
|
|
Invalid asynchronous RPC call handle for this operation.
|
|
|
The RPC pipe object has already been closed.
|
|
|
The RPC call completed before all pipes were processed.
|
|
|
No more data is available from the RPC pipe.
|
|
|
No site name is available for this machine.
|
|
|
The file cannot be accessed by the system.
|
|
|
The name of the file cannot be resolved by the system.
|
|
|
The entry is not of the expected type.
|
|
|
Not all object UUIDs could be exported to the specified entry.
|
|
|
Interface could not be exported to the specified entry.
|
|
|
The specified profile entry could not be added.
|
|
|
The specified profile element could not be added.
|
|
|
The specified profile element could not be removed.
|
|
|
The group element could not be added.
|
|
|
The group element could not be removed.
|
|
|
The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers.
|
|
|
The context has expired and can no longer be used.
|
|
|
The pixel format is invalid.
|
|
|
The specified driver is invalid.
|
|
|
The window style or class attribute is invalid for this operation.
|
|
|
The requested metafile operation is not supported.
|
|
|
The requested transformation operation is not supported.
|
|
|
The requested clipping operation is not supported.
|
|
|
The specified color management module is invalid.
|
|
|
The specified color profile is invalid.
|
|
|
The specified tag was not found.
|
|
|
A required tag is not present.
|
|
|
The specified tag is already present.
|
|
|
The specified color profile is not associated with the specified device.
|
|
|
The specified color profile was not found.
|
|
|
The specified color space is invalid.
|
|
|
Image Color Management is not enabled.
|
|
|
There was an error while deleting the color transform.
|
|
|
The specified color transform is invalid.
|
|
|
The specified transform does not match the bitmap's color space.
|
|
|
The specified named color index is not present in the profile.
|
|
|
The workstation driver is not installed.
|
|
|
The server could not be located.
|
|
|
An internal error occurred. The network cannot access a shared memory segment.
|
|
|
A network resource shortage occurred .
|
|
|
This operation is not supported on workstations.
|
|
|
The device is not connected.
|
|
|
The Server service is not started.
|
|
|
The queue is empty.
|
|
|
The device or directory does not exist.
|
|
|
The operation is invalid on a redirected resource.
|
|
|
The name has already been shared.
|
|
|
The server is currently out of the requested resource.
|
|
|
Requested addition of items exceeds the maximum allowed.
|
|
|
The Peer service supports only two simultaneous users.
|
|
|
The API return buffer is too small.
|
|
|
A remote API error occurred.
|
|
|
An error occurred when opening or reading the configuration file.
|
|
|
A general network error occurred.
|
|
|
The Workstation service is in an inconsistent state. Restart the computer before restarting the Workstation service.
|
|
|
The Workstation service has not been started.
|
|
|
The requested information is not available.
|
|
|
An internal Windows error occurred.
|
|
|
The server is not configured for transactions.
|
|
|
The requested API is not supported on the remote server.
|
|
|
The event name is invalid.
|
|
|
The computer name already exists on the network. Change it and restart the computer.
|
|
|
The specified component could not be found in the configuration information.
|
|
|
The specified parameter could not be found in the configuration information.
|
|
|
A line in the configuration file is too long.
|
|
|
The printer does not exist.
|
|
|
The print job does not exist.
|
|
|
The printer destination cannot be found.
|
|
|
The printer destination already exists.
|
|
|
The printer queue already exists.
|
|
|
No more printers can be added.
|
|
|
No more print jobs can be added.
|
|
|
No more printer destinations can be added.
|
|
|
This printer destination is idle and cannot accept control operations.
|
|
|
This printer destination request contains an invalid control function.
|
|
|
The print processor is not responding.
|
|
|
The spooler is not running.
|
|
|
This operation cannot be performed on the print destination in its current state.
|
|
|
This operation cannot be performed on the printer queue in its current state.
|
|
|
This operation cannot be performed on the print job in its current state.
|
|
|
A spooler memory allocation failure occurred.
|
|
|
The device driver does not exist.
|
|
|
The data type is not supported by the print processor.
|
|
|
The print processor is not installed.
|
|
|
The service database is locked.
|
|
|
The service table is full.
|
|
|
The requested service has already been started.
|
|
|
The service does not respond to control actions.
|
|
|
The service has not been started.
|
|
|
The service name is invalid.
|
|
|
The service is not responding to the control function.
|
|
|
The service control is busy.
|
|
|
The configuration file contains an invalid service program name.
|
|
|
The service could not be controlled in its present state.
|
|
|
The service ended abnormally.
|
|
|
The requested pause, continue, or stop is not valid for this service.
|
|
|
The service control dispatcher could not find the service name in the dispatch table.
|
|
|
The service control dispatcher pipe read failed.
|
|
|
A thread for the new service could not be created.
|
|
|
This workstation is already logged on to the local-area network.
|
|
|
The workstation is not logged on to the local-area network.
|
|
|
The specified username is invalid.
|
|
|
The password parameter is invalid.
|
|
|
The logon processor did not add the message alias.
|
|
|
The logon processor did not add the message alias.
|
|
|
The logoff processor did not delete the message alias.
|
|
|
The logoff processor did not delete the message alias.
|
|
|
Network logons are paused.
|
|
|
A centralized logon-server conflict occurred.
|
|
|
The server is configured without a valid user path.
|
|
|
An error occurred while loading or running the logon script.
|
|
|
The logon server was not specified. Your computer will be logged on as STANDALONE.
|
|
|
The logon server could not be found.
|
|
|
There is already a logon domain for this computer.
|
|
|
The logon server could not validate the logon.
|
|
|
The security database could not be found.
|
|
|
The group name could not be found.
|
|
|
The user name could not be found.
|
|
|
The resource name could not be found.
|
|
|
The group already exists.
|
|
|
The account already exists.
|
|
|
The resource permission list already exists.
|
|
|
This operation is only allowed on the primary domain controller of the domain.
|
|
|
The security database has not been started.
|
|
|
There are too many names in the user accounts database.
|
|
|
A disk I/O failure occurred.
|
|
|
The limit of 64 entries per resource was exceeded.
|
|
|
Deleting a user with a session is not allowed.
|
|
|
The parent directory could not be located.
|
|
|
Unable to add to the security database session cache segment.
|
|
|
This operation is not allowed on this special group.
|
|
|
This user is not cached in user accounts database session cache.
|
|
|
The user already belongs to this group.
|
|
|
The user does not belong to this group.
|
|
|
This user account is undefined.
|
|
|
This user account has expired.
|
|
|
The user is not allowed to log on from this workstation.
|
|
|
The user is not allowed to log on at this time.
|
|
|
The password of this user has expired.
|
|
|
The password of this user cannot change.
|
|
|
This password cannot be used now.
|
|
|
The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.
|
|
|
The password of this user is too recent to change.
|
|
|
The security database is corrupted.
|
|
|
No updates are necessary to this replicant network/local security database.
|
|
|
This replicant database is outdated; synchronization is required.
|
|
|
This network connection does not exist.
|
|
|
This asg_type is invalid.
|
|
|
This device is currently being shared.
|
|
|
The computer name could not be added as a message alias. The name may already exist on the network.
|
|
|
The Messenger service is already started.
|
|
|
The Messenger service failed to start.
|
|
|
The message alias could not be found on the network.
|
|
|
This message alias has already been forwarded.
|
|
|
This message alias has been added but is still forwarded.
|
|
|
This message alias already exists locally.
|
|
|
The maximum number of added message aliases has been exceeded.
|
|
|
The computer name could not be deleted.
|
|
|
Messages cannot be forwarded back to the same workstation.
|
|
|
An error occurred in the domain message processor.
|
|
|
The message was sent, but the recipient has paused the Messenger service.
|
|
|
The message was sent but not received.
|
|
|
The message alias is currently in use. Try again later.
|
|
|
The Messenger service has not been started.
|
|
|
The name is not on the local computer.
|
|
|
The forwarded message alias could not be found on the network.
|
|
|
The message alias table on the remote station is full.
|
|
|
Messages for this alias are not currently being forwarded.
|
|
|
The broadcast message was truncated.
|
|
|
This is an invalid device name.
|
|
|
A write fault occurred.
|
|
|
A duplicate message alias exists on the network.
|
|
|
This message alias will be deleted later.
|
|
|
The message alias was not successfully deleted from all networks.
|
|
|
This operation is not supported on computers with multiple networks.
|
|
|
This shared resource does not exist.
|
|
|
This device is not shared.
|
|
|
A session does not exist with that computer name.
|
|
|
There is not an open file with that identification number.
|
|
|
A failure occurred when executing a remote administration command.
|
|
|
A failure occurred when opening a remote temporary file.
|
|
|
The data returned from a remote administration command has been truncated to 64K.
|
|
|
This device cannot be shared as both a spooled and a non-spooled resource.
|
|
|
The information in the list of servers may be incorrect.
|
|
|
The computer is not active in this domain.
|
|
|
The share must be removed from the Distributed File System before it can be deleted.
|
|
|
The operation is invalid for this device.
|
|
|
This device cannot be shared.
|
|
|
This device was not open.
|
|
|
This device name list is invalid.
|
|
|
The queue priority is invalid.
|
|
|
There are no shared communication devices.
|
|
|
The queue you specified does not exist.
|
|
|
This list of devices is invalid.
|
|
|
The requested device is invalid.
|
|
|
This device is already in use by the spooler.
|
|
|
This device is already in use as a communication device.
|
|
|
This computer name is invalid.
|
|
|
The string and prefix specified are too long.
|
|
|
This path component is invalid.
|
|
|
Could not determine the type of input.
|
|
|
The buffer for types is not big enough.
|
|
|
Profile files cannot exceed 64K.
|
|
|
The start offset is out of range.
|
|
|
The system cannot delete current connections to network resources.
|
|
|
The system was unable to parse the command line in this file.
|
|
|
An error occurred while loading the profile file.
|
|
|
Errors occurred while saving the profile file. The profile was partially saved.
|
|
|
Log file *** is full.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The log file is too large.
ACTION
Clear the log file or increase the MAXERRORLOG entry in the computer's configuration file. If you need assistance, contact your network administrator.
|
|
|
This log file has changed between reads.
|
|
|
Log file *** is corrupt.
NET2379
|
|
|
The source path cannot be a directory.
|
|
|
The source path is illegal.
|
|
|
The destination path is illegal.
|
|
|
The source and destination paths are on different servers.
|
|
|
The Run server you requested is paused.
|
|
|
An error occurred when communicating with a Run server.
|
|
|
An error occurred when starting a background process.
|
|
|
The shared resource you are connected to could not be found.
|
|
|
The LAN adapter number is invalid.
|
|
|
This network connection has files open or requests pending.
|
|
|
Active connections still exist.
|
|
|
This share name or password is invalid.
|
|
|
The device is in use by an active process and cannot be disconnected.
|
|
|
The drive letter is in use locally.
|
|
|
The specified client is already registered for the specified event.
|
|
|
The alert table is full.
|
|
|
An invalid or nonexistent alert name was raised.
|
|
|
The alert recipient is invalid.
|
|
|
A user's session with this server has been deleted because the user's logon hours are no longer valid.
|
|
|
The log file does not contain the requested record number.
|
|
|
The user accounts database is not configured correctly.
|
|
|
This operation is not permitted when the Netlogon service is running.
|
|
|
This operation is not allowed on the last administrative account.
|
|
|
Could not find domain controller for this domain.
|
|
|
Could not set logon information for this user.
|
|
|
The Netlogon service has not been started.
|
|
|
Unable to add to the user accounts database.
|
|
|
This server's clock is not synchronized with the primary domain controller's clock.
|
|
|
A password mismatch has been detected.
|
|
|
The server identification does not specify a valid server.
|
|
|
The session identification does not specify a valid session.
|
|
|
The connection identification does not specify a valid connection.
|
|
|
There is no space for another entry in the table of available servers.
|
|
|
The server has reached the maximum number of sessions it supports.
|
|
|
The server has reached the maximum number of connections it supports.
|
|
|
The server cannot open more files because it has reached its maximum number.
|
|
|
There are no alternate servers registered on this server.
|
|
|
Try down-level (remote admin protocol) version of API instead.
|
|
|
The UPS driver could not be accessed by the UPS service.
|
|
|
The UPS service is not configured correctly.
|
|
|
The UPS service could not access the specified Comm Port.
|
|
|
The UPS indicated a line fail or low battery situation. Service not started.
|
|
|
The UPS service failed to perform a system shut down.
|
|
|
The program below returned an MS-DOS error code:
|
|
|
The program below needs more memory:
|
|
|
The program below called an unsupported MS-DOS function:
|
|
|
The workstation failed to boot.
|
|
|
The file below is corrupt.
|
|
|
No loader is specified in the boot-block definition file.
|
|
|
NetBIOS returned an error: The NCB and SMB are dumped above.
|
|
|
A disk I/O error occurred.
|
|
|
Image parameter substitution failed.
|
|
|
Too many image parameters cross disk sector boundaries.
|
|
|
The image was not generated from an MS-DOS diskette formatted with /S.
|
|
|
Remote boot will be restarted later.
|
|
|
The call to the Remoteboot server failed.
|
|
|
Cannot connect to the Remoteboot server.
|
|
|
Cannot open image file on the Remoteboot server.
|
|
|
Connecting to the Remoteboot server...
|
|
|
Connecting to the Remoteboot server...
|
|
|
Remote boot service was stopped; check the error log for the cause of the problem.
|
|
|
Remote boot startup failed; check the error log for the cause of the problem.
|
|
|
A second connection to a Remoteboot resource is not allowed.
|
|
|
The browser service was configured with MaintainServerList=No.
|
|
|
Service failed to start since none of the network adapters started with this service.
|
|
|
Service failed to start due to bad startup information in the registry.
|
|
|
Service failed to start because its database is absent or corrupt.
|
|
|
Service failed to start because RPLFILES share is absent.
|
|
|
Service failed to start because RPLUSER group is absent.
|
|
|
Cannot enumerate service records.
|
|
|
Workstation record information has been corrupted.
|
|
|
Workstation record was not found.
|
|
|
Workstation name is in use by some other workstation.
|
|
|
Profile record information has been corrupted.
|
|
|
Profile record was not found.
|
|
|
Profile name is in use by some other profile.
|
|
|
There are workstations using this profile.
|
|
|
Configuration record information has been corrupted.
|
|
|
Configuration record was not found.
|
|
|
Adapter id record information has been corrupted.
|
|
|
An internal service error has occurred.
|
|
|
Vendor id record information has been corrupted.
|
|
|
Boot block record information has been corrupted.
|
|
|
The user account for this workstation record is missing.
|
|
|
The RPLUSER local group could not be found.
|
|
|
Boot block record was not found.
|
|
|
Chosen profile is incompatible with this workstation.
|
|
|
Chosen network adapter id is in use by some other workstation.
|
|
|
There are profiles using this configuration.
|
|
|
There are workstations, profiles or configurations using this boot block.
|
|
|
Service failed to backup Remoteboot database.
|
|
|
Adapter record was not found.
|
|
|
Vendor record was not found.
|
|
|
Vendor name is in use by some other vendor record.
|
|
|
(boot name, vendor id) is in use by some other boot block record.
|
|
|
Configuration name is in use by some other configuration.
|
|
|
The internal database maintained by the DFS service is corrupt
|
|
|
One of the records in the internal DFS database is corrupt
|
|
|
There is no DFS name whose entry path matches the input Entry Path
|
|
|
A root or link with the given name already exists
|
|
|
The server share specified is already shared in the DFS
|
|
|
The indicated server share does not support the indicated DFS namespace
|
|
|
The operation is not valid on this portion of the namespace
|
|
|
The operation is not valid on this portion of the namespace
|
|
|
The operation is ambiguous because the link has multiple servers
|
|
|
Unable to create a link
|
|
|
The server is not DFS Aware
|
|
|
The specified rename target path is invalid
|
|
|
The specified DFS link is offline
|
|
|
The specified server is not a server for this link
|
|
|
A cycle in the DFS name was detected
|
|
|
The operation is not supported on a server-based DFS
|
|
|
This link is already supported by the specified server-share
|
|
|
Can't remove the last server-share supporting this root or link
|
|
|
The operation is not supported for an Inter-DFS link
|
|
|
The internal state of the DFS Service has become inconsistent
|
|
|
The DFS Service has been installed on the specified server
|
|
|
The DFS data being reconciled is identical
|
|
|
The DFS root cannot be deleted - Uninstall DFS if required
|
|
|
A child or parent directory of the share is already in a DFS
|
|
|
DFS internal error
|
|
|
This machine is already joined to a domain.
|
|
|
This machine is not currently joined to a domain.
|
|
|
This machine is a domain controller and cannot be unjoined from a domain.
|
|
|
The destination domain controller does not support creating machine accounts in OUs.
|
|
|
The specified workgroup name is invalid.
|
|
|
The specified computer name is incompatible with the default language used on the domain controller.
|
|
|
The specified computer account could not be found. Contact an administrator to verify the account is in the domain. If the account has been deleted unjoin, reboot, and rejoin the domain.
|
|
|
This version of Windows cannot be joined to a domain.
|
|
|
This is the last error in NERR range.
|
|
|
The specified print monitor is unknown.
|
|
|
The specified printer driver is currently in use.
|
|
|
The spool file was not found.
|
|
|
A StartDocPrinter call was not issued.
|
|
|
An AddJob call was not issued.
|
|
|
The specified print processor has already been installed.
|
|
|
The specified print monitor has already been installed.
|
|
|
The specified print monitor does not have the required functions.
|
|
|
The specified print monitor is currently in use.
|
|
|
The requested operation is not allowed when there are jobs queued to the printer.
|
|
|
The requested operation is successful. Changes will not be effective until the system is rebooted.
|
|
|
The requested operation is successful. Changes will not be effective until the service is restarted.
|
|
|
No printers were found.
|
|
|
The printer driver is known to be unreliable.
|
|
|
The printer driver is known to harm the system.
|
|
|
The requested print job has failed to print. A print system update requires the job to be resubmitted.
|
|
|
The printer driver does not contain a valid manifest, or contains too many manifests.
|
|
|
The specified printer cannot be shared.
|
|
|
There is a problem with a configuration of user specified shut down command file. The UPS service started anyway.
|
|
|
A defective sector on drive *** has been replaced (hotfixed).
No data was lost. You should run CHKDSK soon to restore full
performance and replenish the volume's spare sector pool.
The hotfix occurred while processing a remote request.
|
|
|
A disk error occurred on the HPFS volume in drive ***.
The error occurred while processing a remote request.
|
|
|
The user accounts database (NET.ACC) is corrupted. The local security
system is replacing the corrupted NET.ACC with the backup
made on *** at ***.
Any updates made to the database after this time are lost.
|
|
|
The user accounts database (NET.ACC) is missing. The local
security system is restoring the backup database
made on *** at ***.
Any updates made to the database after this time are lost.
|
|
|
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.
|
|
|
The server cannot export directory ***, to client ***.
It is exported from another server.
|
|
|
The replication server could not update directory *** from the source
on *** due to error ***.
|
|
|
Master *** did not send an update notice for directory *** at the expected
time.
|
|
|
User *** has exceeded account limitation *** on server ***.
|
|
|
The primary domain controller for domain *** failed.
|
|
|
Failed to authenticate with ***, a Windows NT or Windows 2000 Domain Controller for
domain ***.
|
|
|
The replicator attempted to log on at *** as *** and failed.
|
|
|
@I *LOGON HOURS
|
|
|
Replicator could not access ***
on *** due to system error ***.
|
|
|
Replicator limit for files in a directory has been exceeded.
|
|
|
Replicator limit for tree depth has been exceeded.
|
|
|
The replicator cannot update directory ***. It has tree integrity
and is the current directory for some process.
|
|
|
Network error *** occurred.
|
|
|
System error *** occurred.
|
|
|
Cannot log on. User is currently logged on and argument TRYUSER is set to NO.
|
|
|
IMPORT path *** cannot be found.
|
|
|
EXPORT path *** cannot be found.
|
|
|
Replicated data has changed in directory ***.
|
|
|
The operation was paused.
|
|
|
The Registry or the information you just typed includes an illegal
value for "***".
EXPLANATION
You specified invalid values for one or more of the service's options.
ACTION
Retype the command with correct values, or change the values for the listed options in the configuration file.
|
|
|
The required parameter was not provided on the command line or in the configuration file.
|
|
|
LAN Manager does not recognize "***" as a valid option.
EXPLANATION
This message should occur only on a down level computer. Any action to correct the problem should be performed on that computer.
This option is not valid for this service.
ACTION
Check the spelling of this option. If you did not type it from the command line, check the configuration file.
|
|
|
A request for resource could not be satisfied.
|
|
|
A problem exists with the system configuration.
|
|
|
A system error has occurred.
|
|
|
An internal consistency error has occurred.
|
|
|
The configuration file or the command line has an ambiguous option.
|
|
|
The configuration file or the command line has a duplicate parameter.
|
|
|
The condition supplied for the app execution request was not satisfied, so the request was not performed.
|
|
|
The supplied handle has been invalidated and may not be used for the requested operation.
|
|
|
The supplied host generation has been invalidated and may not be used for the requested operation.
|
|
|
An attempt to register a process failed because the target host was not in a valid state to receive process registrations.
|
|
|
The host is not in a valid state to support the execution request.
|
|
|
memory
|
|
|
disk space
|
|
|
thread
|
|
|
process
|
|
|
Security Failure.
|
|
|
Bad or missing LAN Manager root directory.
|
|
|
The network software is not installed.
|
|
|
The server is not started.
|
|
|
The server cannot access the user accounts database (NET.ACC).
|
|
|
Incompatible files are installed in the LANMAN tree.
|
|
|
The LANMAN\LOGS directory is invalid.
|
|
|
The domain specified could not be used.
|
|
|
The computer name is being used as a message alias on another computer.
|
|
|
The announcement of the server name failed.
|
|
|
The user accounts database is not configured correctly.
|
|
|
The server is not running with user-level security.
|
|
|
The workstation is not configured properly.
|
|
|
View your error log for details.
|
|
|
Unable to write to this file.
|
|
|
ADDPAK file is corrupted. Delete LANMAN\NETPROG\ADDPAK.SER and reapply all ADDPAKs.
|
|
|
The LM386 server cannot be started because CACHE.EXE is not running.
|
|
|
There is no account for this computer in the security database.
|
|
|
This computer is not a member of the group SERVERS.
|
|
|
The group SERVERS is not present in the local security database.
|
|
|
This 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.
|
|
|
The primary Domain Controller for this domain could not be located.
|
|
|
This computer is configured to be the primary domain controller of its domain.
However, the computer *** is currently claiming to be the primary domain controller
of the domain.
|
|
|
The service failed to authenticate with the primary domain controller.
|
|
|
There is a problem with the security database creation date or serial number.
|
|
|
The operation failed because a network software error occurred.
|
|
|
The system ran out of a resource controlled by the *** option.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The system required more of a resource than was available.
ACTION
Change the value of the listed option in the configuration file to allow the system to access more of the resource.
|
|
|
The service failed to obtain a long-term lock on the segment for network control blocks (NCBs). The error code is the data.
|
|
|
The service failed to release the long-term lock on the segment for network control blocks (NCBs). The error code is the data.
|
|
|
There was an error stopping service ***.
The error code from NetServiceControl is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
A software error occurred.
ACTION
Contact technical support.
|
|
|
Initialization failed because of a system execution failure on
path ***. The system error code is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
A software error occurred.
ACTION
Contact technical support.
|
|
|
An unexpected network control block (NCB) was received. The NCB is the data.
|
|
|
The network is not started.
|
|
|
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
|
|
|
Unable to create or open system semaphore ***.
The error code is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
A software error occurred.
ACTION
Contact technical support.
|
|
|
Initialization failed because of an open/create error on the
file ***. The system error code is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
A software error occurred.
ACTION
Contact technical support.
|
|
|
An unexpected NetBIOS error occurred. The error code is the data.
|
|
|
An illegal server message block (SMB) was received. The SMB is the data.
|
|
|
Initialization failed because the requested service ***
could not be started.
EXPLANATION
A software error occurred.
ACTION
Contact technical support.
|
|
|
Some entries in the error log were lost because of a buffer overflow.
|
|
|
Initialization parameters controlling resource usage other than net buffers are sized so that too much memory is needed.
|
|
|
The server cannot increase the size of a memory segment.
|
|
|
Initialization failed because account file *** is either incorrect
or not present.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The user accounts database, NET.ACC, is missing, damaged, or in a format that is incompatible with this version of LAN Manager.
ACTION
Copy the backup file, NETACC.BKP, to NET.ACC. If NETACC.BKP does not exist, copy NET.ACC or NETACC.BKP from a backup floppy or from the LAN Manager distribution disks.
If you have upgraded your LAN Manager software, you may need
to convert the user accounts database to a new format. See the instructions that came with your upgrade.
|
|
|
Initialization failed because network *** was not started.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
All networks named in the SRVNETS entry of the server's configuration file must use the LAN Manager workstation software.
ACTION
Be sure that all networks named in the SRVNETS entry of the server's configuration file are also named in the WRKNETS entry of that file.
|
|
|
The server failed to start. Either all three chdev parameters must be zero or all three must be nonzero.
|
|
|
A remote API request was halted due to the following
invalid description string: ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The server received an invalid request to run a command. The request may have been damaged by the network.
ACTION
No action is needed.
If this error occurs frequently, contact technical support.
|
|
|
The network *** ran out of network control blocks (NCBs). You may need to increase NCBs
for this network. The following information includes the
number of NCBs submitted by the server when this error occurred:
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The server found a resource shortage in a network driver
when it tried to issue a network control block (NCB).
ACTION
Be sure that the NETn entries in the configuration file specify valid NetBIOS device drivers and that these device drivers are in the LANMAN\DRIVERS directory. Also be sure that the CONFIG.SYS file contains a DEVICE line specifying the absolute paths of the device drivers.
You may be able to increase the NCBs for the listed network by changing an option in the network's NETn entry in the configuration file. See the installation guide that came with your network adapter for information about those options.
If you need assistance, contact your network administrator.
|
|
|
The server cannot create the *** mailslot needed to send
the ReleaseMemory alert message. The error received is:
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The server cannot respond to a ReleaseMemory alert. Otherwise, the server is functioning normally.
ACTION
No action is needed.
|
|
|
The server failed to register for the ReleaseMemory alert,
with recipient ***. The error code from
NetAlertStart is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The server cannot respond to a ReleaseMemory alert. Otherwise, the server is functioning normally.
ACTION
No action is needed.
|
|
|
The server cannot update the AT schedule file. The file is corrupted.
|
|
|
The server encountered an error when calling NetIMakeLMFileName. The error code is the data.
|
|
|
Initialization failed because of a system execution failure on
path ***. There is not enough memory to start the process.
The system error code is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
There is not enough memory available to run the Server service.
ACTION
Stop other applications and services (except the Workstation service) that are running on the computer and try again. If the problem continues, you will have to add memory to the computer.
|
|
|
Longterm lock of the server buffers failed. Check swap disk's free space and restart the system to start the server.
|
|
|
The service has stopped due to repeated consecutive occurrences of a network control block (NCB) error. The last bad NCB follows in raw data.
|
|
|
The Message server has stopped due to a lock on the Message server shared data segment.
|
|
|
A file system error occurred while opening or writing to the
system message log file ***. Message logging has been
switched off due to the error. The error code is the data.
|
|
|
Unable to display message POPUP due to system VIO call error. The error code is the data.
|
|
|
An illegal server message block (SMB) was received. The SMB is the data.
|
|
|
The workstation information segment is bigger than 64K. The size follows, in DWORD format:
|
|
|
The workstation was unable to get the name-number of the computer.
|
|
|
The workstation could not initialize the Async NetBIOS Thread. The error code is the data.
|
|
|
The workstation could not open the initial shared segment. The error code is the data.
|
|
|
The workstation host table is full.
|
|
|
A bad mailslot server message block (SMB) was received. The SMB is the data.
|
|
|
The workstation encountered an error while trying to start the user accounts database. The error code is the data.
|
|
|
The workstation encountered an error while responding to an SSI revalidation request. The function code and the error codes are the data.
|
|
|
The Alerter service had a problem creating the list of
alert recipients. The error code is ***.
EXPLANATION
A software error occurred.
ACTION
Contact technical support.
|
|
|
There was an error expanding *** as a group name. Try
splitting the group into two or more smaller groups.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
An error occurred when LAN Manager tried to identify the members of the specified group. The group is probably too large.
ACTION
Split the group into two or more smaller groups.
|
|
|
There was an error sending *** the alert message -
(
*** )
The error code is ***.
EXPLANATION
An error occurred when an alert message was sent. The user name designated to receive the alert may no longer exist.
ACTION
Use Server Manager to repair the error.
|
|
|
There was an error in creating or reading the alerter mailslot.
The error code is ***.
EXPLANATION
A software error occurred.
ACTION
Verify that the Alerter service has been started. If the service has already been started, contact technical support.
|
|
|
The server could not read the AT schedule file.
|
|
|
The server found an invalid AT schedule record.
|
|
|
The server could not find an AT schedule file so it created one.
|
|
|
The server could not access the *** network with NetBiosOpen.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The server could not start one of its networks.
ACTION
Be sure that each network listed in the SRVNETS entry in the server's configuration file has a corresponding entry in the [networks] section of the configuration file.
|
|
|
The AT command processor could not run ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
You used the AT utility to specify a program that could not run.
ACTION
Check the filename of the program you tried to schedule. If it is in a directory that is not on the computer's search path, be sure to specify its full path.
Be sure that all programs you schedule are executable.
|
|
|
WARNING: Because of a lazy-write error, drive *** now
contains some corrupted data. The cache is stopped.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
An error occurred when the lazy-write process tried to write to the specified hard disk.
ACTION
Run CHKDSK on the specified drive to check for problems with the disk or the files affected by the lazy-write process.
|
|
|
A defective sector on drive *** has been replaced (hotfixed).
No data was lost. You should run CHKDSK soon to restore full
performance and replenish the volume's spare sector pool.
The hotfix occurred while processing a remote request.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The fault-tolerance system found a bad disk sector and rerouted data to a good sector (this is called hotfixing). No data was lost.
ACTION
Run CHKDSK soon to ensure that enough good disk sectors are available for hotfixing.
|
|
|
A disk error occurred on the HPFS volume in drive ***.
The error occurred while processing a remote request.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
An error occurred during an operation on the listed disk because of problems with the disk. The operation probably did not succeed.
ACTION
Retry the operation. If the problem persists and you are unable to recover data from the disk, use backups of the affected files, if you have any.
|
|
|
The user accounts database (NET.ACC) is corrupted. The local security
system is replacing the corrupted NET.ACC with the backup
made at ***.
Any updates made to the database after this time are lost.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The user accounts database file is damaged, so the backup file made at the listed date is now being used. Changes made to the user accounts database since this time were lost. Local security is still in effect.
ACTION
To update the user accounts database, retype changes made to it since the listed date.
|
|
|
The user accounts database (NET.ACC) is missing. The local
security system is restoring the backup database
made at ***.
Any updates made to the database made after this time are lost.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The user accounts database file is missing, so the backup file made at the listed date is now being used. Changes made to the user accounts database since this time were lost. Local security is still in effect.
ACTION
To update the user accounts database, retype changes made to it since the listed date.
|
|
|
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.
|
|
|
Local security could not be started because an error
occurred during initialization. The error code returned is ***.
THE SYSTEM IS NOT SECURE.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
Local security could not start because of the listed error.
ACTION
Find and correct the cause of the listed error, and then restart the computer.
|
|
|
A NetWksta internal error has occurred:
***
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
A software error occurred.
ACTION
Contact technical support.
|
|
|
The redirector is out of a resource: ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The workstation is out of the specified resource.
ACTION
Adjust the workstation's configuration file to increase the amount of this resource. If you need assistance, contact your network administrator.
|
|
|
A server message block (SMB) error occurred on the connection to ***.
The SMB header is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
An error occurred on a request that was sent to the specified
server. The workstation may have been connected to a resource that is no longer shared.
ACTION
Ask a network administrator to reshare the resource so that you can use it.
If this solution fails, contact technical support.
|
|
|
A virtual circuit error occurred on the session to ***.
The network control block (NCB) command and return code is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The connection between your workstation and the specified server was unexpectedly broken. The server may have been restarted or a network problem may have occurred.
ACTION
If the server was restarted, retry the operation to reestablish the connection.
If you need more assistance, contact technical support.
This message displays a network control block (NCB) value and the NCB error that was returned. Save this information for technical support.
|
|
|
Hanging up a stuck session to ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The session with the specified server was ended because the server stopped responding.
ACTION
Ask your network administrator if the server is running. If so, reconnect to the server.
The amount of time a workstation waits for a server
to respond to a request is determined by the SESSTIMEOUT entry in the workstation's configuration file. If your sessions with servers are frequently ended by this error, you may want to increase the value of SESSTIMEOUT.
If you need assistance, contact your administrator.
|
|
|
A network control block (NCB) error occurred (***).
The NCB is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
An unexpected network control block (NCB) error occurred
on the session with the specified server. The server may have been restarted, or a network problem may have occurred.
ACTION
Ask your network administrator if the server was recently restarted.
If you need more assistance, contact technical support. This message displays an NCB value and the NCB error that was returned. Save this information for technical support.
|
|
|
A write operation to *** failed.
Data may have been lost.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
An attempt to write data to a file failed.
ACTION
See if the specified disk is full. Also be sure that you have write permission for the target file.
|
|
|
Reset of driver *** failed to complete the network control block (NCB).
The NCB is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The specified NetBIOS driver found a problem that
required the network adapter card to be reset. Resetting the card did not solve the problem.
ACTION
Contact technical support.
|
|
|
The amount of resource *** requested was more
than the maximum. The maximum amount was allocated.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The amount of the listed resource requested was more than the maximum. The maximum amount was allocated.
ACTION
Ask your network administrator check the workstation's configuration.
|
|
|
The server could not create a thread. The THREADS parameter in the CONFIG.SYS file should be increased.
|
|
|
The server could not close ***.
The file is probably corrupted.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The server found an error while closing the listed file.
ACTION
The file may be damaged. If it is, restore it from a backup copy.
|
|
|
The replicator cannot update directory ***. It has tree integrity
and is the current directory for some process.
EXPLANATION
A directory cannot be replicated when it is the current directory of a process and its value for INTEGRITY is TREE.
ACTION
For the directory to be replicated, be sure it is not the current directory of any process.
|
|
|
The server cannot export directory *** to client ***.
It is exported from another server.
EXPLANATION
This server found that another server is exporting the listed directory to the listed import server.
ACTION
Be sure that only one computer is configured as the export server of this directory for the listed import computer. Check the EXPORTLIST and EXPORTPATH entries in the configuration files of the export servers and the IMPORTLIST and IMPORTPATH entries
in
the configuration file of the import server.
|
|
|
The replication server could not update directory *** from the source
on *** due to error ***.
EXPLANATION
An error prevented this server from updating the listed directory from the export server. The directory cannot be updated until the problem is corrected.
ACTION
Copy the files manually, if necessary, and investigate the cause of the listed error.
|
|
|
Master *** did not send an update notice for directory *** at the expected
time.
EXPLANATION
This server's Replicator service lost contact with
the export server for the listed directory.
ACTION
Be sure the Server and Replicator services are running on the export server.
|
|
|
This computer could not authenticate with ***, a Windows domain controller
for domain ***, and therefore this computer might deny logon requests.
This inability to authenticate might be caused by another computer on the
same network using the same name or the password for this computer account
is not recognized. If this message appears again, contact your system
administrator.
EXPLANATION
This server was denied access to the security database by the domain controller. Until this problem is corrected, the server cannot synchronize user account information with the domain controller.
ACTION
Stop and restart the Netlogon service at this server.
|
|
|
The replicator attempted to log on at *** as *** and failed.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The Replicator service was denied access to the listed export server. Until this problem is corrected, the replicator cannot update the local copies of files exported by that server.
ACTION
Be sure that the local computer has an account on the export server.
The user name and password for this account are specified by the LOGON and PASSWORD entries in the local computer's configuration file. If there is no LOGON entry, then the local computer name is the user name and no password is necessary.
|
|
|
Network error *** occurred.
EXPLANATION
The Replicator service stopped because the listed Windows NT error occurred.
ACTION
To see more information about the error, type:
NET HELPMSG message#
where message# is the error number.
|
|
|
Replicator limit for files in a directory has been exceeded.
|
|
|
Replicator limit for tree depth has been exceeded.
|
|
|
Unrecognized message received in mailslot.
|
|
|
System error *** occurred.
EXPLANATION
The Replicator service stopped because the listed system error occurred.
ACTION
Check the cause of the system error.
|
|
|
Cannot log on. User is currently logged on and argument TRYUSER is set to NO.
|
|
|
IMPORT path *** cannot be found.
EXPLANATION
The import path specified either from the command line or in the configuration file, does not exist.
ACTION
Check the spelling of the IMPORTPATH entry in the configuration file. This entry must specify a directory that exists.
|
|
|
EXPORT path *** cannot be found.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The specified export path does not exist.
ACTION
Check the spelling of the EXPORTPATH entry in the configuration file. This entry must specify a directory that exists.
|
|
|
Replicator failed to update signal file in directory *** due to
*** system error.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The listed system error caused the Replicator service to fail to update its status.
ACTION
Check the cause of the system error.
|
|
|
Disk Fault Tolerance Error
***
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
An error was recorded by the fault-tolerance system.
The error is explained in the original error message.
ACTION
Follow the action recommended in the original message.
|
|
|
Replicator could not access ***
on *** due to system error ***.
EXPLANATION
Because of the listed system error, the Replicator service could not access a file on the listed export server.
ACTION
Be sure the Replicator service's account on the export server has permission to read the directories being replicated. The name of this account can be displayed and changed using the Services option in Computer Management System Tools.
|
|
|
The primary domain controller for domain *** has apparently failed.
EXPLANATION
The domain controller for this domain has stopped.
ACTION
Wait a few minutes and then restart the domain controller.
If this is not possible, you have the option of promoting another server to be the domain controller.
|
|
|
Changing machine account password for account *** failed with
the following error:
***
EXPLANATION
This server found an error while changing the computer's password at the domain controller.
ACTION
If you are using Windows NT Workstation, ask your network administrator to set your computer value back to the default value. Then, using the System option in Control Panel, leave and rejoin the domain.
If you are using Windows NT Server, use the Synchronize With Domain option in Server Manager to synchronize the servers.
|
|
|
An error occurred while updating the logon or logoff information for ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The current logon statistics may not be accurate because an error occurred while logon and logoff information was being updated.
ACTION
No action is needed.
|
|
|
An error occurred while synchronizing with primary domain controller ***
EXPLANATION
The local copy of the security database may be out of synchronization with that of the domain controller because an error occurred while the database was being updated.
ACTION
Use the Synchronize With Domain option in Server Manager to synchronize the security databases.
|
|
|
The session setup to the Windows NT or Windows 2000 Domain Controller *** for the domain ***
failed because *** does not support signing or sealing the Netlogon
session.
Either upgrade the Domain controller or set the RequireSignOrSeal
registry entry on this machine to 0.
|
|
|
A power failure was detected at the server.
|
|
|
The UPS service performed server shut down.
|
|
|
The UPS service did not complete execution of the user specified shut down command file.
|
|
|
The UPS driver could not be opened. The error code is the data.
|
|
|
Power has been restored.
|
|
|
There is a problem with a configuration of user specified shut down command file.
|
|
|
The UPS service failed to execute a user specified shutdown
command file ***. The error code is the data.
|
|
|
Initialization failed because of an invalid or missing
parameter in the configuration file ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The Remoteboot service could not start because the listed entry was missing from the configuration file.
ACTION
Add the listed entry to the server's configuration file.
|
|
|
Initialization failed because of an invalid line in the
configuration file ***. The invalid line is the data.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The Remoteboot service could not start because of an invalid line in the listed configuration file.
ACTION
Check the listed line.
|
|
|
Initialization failed because of an error in the configuration
file ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The Remoteboot service failed to start because of an error in the listed configuration file.
ACTION
Check the listed file.
|
|
|
The file *** has been changed after initialization.
The boot-block loading was temporarily terminated.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The listed file was changed after the Remoteboot service was started. Loading the boot-block stopped temporarily.
ACTION
Stop and restart the Remoteboot service.
|
|
|
The files do not fit to the boot-block configuration
file ***. Change the BASE and ORG definitions or the order
of the files.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The files in the listed boot-block definition file do not fit in the boot block.
ACTION
Change the order of the files or the value of BASE or ORG.
|
|
|
Initialization failed because the dynamic-link
library *** returned an incorrect version number.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The Remoteboot service could not start because the listed dynamic-link library returned the incorrect version number.
ACTION
Be sure you are using the correct versions of the dynamic-link libraries.
|
|
|
There was an unrecoverable error in the dynamic- link library of the service.
|
|
|
The system returned an unexpected error code. The error code is the data.
|
|
|
The fault-tolerance error log file, LANROOT\LOGS\FT.LOG, is more than 64K.
|
|
|
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.
|
|
|
This computer has been successfully joined to *** '***'.
|
|
|
*** *** *** *** *** *** *** *** ***.
|
|
|
Remote IPC
|
|
|
Remote Admin
|
|
|
Logon server share
|
|
|
A network error occurred.
|
|
|
There is not enough memory to start the Workstation service.
|
|
|
An error occurred when reading the NETWORKS entry in the LANMAN.INI file.
|
|
|
This is an invalid argument: ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The listed variable or option (from an entry in the [networks] section of the LANMAN.INI file) is invalid.
ACTION
Check the format of the entries in the [networks] section of the LANMAN.INI file.
|
|
|
The *** NETWORKS entry in the LANMAN.INI file has a
syntax error and will be ignored.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The listed entry in the [networks] section of the LANMAN.INI file has a syntax error.
ACTION
Check the format of the listed entry.
|
|
|
There are too many NETWORKS entries in the LANMAN.INI file.
|
|
|
An error occurred when opening network
device driver *** = ***.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The listed device driver could not be installed.
ACTION
Check that the listed entry in the [networks] section of the LANMAN.INI file is valid.
In the CONFIG.SYS file, check the DEVICE entry that loads this device driver--the parameters of that entry may not be correct.
Also check that the DEVICE entry specifies the correct path of the device driver.
|
|
|
Device driver *** sent a bad BiosLinkage response.
EXPLANATION
This message should occur only on a down-level computer. Any action to correct the problem should be performed on that computer.
The device driver specified is incorrect. It may be incompatible with the network adapter card, or it may be out-of-date.
ACTION
Use a different device driver.
|
|
|
The program cannot be used with this operating system.
|
|
|
The redirector is already installed.
|
|
|
Installing NETWKSTA.SYS Version ***.***.*** (***)
|
|
|
There was an error installing NETWKSTA.SYS. Press ENTER to continue.
|
|
|
Resolver linkage problem.
|
|
|
Your logon time at *** ends at ***.
Please clean up and log off.
|
|
|
You will be automatically disconnected at ***.
|
|
|
Your logon time at *** has ended.
|
|
|
Your logon time at *** ended at ***.
|
|
|
WARNING: You have until *** to logoff. If you
have not logged off at this time, your session will be
disconnected, and any open files or devices you
have open may lose data.
|
|
|
WARNING: You must log off at *** now. You have
two minutes to log off, or you will be disconnected.
|
|
|
You have open files or devices, and a forced disconnection may cause you to lose data.
|
|
|
Default Share for Internal Use
|
|
|
Messenger Service
|
|
|
The command completed successfully.
|
|
|
You used an invalid option.
|
|
|
System error *** has occurred.
EXPLANATION
The specified system error occurred.
ACTION
Correct the problem and retype the command.
|
|
|
The command contains an invalid number of arguments.
|
|
|
The command completed with one or more errors.
|
|
|
You used an option with an invalid value.
|
|
|
The option *** is unknown.
EXPLANATION
The specified option is invalid.
ACTION
Check the spelling of the option you typed.
To see a list of options for this command, type:
NET HELP command
|
|
|
Option *** is ambiguous.
EXPLANATION
The specified option can be confused with other options.
ACTION
Type enough letters of the option so that it is unambiguous.
If the command has two options that both begin with /OPT, such as /OPT and /OPTION, you must type at least four letters to designate the second option.
To see a list of options for this command, type:
NET HELP command
|
|
|
A command was used with conflicting switches.
|
|
|
Could not find subprogram ***.
EXPLANATION
The specified program file could not be found.
ACTION
Check that the program is in the same directory as NET.EXE, which is usually in your system directory.
|
|
|
The software requires a newer version of the operating system.
|
|
|
More data is available than can be returned by Windows.
|
|
|
More help is available by typing NET HELPMSG ***.
|
|
|
This command can be used only on a Windows Domain Controller.
|
|
|
This command cannot be used on a Windows Domain Controller.
|
|
|
These Windows services are started:
|
|
|
The *** service is not started.
|
|
|
The *** service is starting
|
|
|
The *** service could not be started.
|
|
|
The *** service was started successfully.
|
|
|
Stopping the Workstation service also stops the Server service.
|
|
|
The workstation has open files.
|
|
|
The *** service is stopping
|
|
|
The *** service could not be stopped.
|
|
|
The *** service was stopped successfully.
|
|
|
The following services are dependent on the *** service.
Stopping the *** service will also stop these services.
|
|
|
The service is starting or stopping. Please try again later.
|
|
|
The service did not report an error.
|
|
|
An error occurred controlling the device.
|
|
|
The *** service was continued successfully.
|
|
|
The *** service was paused successfully.
|
|
|
The *** service failed to resume.
|
|
|
The *** service failed to pause.
|
|
|
The *** service continue is pending
|
|
|
The *** service pause is pending
|
|
|
*** was continued successfully.
|
|
|
*** was paused successfully.
|
|
|
The *** service has been started by another process and is pending.
|
|
|
A service specific error occurred: ***.
EXPLANATION
A service-specific error occurred.
ACTION
Refer to the Help or documentation for that service to determine the problem.
|
|
|
These workstations have sessions on this server:
|
|
|
These workstations have sessions with open files on this server:
|
|
|
The message alias is forwarded.
|
|
|
You have these remote connections:
|
|
|
Continuing will cancel the connections.
|
|
|
The session from *** has open files.
|
|
|
New connections will be remembered.
|
|
|
New connections will not be remembered.
|
|
|
An error occurred while saving your profile : Access Denied. The state of your remembered connections has not changed.
|
|
|
An error occurred while reading your profile.
|
|
|
An error occurred while restoring the connection to ***.
|
|
|
No network services are started.
|
|
|
There are no entries in the list.
|
|
|
Users have open files on ***. Continuing the operation will force the files closed.
|
|
|
The Workstation service is already running. Windows will ignore command options for the workstation.
|
|
|
There are open files and/or incomplete directory searches pending on the connection to ***.
|
|
|
The request will be processed at a domain controller for domain ***.
|
|
|
The shared queue cannot be deleted while a print job is being spooled to the queue.
|
|
|
*** has a remembered connection to ***.
|
|
|
An error occurred while opening the Help file.
|
|
|
The Help file is empty.
|
|
|
The Help file is corrupted.
|
|
|
Could not find a domain controller for domain ***.
EXPLANATION
Either this domain does not have logon security and therefore does not have a domain controller, or its domain controller is currently unavailable.
ACTION
If this domain does not have logon security, you cannot use this domain. Otherwise, retry the command. If the problem persists, ask your network administrator if the domain controller is running.
|
|
|
This operation is privileged on systems with earlier versions of the software.
|
|
|
The device type is unknown.
|
|
|
The log file has been corrupted.
|
|
|
Program filenames must end with .EXE.
|
|
|
A matching share could not be found so nothing was deleted.
|
|
|
A bad value is in the units-per-week field of the user record.
|
|
|
The password is invalid for ***.
EXPLANATION
You used an incorrect password.
ACTION
Check that you have the correct password, and then retype it.
If you cannot remember your password, see your network administrator to have your password changed.
|
|
|
An error occurred while sending a message to ***.
EXPLANATION
An error occurred when a message was sent to the alias you selected. An additional error message should follow this one. It will tell you what action to take to correct the error.
ACTION
Follow the recommended action in the second error message.
|
|
|
The password or user name is invalid for ***.
EXPLANATION
Either your password or your user name is incorrect.
ACTION
Retry the operation with the correct password or user name.
If you cannot remember your password, see your network administrator to have your password changed.
|
|
|
An error occurred when the share was deleted.
|
|
|
The user name is invalid.
|
|
|
The password is invalid.
|
|
|
The passwords do not match.
|
|
|
Your persistent connections were not all restored.
|
|
|
This is not a valid computer name or domain name.
|
|
|
Default permissions cannot be set for that resource.
|
|
|
A valid password was not entered.
|
|
|
A valid name was not entered.
|
|
|
The resource named cannot be shared.
|
|
|
The permissions string contains invalid permissions.
|
|
|
You can only perform this operation on printers and communication devices.
|
|
|
*** is an invalid user or group name.
EXPLANATION
You typed an invalid user name or group name.
ACTION
Check the spelling of the user or group name. To see a list of existing users, type:
NET USER
To see a list of existing local groups, type:
NET LOCALGROUP
To see a list of existing global groups, type:
NET GROUP
|
|
|
The server is not configured for remote administration.
|
|
|
No users have sessions with this server.
|
|
|
User *** is not a member of group ***.
EXPLANATION
This user is not a member of the group.
ACTION
No action is needed.
|
|
|
User *** is already a member of group ***.
EXPLANATION
This user is already a member of the group.
ACTION
No action is needed.
|
|
|
There is no such user: ***.
EXPLANATION
You typed an unknown user name.
ACTION
Check the spelling of the user name and then retype the command.
|
|
|
This is an invalid response.
|
|
|
No valid response was provided.
|
|
|
The destination list provided does not match the destination list of the printer queue.
|
|
|
Your password cannot be changed until ***.
|
|
|
*** is not a recognized day of the week.
EXPLANATION
The day you specified is invalid. Valid days are Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday.
Valid abbreviations are M, T, W, Th, F, Sa, and Su.
ACTION
Retype the command, using valid names or abbreviations.
|
|
|
The time range specified ends before it starts.
|
|
|
*** is not a recognized hour.
EXPLANATION
You specified an hour in a format that could not be recognized. The hour can be a number from 0 to 12 in 12-hour format or 0 to 24 in 24-hour format. If you use the 12-hour format, you must specify either AM or PM for each time.
ACTION
Retype the command with the correct hour format.
|
|
|
*** is not a valid specification for minutes.
EXPLANATION
You specified the minutes in a format that could not be recognized.
Typing the minutes is optional, but if included, the format must be :00 (a colon and two zeros).
ACTION
Retype the command, either omitting the minutes or using the correct format (:00).
|
|
|
Time supplied is not exactly on the hour.
|
|
|
12 and 24 hour time formats may not be mixed.
|
|
|
*** is not a valid 12-hour suffix.
EXPLANATION
You tried to use the 12-hour format, but the time was followed by text that was neither AM nor PM.
If you use the 12-hour format, you must follow each time with either AM, A.M., PM, or P.M.
ACTION
Retype the command with the correct forms of AM and PM.
|
|
|
An illegal date format has been supplied.
|
|
|
An illegal day range has been supplied.
|
|
|
An illegal time range has been supplied.
|
|
|
Arguments to NET USER are invalid. Check the minimum password length and/or arguments supplied.
|
|
|
The value for ENABLESCRIPT must be YES.
|
|
|
An illegal country/region code has been supplied.
|
|
|
The user was successfully created but could not be added to the USERS local group.
|
|
|
The user context supplied is invalid.
|
|
|
The dynamic-link library *** could not be loaded, or an error
occurred while trying to use it.
EXPLANATION
A system dynamic-link library could not be loaded.
ACTION
Make sure the file specified is in your system directory. If it is not, contact your network administrator.
|
|
|
Sending files is no longer supported.
|
|
|
You may not specify paths for ADMIN$ and IPC$ shares.
|
|
|
User or group *** is already a member of local group ***.
EXPLANATION
The account (user or global group) is already in the local group you are trying to add it to.
ACTION
No action is needed.
|
|
|
There is no such user or group: ***.
EXPLANATION
The user or group specified does not exist.
ACTION
Retype the command with a correct user name or group name.
|
|
|
There is no such computer: ***.
EXPLANATION
The computer account specified does not exist.
ACTION
Retype the command with a correct computer name.
|
|
|
The computer *** already exists.
EXPLANATION
The computer account specified already exists.
ACTION
Choose a different computer name.
|
|
|
There is no such global user or group: ***.
EXPLANATION
The global user or group specified does not exist.
ACTION
Retype the command with a correct user name or group name.
|
|
|
Only disk shares can be marked as cacheable
|
|
|
The system could not find message: ***.
EXPLANATION
The system could not find the message.
ACTION
Contact your system administrator.
|
|
|
This schedule date is invalid.
|
|
|
The LANMAN root directory is unavailable.
|
|
|
The SCHED.LOG file could not be opened.
|
|
|
The Server service has not been started.
|
|
|
The AT job ID does not exist.
|
|
|
The AT schedule file is corrupted.
|
|
|
The delete failed due to a problem with the AT schedule file.
|
|
|
The command line cannot exceed 259 characters.
|
|
|
The AT schedule file could not be updated because the disk is full.
|
|
|
The AT schedule file is invalid. Please delete the file and create a new one.
|
|
|
The AT schedule file was deleted.
|
|
|
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. You can specify the date as M,T,W,Th,F,Sa,Su or 1-31 for the day of the month. You can specify the time in the 24 hour HH:MM format.
|
|
|
The AT command has timed-out. Please try again later.
|
|
|
The minimum password age for user accounts cannot be greater than the maximum password age.
|
|
|
You have specified a value that is incompatible with servers with down-level software. Please specify a lower value.
|
|
|
*** is not a valid computer name.
EXPLANATION
The computer name you specified is invalid.
ACTION
Check the spelling of the computer name.
|
|
|
Message from *** to *** on ***
|
|
|
****
|
|
|
**** unexpected end of message ****
|
|
|
Press ESC to exit
|
|
|
...
|
|
|
Current time at *** is ***
|
|
|
The current local clock is ***
Do you want to set the local computer's time to match the
time at ***? ***:
|
|
|
Could not locate a time-server.
|
|
|
Could not find the domain controller for domain ***.
EXPLANATION
Either this domain does not have logon security and therefore does not have a domain controller, or its domain controller is unavailable.
ACTION
If this domain does not have logon security, you cannot use this command. Otherwise, retry the command. If the problem persists, ask your network administrator if the domain controller is running.
|
|
|
Local time (GMT***) at *** is ***
|
|
|
The user's home directory could not be determined.
|
|
|
The user's home directory has not been specified.
|
|
|
The name specified for the user's home directory (***) is not a universal naming convention (UNC) name.
EXPLANATION
Your home directory is not a network path that can be connected to. The directory must specify a full path, including the server and share names.
ACTION
Ask your network administrator to verify that the home directory path specified in the user account is correct.
|
|
|
Drive *** is now connected to ***. Your home directory is ***\***.
|
|
|
Drive *** is now connected to ***.
|
|
|
There are no available drive letters left.
|
|
|
*** is not a valid domain or workgroup name.
EXPLANATION
The name you specified is not a valid domain or workgroup name.
ACTION
Check the spelling of the name. Retype the command with a valid domain or workgroup name.
|
|
|
The current SNTP value is: ***
|
|
|
This computer is not currently configured to use a specific SNTP server.
|
|
|
This current autoconfigured SNTP value is: ***
|
|
|
You specified too many values for the *** option.
EXPLANATION
You specified too many values for the listed option.
ACTION
Retype the command with the correct number of values. To see the syntax of this command, type:
NET HELP command
|
|
|
You entered an invalid value for the *** option.
EXPLANATION
You typed an invalid value for the listed option.
ACTION
Retype the command with valid values. To see the syntax of this command, type:
NET HELP command
|
|
|
The syntax is incorrect.
|
|
|
You specified an invalid file number.
|
|
|
You specified an invalid print job number.
|
|
|
The user or group account specified cannot be found.
|
|
|
The user was added but could not be enabled for File and Print Services for NetWare.
|
|
|
File and Print Services for NetWare is not installed.
|
|
|
Cannot set user properties for File and Print Services for NetWare.
|
|
|
Password for *** is: ***
|
|
|
NetWare compatible logon
|
|
|
WINS encountered an error while processing the command.
|
|
|
The local WINS cannot be deleted.
|
|
|
The importation from the file failed.
|
|
|
The backup failed. Was a full backup done before?
|
|
|
The backup failed. Check the directory to which you are backing the database.
|
|
|
The name does not exist in the WINS database.
|
|
|
Replication with a nonconfigured partner is not allowed.
|
|
|
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.
|
|
|
The GUID passed was not recognized as valid by a WMI data provider.
|
|
|
The instance name passed was not recognized as valid by a WMI data provider.
|
|
|
The data item ID passed was not recognized as valid by a WMI data provider.
|
|
|
The WMI request could not be completed and should be retried.
|
|
|
The WMI data provider could not be located.
|
|
|
The WMI data provider references an instance set that has not been registered.
|
|
|
The WMI data block or event notification has already been enabled.
|
|
|
The WMI data block is no longer available.
|
|
|
The WMI data service is not available.
|
|
|
The WMI data provider failed to carry out the request.
|
|
|
The WMI MOF information is not valid.
|
|
|
The WMI registration information is not valid.
|
|
|
The WMI data block or event notification has already been disabled.
|
|
|
The WMI data item or data block is read only.
|
|
|
The WMI data item or data block could not be changed.
|
|
|
The media identifier does not represent a valid medium.
|
|
|
The library identifier does not represent a valid library.
|
|
|
The media pool identifier does not represent a valid media pool.
|
|
|
The drive and medium are not compatible or exist in different libraries.
|
|
|
The medium currently exists in an offline library and must be online to perform this operation.
|
|
|
The operation cannot be performed on an offline library.
|
|
|
The library, drive, or media pool is empty.
|
|
|
The library, drive, or media pool must be empty to perform this operation.
|
|
|
No media is currently available in this media pool or library.
|
|
|
A resource required for this operation is disabled.
|
|
|
The media identifier does not represent a valid cleaner.
|
|
|
The drive cannot be cleaned or does not support cleaning.
|
|
|
The object identifier does not represent a valid object.
|
|
|
Unable to read from or write to the database.
|
|
|
The database is full.
|
|
|
The medium is not compatible with the device or media pool.
|
|
|
The resource required for this operation does not exist.
|
|
|
The operation identifier is not valid.
|
|
|
The media is not mounted or ready for use.
|
|
|
The device is not ready for use.
|
|
|
The operator or administrator has refused the request.
|
|
|
The drive identifier does not represent a valid drive.
|
|
|
Library is full. No slot is available for use.
|
|
|
The transport cannot access the medium.
|
|
|
Unable to load the medium into the drive.
|
|
|
Unable to retrieve the drive status.
|
|
|
Unable to retrieve the slot status.
|
|
|
Unable to retrieve status about the transport.
|
|
|
Cannot use the transport because it is already in use.
|
|
|
Unable to open or close the inject/eject port.
|
|
|
Unable to eject the medium because it is in a drive.
|
|
|
A cleaner slot is already reserved.
|
|
|
A cleaner slot is not reserved.
|
|
|
The cleaner cartridge has performed the maximum number of drive cleanings.
|
|
|
Unexpected on-medium identifier.
|
|
|
The last remaining item in this group or resource cannot be deleted.
|
|
|
The message provided exceeds the maximum size allowed for this parameter.
|
|
|
The volume contains system or paging files.
|
|
|
The media type cannot be removed from this library since at least one drive in the library reports it can support this media type.
|
|
|
This offline media cannot be mounted on this system since no enabled drives are present which can be used.
|
|
|
A cleaner cartridge is present in the tape library.
|
|
|
Cannot use the inject/eject port because it is not empty.
|
|
|
Error
|
|
|
OK
|
|
|
Y
|
|
|
N
|
|
|
Any
|
|
|
A
|
|
|
P
|
|
|
(not found)
|
|
|
This file is currently not available for use on this computer.
|
|
|
The remote storage service is not operational at this time.
|
|
|
The remote storage service encountered a media error.
|
|
|
Change
|
|
|
Type the password for ***:
|
|
|
Type a password for the user:
|
|
|
Type the password for the shared resource:
|
|
|
Type your password:
|
|
|
Retype the password to confirm:
|
|
|
Type the user's old password:
|
|
|
Type the user's new password:
|
|
|
Type your new password:
|
|
|
Type the Replicator service password:
|
|
|
Type your user name, or press ENTER if it is ***:
|
|
|
Type the domain or server where you want to change a password, or
press ENTER if it is for domain ***:
|
|
|
Type your user name:
|
|
|
Network statistics for \\***
|
|
|
Printing options for ***
|
|
|
Communication-device queues accessing ***
|
|
|
Print job detail
|
|
|
Communication-device queues at \\***
|
|
|
Printers at ***
|
|
|
Printers accessing ***
|
|
|
Print jobs at ***:
|
|
|
Shared resources at ***
|
|
|
The following running services can be controlled:
|
|
|
Statistics are available for the following running services:
|
|
|
User accounts for \\***
|
|
|
The syntax of this command is:
|
|
|
The options of this command are:
|
|
|
Please enter the name of the Primary Domain Controller:
|
|
|
The string you have entered is too long. The maximum
is ***, please reenter.
|
|
|
Sunday
|
|
|
Monday
|
|
|
Tuesday
|
|
|
Wednesday
|
|
|
Thursday
|
|
|
The file or directory is not a reparse point.
|
|
|
The reparse point attribute cannot be set because it conflicts with an existing attribute.
|
|
|
The data present in the reparse point buffer is invalid.
|
|
|
The tag present in the reparse point buffer is invalid.
|
|
|
There is a mismatch between the tag specified in the request and the tag present in the reparse point.
|
|
|
The object manager encountered a reparse point while retrieving an object.
|
|
|
Th
|
|
|
F
|
|
|
S
|
|
|
Sa
|
|
|
Fast Cache data not found.
|
|
|
Fast Cache data expired.
|
|
|
Fast Cache data corrupt.
|
|
|
Fast Cache data has exceeded its max size and cannot be updated.
|
|
|
Aliases for \\***
|
|
|
Alias name
|
|
|
Comment
|
|
|
Members
|
|
|
User Accounts for \\***
|
|
|
User name
|
|
|
Full Name
|
|
|
Comment
|
|
|
User's comment
|
|
|
Parameters
|
|
|
Country/region code
|
|
|
Privilege level
|
|
|
Operator privileges
|
|
|
Account active
|
|
|
Secure Boot detected that rollback of protected data has been attempted.
|
|
|
The value is protected by Secure Boot policy and cannot be modified or deleted.
|
|
|
The Secure Boot policy is invalid.
|
|
|
A new Secure Boot policy did not contain the current publisher on its update list.
|
|
|
The Secure Boot policy is either not signed or is signed by a non-trusted signer.
|
|
|
Secure Boot is not enabled on this machine.
|
|
|
Secure Boot requires that certain files and drivers are not replaced by other files or drivers.
|
|
|
The Secure Boot Supplemental Policy file was not authorized on this machine.
|
|
|
The Supplemental Policy is not recognized on this device.
|
|
|
The Antirollback version was not found in the Secure Boot Policy.
|
|
|
The Platform ID specified in the Secure Boot policy does not match the Platform ID on this device.
|
|
|
The Secure Boot policy file has an older Antirollback Version than this device.
|
|
|
The Secure Boot policy file does not match the upgraded legacy policy.
|
|
|
The Secure Boot policy file is required but could not be found.
|
|
|
Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy.
|
|
|
Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy.
|
|
|
Home directory
|
|
|
Password required
|
|
|
User may change password
|
|
|
User profile
|
|
|
The copy offload read operation is not supported by a filter.
|
|
|
Computer name
|
|
|
User name
|
|
|
Software version
|
|
|
Workstation active on
|
|
|
Windows NT root directory
|
|
|
Workstation domain
|
|
|
Logon domain
|
|
|
Other domain(s)
|
|
|
COM Open Timeout (sec)
|
|
|
COM Send Count (byte)
|
|
|
COM Send Timeout (msec)
|
|
|
DOS session print time-out (sec)
|
|
|
Maximum error log size (K)
|
|
|
Maximum cache memory (K)
|
|
|
Number of network buffers
|
|
|
Number of character buffers
|
|
|
Size of network buffers
|
|
|
Size of character buffers
|
|
|
Full Computer name
|
|
|
Workstation Domain DNS Name
|
|
|
Windows 2002
|
|
|
Server Name
|
|
|
Server Comment
|
|
|
Send administrative alerts to
|
|
|
Software version
|
|
|
Peer Server
|
|
|
Windows NT
|
|
|
Server Level
|
|
|
Windows NT Server
|
|
|
Server is active on
|
|
|
Server hidden
|
|
|
Single Instance Storage is not available on this volume.
|
|
|
Maximum Logged On Users
|
|
|
Maximum concurrent administrators
|
|
|
Maximum resources shared
|
|
|
Maximum connections to resources
|
|
|
Maximum open files on server
|
|
|
Maximum open files per session
|
|
|
Maximum file locks
|
|
|
Idle session time (min)
|
|
|
Share-level
|
|
|
User-level
|
|
|
Unlimited Server
|
|
|
The Platform Manifest file was not authorized on this machine.
|
|
|
The Platform Manifest file was not valid.
|
|
|
The file is not authorized on this platform because an entry was not found in the Platform Manifest.
|
|
|
The catalog is not authorized on this platform because an entry was not found in the Platform Manifest.
|
|
|
The file is not authorized on this platform because a Binary ID was not found in the embedded signature.
|
|
|
No active Platform Manifest exists on this system.
|
|
|
The Platform Manifest file was not properly signed.
|
|
|
Primary Domain controller for workstation domain:
|
|
|
Lockout threshold:
|
|
|
Lockout duration (minutes):
|
|
|
Lockout observation window (minutes):
|
|
|
Statistics since
|
|
|
Sessions accepted
|
|
|
Sessions timed-out
|
|
|
Sessions errored-out
|
|
|
Kilobytes sent
|
|
|
Kilobytes received
|
|
|
Mean response time (msec)
|
|
|
Network errors
|
|
|
Files accessed
|
|
|
Print jobs spooled
|
|
|
System errors
|
|
|
Password violations
|
|
|
Permission violations
|
|
|
Communication devices accessed
|
|
|
Sessions started
|
|
|
Sessions reconnected
|
|
|
Sessions starts failed
|
|
|
Sessions disconnected
|
|
|
Network I/O's performed
|
|
|
Files and pipes accessed
|
|
|
Times buffers exhausted
|
|
|
Big buffers
|
|
|
Request buffers
|
|
|
Workstation Statistics for \\***
|
|
|
Server Statistics for \\***
|
|
|
Statistics since ***
|
|
|
Connections made
|
|
|
Connections failed
|
|
|
Bytes received
|
|
|
Server Message Blocks (SMBs) received
|
|
|
Bytes transmitted
|
|
|
Server Message Blocks (SMBs) transmitted
|
|
|
Read operations
|
|
|
Write operations
|
|
|
Raw reads denied
|
|
|
Raw writes denied
|
|
|
Network errors
|
|
|
Connections made
|
|
|
Reconnections made
|
|
|
Server disconnects
|
|
|
Sessions started
|
|
|
Hung sessions
|
|
|
Failed sessions
|
|
|
Failed operations
|
|
|
Use count
|
|
|
Failed use count
|
|
|
*** was deleted successfully.
|
|
|
*** was used successfully.
|
|
|
The message was successfully sent to ***.
|
|
|
The message name *** was forwarded successfully.
|
|
|
The message name *** was added successfully.
|
|
|
The message name forwarding was successfully canceled.
|
|
|
*** was shared successfully.
|
|
|
The server *** successfully logged you on as ***.
|
|
|
*** was logged off successfully.
|
|
|
*** was successfully removed from the list of shares the Server creates
on startup.
|
|
|
The password was changed successfully.
|
|
|
*** file(s) copied.
|
|
|
*** file(s) moved.
|
|
|
The message was successfully sent to all users of the network.
|
|
|
The message was successfully sent to domain ***.
|
|
|
The message was successfully sent to all users of this server.
|
|
|
The message was successfully sent to group ****.
|
|
|
Microsoft LAN Manager Version ***
|
|
|
Windows NT Server
|
|
|
Windows NT Workstation
|
|
|
MS-DOS Enhanced Workstation
|
|
|
Created at ***
|
|
|
Server Name Remark
|
|
|
(UNC)
|
|
|
...
|
|
|
Domain
|
|
|
Resources on ***
|
|
|
Invalid network provider. Available networks are:
|
|
|
Disk
|
|
|
Print
|
|
|
Comm
|
|
|
IPC
|
|
|
Status Local Remote Network
|
|
|
OK
|
|
|
Dormant
|
|
|
Paused
|
|
|
Disconnected
|
|
|
Error
|
|
|
Connecting
|
|
|
Reconnecting
|
|
|
Status
|
|
|
Local name
|
|
|
Remote name
|
|
|
Resource type
|
|
|
# Opens
|
|
|
# Connections
|
|
|
Unavailable
|
|
|
Share name Resource Remark
|
|
|
Share name
|
|
|
Resource
|
|
|
Spooled
|
|
|
Permission
|
|
|
Maximum users
|
|
|
No limit
|
|
|
Users
|
|
|
The share name entered may not be accessible from some MS-DOS workstations.
Are you sure you want to use this share name? ***:
|
|
|
Caching
|
|
|
ID Path User name # Locks
|
|
|
File ID
|
|
|
Locks
|
|
|
Permissions
|
|
|
Share name
|
|
|
Type
|
|
|
Used as
|
|
|
Comment
|
|
|
Computer User name Client Type Opens Idle time
|
|
|
Computer
|
|
|
Sess time
|
|
|
Idle time
|
|
|
Share name Type # Opens
|
|
|
Client type
|
|
|
Guest logon
|
|
|
Manual caching of documents
|
|
|
Automatic caching of documents
|
|
|
Automatic caching of programs and documents
|
|
|
Manual caching of documents with BranchCache enabled
|
|
|
Caching disabled
|
|
|
Automatic
|
|
|
Manual
|
|
|
Documents
|
|
|
Programs
|
|
|
Name
|
|
|
Forwarded to
|
|
|
Forwarded to you from
|
|
|
Users of this server
|
|
|
Net Send has been interrupted by a Ctrl+Break from the user.
|
|
|
Name Job # Size Status
|
|
|
jobs
|
|
|
Print
|
|
|
Name
|
|
|
Job #
|
|
|
Size
|
|
|
Status
|
|
|
Separator file
|
|
|
Comment
|
|
|
Priority
|
|
|
Print after
|
|
|
Print until
|
|
|
Print processor
|
|
|
Additional info
|
|
|
Parameters
|
|
|
Print Devices
|
|
|
Printer Active
|
|
|
Printer held
|
|
|
Printer error
|
|
|
Printer being deleted
|
|
|
Printer status unknown
|
|
|
Held until ***
|
|
|
Job #
|
|
|
Submitting user
|
|
|
Notify
|
|
|
Job data type
|
|
|
Job parameters
|
|
|
Waiting
|
|
|
Held in queue
|
|
|
Spooling
|
|
|
Paused
|
|
|
Offline
|
|
|
Error
|
|
|
Out of paper
|
|
|
Intervention required
|
|
|
Printing
|
|
|
on
|
|
|
Paused on ***
|
|
|
Offline on ***
|
|
|
Error on***
|
|
|
Out of Paper on ***
|
|
|
Check printer on ***
|
|
|
Printing on ***
|
|
|
Driver
|
|
|
User name Type Date
|
|
|
Lockout
|
|
|
Service
|
|
|
Server
|
|
|
Server started
|
|
|
Server paused
|
|
|
Server continued
|
|
|
Server stopped
|
|
|
Session
|
|
|
Logon Guest
|
|
|
Logon User
|
|
|
Logon Administrator
|
|
|
Logoff normal
|
|
|
Logon
|
|
|
Logoff error
|
|
|
Logoff auto-disconnect
|
|
|
Logoff administrator-disconnect
|
|
|
Logoff forced by logon restrictions
|
|
|
Service
|
|
|
*** Installed
|
|
|
*** Install Pending
|
|
|
*** Paused
|
|
|
*** Pause Pending
|
|
|
*** Continued
|
|
|
*** Continue Pending
|
|
|
*** Stopped
|
|
|
*** Stop Pending
|
|
|
Account
|
|
|
User account *** was modified.
|
|
|
Group account *** was modified.
|
|
|
User account *** was deleted
|
|
|
Group account *** was deleted
|
|
|
User account *** was added
|
|
|
Group account *** was added
|
|
|
Account system settings were modified
|
|
|
Logon restriction
|
|
|
Limit exceeded: UNKNOWN
|
|
|
Limit exceeded: Logon hours
|
|
|
Limit exceeded: Account expired
|
|
|
Limit exceeded: Workstation ID invalid
|
|
|
Limit exceeded: Account disabled
|
|
|
Limit exceeded: Account deleted
|
|
|
Share
|
|
|
Use ***
|
|
|
Unuse ***
|
|
|
User's session disconnected ***
|
|
|
Administrator stopped sharing resource ***
|
|
|
User reached limit for ***
|
|
|
Bad password
|
|
|
Administrator privilege required
|
|
|
Access
|
|
|
*** permissions added
|
|
|
*** permissions modified
|
|
|
*** permissions deleted
|
|
|
Access denied
|
|
|
Unknown
|
|
|
Other
|
|
|
Duration:
|
|
|
Duration: Not available
|
|
|
Duration: Less than one second
|
|
|
(none)
|
|
|
Closed ***
|
|
|
Closed *** (disconnected)
|
|
|
Administrator closed ***
|
|
|
Access ended
|
|
|
Log on to network
|
|
|
Logon denied
|
|
|
Program Message Time
|
|
|
Account locked due to *** bad passwords
|
|
|
Account unlocked by administrator
|
|
|
Log off network
|
|
|
The operation cannot be completed because other resources are dependent on this resource.
|
|
|
The cluster resource dependency cannot be found.
|
|
|
The cluster resource cannot be made dependent on the specified resource because it is already dependent.
|
|
|
The cluster resource is not online.
|
|
|
A cluster node is not available for this operation.
|
|
|
The cluster resource is not available.
|
|
|
The cluster resource could not be found.
|
|
|
The cluster is being shut down.
|
|
|
A cluster node cannot be evicted from the cluster unless the node is down or it is the last node.
|
|
|
The object already exists.
|
|
|
The object is already in the list.
|
|
|
The cluster group is not available for any new requests.
|
|
|
The cluster group could not be found.
|
|
|
The operation could not be completed because the cluster group is not online.
|
|
|
The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.
|
|
|
The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group.
|
|
|
The cluster resource could not be created in the specified resource monitor.
|
|
|
The cluster resource could not be brought online by the resource monitor.
|
|
|
The operation could not be completed because the cluster resource is online.
|
|
|
The cluster resource could not be deleted or brought offline because it is the quorum resource.
|
|
|
The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.
|
|
|
The cluster software is shutting down.
|
|
|
The group or resource is not in the correct state to perform the requested operation.
|
|
|
The properties were stored but not all changes will take effect until the next time the resource is brought online.
|
|
|
The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.
|
|
|
The cluster resource could not be deleted since it is a core resource.
|
|
|
The quorum resource failed to come online.
|
|
|
The quorum log could not be created or mounted successfully.
|
|
|
The cluster log is corrupt.
|
|
|
The record could not be written to the cluster log since it exceeds the maximum size.
|
|
|
The cluster log exceeds its maximum size.
|
|
|
No checkpoint record was found in the cluster log.
|
|
|
The minimum required disk space needed for logging is not available.
|
|
|
The cluster node failed to take control of the quorum resource because the resource is owned by another active node.
|
|
|
A cluster network is not available for this operation.
|
|
|
A cluster node is not available for this operation.
|
|
|
All cluster nodes must be running to perform this operation.
|
|
|
A cluster resource failed.
|
|
|
The cluster node is not valid.
|
|
|
The cluster node already exists.
|
|
|
A node is in the process of joining the cluster.
|
|
|
The cluster node was not found.
|
|
|
The cluster local node information was not found.
|
|
|
The cluster network already exists.
|
|
|
The cluster network was not found.
|
|
|
The cluster network interface already exists.
|
|
|
The cluster network interface was not found.
|
|
|
The cluster request is not valid for this object.
|
|
|
The cluster network provider is not valid.
|
|
|
The cluster node is down.
|
|
|
The cluster node is not reachable.
|
|
|
The cluster node is not a member of the cluster.
|
|
|
A cluster join operation is not in progress.
|
|
|
The cluster network is not valid.
|
|
|
Mar
|
|
|
The cluster node is up.
|
|
|
The cluster IP address is already in use.
|
|
|
The cluster node is not paused.
|
|
|
No cluster security context is available.
|
|
|
The cluster network is not configured for internal cluster communication.
|
|
|
The cluster node is already up.
|
|
|
The cluster node is already down.
|
|
|
The cluster network is already online.
|
|
|
The cluster network is already offline.
|
|
|
The cluster node is already a member of the cluster.
|
|
|
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.
|
|
|
One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
|
|
|
This operation cannot currently be performed on the cluster group containing the quorum resource.
|
|
|
The cluster quorum resource is not allowed to have any dependencies.
|
|
|
The cluster node is paused.
|
|
|
The cluster resource cannot be brought online. The owner node cannot run this resource.
|
|
|
The cluster node is not ready to perform the requested operation.
|
|
|
The cluster node is shutting down.
|
|
|
The cluster join operation was aborted.
|
|
|
The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet.
|
|
|
This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.
|
|
|
The system configuration changed during the cluster join or form operation. The join or form operation was aborted.
|
|
|
The specified resource type was not found.
|
|
|
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.
|
|
|
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.
|
|
|
No authentication package could be registered with the RPC server.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
A non locker code got a request to reserve the lock for making global updates.
|
|
|
The quorum disk could not be located by the cluster service.
|
|
|
The backed up cluster database is possibly corrupt.
|
|
|
A DFS root already exists in this cluster node.
|
|
|
An attempt to modify a resource property failed because it conflicts with another existing property.
|
|
|
This operation is not supported on a cluster without an Administrator Access Point.
|
|
|
Denmark
|
|
|
Sweden
|
|
|
Norway
|
|
|
Germany
|
|
|
Australia
|
|
|
Japan
|
|
|
Korea
|
|
|
China (PRC)
|
|
|
Taiwan
|
|
|
Asia
|
|
|
Portugal
|
|
|
Finland
|
|
|
Arabic
|
|
|
Hebrew
|
|
|
A power failure has occurred at ***. Please terminate all activity with this server.
|
|
|
Power has been restored at ***. Normal operations have resumed.
|
|
|
The UPS service is starting shut down at ***.
|
|
|
The UPS service is about to perform final shut down.
|
|
|
The Workstation must be started with the NET START command.
|
|
|
Remote IPC
|
|
|
Remote Admin
|
|
|
Default share
|
|
|
The password entered is longer than 14 characters. Computers
with Windows prior to Windows 2000 will not be able to use
this account. Do you want to continue this operation? ***:
|
|
|
*** has a remembered connection to ***. Do you
want to overwrite the remembered connection? ***:
|
|
|
Do you want to resume loading the profile? The command which
caused the error will be ignored. ***:
|
|
|
Do you want to continue this operation? ***:
|
|
|
Do you want to add this? ***:
|
|
|
Do you want to continue this operation? ***:
|
|
|
Is it OK to start it? ***:
|
|
|
Do you want to start the Workstation service? ***:
|
|
|
Is it OK to continue disconnecting and force them closed? ***:
|
|
|
The printer does not exist. Do you want to create it? ***:
|
|
|
Never
|
|
|
Never
|
|
|
Never
|
|
|
NET.HLP
|
|
|
NET.HLP
|
|
|
The network control block (NCB) request completed successfully. The NCB is the data.
|
|
|
Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS. The NCB is the data.
|
|
|
The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the data.
|
|
|
The command specified in the network control block (NCB) is illegal. The NCB is the data.
|
|
|
The message correlator specified in the network control block (NCB) is invalid. The NCB is the data.
|
|
|
A network control block (NCB) command timed-out. The session may have terminated abnormally. The NCB is the data.
|
|
|
An incomplete network control block (NCB) message was received. The NCB is the data.
|
|
|
The buffer address specified in the network control block (NCB) is illegal. The NCB is the data.
|
|
|
The session number specified in the network control block (NCB) is not active. The NCB is the data.
|
|
|
No resource was available in the network adapter. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
The session specified in the network control block (NCB) was closed. The NCB is the data.
|
|
|
The network control block (NCB) command was canceled. The NCB is the data.
|
|
|
The message segment specified in the network control block (NCB) is illogical. The NCB is the data.
|
|
|
The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
The network adapter name table is full. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
The network name has active sessions and is now de-registered. The network control block (NCB) command completed. The NCB is the data.
|
|
|
A previously issued Receive Lookahead command is active for this session. The network control block (NCB) command was rejected. The NCB is the data.
|
|
|
The local session table is full. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the data.
|
|
|
The name number specified in the network control block (NCB) is illegal. The NCB is the data.
|
|
|
The call name specified in the network control block (NCB) cannot be found or did not answer. The NCB is the data.
|
|
|
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.
|
|
|
The name specified in the network control block (NCB) is in use on a remote adapter. The NCB is the data.
|
|
|
The name specified in the network control block (NCB) has been deleted. The NCB is the data.
|
|
|
The session specified in the network control block (NCB) ended abnormally. The NCB is the data.
|
|
|
The network protocol has detected two or more identical names on the network. The network control block (NCB) is the data.
|
|
|
An unexpected protocol packet was received. There may be an incompatible remote device. The network control block (NCB) is the data.
|
|
|
The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
There are too many network control block (NCB) commands outstanding. The NCB request was refused. The NCB is the data.
|
|
|
The adapter number specified in the network control block (NCB) is illegal. The NCB is the data.
|
|
|
The network control block (NCB) command completed while a cancel was occurring. The NCB is the data.
|
|
|
The name specified in the network control block (NCB) is reserved. The NCB is the data.
|
|
|
The network control block (NCB) command is not valid to cancel. The NCB is the data.
|
|
|
There are multiple network control block (NCB) requests for the same session. The NCB request was refused. The NCB is the data.
|
|
|
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.
|
|
|
The maximum number of applications was exceeded. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
The requested resources are not available. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
A system error has occurred. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
A ROM checksum failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
A RAM test failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
A digital loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
An analog loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
An interface failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
An unrecognized network control block (NCB) return code was received. The NCB is the data.
|
|
|
A network adapter malfunction has occurred. The network control block (NCB) request was refused. The NCB is the data.
|
|
|
The network control block (NCB) command is still pending. The NCB is the data.
|
|
|
The update log on *** is over 80% capacity. The primary
domain controller *** is not retrieving the updates.
|
|
|
The update log on *** is full, and no further updates
can be added until the primary domain controller ***
retrieves the updates.
|
|
|
The time difference with the primary domain controller ***
exceeds the maximum allowed skew of *** seconds.
|
|
|
The account of user *** has been locked out on ***
due to *** bad password attempts.
|
|
|
The *** log file cannot be opened.
|
|
|
The *** log file is corrupted and will be cleared.
|
|
|
The Application log file could not be opened. *** will be used as the
default log file.
|
|
|
The *** Log is full. If this is the first time you have seen this
message take the following steps:
Start, Settings, Control Panel, Administrative Tools, Event Viewer
Select *** Log, from the action menu choose Clear All Events, choose not
to save.
If this dialog persists, contact your helpdesk/system administrator.
|
|
|
The security database full synchronization has been initiated by the server ***.
|
|
|
Windows could not be started as configured. A previous working configuration was used instead.
|
|
|
The exception 0x*** occurred in the application *** at location 0x***.
|
|
|
The servers *** and *** both claim to be an NT Domain Controller for
the *** domain. One of the servers should be removed from the
domain because the servers have different security identifiers
(SID).
|
|
|
The server *** and *** both claim to be the primary domain
controller for the *** domain. One of the servers should be
demoted or removed from the domain.
|
|
|
The computer *** tried to connect to the server *** using
the trust relationship established by the *** domain. However, the
computer lost the correct security identifier (SID)
when the domain was reconfigured. Reestablish the trust
relationship.
|
|
|
The computer has rebooted from a bugcheck. The bugcheck was:
***.
***
A full dump was not saved.
|
|
|
The computer has rebooted from a bugcheck. The bugcheck was:
***.
***
A dump was saved in: ***.
|
|
|
The computer or domain *** trusts domain ***. (This may be an indirect
trust.) However, *** and *** have the same machine security identifier
(SID). NT should be re-installed on either *** or ***.
|
|
|
The computer or domain *** trusts domain ***. (This may be an indirect
trust.) However, *** is not a valid name for a trusted domain.
The name of the trusted domain should be changed to a valid name.
|
|
|
Could not share the User or Script path.
|
|
|
The password for this computer is not found in the local security database.
|
|
|
An internal error occurred while accessing the computer's local or network security database.
|
|
|
The Netlogon service could not initialize the replication data
structures successfully. The service was terminated. The following
error occurred:
***
|
|
|
The Netlogon service failed to update the domain trust list. The
following error occurred:
***
|
|
|
The Netlogon service could not add the RPC interface. The
service was terminated. The following error occurred:
***
|
|
|
The Netlogon service could not read a mailslot message from *** due
to the following error:
***
|
|
|
The Netlogon service failed to register the service with the
service controller. The service was terminated. The following
error occurred:
***
|
|
|
The change log cache maintained by the Netlogon service for
database changes is corrupted. The Netlogon service is resetting
the change log.
|
|
|
The Netlogon service could not create server share ***. The following
error occurred:
***
|
|
|
The down-level logon request for the user *** from *** failed.
|
|
|
The down-level logoff request for the user *** from *** failed.
|
|
|
The Windows NT or Windows 2000 *** logon request for the user ***\*** from *** (via ***)
failed.
|
|
|
The Windows NT or Windows 2000 *** logoff request for the user ***\*** from ***
failed.
|
|
|
The partial synchronization request from the server *** completed
successfully. *** changes(s) has(have) been returned to the
caller.
|
|
|
The partial synchronization request from the server *** failed with
the following error:
***
|
|
|
The full synchronization request from the server *** completed
successfully. *** object(s) has(have) been returned to
the caller.
|
|
|
The full synchronization request from the server *** failed with
the following error:
***
|
|
|
The partial synchronization replication of the *** database from the
primary domain controller *** completed successfully. *** change(s) is(are)
applied to the database.
|
|
|
The partial synchronization replication of the *** database from the
primary domain controller *** failed with the following error:
***
|
|
|
The full synchronization replication of the *** database from the
primary domain controller *** completed successfully.
|
|
|
The full synchronization replication of the *** database from the
primary domain controller *** failed with the following error:
***
|
|
|
No Domain Controller is available for domain *** due to the following:
***.
Make sure that the computer is connected to the network and try
again. If the problem persists, please contact your domain administrator.
|
|
|
The session setup to the Windows NT or Windows 2000 Domain Controller *** for the domain ***
failed because the computer *** does not have a local security database account.
|
|
|
The session setup to the Windows NT or Windows 2000 Domain Controller *** for the domain ***
failed because the Domain Controller does not have an account
for the computer ***.
|
|
|
The session setup from the computer *** failed to authenticate.
The name(s) of the account(s) referenced in the security database is
***. The following error occurred:
***
|
|
|
The session setup from the computer *** failed because there is
no trust account in the security database for this computer. The name of
the account referenced in the security database is ***.
|
|
|
Could not register control handler with service controller ***.
|
|
|
Could not set service status with service controller ***.
|
|
|
Could not find the computer name ***.
|
|
|
Could not load *** device driver.
|
|
|
Could not load any transport.
|
|
|
Replication of the *** Domain Object "***" from primary domain controller
*** failed with the following error:
***
|
|
|
Replication of the *** Global Group "***" from primary domain controller
*** failed with the following error:
***
|
|
|
Replication of the *** Local Group "***" from primary domain controller
*** failed with the following error:
***
|
|
|
Replication of the *** User "***" from primary domain controller
*** failed with the following error:
***
|
|
|
Replication of the *** Policy Object "***" from primary domain controller
*** failed with the following error:
***
|
|
|
Replication of the *** Trusted Domain Object "***" from primary domain controller
*** failed with the following error:
***
|
|
|
Replication of the *** Account Object "***" from primary domain controller
*** failed with the following error:
***
|
|
|
Replication of the *** Secret "***" from primary domain controller
*** failed with the following error:
***
|
|
|
The system returned the following unexpected error code:
***
|
|
|
Netlogon has detected two machine accounts for server "***".
The server can be either a Windows 2000 Server that is a member of the
domain or the server can be a LAN Manager server with an account in the
SERVERS global group. It cannot be both.
|
|
|
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.
|
|
|
The Browser driver returned the following error to Netlogon:
***
|
|
|
Netlogon could not register the ***<1B> name for the following reason:
***
|
|
|
Service failed to retrieve messages needed to boot remote boot clients.
|
|
|
Service experienced a severe error and can no longer provide remote boot for 3Com 3Start remote boot clients.
|
|
|
Service experienced a severe system error and will shut itself down.
|
|
|
Client with computer name *** failed to acknowledge receipt of the
boot data. Remote boot of this client was not completed.
|
|
|
Client with computer name *** was not booted due to an error in opening
file ***.
|
|
|
Client with computer name *** was not booted due to an error in reading
file ***.
|
|
|
Client with computer name *** was not booted due to insufficient memory
at the remote boot server.
|
|
|
Client with computer name *** will be booted without using checksums
because checksum for file *** could not be calculated.
|
|
|
Client with computer name *** was not booted due to too many lines in
file ***.
|
|
|
Client with computer name *** was not booted because the boot block
configuration file *** for this client does not contain boot block
line and/or loader line.
|
|
|
Client with computer name *** was not booted due to a bad size of
file ***.
|
|
|
Client with computer name *** was not booted due to remote boot
service internal error.
|
|
|
Client with computer name *** was not booted because file *** has an
invalid boot header.
|
|
|
Client with computer name *** was not booted due to network error.
|
|
|
Client with adapter id *** was not booted due to lack of resources.
|
|
|
Service experienced error copying file or directory ***.
|
|
|
Service experienced error deleting file or directory ***.
|
|
|
Service experienced error setting permissions on file or directory ***.
|
|
|
Service experienced error evaluating RPL configurations.
|
|
|
Service experienced error creating RPL profiles for all configurations.
|
|
|
Service experienced error accessing registry.
|
|
|
Service experienced error replacing possibly outdated RPLDISK.SYS.
|
|
|
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.
|
|
|
Service failed to back up its database.
|
|
|
Service failed to initialize from its database. The database may be missing or corrupted. Service will attempt restoring the database from the backup.
|
|
|
Service failed to restore its database from the backup. Service will not start.
|
|
|
Service successfully restored its database from the backup.
|
|
|
Service failed to initialize from its restored database. Service will not start.
|
|
|
The session setup to the Windows NT or Windows 2000 Domain Controller *** from computer
*** using account *** failed. *** is declared to be a BDC in domain ***.
However, *** tried to connect as either a DC in a trusted domain,
a member workstation in domain ***, or as a server in domain ***.
Use the Active Directory Users and Computers tool or Server Manager to remove the BDC account for ***.
|
|
|
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.
|
|
|
Global group SERVERS exists in domain *** and has members.
This group defines Lan Manager BDCs in the domain.
Lan Manager BDCs are not permitted in NT domains.
|
|
|
The DNS server (with IP address ***) 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. The DNS server
returned an error code given in the Data field.
|
|
|
Registration of the DNS record '***' failed on the DNS server (with IP address ***)
with the following error:
***
The DNS server returned an error code given in the Data field.
|
|
|
Deregistration of the DNS record '***' failed on the DNS server (with IP address ***)
with the following error:
***
The DNS server returned an error code given in the Data field.
Although this is not a critical error as it doesn't prevent normal behavior of
the Domain Controller, we strongly recommend to ensure the deletion of the record
from DNS to prevent unnecessary connections to this computer.
|
|
|
Failed to create/open file *** with the following error:
***
|
|
|
Netlogon got the following error while trying to get the subnet to site
mapping information from the DS:
***
|
|
|
'***' tried to determine its site by looking up its IP address ('***')
in the Configuration\Sites\Subnets container in the DS. No subnet matched
the IP address. Consider adding a subnet object for this IP address.
|
|
|
The site name for this computer is '***'. That site name is not a valid
site name. A site name must be a valid DNS label.
Rename the site to be a valid name.
|
|
|
The subnet object '***' appears in the Configuration\Sites\Subnets
container in the DS. The name is not syntactically valid. The valid
syntax is xx.xx.xx.xx/yy where xx.xx.xx.xx is a valid IP subnet number
and yy is the number of bits in the subnet mask.
Correct the name of the subnet object.
|
|
|
Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.
|
|
|
Dynamic registration or deregistration of one or more DNS records failed with the following error:
***
|
|
|
The session setup to the Windows NT or Windows 2000 Domain Controller *** for the domain ***
is not responsive. The current RPC call from Netlogon on \\*** to *** has been cancelled.
|
|
|
Site '***' does not have any Domain Controllers for domain '***'.
Domain Controllers in site '***' have been automatically
selected to cover site '***' for domain '***' based on configured
Directory Server replication costs.
|
|
|
This Domain Controller no longer automatically covers site '***' for domain '***'.
|
|
|
Site '***' does not have any Global Catalog servers for forest '***'.
Global Catalog servers in site '***' have been automatically
selected to cover site '***' for forest '***' based on configured
Directory Server replication costs.
|
|
|
This Global Catalog server no longer automatically covers site '***' for forest '***'.
|
|
|
Attempt to update HOST Service Principal Names (SPNs) of the computer
object in Active Directory failed. The updated values were '***' and '***'.
The following error occurred:
***
|
|
|
Attempt to update DNS Host Name of the computer object
in Active Directory failed. The updated value was '***'.
The following error occurred:
***
|
|
|
No suitable Domain Controller is available for domain ***.
An NT4 or older domain controller is available but it cannot
be used for authentication purposes in the Windows 2000 or newer
domain that this computer is a member of.
The following error occurred:
***
|
|
|
The domain of this computer, *** has been downgraded from Windows 2000
or newer to Windows NT4 or older. The computer cannot function properly
in this case for authentication purposes. This computer needs to rejoin
the domain.
The following error occurred:
***
|
|
|
Site '***' does not have any LDAP servers for non-domain NC '***'.
LDAP servers in site '***' have been automatically selected to
cover site '***' for non-domain NC '***' based on configured
Directory Server replication costs.
|
|
|
This LDAP server no longer automatically covers site '***' for non-domain NC '***'.
|
|
|
Site '***' is no longer manually configured in the registry as
covered by this Domain Controller for domain '***'. As a result,
site '***' does not have any Domain Controllers for domain '***'.
Domain Controllers in site '***' have been automatically
selected to cover site '***' for domain '***' based on configured
Directory Server replication costs.
|
|
|
This Domain Controller no longer automatically covers site '***' for domain '***'.
However, site '***' is still (manually) covered by this Domain Controller for
domain '***' since this site has been manually configured in the registry.
|
|
|
Site '***' is no longer manually configured in the registry as
covered by this Global Catalog server for forest '***'. As a result,
site '***' does not have any Global Catalog servers for forest '***'.
Global Catalog servers in site '***' have been automatically
selected to cover site '***' for forest '***' based on configured
Directory Server replication costs.
|
|
|
This Global Catalog server no longer automatically covers site '***' for forest '***'.
However, site '***' is still (manually) covered by this Global catalog for
forest '***' since this site has been manually configured in the registry.
|
|
|
Site '***' is no longer manually configured in the registry as
covered by this LDAP server for non-domain NC '***'. As a result,
site '***' does not have any LDAP servers for non-domain NC '***'.
LDAP servers in site '***' have been automatically
selected to cover site '***' for non-domain NC '***' based on
configured Directory Server replication costs.
|
|
|
This LDAP server no longer automatically covers site '***' for non-domain NC '***'.
However, site '***' is still (manually) covered by this LDAP server for
non-domain NC '***' since this site has been manually configured in the registry.
|
|
|
Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes
of the computer object in Active Directory failed because the Domain Controller
'***' had more than one account with the name '***' corresponding to this computer.
Not having SPNs registered may result in authentication failures for this computer.
Contact your domain administrator who may need to manually resolve the account name
collision.
|
|
|
Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes
of the computer object in Active Directory failed because this computer account
name, '***' could not be mapped to the computer object on Domain Controller '***'.
Not having SPNs registered may result in authentication failures for this computer.
Contact your domain administrator. The following technical information may be
useful for the resolution of this failure:
DsCrackNames status = 0x***, crack error = 0x***.
|
|
|
None of the IP addresses (***) of this Domain Controller map to the configured site '***'.
While this may be a temporary situation due to IP address changes, it is generally
recommended that the IP address of the Domain Controller (accessible to machines in
its domain) maps to the Site which it services. If the above list of IP addresses is
stable, consider moving this server to a site (or create one if it does not already
exist) such that the above IP address maps to the selected site. This may require the
creation of a new subnet object (whose range includes the above IP address) which maps
to the selected site object.
|
|
|
The following error occurred while reading a parameter '***' in the
Netlogon *** registry section:
***
|
|
|
The Netlogon *** registry key contains an invalid value 0x*** for parameter '***'.
The minimum and maximum values allowed for this parameter are 0x*** and 0x***, respectively.
The value of 0x*** has been assigned to this parameter.
|
|
|
The session setup from the computer *** failed to authenticate.
The following error occurred:
***
|
|
|
An operation was attempted that is incompatible with the current membership state of the node.
|
|
|
The quorum resource does not contain the quorum log.
|
|
|
The membership engine requested shutdown of the cluster service on this node.
|
|
|
The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.
|
|
|
A matching cluster network for the specified IP address could not be found.
|
|
|
The actual data type of the property did not match the expected data type of the property.
|
|
|
The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer.
|
|
|
Two or more parameter values specified for a resource's properties are in conflict.
|
|
|
This computer cannot be made a member of a cluster.
|
|
|
This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.
|
|
|
A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster.
|
|
|
The specified file could not be encrypted.
|
|
|
The specified file could not be decrypted.
|
|
|
The specified file is encrypted and the user does not have the ability to decrypt it.
|
|
|
There is no valid encryption recovery policy configured for this system.
|
|
|
The required encryption driver is not loaded for this system.
|
|
|
The file was encrypted with a different encryption driver than is currently loaded.
|
|
|
There are no EFS keys defined for the user.
|
|
|
The specified file is not encrypted.
|
|
|
The specified file is not in the defined EFS export format.
|
|
|
The specified file is read only.
|
|
|
The directory has been disabled for encryption.
|
|
|
The server is not trusted for remote encryption operation.
|
|
|
Recovery policy configured for this system contains invalid recovery certificate.
|
|
|
The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file.
|
|
|
The disk partition does not support file encryption.
|
|
|
This machine is disabled for file encryption.
|
|
|
A newer system is required to decrypt this encrypted file.
|
|
|
The list of servers for this workgroup is not currently available
|
|
|
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.
|
|
|
The specified session name is invalid.
|
|
|
The specified protocol driver is invalid.
|
|
|
The specified protocol driver was not found in the system path.
|
|
|
The specified terminal connection driver was not found in the system path.
|
|
|
A registry key for event logging could not be created for this session.
|
|
|
A service with the same name already exists on the system.
|
|
|
A close operation is pending on the session.
|
|
|
There are no free output buffers available.
|
|
|
The MODEM.INF file was not found.
|
|
|
The modem name was not found in MODEM.INF.
|
|
|
The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.
|
|
|
The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.
|
|
|
Carrier detect has failed or carrier has been dropped due to disconnect.
|
|
|
Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.
|
|
|
Busy signal detected at remote site on callback.
|
|
|
Voice detected at remote site on callback.
|
|
|
Transport driver error
|
|
|
The specified session cannot be found.
|
|
|
The specified session name is already in use.
|
|
|
The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.
|
|
|
An attempt has been made to connect to a session whose video mode is not supported by the current client.
|
|
|
The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.
|
|
|
Your interactive logon privilege has been disabled. Please contact your administrator.
|
|
|
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.
|
|
|
The client failed to respond to the server connect message.
|
|
|
Disconnecting the console session is not supported.
|
|
|
Reconnecting a disconnected session to the console is not supported.
|
|
|
The request to control another session remotely was denied.
|
|
|
The requested session access is denied.
|
|
|
The specified terminal connection driver is invalid.
|
|
|
The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on.
|
|
|
The requested session is not configured to allow remote control.
|
|
|
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 unique license number.
|
|
|
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 contact your system administrator.
|
|
|
The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.
|
|
|
The client you are using is not licensed to use this system. Your logon request is denied.
|
|
|
The system license has expired. Your logon request is denied.
|
|
|
Remote control could not be terminated because the specified session is not currently being remotely controlled.
|
|
|
The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported.
|
|
|
The file replication service API was called incorrectly.
|
|
|
The file replication service cannot be started.
|
|
|
The file replication service cannot be stopped.
|
|
|
The file replication service API terminated the request. The event log may have more information.
|
|
|
The file replication service terminated the request. The event log may have more information.
|
|
|
The file replication service cannot be contacted. The event log may have more information.
|
|
|
The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information.
|
|
|
The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.
|
|
|
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.
|
|
|
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.
|
|
|
The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information.
|
|
|
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.
|
|
|
The file replication service cannot populate the system volume because of an internal error. The event log may have more information.
|
|
|
The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information.
|
|
|
The file replication service cannot process the request. The system volume is busy with a previous request.
|
|
|
The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information.
|
|
|
The file replication service detected an invalid parameter.
|
|
|
An error occurred while installing the directory service. For more information, see the event log.
|
|
|
The directory service evaluated group memberships locally.
|
|
|
The specified directory service attribute or value does not exist.
|
|
|
The attribute syntax specified to the directory service is invalid.
|
|
|
The attribute type specified to the directory service is not defined.
|
|
|
The specified directory service attribute or value already exists.
|
|
|
The directory service is busy.
|
|
|
The directory service is unavailable.
|
|
|
The directory service was unable to allocate a relative identifier.
|
|
|
The directory service has exhausted the pool of relative identifiers.
|
|
|
The requested operation could not be performed because the directory service is not the master for that type of operation.
|
|
|
The directory service was unable to initialize the subsystem that allocates relative identifiers.
|
|
|
The requested operation did not satisfy one or more constraints associated with the class of the object.
|
|
|
The directory service can perform the requested operation only on a leaf object.
|
|
|
The directory service cannot perform the requested operation on the RDN attribute of an object.
|
|
|
The directory service detected an attempt to modify the object class of an object.
|
|
|
The requested cross-domain move operation could not be performed.
|
|
|
Unable to contact the global catalog server.
|
|
|
The policy object is shared and can only be modified at the root.
|
|
|
The policy object does not exist.
|
|
|
The requested policy information is only in the directory service.
|
|
|
A domain controller promotion is currently active.
|
|
|
A domain controller promotion is not currently active
|
|
|
An operations error occurred.
|
|
|
A protocol error occurred.
|
|
|
The time limit for this request was exceeded.
|
|
|
The size limit for this request was exceeded.
|
|
|
The administrative limit for this request was exceeded.
|
|
|
The compare response was false.
|
|
|
The compare response was true.
|
|
|
The requested authentication method is not supported by the server.
|
|
|
A more secure authentication method is required for this server.
|
|
|
Inappropriate authentication.
|
|
|
The authentication mechanism is unknown.
|
|
|
A referral was returned from the server.
|
|
|
The server does not support the requested critical extension.
|
|
|
This request requires a secure connection.
|
|
|
Inappropriate matching.
|
|
|
A constraint violation occurred.
|
|
|
There is no such object on the server.
|
|
|
There is an alias problem.
|
|
|
An invalid dn syntax has been specified.
|
|
|
The object is a leaf object.
|
|
|
There is an alias dereferencing problem.
|
|
|
The server is unwilling to process the request.
|
|
|
A loop has been detected.
|
|
|
There is a naming violation.
|
|
|
The result set is too large.
|
|
|
The operation affects multiple DSAs
|
|
|
The server is not operational.
|
|
|
A local error has occurred.
|
|
|
An encoding error has occurred.
|
|
|
A decoding error has occurred.
|
|
|
The search filter cannot be recognized.
|
|
|
One or more parameters are illegal.
|
|
|
The specified method is not supported.
|
|
|
No results were returned.
|
|
|
The specified control is not supported by the server.
|
|
|
A referral loop was detected by the client.
|
|
|
The preset referral limit was exceeded.
|
|
|
The search requires a SORT control.
|
|
|
The search results exceed the offset range specified.
|
|
|
The root object must be the head of a naming context. The root object cannot have an instantiated parent.
|
|
|
The add replica operation cannot be performed. The naming context must be writeable in order to create the replica.
|
|
|
A reference to an attribute that is not defined in the schema occurred.
|
|
|
The maximum size of an object has been exceeded.
|
|
|
An attempt was made to add an object to the directory with a name that is already in use.
|
|
|
An attempt was made to add an object of a class that does not have an RDN defined in the schema.
|
|
|
An attempt was made to add an object using an RDN that is not the RDN defined in the schema.
|
|
|
None of the requested attributes were found on the objects.
|
|
|
The user buffer is too small.
|
|
|
The attribute specified in the operation is not present on the object.
|
|
|
Illegal modify operation. Some aspect of the modification is not permitted.
|
|
|
The specified object is too large.
|
|
|
The specified instance type is not valid.
|
|
|
The operation must be performed at a master DSA.
|
|
|
The object class attribute must be specified.
|
|
|
A required attribute is missing.
|
|
|
An attempt was made to modify an object to include an attribute that is not legal for its class.
|
|
|
The specified attribute is already present on the object.
|
|
|
The specified attribute is not present, or has no values.
|
|
|
Multiple values were specified for an attribute that can have only one value.
|
|
|
A value for the attribute was not in the acceptable range of values.
|
|
|
The specified value already exists.
|
|
|
The attribute cannot be removed because it is not present on the object.
|
|
|
The attribute value cannot be removed because it is not present on the object.
|
|
|
The specified root object cannot be a subref.
|
|
|
Chaining is not permitted.
|
|
|
Chained evaluation is not permitted.
|
|
|
The operation could not be performed because the object's parent is either uninstantiated or deleted.
|
|
|
Having a parent that is an alias is not permitted. Aliases are leaf objects.
|
|
|
The object and parent must be of the same type, either both masters or both replicas.
|
|
|
The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object.
|
|
|
Directory object not found.
|
|
|
The aliased object is missing.
|
|
|
The object name has bad syntax.
|
|
|
It is not permitted for an alias to refer to another alias.
|
|
|
The alias cannot be dereferenced.
|
|
|
The operation is out of scope.
|
|
|
The operation cannot continue because the object is in the process of being removed.
|
|
|
The DSA object cannot be deleted.
|
|
|
A directory service error has occurred.
|
|
|
The operation can only be performed on an internal master DSA object.
|
|
|
The object must be of class DSA.
|
|
|
Insufficient access rights to perform the operation.
|
|
|
The object cannot be added because the parent is not on the list of possible superiors.
|
|
|
Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM).
|
|
|
The name has too many parts.
|
|
|
The name is too long.
|
|
|
The name value is too long.
|
|
|
The directory service encountered an error parsing a name.
|
|
|
The directory service cannot get the attribute type for a name.
|
|
|
The name does not identify an object; the name identifies a phantom.
|
|
|
The security descriptor is too short.
|
|
|
The security descriptor is invalid.
|
|
|
Failed to create name for deleted object.
|
|
|
The parent of a new subref must exist.
|
|
|
The object must be a naming context.
|
|
|
It is not permitted to add an attribute which is owned by the system.
|
|
|
The class of the object must be structural; you cannot instantiate an abstract class.
|
|
|
The schema object could not be found.
|
|
|
A local object with this GUID (dead or alive) already exists.
|
|
|
The operation cannot be performed on a back link.
|
|
|
The cross reference for the specified naming context could not be found.
|
|
|
The operation could not be performed because the directory service is shutting down.
|
|
|
The directory service request is invalid.
|
|
|
The role owner attribute could not be read.
|
|
|
The requested FSMO operation failed. The current FSMO holder could not be contacted.
|
|
|
Modification of a DN across a naming context is not permitted.
|
|
|
The attribute cannot be modified because it is owned by the system.
|
|
|
Only the replicator can perform this function.
|
|
|
The specified class is not defined.
|
|
|
The specified class is not a subclass.
|
|
|
The name reference is invalid.
|
|
|
A cross reference already exists.
|
|
|
It is not permitted to delete a master cross reference.
|
|
|
Subtree notifications are only supported on NC heads.
|
|
|
Notification filter is too complex.
|
|
|
Schema update failed: duplicate RDN.
|
|
|
Schema update failed: duplicate OID.
|
|
|
Schema update failed: duplicate MAPI identifier.
|
|
|
Schema update failed: duplicate schema-id GUID.
|
|
|
Schema update failed: duplicate LDAP display name.
|
|
|
Schema update failed: range-lower less than range upper.
|
|
|
Schema update failed: syntax mismatch.
|
|
|
Schema deletion failed: attribute is used in must-contain.
|
|
|
Schema deletion failed: attribute is used in may-contain.
|
|
|
Schema update failed: attribute in may-contain does not exist.
|
|
|
Schema update failed: attribute in must-contain does not exist.
|
|
|
Schema update failed: class in aux-class list does not exist or is not an auxiliary class.
|
|
|
Schema update failed: class in poss-superiors does not exist.
|
|
|
Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules.
|
|
|
Schema update failed: Rdn-Att-Id has wrong syntax.
|
|
|
Schema deletion failed: class is used as auxiliary class.
|
|
|
Schema deletion failed: class is used as sub class.
|
|
|
Schema deletion failed: class is used as poss superior.
|
|
|
Schema update failed in recalculating validation cache.
|
|
|
The tree deletion is not finished. The request must be made again to continue deleting the tree.
|
|
|
The requested delete operation could not be performed.
|
|
|
Cannot read the governs class identifier for the schema record.
|
|
|
The attribute schema has bad syntax.
|
|
|
The attribute could not be cached.
|
|
|
The class could not be cached.
|
|
|
The attribute could not be removed from the cache.
|
|
|
The class could not be removed from the cache.
|
|
|
The distinguished name attribute could not be read.
|
|
|
No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest.
|
|
|
The instance type attribute could not be retrieved.
|
|
|
An internal error has occurred.
|
|
|
A database error has occurred.
|
|
|
The attribute GOVERNSID is missing.
|
|
|
An expected attribute is missing.
|
|
|
The specified naming context is missing a cross reference.
|
|
|
A security checking error has occurred.
|
|
|
The schema is not loaded.
|
|
|
Schema allocation failed. Please check if the machine is running low on memory.
|
|
|
Failed to obtain the required syntax for the attribute schema.
|
|
|
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.
|
|
|
The replication operation failed because of a schema mismatch between the servers involved.
|
|
|
The DSA object could not be found.
|
|
|
The naming context could not be found.
|
|
|
The naming context could not be found in the cache.
|
|
|
The child object could not be retrieved.
|
|
|
The modification was not permitted for security reasons.
|
|
|
The operation cannot replace the hidden record.
|
|
|
The hierarchy file is invalid.
|
|
|
The attempt to build the hierarchy table failed.
|
|
|
The directory configuration parameter is missing from the registry.
|
|
|
The attempt to count the address book indices failed.
|
|
|
The allocation of the hierarchy table failed.
|
|
|
The directory service encountered an internal failure.
|
|
|
The directory service encountered an unknown failure.
|
|
|
A root object requires a class of 'top'.
|
|
|
This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.
|
|
|
The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.
|
|
|
The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.
|
|
|
The replication operation failed.
|
|
|
An invalid parameter was specified for this replication operation.
|
|
|
The directory service is too busy to complete the replication operation at this time.
|
|
|
The distinguished name specified for this replication operation is invalid.
|
|
|
The naming context specified for this replication operation is invalid.
|
|
|
The distinguished name specified for this replication operation already exists.
|
|
|
The replication system encountered an internal error.
|
|
|
The replication operation encountered a database inconsistency.
|
|
|
The server specified for this replication operation could not be contacted.
|
|
|
The replication operation encountered an object with an invalid instance type.
|
|
|
The replication operation failed to allocate memory.
|
|
|
The replication operation encountered an error with the mail system.
|
|
|
The replication reference information for the target server already exists.
|
|
|
The replication reference information for the target server does not exist.
|
|
|
The naming context cannot be removed because it is replicated to another server.
|
|
|
The replication operation encountered a database error.
|
|
|
The naming context is in the process of being removed or is not replicated from the specified server.
|
|
|
Replication access was denied.
|
|
|
The requested operation is not supported by this version of the directory service.
|
|
|
The replication remote procedure call was cancelled.
|
|
|
The source server is currently rejecting replication requests.
|
|
|
The destination server is currently rejecting replication requests.
|
|
|
The replication operation failed due to a collision of object names.
|
|
|
The replication source has been reinstalled.
|
|
|
The replication operation failed because a required parent object is missing.
|
|
|
The replication operation was preempted.
|
|
|
The replication synchronization attempt was abandoned because of a lack of updates.
|
|
|
The replication operation was terminated because the system is shutting down.
|
|
|
Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set.
|
|
|
The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.
|
|
|
The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.
|
|
|
The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer.
|
|
|
Schema update failed: An attribute with the same link identifier already exists.
|
|
|
Name translation: Generic processing error.
|
|
|
Name translation: Could not find the name or insufficient right to see name.
|
|
|
Name translation: Input name mapped to more than one output name.
|
|
|
Name translation: Input name found, but not the associated output format.
|
|
|
Name translation: Unable to resolve completely, only the domain was found.
|
|
|
Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.
|
|
|
Modification of a constructed attribute is not allowed.
|
|
|
The OM-Object-Class specified is incorrect for an attribute with the specified syntax.
|
|
|
The replication request has been posted; waiting for reply.
|
|
|
The requested operation requires a directory service, and none was available.
|
|
|
The LDAP display name of the class or attribute contains non-ASCII characters.
|
|
|
The requested search operation is only supported for base searches.
|
|
|
The search failed to retrieve attributes from the database.
|
|
|
The schema update operation tried to add a backward link attribute that has no corresponding forward link.
|
|
|
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.
|
|
|
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.
|
|
|
Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.
|
|
|
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.
|
|
|
Destination of a cross-domain move is not authoritative for the destination naming context.
|
|
|
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.
|
|
|
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.
|
|
|
Another operation which requires exclusive access to the PDC FSMO is already in progress.
|
|
|
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.
|
|
|
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, e.g.: trust account or restricted RID, which prevent its move.
|
|
|
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.
|
|
|
A naming context head must be the immediate child of another naming context head, not of an interior node.
|
|
|
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 catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters)
|
|
|
Destination domain must be in native mode.
|
|
|
The operation cannot be performed because the server does not have an infrastructure container in the domain of interest.
|
|
|
Cross-domain move of non-empty account groups is not allowed.
|
|
|
Cross-domain move of non-empty resource groups is not allowed.
|
|
|
The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.
|
|
|
Tree deletions starting at an object which has an NC head as a descendant are not allowed.
|
|
|
The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.
|
|
|
The directory service failed to identify the list of objects to delete while attempting a tree deletion.
|
|
|
Only an administrator can modify the membership list of an administrative group.
|
|
|
Cannot change the primary group ID of a domain controller account.
|
|
|
An attempt is made to modify the base schema.
|
|
|
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 adding or deleting an auxiliary class) is not allowed.
|
|
|
Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.
|
|
|
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.
|
|
|
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.
|
|
|
The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.
|
|
|
The specified group type is invalid.
|
|
|
You cannot nest global groups in a mixed domain if the group is security-enabled.
|
|
|
You cannot nest local groups in a mixed domain if the group is security-enabled.
|
|
|
A global group cannot have a local group as a member.
|
|
|
A global group cannot have a universal group as a member.
|
|
|
A universal group cannot have a local group as a member.
|
|
|
A global group cannot have a cross-domain member.
|
|
|
A local group cannot have another cross domain local group as a member.
|
|
|
A group with primary members cannot change to a security-disabled group.
|
|
|
The schema cache load failed to convert the string default SD on a class-schema object.
|
|
|
Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)
|
|
|
The DSA operation is unable to proceed because of a DNS lookup failure.
|
|
|
While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.
|
|
|
The Security Descriptor attribute could not be read.
|
|
|
The object requested was not found, but an object with that key was found.
|
|
|
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
|
|
|
Security Account Manager needs to get the boot password.
|
|
|
Security Account Manager needs to get the boot key from floppy disk.
|
|
|
Directory Service cannot start.
|
|
|
Directory Services could not start.
|
|
|
The connection between client and server requires packet privacy or better.
|
|
|
The source domain may not be in the same forest as destination.
|
|
|
The destination domain must be in the forest.
|
|
|
The operation requires that destination domain auditing be enabled.
|
|
|
The operation couldn't locate a DC for the source domain.
|
|
|
The source object must be a group or user.
|
|
|
The source object's SID already exists in destination forest.
|
|
|
The source and destination object must be of the same type.
|
|
|
Schema information could not be included in the replication request.
|
|
|
The replication operation could not be completed due to a schema incompatibility.
|
|
|
The replication operation could not be completed due to a previous schema incompatibility.
|
|
|
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.
|
|
|
The requested domain could not be deleted because there exist domain controllers that still host this domain.
|
|
|
The requested operation can be performed only on a global catalog server.
|
|
|
A local group can only be a member of other local groups in the same domain.
|
|
|
Foreign security principals cannot be members of universal groups.
|
|
|
The attribute is not allowed to be replicated to the GC because of security reasons.
|
|
|
The checkpoint with the PDC could not be taken because there too many modifications being processed currently.
|
|
|
The operation requires that source domain auditing be enabled.
|
|
|
Security principal objects can only be created inside domain naming contexts.
|
|
|
A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.
|
|
|
A Filter was passed that uses constructed attributes.
|
|
|
The unicodePwd attribute value must be enclosed in double quotes.
|
|
|
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.
|
|
|
For security reasons, the operation must be run on the destination DC.
|
|
|
For security reasons, the source DC must be NT4SP4 or greater.
|
|
|
Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.
|
|
|
The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set.
|
|
|
The version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain.
|
|
|
The version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set.
|
|
|
The version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain.
|
|
|
The version of the operating system installed on this server is incompatible with the functional level of the domain or forest.
|
|
|
The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level.
|
|
|
The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level.
|
|
|
The sort order requested is not supported.
|
|
|
The requested name already exists as a unique identifier.
|
|
|
The machine account was created pre-NT4. The account needs to be recreated.
|
|
|
The database is out of version store.
|
|
|
Unable to continue operation because multiple conflicting controls were used.
|
|
|
Unable to find a valid security descriptor reference domain for this partition.
|
|
|
Schema update failed: The link identifier is reserved.
|
|
|
Schema update failed: There are no link identifiers available.
|
|
|
An account group cannot have a universal group as a member.
|
|
|
Rename or move operations on naming context heads or read-only objects are not allowed.
|
|
|
Move operations on objects in the schema naming context are not allowed.
|
|
|
A system flag has been set on the object and does not allow the object to be moved or renamed.
|
|
|
This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.
|
|
|
Unable to resolve completely, a referral to another forest is generated.
|
|
|
The requested action is not supported on standard server.
|
|
|
Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question.
|
|
|
The directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master.
|
|
|
The thread limit for this request was exceeded.
|
|
|
The Global catalog server is not in the closest site.
|
|
|
The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute.
|
|
|
The Directory Service failed to enter single user mode.
|
|
|
The Directory Service cannot parse the script because of a syntax error.
|
|
|
The Directory Service cannot process the script because of an error.
|
|
|
The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress).
|
|
|
The directory service binding must be renegotiated due to a change in the server extensions information.
|
|
|
Operation not allowed on a disabled cross ref.
|
|
|
Schema update failed: No values for msDS-IntId are available.
|
|
|
Schema update failed: Duplicate msDS-INtId. Retry the operation.
|
|
|
Schema deletion failed: attribute is used in rDNAttID.
|
|
|
The directory service failed to authorize the request.
|
|
|
The Directory Service cannot process the script because it is invalid.
|
|
|
The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data.
|
|
|
DNS server unable to interpret format.
|
|
|
DNS server failure.
|
|
|
DNS name does not exist.
|
|
|
DNS request not supported by name server.
|
|
|
DNS operation refused.
|
|
|
DNS name that ought not exist, does exist.
|
|
|
DNS RR set that ought not exist, does exist.
|
|
|
DNS RR set that ought to exist, does not exist.
|
|
|
DNS server not authoritative for zone.
|
|
|
DNS name in update or prereq is not in zone.
|
|
|
DNS signature failed to verify.
|
|
|
DNS bad key.
|
|
|
DNS signature validity expired.
|
|
|
No records found for given DNS query.
|
|
|
Bad DNS packet.
|
|
|
No DNS packet.
|
|
|
DNS error, check rcode.
|
|
|
Unsecured DNS packet.
|
|
|
Invalid DNS type.
|
|
|
Invalid IP address.
|
|
|
Invalid property.
|
|
|
Try DNS operation again later.
|
|
|
Record for given name and type is not unique.
|
|
|
DNS name does not comply with RFC specifications.
|
|
|
DNS name is a fully-qualified DNS name.
|
|
|
DNS name is dotted (multi-label).
|
|
|
DNS name is a single-part name.
|
|
|
DNS name contains an invalid character.
|
|
|
DNS name is entirely numeric.
|
|
|
The operation requested is not permitted on a DNS root server.
|
|
|
DNS zone does not exist.
|
|
|
DNS zone information not available.
|
|
|
Invalid operation for DNS zone.
|
|
|
Invalid DNS zone configuration.
|
|
|
DNS zone has no start of authority (SOA) record.
|
|
|
DNS zone has no Name Server (NS) record.
|
|
|
DNS zone is locked.
|
|
|
DNS zone creation failed.
|
|
|
DNS zone already exists.
|
|
|
DNS automatic zone already exists.
|
|
|
Invalid DNS zone type.
|
|
|
Secondary DNS zone requires master IP address.
|
|
|
DNS zone not secondary.
|
|
|
Need secondary IP address.
|
|
|
WINS initialization failed.
|
|
|
Need WINS servers.
|
|
|
NBTSTAT initialization call failed.
|
|
|
Invalid delete of start of authority (SOA)
|
|
|
A conditional forwarding zone already exists for that name.
|
|
|
This zone must be configured with one or more master DNS server IP addresses.
|
|
|
The operation cannot be performed because this zone is shut down.
|
|
|
Primary DNS zone requires datafile.
|
|
|
Invalid datafile name for DNS zone.
|
|
|
Failed to open datafile for DNS zone.
|
|
|
Failed to write datafile for DNS zone.
|
|
|
Failure while reading datafile for DNS zone.
|
|
|
DNS record does not exist.
|
|
|
DNS record format error.
|
|
|
Node creation failure in DNS.
|
|
|
Unknown DNS record type.
|
|
|
DNS record timed out.
|
|
|
Name not in DNS zone.
|
|
|
CNAME loop detected.
|
|
|
Node is a CNAME DNS record.
|
|
|
A CNAME record already exists for given name.
|
|
|
Record only at DNS zone root.
|
|
|
DNS record already exists.
|
|
|
Secondary DNS zone data error.
|
|
|
Could not create DNS cache data.
|
|
|
DNS name does not exist.
|
|
|
Could not create pointer (PTR) record.
|
|
|
DNS domain was undeleted.
|
|
|
The directory service is unavailable.
|
|
|
DNS zone already exists in the directory service.
|
|
|
DNS server not creating or reading the boot file for the directory service integrated DNS zone.
|
|
|
DNS AXFR (zone transfer) complete.
|
|
|
DNS zone transfer failed.
|
|
|
Added local WINS server.
|
|
|
Secure update call needs to continue update request.
|
|
|
TCP/IP network protocol not installed.
|
|
|
No DNS servers configured for local system.
|
|
|
The specified directory partition does not exist.
|
|
|
The specified directory partition already exists.
|
|
|
This DNS server is not enlisted in the specified directory partition.
|
|
|
This DNS server is already enlisted in the specified directory partition.
|
|
|
A blocking operation was interrupted by a call to WSACancelBlockingCall.
|
|
|
The file handle supplied is not valid.
|
|
|
An attempt was made to access a socket in a way forbidden by its access permissions.
|
|
|
The system detected an invalid pointer address in attempting to use a pointer argument in a call.
|
|
|
An invalid argument was supplied.
|
|
|
Too many open sockets.
|
|
|
A non-blocking socket operation could not be completed immediately.
|
|
|
A blocking operation is currently executing.
|
|
|
An operation was attempted on a non-blocking socket that already had an operation in progress.
|
|
|
An operation was attempted on something that is not a socket.
|
|
|
A required address was omitted from an operation on a socket.
|
|
|
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.
|
|
|
A protocol was specified in the socket function call that does not support the semantics of the socket type requested.
|
|
|
An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call.
|
|
|
The requested protocol has not been configured into the system, or no implementation for it exists.
|
|
|
The support for the specified socket type does not exist in this address family.
|
|
|
The attempted operation is not supported for the type of object referenced.
|
|
|
The protocol family has not been configured into the system or no implementation for it exists.
|
|
|
An address incompatible with the requested protocol was used.
|
|
|
Only one usage of each socket address (protocol/network address/port) is normally permitted.
|
|
|
The requested address is not valid in its context.
|
|
|
A socket operation encountered a dead network.
|
|
|
A socket operation was attempted to an unreachable network.
|
|
|
The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
|
|
|
An established connection was aborted by the software in your host machine.
|
|
|
An existing connection was forcibly closed by the remote host.
|
|
|
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
|
|
|
A connect request was made on an already connected socket.
|
|
|
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.
|
|
|
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.
|
|
|
Too many references to some kernel object.
|
|
|
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.
|
|
|
No connection could be made because the target machine actively refused it.
|
|
|
Cannot translate name.
|
|
|
Name component or name was too long.
|
|
|
A socket operation failed because the destination host was down.
|
|
|
A socket operation was attempted to an unreachable host.
|
|
|
Cannot remove a directory that is not empty.
|
|
|
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously.
|
|
|
Ran out of quota.
|
|
|
Ran out of disk quota.
|
|
|
File handle reference is no longer available.
|
|
|
Item is not available locally.
|
|
|
WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.
|
|
|
The Windows Sockets version requested is not supported.
|
|
|
Either the application has not called WSAStartup, or WSAStartup failed.
|
|
|
Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.
|
|
|
No more results can be returned by WSALookupServiceNext.
|
|
|
A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
|
|
|
The procedure call table is invalid.
|
|
|
The requested service provider is invalid.
|
|
|
The requested service provider could not be loaded or initialized.
|
|
|
A system call has failed.
|
|
|
No such service is known. The service cannot be found in the specified name space.
|
|
|
The specified class was not found.
|
|
|
No more results can be returned by WSALookupServiceNext.
|
|
|
A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
|
|
|
A database query failed because it was actively refused.
|
|
|
No such host is known.
|
|
|
This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
|
|
|
A non-recoverable error occurred during a database lookup.
|
|
|
The requested name is valid, but no data of the requested type was found.
|
|
|
At least one reserve has arrived.
|
|
|
At least one path has arrived.
|
|
|
There are no senders.
|
|
|
There are no receivers.
|
|
|
Reserve has been confirmed.
|
|
|
Error due to lack of resources.
|
|
|
Rejected for administrative reasons - bad credentials.
|
|
|
Unknown or conflicting style.
|
|
|
Problem with some part of the filterspec or providerspecific buffer in general.
|
|
|
Problem with some part of the flowspec.
|
|
|
General QOS error.
|
|
|
An invalid or unrecognized service type was found in the flowspec.
|
|
|
An invalid or inconsistent flowspec was found in the QOS structure.
|
|
|
Invalid QOS provider-specific buffer.
|
|
|
An invalid QOS filter style was used.
|
|
|
An invalid QOS filter type was used.
|
|
|
An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR.
|
|
|
An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer.
|
|
|
An incorrect number of flow descriptors was specified in the QOS structure.
|
|
|
An unrecognized object was found in the QOS provider-specific buffer.
|
|
|
An invalid policy object was found in the QOS provider-specific buffer.
|
|
|
An invalid QOS flow descriptor was found in the flow descriptor list.
|
|
|
An invalid or inconsistent flowspec was found in the QOS provider specific buffer.
|
|
|
An invalid FILTERSPEC was found in the QOS provider-specific buffer.
|
|
|
An invalid shape discard mode object was found in the QOS provider specific buffer.
|
|
|
An invalid shaping rate object was found in the QOS provider-specific buffer.
|
|
|
A reserved policy element was found in the QOS provider-specific buffer.
|
|
|
The specified quick mode policy already exists.
|
|
|
The specified quick mode policy was not found.
|
|
|
The specified quick mode policy is being used.
|
|
|
The specified main mode policy already exists.
|
|
|
The specified main mode policy was not found
|
|
|
The specified main mode policy is being used.
|
|
|
The specified main mode filter already exists.
|
|
|
The specified main mode filter was not found.
|
|
|
The specified transport mode filter already exists.
|
|
|
The specified transport mode filter does not exist.
|
|
|
The specified main mode authentication list exists.
|
|
|
The specified main mode authentication list was not found.
|
|
|
The specified main mode authentication list is being used.
|
|
|
The specified default main mode policy was not found.
|
|
|
The specified default main mode authentication list was not found.
|
|
|
The specified default quick mode policy was not found.
|
|
|
The specified tunnel mode filter exists.
|
|
|
The specified tunnel mode filter was not found.
|
|
|
The Main Mode filter is pending deletion.
|
|
|
The transport filter is pending deletion.
|
|
|
The tunnel filter is pending deletion.
|
|
|
The Main Mode policy is pending deletion.
|
|
|
The Main Mode authentication bundle is pending deletion.
|
|
|
The Quick Mode policy is pending deletion.
|
|
|
ERROR_IPSEC_IKE_NEG_STATUS_BEGIN
|
|
|
IKE authentication credentials are unacceptable
|
|
|
IKE security attributes are unacceptable
|
|
|
IKE Negotiation in progress
|
|
|
General processing error
|
|
|
Negotiation timed out
|
|
|
IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store.
|
|
|
IKE SA deleted by peer before establishment completed
|
|
|
IKE SA deleted before establishment completed
|
|
|
Negotiation request sat in Queue too long
|
|
|
Negotiation request sat in Queue too long
|
|
|
Negotiation request sat in Queue too long
|
|
|
Negotiation request sat in Queue too long
|
|
|
No response from peer
|
|
|
Negotiation took too long
|
|
|
Negotiation took too long
|
|
|
Unknown error occurred
|
|
|
Certificate Revocation Check failed
|
|
|
Invalid certificate key usage
|
|
|
Invalid certificate type
|
|
|
IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key.
|
|
|
Failure in Diffie-Hellman computation
|
|
|
Invalid header
|
|
|
No policy configured
|
|
|
Failed to verify signature
|
|
|
Failed to authenticate using Kerberos
|
|
|
Peer's certificate did not have a public key
|
|
|
Error processing error payload
|
|
|
Error processing SA payload
|
|
|
Error processing Proposal payload
|
|
|
Error processing Transform payload
|
|
|
Error processing KE payload
|
|
|
Error processing ID payload
|
|
|
Error processing Cert payload
|
|
|
Error processing Certificate Request payload
|
|
|
Error processing Hash payload
|
|
|
Error processing Signature payload
|
|
|
Error processing Nonce payload
|
|
|
Error processing Notify payload
|
|
|
Error processing Delete Payload
|
|
|
Error processing VendorId payload
|
|
|
Invalid payload received
|
|
|
Soft SA loaded
|
|
|
Soft SA torn down
|
|
|
Invalid cookie received.
|
|
|
Peer failed to send valid machine certificate
|
|
|
Certification Revocation check of peer's certificate failed
|
|
|
New policy invalidated SAs formed with old policy
|
|
|
There is no available Main Mode IKE policy.
|
|
|
Failed to enabled TCB privilege.
|
|
|
Failed to load SECURITY.DLL.
|
|
|
Failed to obtain security function table dispatch address from SSPI.
|
|
|
Failed to query Kerberos package to obtain max token size.
|
|
|
Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup.
|
|
|
Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).
|
|
|
Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters.
|
|
|
Given filter is invalid
|
|
|
Memory allocation failed.
|
|
|
Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine.
|
|
|
Invalid policy
|
|
|
Invalid DOI
|
|
|
Invalid situation
|
|
|
Diffie-Hellman failure
|
|
|
Invalid Diffie-Hellman group
|
|
|
Error encrypting payload
|
|
|
Error decrypting payload
|
|
|
Policy match error
|
|
|
Unsupported ID
|
|
|
Hash verification failed
|
|
|
Invalid hash algorithm
|
|
|
Invalid hash size
|
|
|
Invalid encryption algorithm
|
|
|
Invalid authentication algorithm
|
|
|
Invalid certificate signature
|
|
|
Load failed
|
|
|
Deleted via RPC call
|
|
|
Temporary state created to perform reinitialization. This is not a real failure.
|
|
|
The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine.
|
|
|
Key length in certificate is too small for configured security requirements.
|
|
|
Max number of established MM SAs to peer exceeded.
|
|
|
IKE received a policy that disables negotiation.
|
|
|
Reached maximum quick mode limit for the main mode. New main mode will be started.
|
|
|
The requested section was not present in the activation context.
|
|
|
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
|
|
|
The application binding data format is invalid.
|
|
|
The referenced assembly is not installed on your system.
|
|
|
The manifest file does not begin with the required tag and format information.
|
|
|
The manifest file contains one or more syntax errors.
|
|
|
The application attempted to activate a disabled activation context.
|
|
|
The requested lookup key was not found in any active activation context.
|
|
|
A component version required by the application conflicts with another component version already active.
|
|
|
The type requested activation context section does not match the query API used.
|
|
|
Lack of system resources has required isolated activation to be disabled for the current thread of execution.
|
|
|
An attempt to set the process default activation context failed because the process default activation context was already set.
|
|
|
The encoding group identifier specified is not recognized.
|
|
|
The encoding requested is not recognized.
|
|
|
The manifest contains a reference to an invalid URI.
|
|
|
The application manifest contains a reference to a dependent assembly which is not installed
|
|
|
The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed
|
|
|
The manifest contains an attribute for the assembly identity which is not valid.
|
|
|
The manifest is missing the required default namespace specification on the assembly element.
|
|
|
The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1".
|
|
|
The private manifest probed has crossed a path with an unsupported reparse point.
|
|
|
Two or more components referenced directly or indirectly by the application manifest have files by the same name.
|
|
|
Two or more components referenced directly or indirectly by the application manifest have window classes with the same name.
|
|
|
Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs.
|
|
|
Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs.
|
|
|
Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs.
|
|
|
Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs.
|
|
|
Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted.
|
|
|
A component's file does not match the verification information present in the component manifest.
|
|
|
The policy manifest contains one or more syntax errors.
|
|
|
Manifest Parse Error : A string literal was expected, but no opening quote character was found.
|
|
|
Manifest Parse Error : Incorrect syntax was used in a comment.
|
|
|
Manifest Parse Error : A name was started with an invalid character.
|
|
|
Manifest Parse Error : A name contained an invalid character.
|
|
|
Manifest Parse Error : A string literal contained an invalid character.
|
|
|
Manifest Parse Error : Invalid syntax for an xml declaration.
|
|
|
Manifest Parse Error : An Invalid character was found in text content.
|
|
|
Manifest Parse Error : Required white space was missing.
|
|
|
Manifest Parse Error : The character '>' was expected.
|
|
|
Manifest Parse Error : A semi colon character was expected.
|
|
|
Manifest Parse Error : Unbalanced parentheses.
|
|
|
Manifest Parse Error : Internal error.
|
|
|
Manifest Parse Error : Whitespace is not allowed at this location.
|
|
|
Manifest Parse Error : End of file reached in invalid state for current encoding.
|
|
|
Manifest Parse Error : Missing parenthesis.
|
|
|
Manifest Parse Error : A single or double closing quote character (\' or \") is missing.
|
|
|
Manifest Parse Error : Multiple colons are not allowed in a name.
|
|
|
Manifest Parse Error : Invalid character for decimal digit.
|
|
|
Manifest Parse Error : Invalid character for hexadecimal digit.
|
|
|
Manifest Parse Error : Invalid unicode character value for this platform.
|
|
|
Manifest Parse Error : Expecting whitespace or '?'.
|
|
|
Manifest Parse Error : End tag was not expected at this location.
|
|
|
Manifest Parse Error : Duplicate attribute.
|
|
|
Manifest Parse Error : Only one top level element is allowed in an XML document.
|
|
|
Manifest Parse Error : Invalid at the top level of the document.
|
|
|
Manifest Parse Error : Invalid xml declaration.
|
|
|
Manifest Parse Error : XML document must have a top level element.
|
|
|
Manifest Parse Error : Unexpected end of file.
|
|
|
Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset.
|
|
|
Manifest Parse Error : Element was not closed.
|
|
|
Manifest Parse Error : End element was missing the character '>'.
|
|
|
Manifest Parse Error : A string literal was not closed.
|
|
|
Manifest Parse Error : A comment was not closed.
|
|
|
Manifest Parse Error : A declaration was not closed.
|
|
|
Manifest Parse Error : A CDATA section was not closed.
|
|
|
Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml".
|
|
|
Manifest Parse Error : System does not support the specified encoding.
|
|
|
Manifest Parse Error : Switch from current encoding to specified encoding not supported.
|
|
|
Manifest Parse Error : The name 'xml' is reserved and must be lower case.
|
|
|
Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'.
|
|
|
Manifest Parse Error : The standalone attribute cannot be used in external entities.
|
|
|
Manifest Parse Error : Invalid version number.
|
|
|
Manifest Parse Error : Missing equals sign between attribute and attribute value.
|
|
|
Assembly Protection Error : Unable to recover the specified assembly.
|
|
|
Assembly Protection Error : The public key for an assembly was too short to be allowed.
|
|
|
Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest.
|
|
|
An HRESULT could not be translated to a corresponding Win32 error code.
|
|
|
Assembly Protection Error : The catalog for an assembly is missing.
|
|
|
The supplied assembly identity is missing one or more attributes which must be present in this context.
|
|
|
The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names.
|