Toggle navigation
hresult
Home
/
Facilities
/
FACILITY_DRT
/
0x8062210D
Error 0x8062210D
Value: -2141052659 | 0x8062210D | 2153914637
What does it mean ?
DRT_E_INVALID_INSTANCE_PREFIX
The DRT instance prefix is invalid.
Value: 8461 | 0x210D | 0b0010000100001101
Where does it come from ?
FACILITY_DRT
Microsoft Distributed Routing Table
Value: 98 | 0x062 | 0b01100010
StackOverflow
{{ item.title | htmlDecode}}
Other Errors for FACILITY_DRT
0x8062210B
- DRT_E_TRANSPORT_STILL_BOUND
0x8062200E
- DRT_E_BOOTSTRAPPROVIDER_IN_USE
0x80622000
- DRT_E_INVALID_PORT
0x80622008
- DRT_E_NO_ADDRESSES_AVAILABLE
0x80622102
- DRT_E_TRANSPORT_NOT_BOUND
0x80621007
- DRT_E_INVALID_MAX_ADDRESSES
0x8062210E
- DRT_E_INVALID_SECURITY_MODE
0x8062210C
- DRT_E_INSUFFICIENT_BUFFER
0x8062200B
- DRT_E_TRANSPORTPROVIDER_NOT_ATTACHED
0x80621011
- DRT_E_INVALID_MAX_ENDPOINTS
0x80622108
- DRT_E_INVALID_SETTINGS
0x80622006
- DRT_E_INVALID_SCOPE
0x80622106
- DRT_E_TRANSPORT_EXECUTING_CALLBACK
0x80621009
- DRT_E_INVALID_KEY
0x80621004
- DRT_E_INVALID_CERT_CHAIN
0x80622107
- DRT_E_TRANSPORT_ALREADY_EXISTS_FOR_SCOPE
0x8062200F
- DRT_E_BOOTSTRAPPROVIDER_NOT_ATTACHED
0x80622105
- DRT_E_TRANSPORT_NO_DEST_ADDRESSES
0x80622007
- DRT_E_TRANSPORT_SHUTTING_DOWN
0x80621002
- DRT_E_INVALID_KEY_SIZE