RDP error details

Follow

When you connecting to remote computer or RDS server, you may run into errors like the following example screenshot. You can lookup the detailed error reason in the following table with the error code shown on the Splashtop Business client app. 

conn-error_en-US.png

 

RDP error table: 

CODE Reason
0x00000AC0 RDP commandline parameters parse error.
0x00000AC1 Failed to load SF related modules
0x00000AC3 Disable access to the destination address in the current rule of ip address restrict.
0x00010001 The disconnection was initiated by an administrative tool on the server in another session.
0x00010002 The disconnection was due to a forced logoff initiated by an administrative tool on the server in another session.
0x00010003 The idle session limit timer on the server has elapsed.
0x00010004 The active session limit timer on the server has elapsed.
0x00010005 Another user connected to the server, forcing the disconnection of the current connection.
0x00010006 The server ran out of available memory resources.
0x00010007 The server denied the connection.
0x00010009 The user cannot connect to the server due to insufficient access privileges.
0x0001000A The server does not accept saved user credentials and requires that the user enter their credentials for each connection.
0x0001000B The disconnection was initiated by an administrative tool on the server running in the user's session.
0x0001000C The disconnection was initiated by the user logging off their session on the server.
0x0001000F The display driver in the remote session did not report any status within the time allotted for startup.
0x00010010 The DWM process running in the remote session terminated unexpectedly.
0x00010011 The display driver in the remote session was unable to complete all the tasks required for startup.
0x00010012 The display driver in the remote session started up successfully, but due to internal failures was not usable by the remoting stack.
0x00010017 The Winlogon process running in the remote session terminated unexpectedly.
0x00010018 The CSRSS process running in the remote session terminated unexpectedly.
0x00010100 An internal error has occurred in the Terminal Services licensing component.
0x00010101 A Remote Desktop License Server ([MS-RDPELE] section 1.1) could not be found to provide a license.
0x00010102 There are no Client Access Licenses ([MS-RDPELE] section 1.1) available for the target remote computer.
0x00010103 The remote computer received an invalid licensing message from the client.
0x00010104 The Client Access License ([MS-RDPELE] section 1.1) stored by the client has been modified.
0x00010105 The Client Access License ([MS-RDPELE] section 1.1) stored by the client is in an invalid format.
0x00010106 Network problems have caused the licensing protocol ([MS-RDPELE] section 1.3.3) to be terminated.
0x00010107 The client prematurely ended the licensing protocol ([MS-RDPELE] section 1.3.3).
0x00010108 A licensing message ([MS-RDPELE] sections 2.2 and 5.1) was incorrectly encrypted.
0x00010109 The Client Access License ([MS-RDPELE] section 1.1) stored by the client could not be upgraded or renewed.
0x0001010A The remote computer is not licensed to accept remote connections.
0x00010400 The target endpoint could not be found.
0x00010402 The target endpoint to which the client is being redirected is disconnecting from the Connection Broker.
0x00010404 An error occurred while the connection was being redirected to the target endpoint.
0x00010405 An error occurred while the target endpoint (a virtual machine) was being awakened.
0x00010406 An error occurred while the target endpoint (a virtual machine) was being started.
0x00010407 The IP address of the target endpoint (a virtual machine) cannot be determined.
0x00010408 There are no available endpoints in the pool managed by the Connection Broker.
0x00010409 Processing of the connection has been cancelled.
0x00010410 The settings contained in the routingToken field of the X.224 Connection Request PDU (section 2.2.1.1) cannot be validated.
0x00010411 A time-out occurred while the target endpoint (a virtual machine) was being started.
0x00010412 A session monitoring error occurred while the target endpoint (a virtual machine) was being started.
0x000110C9 Unknown pduType2 field in a received Share Data Header (section 2.2.8.1.1.1.2).
0x000110CA Unknown pduType field in a received Share Control Header (section 2.2.8.1.1.1.1).
0x000110CB An out-of-sequence Slow-Path Data PDU (section 2.2.8.1.1.1.1) has been received.
0x000110CD An out-of-sequence Slow-Path Non-Data PDU (section 2.2.8.1.1.1.1) has been received.
0x000110CE A Control PDU (sections 2.2.1.15 and 2.2.1.16) has been received with an invalid action field.
0x000110CF (a) A Slow-Path Input Event (section 2.2.8.1.1.3.1.1) has been received with an invalid messageType field.\n(b) A Fast-Path Input Event (section 2.2.8.1.2.2) has been received with an invalid eventCode field.
0x000110D0 (a) A Slow-Path Mouse Event (section 2.2.8.1.1.3.1.1.3) or Extended Mouse Event (section 2.2.8.1.1.3.1.1.4) has been received with an invalid pointerFlags field.\n(b) A Fast-Path Mouse Event (section 2.2.8.1.2.2.3) or Fast-Path Extended Mouse Event (section 2.2.8.1.2.2.4) has been received with an invalid pointerFlags field.
0x000110D1 An invalid Refresh Rect PDU (section 2.2.11.2) has been received.
0x000110D2 The server failed to construct the GCC Conference Create Response user data (section 2.2.1.4).
0x000110D3 Processing during the Channel Connection phase of the RDP Connection Sequence (see section 1.3.1.1 for an overview of the RDP Connection Sequence phases) has failed.
0x000110D4 A Confirm Active PDU (section 2.2.1.13.2) was received from the client with an invalid shareId field.
0x000110D5 A Confirm Active PDU (section 2.2.1.13.2) was received from the client with an invalid originatorId field.
0x000110DA There is not enough data to process a Persistent Key List PDU (section 2.2.1.17).
0x000110DB A Persistent Key List PDU (section 2.2.1.17) marked as PERSIST_PDU_FIRST (0x01) was received after the reception of a prior Persistent Key List PDU also marked as PERSIST_PDU_FIRST.
0x000110DC A Persistent Key List PDU (section 2.2.1.17) was received which specified a total number of bitmap cache entries larger than 262144.
0x000110DD A Persistent Key List PDU (section 2.2.1.17) was received which specified an invalid total number of keys for a bitmap cache (the number of entries that can be stored within each bitmap cache is specified in the Revision 1 or 2 Bitmap Cache Capability Set (section 2.2.7.1.4) that is sent from client to server).
0x000110DE There is not enough data to process Input Event PDU Data (section 2.2.8.1.1.3.1) or a Fast-Path Input Event PDU (section 2.2.8.1.2).
0x000110DF There is not enough data to process the shareDataHeader, NumInfoBlocks, Pad1, and Pad2 fields of the Bitmap Cache Error PDU Data ([MS-RDPEGDI] section 2.2.2.3.1.1).
0x000110E0 (a) The dataSignature field of the Fast-Path Input Event PDU (section 2.2.8.1.2) does not contain enough data.\n(b) The fipsInformation and dataSignature fields of the Fast-Path Input Event PDU (section 2.2.8.1.2) do not contain enough data.
0x000110E1 (a) There is not enough data in the Client Network Data (section 2.2.1.3.4) to read the virtual channel configuration data.\n(b) There is not enough data to read a complete Channel PDU Header (section 2.2.6.1.1).
0x000110E2 (a) There is not enough data to process Control PDU Data (section 2.2.1.15.1).\n(b) There is not enough data to read a complete Share Control Header (section 2.2.8.1.1.1.1).\n(c) There is not enough data to read a complete Share Data Header (section 2.2.8.1.1.1.2) of a Slow-Path Data PDU (section 2.2.8.1.1.1.1).\n(d) There is not enough data to process Font List PDU Data (section 2.2.1.18.1).
0x000110E3 (a) There is not enough data to process Suppress Output PDU Data (section 2.2.11.3.1).\n(b) The allowDisplayUpdates field of the Suppress Output PDU Data (section 2.2.11.3.1) is invalid.
0x000110E5 (a) There is not enough data to read the shareControlHeader, shareId, originatorId, lengthSourceDescriptor, and lengthCombinedCapabilities fields of the Confirm Active PDU Data (section 2.2.1.13.2.1).\n(b) There is not enough data to read the sourceDescriptor, numberCapabilities, pad2Octets, and capabilitySets fields of the Confirm Active PDU Data (section 2.2.1.13.2.1).
0x000110E7 There is not enough data to read the capabilitySetType and the lengthCapability fields in a received Capability Set (section 2.2.1.13.1.1.1).
0x000110E8 A Capability Set (section 2.2.1.13.1.1.1) has been received with a lengthCapability field that contains a value greater than the total length of the data received.
0x000110E9 (a) Both the colorPointerCacheSize and pointerCacheSize fields in the Pointer Capability Set (section 2.2.7.1.5) are set to zero.\n(b) The pointerCacheSize field in the Pointer Capability Set (section 2.2.7.1.5) is not present, and the colorPointerCacheSize field is set to zero.
0x000110EA The capabilities received from the client in the Confirm Active PDU (section 2.2.1.13.2) were not accepted by the server.
0x000110EC An error occurred while using the bulk compressor (section 3.1.8 and [MS-RDPEGDI] section 3.1.8) to decompress a Virtual Channel PDU (section 2.2.6.1)
0x000110ED An invalid bulk compression package was specified in the flags field of the Channel PDU Header (section 2.2.6.1.1).
0x000110EF An invalid MCS channel ID was specified in the mcsPdu field of the Virtual Channel PDU (section 2.2.6.1).
0x000110F0 The client requested more than the maximum allowed 31 static virtual channels in the Client Network Data (section 2.2.1.3.4).
0x000110F3 The INFO_RAIL flag (0x00008000) MUST be set in the flags field of the Info Packet (section 2.2.1.11.1.1) as the session on the remote server can only host remote applications.
0x000110F4 The client sent a Persistent Key List PDU (section 2.2.1.17) without including the prerequisite Revision 2 Bitmap Cache Capability Set (section 2.2.7.1.4.2) in the Confirm Active PDU (section 2.2.1.13.2).
0x000110F5 The NumInfoBlocks field in the Bitmap Cache Error PDU Data is inconsistent with the amount of data in the Info field ([MS-RDPEGDI] section 2.2.2.3.1.1).
0x000110F6 There is not enough data to process an Offscreen Bitmap Cache Error PDU ([MS-RDPEGDI] section 2.2.2.3.2).
0x000110F7 There is not enough data to process a DrawNineGrid Cache Error PDU ([MS-RDPEGDI] section 2.2.2.3.3).
0x000110F8 There is not enough data to process a GDI+ Error PDU ([MS-RDPEGDI] section 2.2.2.3.4).
0x00011111 There is not enough data to read a Basic Security Header (section 2.2.8.1.1.2.1).
0x00011112 There is not enough data to read a Non-FIPS Security Header (section 2.2.8.1.1.2.2) or FIPS Security Header (section 2.2.8.1.1.2.3).
0x00011113 There is not enough data to read the basicSecurityHeader and length fields of the Security Exchange PDU Data (section 2.2.1.10.1).
0x00011114 There is not enough data to read the CodePage, flags, cbDomain, cbUserName, cbPassword, cbAlternateShell, cbWorkingDir, Domain, UserName, Password, AlternateShell, and WorkingDir fields in the Info Packet (section 2.2.1.11.1.1).
0x00011115 There is not enough data to read the CodePage, flags, cbDomain, cbUserName, cbPassword, cbAlternateShell, and cbWorkingDir fields in the Info Packet (section 2.2.1.11.1.1).
0x00011116 There is not enough data to read the clientAddressFamily and cbClientAddress fields in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011117 There is not enough data to read the clientAddress field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011118 There is not enough data to read the cbClientDir field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011119 There is not enough data to read the clientDir field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x0001111A There is not enough data to read the clientTimeZone field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x0001111B There is not enough data to read the clientSessionId field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x0001111C There is not enough data to read the performanceFlags field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x0001111D There is not enough data to read the cbAutoReconnectLen field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x0001111E There is not enough data to read the autoReconnectCookie field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x0001111F The cbAutoReconnectLen field in the Extended Info Packet (section 2.2.1.11.1.1.1) contains a value which is larger than the maximum allowed length of 128 bytes.
0x00011120 There is not enough data to read the clientAddressFamily and cbClientAddress fields in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011121 There is not enough data to read the clientAddress field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011122 There is not enough data to read the cbClientDir field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011123 There is not enough data to read the clientDir field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011124 There is not enough data to read the clientTimeZone field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011125 There is not enough data to read the clientSessionId field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011126 There is not enough data to read the Client Info PDU Data (section 2.2.1.11.1).
0x00011129 The monitorCount field in the Client Monitor Data (section 2.2.1.3.6) is invalid.
0x0001112A The server-side decompression buffer is invalid, or the size of the decompressed VC data exceeds the chunking size specified in the Virtual Channel Capability Set (section 2.2.7.1.10).
0x0001112B The size of a received Virtual Channel PDU (section 2.2.6.1) exceeds the chunking size specified in the Virtual Channel Capability Set (section 2.2.7.1.10).
0x0001112C There is not enough data to read a TS_FRAME_ACKNOWLEDGE_PDU ([MS-RDPRFX] section 2.2.3.1).
0x0001112D The graphics mode requested by the client is not supported by the server.
0x0001112E The server-side graphics subsystem failed to reset.
0x0001112F The server-side graphics subsystem is in an error state and unable to continue graphics encoding.
0x00011130 There is not enough data to read the cbDynamicDSTTimeZoneKeyName field in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011131 The length reported in the cbDynamicDSTTimeZoneKeyName field of the Extended Info Packet (section 2.2.1.11.1.1.1) is too long.
0x00011132 The dynamicDaylightTimeDisabled field is not present in the Extended Info Packet (section 2.2.1.11.1.1.1).
0x00011133 An error occurred when processing dynamic virtual channel data ([MS-RDPEDYC] section 3.3.5).
0x00011134 The width or height of the virtual desktop defined by the monitor layout in the Client Monitor Data (section 2.2.1.3.6) is larger than the maximum allowed value of 32,766.
0x00011135 The monitor geometry defined by the Client Monitor Data (section 2.2.1.3.6) is invalid.
0x00011136 The monitorCount field in the Client Monitor Data(section 2.2.1.3.6) is too large.
0x00011191 An attempt to update the session keys while using Standard RDP Security mechanisms (section 5.3.7) failed.
0x00011192 (a) Decryption using Standard RDP Security mechanisms (section 5.3.6) failed.\n(b) Session key creation using Standard RDP Security mechanisms (section 5.3.5) failed.
0x00011193 Encryption using Standard RDP Security mechanisms (section 5.3.6) failed.
0x00011194 Failed to find a usable Encryption Method (section 5.3.2) in the encryptionMethods field of the Client Security Data (section 2.2.1.4.3).
0x00011195 Unencrypted data was encountered in a protocol stream which is meant to be encrypted with Standard RDP Security mechanisms (section 5.3.6).
0x00011196 The peer connection was lost.
0x00020001 A configuration error prevented a connection to be established.
0x00020002 A undefined connection error occurred.
0x00020003 The connection attempt was aborted due to post connect configuration errors.
0x00020004 The DNS entry could not be resolved.
0x00020005 The DNS host name was not found.
0x00020006 The connection failed.
0x00020007 The connection failed at initial MCS connect
0x00020008 The connection failed at TLS connect.
0x00020009 An authentication failure aborted the connection.
0x0002000A Insufficient privileges to establish a connection.
0x0002000B The connection was cancelled.
0x0002000C The connection failed at negotiating security settings.
0x0002000D The connection transport layer failed.
0x0002000E The password has expired and must be changed.
0x0002000F The password has certainly expired and must be changed.
0x00020010 The client has been revoked.
0x00020011 The KDC is unreachable.
0x00020012 The account is disabled.
0x00020013 The password must be changed.
0x00020014 Logon failed.
0x00020015 Wrong password supplied.
0x00020016 Access denied.
0x00020017 Account restriction.
0x00020018 Account locked out.
0x00020019 Account expired.
0x0002001A Logon type not granted.
0x0002001B Credentials invalid or missing.
0 out of 0 found this helpful