This topic lists the custom error codes that can be returned by Real-Time and Native Library APIs in wRTOS.
| Error code | Description |
|---|---|
|
RT_ERROR_INTERNAL_X |
Internal error, where X is an internal Subsystem error code. |
|
RT_ERROR_SUCCESS (0x20000000) |
The operation was successful. |
|
RT_ERROR_NO_RUNTIME_LICENSE 536870913 (0x20000001) |
No wRTOS Runtime license is available. |
|
RT_ERROR_EXPIRED_RUNTIME_LICENSE 536870914 (0x20000002) |
The wRTOS Runtime license has expired. |
|
RT_ERROR_NO_LICENSE 536870915 (0x20000003) |
No valid license was found for the given product feature code. |
|
RT_ERROR_MODULE_NO_SDK_LICENSE 536870916 (0x20000004) |
No wRTOS SDK license was available when this application (or an RTDLL on which it depends) was built. You may be able to resolve this error by rebuilding the application. |
|
RT_ERROR_MODULE_EVAL_SDK_LICENSE 536870917 (0x20000005) |
This application (or an RTDLL on which it depends) was built with an evaluation wRTOS SDK license. It cannot be executed when the wRTOS Runtime license is a retail license. You may be able to resolve this error by rebuilding the application. |
|
RT_ERROR_MODULE_LICENSE_INFO_MISSING 536870918 (0x20000006) |
This application (or an RTDLL on which it depends) is missing important wRTOS license information. You may be able to resolve this error by rebuilding the application. |
|
RT_ERROR_MODULE_LICENSE_INFO_CORRUPT 536870919 (0x20000007) |
This application (or an RTDLL on which it depends) contains corrupted license information. You may be able to resolve this error by rebuilding the application. |
|
RT_ERROR_MODULE_UNSUPPORTED_SDK 536870920 (0x20000008) |
One or more object files in this application (or an RTDLL on which it depends) were built using a wRTOS SDK version that is incompatible with the current wRTOS Runtime. You may be able to resolve this error by rebuilding the application. |
|
RT_ERROR_CORRUPT_LICENSE_DATA 536870921 (0x20000009) |
This license data is corrupt. |
|
RT_ERROR_SERVICE_ACCESS_FAILURE 536870922 (0x2000000A) |
The wRTOS Subsystem was unable to communicate with the required services. |
|
RT_ERROR_INTERNAL_1 (0x2000000B) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_2 (0x2000000C) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_3 (0x2000000D) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_4 (0x2000000E) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_5 (0x2000000F) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_6 (0x200000010) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_7 (0x200000011) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_8 (0x200000012) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_9 (0x200000013) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_10 (0x2000000K) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_11 (0x200000015) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_12 (0x200000016) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_13 (0x200000017) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INVALID_BINARY_FORMAT 536870936 (0x20000018)
|
A real-time application attempted to load a Windows DLL, either explicitly or implicitly, instead of a Real-Time DLL (RTDLL). |
|
RT_ERROR_RESTART_SUBSYSTEM 536870937 (0x20000019) |
The wRTOS Subsystem needs to be restarted for a configuration change to take effect. |
|
RT_ERROR_SUBSYSTEM_NOT_CONFIGURED 536870938 (0x2000001A) |
The wRTOS Subsystem is not configured, but an operation was attempted that requires it to be configured. |
|
RT_ERROR_STRUCTURE_TOO_SMALL 536870939 (0x2000001B) |
A structure passed to an API is too small. |
|
RT_ERROR_INTERNAL_14 (0x20000001C) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_NO_NETWORK_LICENSE 536870941 (0x2000001D) |
The wRTOS TCP/IP StackNetwork has no license, but an operation was attempted that requires it to be licensed. |
|
RT_ERROR_SUBSYSTEM_STARTSTOP_LOCK_FAILURE 536870942 (0x2000001eE) |
An operation failed to acquire the mutex that serializes starting/stopping the wRTOS Subsystem. |
|
RT_ERROR_TIMEOUT_STARTING_SUBSYSTEM 536870943 (0x2000001F) |
A timeout occurred while attempting to start the wRTOS Subsystem. |
|
RT_ERROR_TIMEOUT_STOPPING_SUBSYSTEM 536870944 (0x20000020) |
A timeout occurred while attempting to stop the wRTOS Subsystem. |
|
RT_ERROR_TIMEOUT_STARTING_NETWORK 536870945 (0x20000021) |
A timeout occurred while attempting to start the wRTOS TCP/IP Stack. |
|
RT_ERROR_INTERNAL_15 (0x200000022) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_16 (0x200000023) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_SUBSYSTEM_NOT_STARTED 536870948 (0x20000024) |
The wRTOS Subsystem is not started but an operation was attempted that requires it to be started. |
|
RT_ERROR_SUBSYSTEM_NOT_STOPPED 536870949 (0x20000025) |
The subsystem is not stopped but an operation was attempted that requires it to be stopped. |
|
RT_ERROR_RTSS_PROCESSES_RUNNING 536870950 (0x20000026) |
The subsystem cannot be stopped, because one or more real-time processes are running. |
|
RT_ERROR_PROXY_PROCESSES_RUNNING 536870951 (0x20000027) |
The subsystem cannot be stopped, because one or more real-time proxy processes are running. |
|
RT_ERROR_CUSTOM_TRIGGER_DISALLOWED (0x20000028) |
The monitoring framework cannot set triggers on MF_KIND_CUSTOM_EVENT. |
|
RT_ERROR_NETWORK_STOPPED 536870953 (0x20000029) |
The wRTOS TCP/IP Stack is stopped. |
|
RT_ERROR_NETWORK_STARTED 536870954 (0x2000002A) |
The wRTOS TCP/IP Stack is running. |
|
RT_ERROR_NETWORK_NOT_INSTALLED 536870956 (0x2000002C) |
An operation was attempted that requires the wRTOS Network to be installed, but it is not installed. |
|
RT_ERROR_INTERNAL_18 (0x20000002D) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_NETWORK_CLIENTS_EXIST 536870958 (0x2000002E) |
The wRTOS TCP/IP Stack cannot be stopped, because one or more stack client processes are still running. |
|
RT_ERROR_SUBSYSTEM_START_STOP_IN_PROGRESS 536870959 (0x2000002F) |
The subsystem is busy starting or stopping. |
|
RT_ERROR_RESTART_NETWORK 536870960 (0x20000030) |
The wRTOS TCP/IP Stack and NL2 need to be restarted for configuration changes to take effect. |
|
RT_ERROR_TOO_MANY_NETWORK_INTERFACES 536870961 (0x20000031) |
There are no interface slots left. The maximum number of interfaces is 99. |
|
RT_ERROR_MONITORING_ENABLED 536870962 (0x20000032) |
Monitoring is already enabled. |
|
RT_ERROR_MONITORING_DISABLED 536870963 (0x20000033) |
Monitoring is already disabled. |
|
RT_ERROR_MONITORING_STARTED 536870964 (0x20000034) |
Monitoring is already started. |
|
RT_ERROR_MONITORING_STOPPED 536870965 (0x20000035) |
Monitoring is already stopped. |
|
RT_ERROR_RESTART_WINDOWS 536870968 (0x20000038) |
Windows needs to be restarted. |
|
RT_ERROR_NETWORK_STOP_TIMEOUT 536870969 (0x20000039) |
A timeout occurred while attempting to stop the wRTOS TCP/IP Stack. |
|
RT_ERROR_INTERNAL_19 (0x20000003A) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_20 (0x20000003B) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_21 (0x20000003C) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_WARNING_INCONSISTENT_PROCESSOR_CONFIGURATION 536870973 (0x2000003D) |
An API succeeded but needed to modify configured processor numbers to prevent invalid process numbers. |
|
RT_WARNING_TIMER_VALUES_ROUNDED 536870974 (0x2000003E) |
An API succeeded but needed to modify configured timers or timeout values to maintain wRTOS Subsystem consistency. |
|
RT_ERROR_INTERNAL_22 (0x20000003F) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERNAL_23 (0x200000040) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_FRIENDLY_NAME_INVALID 536870978 (0x20000042) |
Network interface configuration friendly name is invalid. |
|
RT_ERROR_DRIVER_INVALID 536870979 (0x20000043) |
Network interface configuration driver name is invalid. |
|
RT_ERROR_FILTER_DRIVER_INVALID 536870980 (0x20000044) |
Network interface configuration filter driver name is invalid. |
|
RT_ERROR_DEVICE_INSTANCE_ID_INVALID 536870981 (0x20000045) |
Network interface configuration instance ID is invalid. |
|
RT_ERROR_GATEWAY_INVALID 536870982 (0x20000046) |
Network interface configuration gateway is invalid. |
|
RT_ERROR_PCI_BUS_LOCATION_INVALID 536870983 (0x20000047) |
Network interface configuration PCI bus location is invalid. |
|
RT_ERROR_IPV6_ADDRESS_INVALID 536870984 (0x20000048) |
Network interface configuration IPv6 address is invalid. |
|
RT_ERROR_NUMBER_OF_IPV4_CONFIGURATIONS_TOO_SMALL 536870985 (0x20000049) |
Network interface configuration number of IPv4 configurations is too small. |
|
RT_ERROR_NUMBER_OF_IPV4_CONFIGURATIONS_TOO_HIGH 536870986 (0x2000004A) |
Network interface configuration number of IPv4 configurations is too high. |
|
RT_ERROR_IPV4_ADDRESS_INVALID 536870987 (0x2000004B) |
Network interface configuration IPv4 address is invalid. |
|
RT_ERROR_NETMASK_INVALID 536870988 (0x2000004C) |
Network interface configuration netmask is invalid. |
|
RT_ERROR_IPV6_PREFIX_INVALID 536870989 (0x2000004D) |
Network interface configuration IPv6 prefix is invalid. |
|
RT_ERROR_INTERRUPT_PRIORITY_INVALID 536870990 (0x2000004E) |
Network interface configuration interrupt priority is invalid. |
|
RT_ERROR_MTU_INVALID 536870991 (0x2000004F) |
Network interface configuration MTU is invalid. |
|
RT_ERROR_RECEIVEIDEALPROCESSOR_INVALID 536870992 (0x20000050) |
Network interface configuration ReceiveIdealProcessor is invalid. |
|
RT_ERROR_INTERRUPTIDEALPROCESSOR_INVALID 536870993 (0x20000051) |
Network interface configuration InterruptIdealProcessor is invalid. |
|
RT_ERROR_LINK_STATUS_PRIORITY_INVALID 536870995 (0x20000053) |
Network interface configuration link status priority is invalid. |
|
RT_ERROR_RECEIVE_PRIORITY_INVALID 536870996 (0x20000054) |
Network interface configuration receive priority is invalid. |
|
RT_ERROR_INTERRUPT_TYPE_INVALID 536870997 (0x20000055) |
Network interface configuration interrupt type is invalid. |
|
RT_ERROR_NUMBER_OF_RECEIVE_BUFFERS_INVALID 536870998 (0x20000056) |
Network interface configuration number of receive buffers is invalid. |
|
RT_ERROR_NUMBER_OF_TRANSMIT_BUFFERS_INVALID 536870999 (0x20000057) |
Network interface configuration number of transmit buffers is invalid. |
|
RT_ERROR_INTERNAL_25 (0x200000058) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_DUPLICATE_SEARCH_PATH 536871002 (0x2000005A) |
A folder was specified more than once in the search path. |
|
RT_ERROR_REGISTRY_MISSING 536871003 (0x2000005B) |
An error occurred when accessing a wRTOS Registry key or value. |
|
RT_ERROR_INTERNAL_26 (0x20000005C) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_SCHEDULED_PROCESS_LOCK_FAILURE 536871005 (0x2000005D) |
An operation failed to acquire the mutex that serializes scheduled process operations. |
|
RT_ERROR_INTERNAL_27 (0x20000005E) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_SCHEDULED_PROCESS_NOT_FOUND 536871007 (0x2000005F) |
No scheduled process was found for the given ID or order. |
|
RT_ERROR_INCORRECT_INTERRUPT_TYPE 536871008 (0x20000060) |
The specified interrupt type is incorrect. |
|
RT_ERROR_FAILED_TO_ATTACH_INTERRUPT 536871009 (0x20000061) |
Failed to attach to the interrupt. |
|
RT_ERROR_TRANSLATING_PCI_BUS_ADDRESS 536871010 (0x20000062) |
Error translating the PCI bus address. |
|
RT_ERROR_MAPPING_REGISTERS 536871011 (0x20000063) |
Error mapping memory registers. |
|
RT_ERROR_MAC_ADDRESS_MISMATCH 536871012 (0x20000064) |
The adapter's MAC address does not match the configuration. |
|
RT_INVALID_INTERRUPT_PRIORITY 536871014 (0x20000066) |
The specified interrupt priority is invalid. |
|
RT_ERROR_TCPIP_MEMORY_INVALID 536871016 (0x20000068) |
The TCP/IP Memory configuration parameter exceeds the minimum size of the TCP/IP MSpace. |
|
RT_ERROR_FEATURE_NOT_AVAILABLE 536871017 (0x20000069) |
The feature is not available on this system. Cannot change values pertaining to this feature. |
|
RT_ERROR_INTERNAL_29 (0x20000006A) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_CONSOLE_LOG_PATH_NAME_TOO_LONG 536871019 (0x2000006B) |
Maximum server console log path name length exceeded. |
|
RT_ERROR_CANT_DETERMINE_NUM_PROCESSORS 536871020 (0x2000006C) |
Unable to determine the number of processors on this system. |
|
RT_ERROR_INVALID_IDEAL_PROCESSOR 536871021 (0x2000006D) |
The specified ideal processor is invalid. |
|
RT_ERROR_INVALID_AFFINITY_MASK 536871022 (0x2000006E) |
The specified affinity mask is invalid. |
|
RT_ERROR_INTERNAL_30 (0x20000006F) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_MAX_MODULES_LIMIT_REACHED 536871024 (0x20000070) |
Maximum number of loaded modules has been reached. To change this limit, see Loaded Modules Maximum in LoadLibrary. |
|
RT_ERROR_INTERNAL_31 (0x200000071) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_WRTOS_BOOT_CONFIG 536871026 (0x20000072) |
The System is not currently booted from the wRTOS boot configuration. |
|
RT_ERROR_UNKNOWN_MONITORING_EVENT 536871027 (0x20000073) |
The Monitoring API called did not recognize an MF_EVENT_KIND passed into it. This could be caused by user error or due to mismatch of SDK and Runtime. |
|
RT_ERROR_WRTOS_TOO_MANY_CORES 536871028 (0x20000074) |
The number of Windows processors plus number of RTSS process exceeds the number of cores of the system. |
|
RT_ERROR_MONITORING_PAUSED 536871030 (0x20000076) |
Monitoring cannot be paused when it is already paused. |
|
RT_ERROR_CREATING_MONITOR_SESSION 536871031 (0x20000077) |
Monitoring cannot create session file. |
|
RT_ERROR_XMITCOMPLETEIDEALPROCESSOR_INVALID 536871032 (0x20000078) |
Network interface field XmitCompleteIdealProcessor is invalid. |
|
RT_ERROR_XMITCOMPLETEPRIORITY_INVALID 536871033 (0x20000079) |
Network interface field XmitCompletePriority is invalid. |
|
RT_ERROR_DEFAULTRECEIVEQUEUE_INVALID 536871034 (0x2000007A) |
Network interface field DefaultReceiveQueue is invalid. |
|
RT_ERROR_NUMBEROFRECVQUEUES_INVALID 536871035 (0x2000007B) |
Network interface field NumberOfRecvQueues is invalid. |
|
RT_ERROR_NUMBEROFXMITQUEUE_INVALID 536871036 (0x2000007C) |
Network interface field NumberOfXmitQueues is invalid. |
|
RT_ERROR_MAXPACKETSIZE_INVALID 536871037 (0x2000007D) |
Network interface field MaxPacketSize is invalid. |
|
RT_ERROR_MAXSOCKETS_INVALID 536871042 (0x20000082) |
The maximum sockets value for the network is invalid. |
|
RT_ERROR_MAXCONCURRENCY_INVALID 536871043 (0x20000083) |
The maximum concurrency value for the network is invalid. |
|
RT_ERROR_TICKINTERVAL_OUT_OF_BOUNDS 536871044 (0x20000084) |
The tick interval for the network is out of bounds. |
|
RT_ERROR_TIMERPRIORITY_INVALID 536871045 (0x20000085) |
The timer thread priority for the network is invalid. |
|
RT_ERROR_TIMERIDEALPROCESSOR_INVALID 536871046 (0x20000086) |
The timer thread's ideal processor for the network is invalid. |
|
RT_ERROR_NETWORKIDEALPROCESSOR_INVALID 536871047 (0x20000087) |
The NL2 or TCP/IP Stack's ideal processor is invalid. |
|
RT_ERROR_IPREASSEMBLY_INVALID 536871048 (0x20000088) |
The IP Reassembly value for the network is invalid. |
|
RT_ERROR_HALTIMER_INVALID 536871049 (0x20000089) |
The HAL Timer Period for the subsystem is invalid. |
|
RT_ERROR_DEFAULTTIMEQUANTUM_INVALID 536871050 (0x2000008A) |
The Default Time Quantum for the subsystem is invalid. |
|
RT_ERROR_TCPIP_CLIENTS_EXIST 536871054 (0x2000008E) |
Cannot stop the TCP/IP because Stack clients are running. |
|
RT_ERROR_TIMEOUT_QUERYING_TCPIP_STATUS 536871056 (0x20000090) |
A timeout occurred while querying TCP/IP status. |
|
RT_ERROR_TIMEOUT_QUERYING_TCPIP_CLIENT_PIDS 536871059 (0x20000093) |
A timeout occurred while querying TCP/IP client process IDs. |
|
RT_ERROR_INVALID_THREAD_PRIORITY (0x20000094) |
Invalid thread priority. |
|
RT_ERROR_TCPIP_STACK_TERMINATED_UNEXPECTEDLY 536871062 (0x20000096) |
The wRTOS TCP/IP Stack terminated unexpectedly. |
|
RT_ERROR_TOO_MANY_IP_ADDRESSES 536871063 (0x20000097) |
Cannot configure more than 12 IP addresses for a single interface. |
|
RT_ERROR_RESTART_TCPIP 536871064 (0x20000098) |
The wRTOS TCP/IP Stack to be restarted for configuration changes to take effect. |
|
RT_ERROR_TCPIP_STACK_FATAL_ERROR 536871065 (0x20000099) |
Fatal error in the wRTOS TCP/IP Stack. |
|
RT_ERROR_STACK_STARTED 536871067 (0x2000009B) |
The wRTOS TCP/IP Stack is already started. |
|
RT_ERROR_STACK_STOPPED 536871068 (0x2000009C) |
The wRTOS TCP/IP Stack is already stopped. |
|
RT_ERROR_STACK_STOP_TIMEOUT 536871069 (0x2000009D) |
The wRTOS TCP/IP Stack timed out while trying to stop. |
|
RT_ERROR_INTERNAL_33 (0x20000009E) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_INTERFACE_NOT_CONVERTED 536871071 (0x2000009F) |
Network interface is not converted to wRTOS. |
|
RT_ERROR_INTERNAL_34 (0x2000000A0) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_TICKINTERVAL_NOT_MULTIPLE_OF_HAL_TIMER 536871073 (0x200000A1) |
The tick interval for the network is not a multiple of HAL timer interval. |
|
RT_ERROR_DUPLICATE_IPV4 536871074 (0x200000A2) |
A duplicate IPv4 address was found. |
|
RT_ERROR_INVALID_TCPIP_SUPPORT 536871075 (0x200000A3) |
TCP/IP support is in an invalid configuration for this interface. |
|
RT_ERROR_SCHEDULED_PROCESS_INIT_MEMORY_INVALID 536871076 (0x200000A4) |
Scheduled process initial memory size is invalid. |
|
RT_ERROR_SCHEDULED_PROCESS_EXPAND_MEMORY_INVALID 536871077 (0x200000A5) |
Scheduled process expand memory size is invalid. |
|
RT_ERROR_INTERNAL_35 (0x2000000A6) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_MEMORY_CORRUPTION 536871080 (0x200000A8) |
Memory corruption detected. |
|
RT_ERROR_API_REPLACED 536871081 (0x200000A9) |
This API has been replaced. |
|
RT_ERROR_INVALID_REMOTE_DEBUGGER_PORT 536871082 (0x200000AA) |
The remote debugger's port parameter is invalid. |
|
RT_ERROR_INVALID_REMOTE_DEBUGGER_NAME 536871083 (0x200000AB) |
The remote debugger's name parameter is invalid. |
|
RT_ERROR_DEBUGGER_LISTENING 536871086 (0x200000AE) |
The remote debugger Host Settings cannot be altered while the debugger is actively listening. |
|
RT_ERROR_MONITORING_LOGS_FULL 536871087 (0x200000AF) |
The folder for Monitoring Logs has hit it's designated capacity. |
|
RT_ERROR_MONITORING_FOLDER_DOES_NOT_EXIST 536871088 (0x200000B0) |
The monitoring folder is not present on this machine. |
|
RT_ERROR_DUPLICATE_IPV6 536871089 (0x200000B1) |
A duplicate IPv6 address was found. |
|
RT_ERROR_TIMEREXECUTEPRIORITY_INVALID 536871091 (0x200000B2) |
The TCP/IP Stack's timer execute priority value is invalid. |
|
RT_ERROR_MTBSIZE_INVALID 536871092 (0x200000B3) |
The MTBSize for monitoring is invalid. |
|
RT_ERROR_MONLOGSIZE_INVALID 536871093 (0x200000B4) |
The monitoring log size is invalid. |
|
RT_ERROR_SPEED_DUPLEX_INVALID 536871094 (0x200000B5) |
Network interface field Speed Duplex is invalid. |
|
RT_ERROR_IPV4_HOST_ID_INVALID 536871095 (0x200000B6) |
Network interface Host ID is invalid. |
|
RT_ERROR_IPV4_NETWORK_ID_INVALID 536871096 (0x200000B7) |
Network interface Network ID is invalid. |
|
RT_ERROR_INTERNAL_36 (0x2000000B8) |
An internal error occurred. Please contact IntervalZero Support for more information. |
|
RT_ERROR_MAXPACKETSIZE_TOO_LARGE 536871098 (0x200000B9) |
Network interface maximum packet larger than supported. |
|
RT_ERROR_TCPIP_PRIORITY_RELATION_INVALID 536871099 (0x200000BA) |
TCP/IP configuration parameter Timer Priority must be less than configuration parameter Timer Execute Priority. |
|
RT_ERROR_UNSUPPORTED_MODULE_TYPE (0x200000BB) |
Module is not an RTSS or RTDLL file. |
|
RT_ERROR_DUPLICATE_NETWORK_DEVICE 536871101 (0x200000BC) |
A network interface was found that uses the same device. |
|
RT_ERROR_INTERFACE_NAME_INVALID (0x200000BD) |
The network interface name is invalid. |
|
RT_ERROR_INTERFACE_NAME_ALREADY_EXISTS (0x200000BE) |
The network interface name already exists. |
|
RT_ERROR_INTERFACE_NAME_NOT_FOUND (0x200000BF) |
The network interface name was not found. |
|
RT_ERROR_INTERFACE_MSIX_MESSAGE_ID_INVALID (0x200000C0) |
Invalid network interface MSIX message ID. |
|
RT_ERROR_INTERFACE_TX_QUEUE_INDEX_INVALID (0x200000C1) |
Invalid network interface transmit queue index. |
|
RT_ERROR_INTERFACE_RX_QUEUE_INDEX_INVALID (0x200000C2) |
Invalid network interface receive queue index. |
|
RT_ERROR_MISMATCHED_SIZE_FIELDS (0x200000C3) |
The value of the Size field in one or more array elements is not equal. |
|
RT_ERROR_DUPLICATE_DEVICE_INSTANCE_ID (0x200000C4) |
Duplicate Device Instance ID. |
|
RT_ERROR_INVALID_INGRESS_TIMESTAMPING_UDP_PORT (0x200000C5) |
Invalid ingress timestamping UDP port. |
|
RT_ERROR_INVALID_NONMSIX_IST_PRIORITY (0x200000C6) |
Invalid non-MSIX IST priority. |
|
RT_ERROR_INVALID_INGRESS_TIMESTAMPING_RULE (0x200000C7) |
Invalid ingress timestamping rule. |
|
RT_ERROR_INVALID_NONMSIX_IST_IDEAL_PROCESSOR (0x200000C8) |
Invalid non-MSIX IST ideal processor. |
|
RT_ERROR_INVALID_MSIX_NON_QUEUE_MESSAGE_ID (0x200000C9) |
Invalid MSI-X non-queue message ID. |
|
RT_ERROR_INVALID_TX_QUEUE_PRIORITY (0x200000CA) |
Invalid transmit queue sharing thread priority. |
|
RT_ERROR_DUPLICATE_TX_QUEUE_INDEX (0x200000CB) |
Duplicate transmit queue index. |
|
RT_ERROR_INVALID_TX_QUEUE_IDEAL_PROCESSOR (0x200000CC) |
Invalid transmit queue sharing thread ideal processor. |
|
RT_ERROR_INVALID_TX_QUEUE_THREAD_PRIORITY (0x200000CD) |
Invalid transmit queue sharing thread priority. |
|
RT_ERROR_INVALID_TX_QUEUE_MSIX_MESSAGE_ID (0x200000CE) |
Invalid transmit queue MSI-X message ID. |
|
RT_ERROR_INVALID_RX_QUEUE_PRIORITY (0x200000CF) |
Invalid receive queue sharing thread priority. |
|
RT_ERROR_DUPLICATE_RX_QUEUE_INDEX (0x200000D0) |
The receive queue index is a duplicate. |
|
RT_ERROR_INVALID_RX_QUEUE_IDEAL_PROCESSOR (0x200000D1) |
Invalid receive queue sharing thread ideal processor. |
|
RT_ERROR_INVALID_RX_QUEUE_THREAD_PRIORITY (0x200000D2) |
Invalid receive queue sharing thread priority. |
|
RT_ERROR_INVALID_RX_QUEUE_MSIX_MESSAGE_ID (0x200000D3) |
Invalid receive queue MSI-X message ID. |
|
RT_ERROR_DUPLICATE_MSIX_MESSAGE_ID (0x200000D4) |
Duplicate MSI-X message ID. |
|
RT_ERROR_INVALID_MSIX_MESSAGE_IST_IDEAL_PROCESSOR (0x200000D5) |
Invalid MSI-X message IST ideal processor. |
|
RT_ERROR_INVALID_MSIX_MESSAGE_IST_PRIORITY (0x200000D6) |
Invalid MSI-X message IST priority. |
|
RT_ERROR_INCONSISTENT_COUNT_POINTER_PAIR (0x200000D7) |
Array pointer is inconsisent with array element count. |
|
RT_ERROR_DUPLICATE_PCI_BUS_LOCATION (0x200000D8) |
Enabled NL2 interfaces have duplicate PCI Bus Locations. |
|
RT_ERROR_UPPER_LEVEL_PROTOCOL_DLL_NOT_FOUND (0x200000D9) |
Failed to find an upper-level protocol DLL. |
|
RT_ERROR_UPPER_LEVEL_PROTOCOL_FUNCTION_NOT_FOUND (0x200000DA) |
Failed to find upper-level protocol validation function. |
|
RT_ERROR_CONSOLE_CONFIG_TCPPORT_INVALID (0x200000DB) |
The console TCP Port value is invalid. |
|
RT_ERROR_CONSOLE_CONFIG_DISPLAYBUFFERSIZE_INVALID (0x200000DC) |
The console Display Buffer Size value is invalid. |
|
RT_ERROR_CONSOLE_CONFIG_LOGFOLDERMAXSIZE_INVALID (0x200000DD) |
The console Log Folder Max Size value is invalid. |
|
RT_ERROR_MEMORY_CONFIG_PROCESSEXTMSPACEMINIMUMSIZEPOOL_INVALID (0x200000DE) |
The Process External Memory Space Pool Minimum Size value is invalid. |
|
RT_ERROR_MEMORY_CONFIG_PROCESSMSPACEPOOLEXPANDSIZE_INVALID (0x200000DF) |
The Process Memory Space Pool Expand Size value is invalid. |
|
RT_ERROR_MEMORY_CONFIG_SYSTEMEXTMSPACEMINIMUMSIZEPOOL_INVALID (0x200000E0) |
The System External Memory Space Pool Minimum Size value is invalid. |
|
RT_ERROR_MEMORY_CONFIG_SYSTEMMSPACEPOOLEXPANDSIZE_INVALID (0x200000E1) |
The System Memory Space Pool Expand Size value is invalid. |
|
RT_ERROR_MEMORY_CONFIG_SYSTEMINTMSPACEPOOLMINIMUMSIZE_INVALID (0x200000E2) |
The System Internal Memory Space Pool Minimum Size value is invalid. |
|
RT_ERROR_MEMORY_CONFIG_PROCESSINTMSPACEPOOLMINIMUMSIZE_INVALID (0x200000E3) |
The Process Internal Memory Space Pool Minimum Size value is invalid. |
|
RT_ERROR_MONITOR_CONFIG_MTBSIZE_INVALID (0x200000E6) |
The Process Internal Memory Space Pool Minimum Size value is invalid. |
|
RT_ERROR_TOO_MANY_REQUESTED_CORES (0x200000E7) |
The number of requested cores is greater than the allowed number of processors for the current license. |
|
RT_ERROR_SEARCHPATH_TOO_LONG (0x200000E8) |
A SearchPath value contained within the list of paths for the real-time OS is too long. |
|
RT_ERROR_SUBSYSTEM_CONFIG_MBAMODE_NOT_AVAILABLE (0x200000E9) |
The system does not support Intel® Memory Bandwidth Technology (MBA) mode for performance differentiation among RTSS threads. |
|
RT_ERROR_SUBSYSTEM_CONFIG_CATMODE_NOT_AVAILABLE (0x200000EA) |
The system does not support Intel® Cache Allocation Technology (CAT) mode for performance differentiation among RTSS threads. |
|
RT_ERROR_SUBSYSTEM_CONFIG_RDTSTATE_NOT_AVAILABLE (0x200000EB) |
The system does not support Intel® Resource Director Technology (RDT). |
