RTX64 Error Codes
This topic lists the custom error codes that can be returned by Real-Time and Native Library APIs in RTX64.
| Error Code | Description |
|---|---|
|
RT_ERROR_INTERNAL_X |
Internal error, where X is an internal Subsystem error code. |
|
RT_ERROR_NO_RUNTIME_LICENSE 536870913 (0x20000001) |
No RTX64 Runtime license is available. |
|
RT_ERROR_EXPIRED_RUNTIME_LICENSE 536870914 (0x20000002) |
The RTX64 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 RTX64 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 RTX64 SDK license. It cannot be executed when the RTX64 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 RTX64 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 an RTX64 SDK version that is incompatible with the current RTX64 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 RTX64 Subsystem was unable to communicate with the required services. |
|
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 RTX64 subsystem needs to be restarted for a configuration change to take effect. |
|
RT_ERROR_SUBSYSTEM_NOT_CONFIGURED 536870938 (0x2000001a) |
The RTX64 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_NO_STACK_LICENSE 536870941 (0x2000001d) |
The RTX64 TCP/IP stack has no license, but an operation was attempted that requires // it to be licensed. |
|
RT_ERROR_SUBSYSTEM_STARTSTOP_LOCK_FAILURE 536870942 (0x2000001e) |
An operation failed to acquire the mutex that serializes starting/stopping the RTX64 subsystem. |
|
RT_ERROR_TIMEOUT_STARTING_SUBSYSTEM 536870943 (0x2000001f) |
A timeout occurred while attempting to start the RTX64 subsystem. |
|
RT_ERROR_TIMEOUT_STOPPING_SUBSYSTEM 536870944 (0x20000020) |
A timeout occurred while attempting to stop the RTX64 subsystem. |
|
RT_ERROR_TIMEOUT_STARTING_NETWORK 536870945 (0x20000021) |
A timeout occurred while attempting to start the RTX64 TCP/IP stack. |
|
RT_ERROR_SUBSYSTEM_NOT_STARTED 536870948 (0x20000024) |
The RTX64 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_NETWORK_STARTSTOP_LOCK_FAILURE 536870952 (0x20000028) |
An operation failed to acquire the mutex that serializes starting/stopping the RTX64 TCP/IP stack. |
|
RT_ERROR_NETWORK_STOPPED 536870953 (0x20000029) |
The RTX64 TCP/IP stack is stopped. |
|
RT_ERROR_NETWORK_STARTED 536870954 (0x2000002a) |
The RTX64 TCP/IP stack is running. |
|
RT_ERROR_NETWORK_NOT_INSTALLED 536870956 (0x2000002c) |
An operation was attempted that requires the RTX64 TCP/IP stack to be installed, but it is not installed. |
|
RT_ERROR_NETWORK_CLIENTS_EXIST 536870958 (0x2000002e) |
The RTX64 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 RTX64 TCP/IP stack and NAL 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_ALREADY_ENABLED 536870962 (0x20000032) |
Monitoring is already enabled. |
|
RT_ERROR_MONITORING_ALREADY_DISABLED 536870963 (0x20000033) |
Monitoring is already disabled. |
|
RT_ERROR_MONITORING_ALREADY_STARTED 536870964 (0x20000034) |
Monitoring is already started. |
|
RT_ERROR_MONITORING_ALREADY_STOPPED 536870965 (0x20000035) |
Monitoring is already stopped. |
|
RT_ERROR_MONITORING_IS_STARTED 536870966 (0x20000036) |
Monitoring cannot be disabled, because it is started. |
|
RT_ERROR_MONITORING_NOT_ENABLED 536870967 (0x20000037) |
Monitoring cannot be started, paused, or resumed, because it is not enabled. |
|
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 RTX64 TCP/IP stack. |
|
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 RTX64 subsystem consistency. |
|
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 PCI BUS location 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_LINKSTATUSIDEALPROCESSOR_INVALID 536870994 (0x20000052) |
Network interface configuration LinkStatusIdealProcessor 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_LINK_STATUS_INVALID 536871001 (0x20000059) |
Network interface configuration link status property is invalid. |
|
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 an RTX64 Registry key or value. |
|
RT_ERROR_SCHEDULED_PROCESS_LOCK_FAILURE 536871005 (0x2000005d) |
An operation failed to acquire the mutex that serializes scheduled process operations. |
|
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_NAL_PROCESS_ALREADY_LOADED 536871013 (0x20000065) |
Cannot start a new instance of the NAL since it is already loaded. |
|
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_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_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_RTX64_BOOT_CONFIG 536871026 (0x20000072) |
The System is not currently booted from the RTX64 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_RTX64_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_INVALID_STATE_TRANSITION 536871029 (0x20000075) |
Monitoring cannot transition from the current state to the requested state. |
|
RT_ERROR_MONITORING_ALREADY_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_NAL_STARTED 536871039 (0x2000007f) |
The RTX64 NAL is started. |
|
RT_ERROR_TIMEOUT_STARTING_NAL 536871040 (0x20000080) |
Timeout starting NAL. The state of the NAL may change after this error has been generated. |
|
RT_ERROR_NAL_TERMINATED_UNEXPECTEDLY 536871041 (0x20000081) |
NAL process terminated unexpectedly. |
|
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 NAL or TCPIP 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_TIMEOUT_STOPPING_NAL 536871051 (0x2000008b) |
Timeout stopping NAL. The state of the NAL may change after this error has been generated. |
|
RT_ERROR_NAL_STOPPED 536871052 (0x2000008c) |
The RTX64 NAL is stopped. |
|
RT_ERROR_NAL_CLIENTS_EXIST 536871053 (0x2000008d) |
Cannot stop the NAL because NAL clients are running. |
|
RT_ERROR_TCPIP_CLIENTS_EXIST 536871054 (0x2000008e) |
Cannot stop the RT-TCP/IP because Stack clients are running. |
|
RT_ERROR_TIMEOUT_QUERYING_NAL_STATUS 536871055 (0x2000008f) |
A timeout occurred while querying NAL status. |
|
RT_ERROR_TIMEOUT_QUERYING_TCPIP_STATUS 536871056 (0x20000090) |
A timeout occurred while querying TCPIP status. |
|
RT_ERROR_TIMEOUT_QUERYING_INTERFACE_STATUS 536871057 (0x20000091) |
A timeout occurred while querying network interface status. |
|
RT_ERROR_TIMEOUT_QUERYING_NAL_CLIENT_PIDS 536871058 (0x20000092) |
A timeout occurred while querying NAL client process IDs. |
|
RT_ERROR_TIMEOUT_QUERYING_TCPIP_CLIENT_PIDS 536871059 (0x20000093) |
A timeout occurred while querying TCPIP client process IDs. |
|
RT_ERROR_INVALID_NAL_THREAD_PRIORITY 536871060 (0x20000094) |
Invalid NAL thread priority. |
|
RT_ERROR_TOO_MANY_NAL_CLIENTS 536871061 (0x20000095) |
Cannot initialize more NAL clients. The maximum number of NAL clients is 2048. |
|
RT_ERROR_TCPIP_STACK_TERMINATED_UNEXPECTEDLY 536871062 (0x20000096) |
The RTX64 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 RTX64 TCP/IP stack to be restarted for configuration changes to take effect. |
|
RT_ERROR_TCPIP_STACK_FATAL_ERROR 536871065 (0x20000099) |
Fatal error in the RTX64 TCP/IP stack. |
|
RT_ERROR_STACK_NOT_INSTALLED 536871066 (0x2000009a) |
The RTX64 TCP/IP stack is not installed. |
|
RT_ERROR_STACK_STARTED 536871067 (0x2000009b) |
The RTX64 TCP/IP stack is already started. |
|
RT_ERROR_STACK_STOPPED 536871068 (0x2000009c) |
The RTX64 TCP/IP stack is already stopped. |
|
RT_ERROR_STACK_STOP_TIMEOUT 536871069 (0x2000009d) |
The RTX64 TCP/IP stack timed out while trying to stop. |
|
RT_ERROR_INTERFACE_NOT_CONVERTED 536871071 (0x2000009f) |
Network interface is not converted to RTX64. |
|
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) |
TCPIP 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_NALDISPATCHIDEALPROCESSOR_INVALID 536871079 (0x200000a7) |
The NAL dispatch thread's ideal processor is invalid. |
|
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_TIMEOUT_STOPPING_DEBUGGER_LISTEN 536871084 (0x200000ac) |
The remote debugger did not stop listening after being given the command to stop. |
|
RT_ERROR_TIMEOUT_STARTING_DEBUGGER_LISTEN 536871085 (0x200000ad) |
The remote debugger did not start listening after being given the command to start. |
|
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_TCPIP_HEAP_MSPACE_INVALID 536871089 (0x200000b1) |
The TCP/IP MSpace size must be at least 2176 KB larger than the TCP/IP Memory configuration parameter when auto-expand of the TCP/IP MSpaces is disabled. |
|
RT_ERROR_DUPLICATE_IPV6 536871090 (0x200000b2) |
A duplicate IPv6 address was found. |
|
RT_ERROR_TIMEREXECUTEPRIORITY_INVALID 536871091 (0x200000b3) |
The TCP/IP stack's timer execute priority value is invalid. |
|
RT_ERROR_MTBSIZE_INVALID 536871092 (0x200000b4) |
The MTBSize for monitoring is invalid. |
|
RT_ERROR_MONLOGSIZE_INVALID 536871093 (0x200000b5) |
The monitoring log size is invalid. |
|
RT_ERROR_SPEED_DUPLEX_INVALID 536871094 (0x200000b6) |
Network interface field Speed Duplex is invalid. |
|
RT_ERROR_IPV4_HOST_ID_INVALID 536871095 (0x200000b7) |
Network interface Host ID is invalid. |
|
RT_ERROR_IPV4_NETWORK_ID_INVALID 536871096 (0x200000b8) |
Network interface Network ID is invalid. |
|
RT_ERROR_MAXPACKETSIZE_TOO_LARGE 536871098 (0x200000ba) |
Network interface maximum packet larger than supported. |
|
RT_ERROR_TCPIP_PRIORITY_RELATION_INVALID 536871099 (0x200000bb) |
TCP/IP configuration parameter Timer Priority must be less than configuration parameter Timer Execute Priority. |
|
RT_ERROR_DUPLICATE_NETWORK_DEVICE 536871101 (0x200000bd) |
A network interface was found that uses the same device. |
