COM Error Codes (FWP, WS, NDIS, HyperV)
The following table provides a list of error codes used by COM-based APIs.
If you are experiencing difficulty with an application you are installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, go to https://support.microsoft.com.
| Constant/value | Description |
|---|---|
|
The callout does not exist. |
|
The filter condition does not exist. |
|
The filter does not exist. |
|
The layer does not exist. |
|
The provider does not exist. |
|
The provider context does not exist. |
|
The sublayer does not exist. |
|
The object does not exist. |
|
An object with that GUID or LUID already exists. |
|
The object is referenced by other objects so cannot be deleted. |
|
The call is not allowed from within a dynamic session. |
|
The call was made from the wrong session so cannot be completed. |
|
The call must be made from within an explicit transaction. |
|
The call is not allowed from within an explicit transaction. |
|
The explicit transaction has been forcibly canceled. |
|
The session has been canceled. |
|
The call is not allowed from within a read-only transaction. |
|
The call timed out while waiting to acquire the transaction lock. |
|
Collection of network diagnostic events is disabled. |
|
The operation is not supported by the specified layer. |
|
The call is allowed for kernel-mode callers only. |
|
The call tried to associate two objects with incompatible lifetimes. |
|
The object is built in so cannot be deleted. |
|
The maximum number of callouts has been reached. |
|
A notification could not be delivered because a message queue is at its maximum capacity. |
|
The traffic parameters do not match those for the security association context. |
|
The call is not allowed for the current security association state. |
|
A required pointer is null. |
|
An enumerator is not valid. |
|
The flags field contains an invalid value. |
|
A network mask is not valid. |
|
An FWP_RANGE is not valid. |
|
The time interval is not valid. |
|
An array that must contain at least one element is zero length. |
|
The displayData.name field cannot be null. |
|
The action type is not one of the allowed action types for a filter. |
|
The filter weight is not valid. |
|
A filter condition contains a match type that is not compatible with the operands. |
|
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. |
|
An integer value is outside the allowed range. |
|
A reserved field is nonzero. |
|
A filter cannot contain multiple conditions operating on a single field. |
|
A policy cannot contain the same keying module more than once. |
|
The action type is not compatible with the layer. |
|
The action type is not compatible with the sublayer. |
|
The raw context or the provider context is not compatible with the layer. |
|
The raw context or the provider context is not compatible with the callout. |
|
The authentication method is not compatible with the policy type. |
|
The Diffie-Hellman group is not compatible with the policy type. |
|
An IKE policy cannot contain an Extended Mode policy. |
|
The enumeration template or subscription will never match any objects. |
|
The provider context is of the wrong type. |
|
The parameter is incorrect. |
|
The maximum number of sublayers has been reached. |
|
The notification function for a callout returned an error. |
|
The IPsec authentication transform is not valid. |
|
The IPsec cipher transform is not valid. |
|
The IPsec cipher transform is not compatible with the policy. |
|
The combination of IPsec transform types is not valid. |
|
A policy cannot contain the same auth method more than once. |
|
A tunnel endpoint configuration is invalid. |
|
The WFP MAC Layers are not ready. |
|
A key manager capable of key dictation is already registered |
|
A key manager dictated invalid keys |
|
The BFE IPsec Connection Tracking is disabled. |
|
The DNS name is invalid. |
|
The engine option is still enabled due to other configuration settings. |
|
The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine. |
|
The packet should be dropped, no ICMP should be sent. |
|
The function call is completing asynchronously. |
|
There are no more messages available on the channel. |
|
The input data was not in the expected format or did not have the expected value. |
|
The operation could not be completed because the object is in a faulted state due to a previous error. |
|
The operation could not be completed because it would lead to numeric overflow. |
|
The operation is not allowed due to the current state of the object. |
|
The operation was aborted. |
|
Access was denied by the remote endpoint. |
|
The operation did not complete within the time allotted. |
|
The operation was abandoned. |
|
A quota was exceeded. |
|
The information was not available in the specified language. |
|
Security verification was not successful for the received data. |
|
The address is already being used. |
|
The address is not valid for this context. |
|
The remote endpoint does not exist or could not be located. |
|
The remote endpoint is not currently in service at this location. |
|
The remote endpoint could not process the request. |
|
The remote endpoint was not reachable. |
|
The operation was not supported by the remote endpoint. |
|
The remote endpoint is unable to process the request due to being overloaded. |
|
A message containing a fault was received from the remote endpoint. |
|
The connection with the remote endpoint was terminated. |
|
The HTTP proxy server could not process the request. |
|
Access was denied by the HTTP proxy server. |
|
The requested feature is not available on this platform. |
|
The HTTP proxy server requires HTTP authentication scheme 'basic'. |
|
The HTTP proxy server requires HTTP authentication scheme 'digest'. |
|
The HTTP proxy server requires HTTP authentication scheme 'NTLM'. |
|
The HTTP proxy server requires HTTP authentication scheme 'negotiate'. |
|
The remote endpoint requires HTTP authentication scheme 'basic'. |
|
The remote endpoint requires HTTP authentication scheme 'digest'. |
|
The remote endpoint requires HTTP authentication scheme 'NTLM'. |
|
The remote endpoint requires HTTP authentication scheme 'negotiate'. |
|
The endpoint address URL is invalid. |
|
Unrecognized error occurred in the Windows Web Services framework. |
|
A security token was rejected by the server because it has expired. |
|
A security operation failed in the Windows Web Services framework. |
|
The binding to the network interface is being closed. |
|
An invalid version was specified. |
|
An invalid characteristics table was used. |
|
Failed to find the network interface or network interface is not ready. |
|
Failed to open the network interface. |
|
Network interface has encountered an internal unrecoverable failure. |
|
The multicast list on the network interface is full. |
|
An attempt was made to add a duplicate multicast address to the list. |
|
At attempt was made to remove a multicast address that was never added. |
|
Netowork interface aborted the request. |
|
Network interface cannot process the request because it is being reset. |
|
Netword interface does not support this request. |
|
An attempt was made to send an invalid packet on a network interface. |
|
Network interface is not ready to complete this operation. |
|
The length of the buffer submitted for this operation is not valid. |
|
The data used for this operation is not valid. |
|
The length of buffer submitted for this operation is too small. |
|
Network interface does not support this OID (Object Identifier) |
|
The network interface has been removed. |
|
Network interface does not support this media type. |
|
An attempt was made to remove a token ring group address that is in use by other components. |
|
An attempt was made to map a file that cannot be found. |
|
An error occurred while NDIS tried to map the file. |
|
An attempt was made to map a file that is alreay mapped. |
|
An attempt to allocate a hardware resource failed because the resource is used by another component. |
|
The I/O operation failed because network media is disconnected or wireless access point is out of range. |
|
The network address used in the request is invalid. |
|
The specified request is not a valid operation for the target device. |
|
The offload operation on the network interface has been paused. |
|
Network interface was not found. |
|
The revision number specified in the structure is not supported. |
|
The specified port does not exist on this network interface. |
|
The current state of the specified port on this network interface does not support the requested operation. |
|
The miniport adapter is in low power state. |
|
This operation requires the miniport adapter to be reinitialized. |
|
The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation. |
|
The wireless local area network interface is busy and cannot perform the requested operation. |
|
The wireless local area network interface is powered down and doesn't support the requested operation. |
|
The list of wake on LAN patterns is full. |
|
The list of low power protocol offloads is full. |
|
The request will be completed later by NDIS status indication. |
|
The TCP connection is not offloadable because of a local policy setting. |
|
The TCP connection is not offloadable by the Chimney Offload target. |
|
The IP Path object is not in an offloadable state. |
|
The hypervisor does not support the operation because the specified hypercall code is not supported. |
|
The hypervisor does not support the operation because the encoding for the hypercall input register is not supported. |
|
The hypervisor could not perform the operation because a parameter has an invalid alignment. |
|
The hypervisor could not perform the operation because an invalid parameter was specified. |
|
Access to the specified object was denied. |
|
The hypervisor could not perform the operation because the partition is entering or in an invalid state. |
|
The operation is not allowed in the current state. |
|
The hypervisor does not recognize the specified partition property. |
|
The specified value of a partition property is out of range or violates an invariant. |
|
There is not enough memory in the hypervisor pool to complete the operation. |
|
The maximum partition depth has been exceeded for the partition hierarchy. |
|
A partition with the specified partition Id does not exist. |
|
The hypervisor could not perform the operation because the specified VP index is invalid. |
|
The hypervisor could not perform the operation because the specified port identifier is invalid. |
|
The hypervisor could not perform the operation because the specified connection identifier is invalid. |
|
Not enough buffers were supplied to send a message. |
|
The previous virtual interrupt has not been acknowledged. |
|
The previous virtual interrupt has already been acknowledged. |
|
The indicated partition is not in a valid state for saving or restoring. |
|
The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled. |
|
The hypervisor could not perform the operation because the object or value was either already in use or being used for a purpose that would not permit completing the operation. |
|
The proximity domain information is invalid. |
|
An attempt to retrieve debugging data failed because none was available. |
|
The physical connection being used for debugging has not recorded any receive activity since the last operation. |
|
There are not enough resources to complete the operation. |
|
A hypervisor feature is not available to the user. |
|
The maximum number of domains supported by the platform I/O remapping hardware is currently in use. No domains are available to assign this device to this partition. |
|
The hypervisor could not perform the operation because the specified LP index is invalid. |
|
No hypervisor is present on this system. |
|
The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The partition name of the virtualization infrastructure driver exceeds the maximum. |
|
The message queue name of the virtualization infrastructure driver exceeds the maximum. |
|
Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists. |
|
The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
A message queue with the same name already exists for the virtualization infrastructure driver. |
|
The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed. |
|
Cannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration. |
|
The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology. |
|
The memory block for the virtualization infrastructure driver is already associated with a message queue. |
|
The handle is not a valid memory block handle for the virtualization infrastructure driver. |
|
The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The handle is not a valid message queue handle for the virtualization infrastructure driver. |
|
The handle is not a valid page range handle for the virtualization infrastructure driver. |
|
Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block. |
|
The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver. |
|
Notifications cannot be created on the memory block because it is use. |
|
The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
Cannot add a virtual processor to the partition because the maximum has been reached. |
|
Cannot stop the virtual processor immediately because of a pending intercept. |
|
Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
|
Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. |
|
Cannot restore this virtual machine because an item read from the saved state data is not recognized. Delete the saved state data and then try to start the virtual machine. |
|
Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine. |
|
A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration. |
Requirements
| Requirement | Value |
|---|---|
| Header |
|
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for