A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. Promotion was required 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 can be opened for execute only by a transacted reader. The request to thaw frozen transactions was ignored because transactions were not previously frozen.
The target volume is not a snapshot volume. This operation is valid only on a volume mounted as a snapshot. The savepoint operation failed because files are open on the transaction, which is not permitted. The call to create a transaction manager object failed because the Tm Identity that is stored in the log file does not match the Tm Identity that was passed in as an argument. 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 manager has been shut down. The specified resource manager was unable to create an enlistment because its associated transaction manager is not online.
The specified transaction manager was unable to create the objects contained in its log file in the Ob namespace. Therefore, the transaction manager 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 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 to be logged was too long. This can occur because either there are too many enlistments on this transaction or the combined RecoveryInformation being logged on behalf of those enlistments is too long. The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. The handle is no longer properly associated with its transaction. It might 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. The log service encountered an attempt to read from a marshaling area with an invalid read context.
The number of reserved log records or the adjustment of the number of reserved log records is invalid. 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 next time you reboot the computer, a dialog box will allow you to upload data about this failure to Microsoft. Minifilters should never return this value. Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock.
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is loaded as a driver.
The filter is not ready for attachment to volumes because it has not finished initializing FltStartFiltering has not been called. The filter must clean up any operation-specific context at this time because it is being removed from the system before the operation is completed by the lower drivers. The Filter Manager had an internal error from which it cannot recover; therefore, the operation has failed. This is usually the result of a filter returning an invalid value from a pre-operation callback.
The object specified for this action is in the process of being deleted; therefore, the action requested cannot be completed at this time. The name requested was not found in the Filter Manager name cache and could not be retrieved from the file system. The provided monitor descriptor block is either corrupted or does not contain the monitor's detailed serial number. The provided monitor descriptor block is either corrupted or does not contain the monitor's user-friendly name.
An object being referenced has already reached the maximum reference count and cannot be referenced further. The specified VidPN topology is valid but is not supported by this model of the display adapter. The specified VidPN topology is valid but is not currently supported by the display adapter due to allocation of its resources. The specified VidPN modality is not supported for example, at least two of the pinned modes are not co-functional. The miniport does not have a recommendation regarding the request to provide a functional VidPN given the current display adapter configuration.
The system failed to determine a mode that is supported by both the display adapter and the monitor connected to it. The number of video present targets must be greater than or equal to the number of video present sources.
Two or more of the specified resources are not related to each other, as defined by the interface semantics. The specified content geometry transformation is not supported on the respective VidPN present path. Only one unassigned mode set can exist at any one time for a particular VidPN source or target. The specified primary surface has a different private-format attribute than the current primary surface.
The miniport requested that augmentation be canceled for the specified source of the specified VidPN's topology. The client VidPN is not set on this adapter for example, no user mode-initiated mode changes have taken place on this adapter. An attempt was made to start a lead link display adapter when the chain links had not yet started. An attempt was made to turn on a lead link display adapter when the chain links were turned off.
The adapter link was found in an inconsistent state. An array passed to a function cannot hold all of the data that the function wants to put in it.
This function failed because the GDI display device passed to it was not attached to the Windows desktop. The PVP does not support mirroring display devices because they do not have any protected outputs. The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is null, is not correctly aligned, or it points to an invalid address or a kernel mode address.
This function failed because the GDI device passed to it did not have any monitors associated with it. A certificate could not be returned because the certificate buffer passed to the function was too small. DxgkDdiOpmCreateProtectedOutput could not create a protected output because the video present yarget is in spanning mode. DxgkDdiOpmCreateProtectedOutput could not create a protected output because the video present target is in theater mode.
The function call failed because the display adapter's hardware functionality scan HFS failed to validate the graphics hardware.
DxgkDdiOPMConfigureProtectedOutput cannot enable the specified output protection technology because the output's screen resolution is too high. The operating system asynchronously destroyed this OPM-protected output because the operating system state changed. This error typically occurs because the monitor PDO associated with this protected output was removed or stopped, the protected output's session became a nonconsole session, or the protected output's desktop became inactive.
OPM functions cannot be called when a session is changing its type. This error is returned only if a protected output has OPM semantics. This error is returned only if a protected output has COPP semantics.
This error implies that the data was corrupted while it was being transmitted from a monitor to a computer. The operating system asynchronously destroyed the monitor that corresponds to this handle because the operating system's state changed.
This error typically occurs because the monitor PDO associated with this handle was removed or stopped, or a display mode change occurred. This function can be used only if a program is running in the local console session. It cannot be used if a program is running on a remote desktop session or on a terminal server session. The function failed because the specified GDI display device was not attached to the Windows desktop.
This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them. A pointer parameter is invalid if it is null, is not correctly aligned, or points to an invalid address or to a kernel mode address. This function failed because the GDI device passed to it did not have a monitor associated with it. An array passed to the function cannot hold all of the data that the function must copy into the array.
The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type.
The BitLocker encryption key could not be obtained from the startup key or the recovery password. The system boot information changed or the TPM locked out access to BitLocker encryption keys until the computer is restarted. Boot debugging is enabled. Bitlocker Drive Encryption failed to recover from aborted conversion. This could be due to either all conversion logs being corrupted or the media being write-protected.
An attempt to allocate a hardware resource failed because the resource is used by another component. The current state of the specified port on this network interface does not support the requested operation. The wireless LAN interface is in auto-configuration mode and does not support the requested parameter change operation.
IPsec Dos Protection failed to create state because there are already maximum number of entries allowed by policy. IPsec Dos Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.
IPsec Dos Protection failed to create per internal IP ratelimit queue because there is already maximum number of queues allowed by policy. The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk.
The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk. A differencing disk is indicated in its own parent chain.
There was an error opening a virtual hard disk further up the chain. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article. Returned by enumeration APIs to indicate more information is available to successive calls.
A file system or file system filter driver has successfully completed an FsFilter operation. This is unexpected, indicating that the callback missed restoring the priority.
The ALPC message being canceled has already been retrieved from the queue on the other side. The receive operation was successful. Check the ALPC completion list for the received message. The specified content transformation is not pinned on the specified VidPN present path.
The display adapter is being polled for children too frequently at the same polling level. A transaction scope could not be entered because the scope handler has not been initialized. An attempt was made to attach to a device that was already attached to another device.
An attempt was made to query image information on a section that does not map an image. A non-close operation has been requested of a file object that has a delete pending. Indicates a particular security ID cannot be assigned as the primary group of an object. No more authority agent values are available for the particular identifier authority value. An attempt was made to open an anonymous-level token. Anonymous tokens cannot be opened. Space to store the file that is waiting to be printed is not available on the server.
The number of active profiling objects is at the maximum and no more can be started. An attempt was made to exceed the limit on the number of domains per server for this release.
Indicates a security descriptor is not in the necessary format absolute or self-relative. An attempt was made to access a network file, but the network software was not yet started. An attempt was made to start the redirector, but the redirector has already been started. Run the Chkdsk utility. The logon session is not in a state that is consistent with the requested operation. RtlFindMessage could not locate the requested message ID in the message table resource.
An attempt was made to duplicate an object handle into or out of an exiting process. Indicates that the user supplied an invalid descriptor when trying to set up LDT descriptors. The specified image file did not have the correct format. It appears to be NE format. An attempt was made to map a file of size zero with the maximum size specified as zero. Indicates a name that was specified as a remote computer name is syntactically invalid.
The specified image file did not have the correct format: it appears to be LE format. The specified image file did not have the correct format: it did not have an initial MZ. When accessing a new tape of a multi-volume partition, the current blocksize is incorrect. An illegal operation was attempted on a registry key that has been marked for deletion. The workstation does not have a trust secret for the primary domain in the local LSA database. The network logon failed. This might be because the validation authority cannot be reached.
An attempt was made to acquire a mutant such that its maximum count would have been exceeded. Short name settings cannot be changed on this volume due to the global registry setting. The transport rejected the specified network address due to invalid use of a wildcard. The transport address could not be opened because all the available addresses are in use.
The transport can only process the specified request on the server side of a session. The transport can only process the specified request on the client side of a session. The attempt to insert the ID in the index failed because the ID is already in the index. No service is operating at the destination port of the transport on the remote system. The requested operation cannot be performed on a file with a user mapped section open. You have attempted to load a legacy device driver while its device instance had been disabled.
The NTFS symbolic link could not be resolved even though the initial file name is valid. The specified file is encrypted and the user does not have the ability to decrypt it. The reparse attribute cannot be set because it is incompatible with an existing attribute.
Mutual Authentication failed. The server password is out of date at the domain controller. Cannot change to a security-disabled group because primary members are in this group. The crypto system or checksum function is invalid because a required function is unavailable.
The Kerberos protocol encountered an error while attempting to use the smart card subsystem. A machine check error has occurred. Check the system event log for additional information. The driver could not be loaded because a previous version of the driver is still in memory. The group cannot be converted due to attribute restrictions on the requested group type. An attempt to delay-load a. The attempt to purge this file from memory failed to purge some or all the data from memory. A reboot might be required.
Data cannot be moved because the source device cannot communicate with the destination device. Either the target process, or the target thread's containing process, is a protected process. A threadpool worker thread entered a callback, which left transaction state.
This is unexpected, indicating that the callback missed clearing the transaction. A threadpool worker thread entered a callback, which left the loader lock held.
This is unexpected, indicating that the callback missed releasing the lock. A threadpool worker thread entered a callback, which left with preferred languages set.
This is unexpected, indicating that the callback missed clearing them. A threadpool worker thread entered a callback, which left with background priorities set. This is unexpected, indicating that the callback missed restoring the original priorities.
This indicates that the caller made the connection request in the wrong routing compartment. This indicates that there was an AuthIP failure when attempting to connect to the remote host.
Offload read operations cannot be performed on: Compressed files Sparse files Encrypted files File system metadata files. Offload write operations cannot be performed on: Compressed files Sparse files Encrypted files File system metadata files. The client you are using is not licensed to use this system.
Your logon request is denied. The application attempted to enable DOS graphics mode. DOS graphics mode is not supported. A process has requested access to a session, but has not been granted those access rights. Your interactive logon privilege has been disabled. The resource loader failed to load an MUI file because the file failed to pass validation.
The activation context being deactivated is not active for the current thread of execution. A component used by the isolation facility has requested that the process be terminated. The activation context activation stack for the running thread of execution is corrupt.
The character encoding in the XML declaration did not match the encoding used in the document. The function attempted to use a name that is reserved for use by another transaction. The requested operation was made in the context of a transaction that is no longer active. The resource manager attempted to prepare a transaction that it has not successfully joined. The remote server sent mismatching version number or Fid for a file opened with transactions.
The requested operation is not valid on the transaction object in its current state. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article. Causes the manage-bde command-line tool to send the return code of 0 if the volume is protected and 1 if the volume is unprotected; most commonly used for batch scripts to determine if a drive is BitLocker-protected.
See how to enable scripts. Account Lockout Status LockoutStatus. Details Version:. File Name:. Date Published:. File Size:.
0コメント