Windows / Modules / mstscax.dll
mstscax.dll
Remote Desktop Client API
Associated Error Codes
Below lists error codes and symbolic names found for this module.
Code | Description |
---|---|
0x00007256 | top Client API 0x10000009 Access Denied |
0x1000000A | Client has disconnected |
0x1000000B | Authentication Failure |
0x1000000C | Failed to get a license |
0x1000000D | Operation has timed out |
0x1000000E | Invalid State |
0x1000000F | Connection to gateway server failed |
0x10000010 | Network Unavailable |
0x10000011 | DNS resolution failure |
0x10000012 | Sign verification failed |
0x10000013 | Resource check failed |
0x10000014 | Logon failed |
0x30000000 | Info |
0x3000000A | This event is raised during the connection process |
0x3000000B | This event is raised during the disconnection process |
0x3000000C | This event is raised during the authentication process |
0x3000000D | This event is raised while trying to automatically reconnect to the server |
0x3000000E | This event is raised during resolving the server name |
0x3000000F | This event is raised while trying to get a valid license |
0x30000010 | This event is raised in the gateway transport |
0x30000011 | This event is raised when data is received from the server |
0x30000012 | This event is raised when data is sent to the server |
0x30000013 | This event is raised during a state transition. |
0x30000014 | This event is raised when the client has not been shutdown cleanly. |
0x30000015 | This event is raised when the user tries to sign out from the OOB client. |
0x30000016 | This event is raised when the user manually tries to do feed refresh. |
0x30000017 | This event is raised when the user tries to login in ADAL page using different user name. |
0x30000018 | This event is raised when a workspace event like subscribe/update succeeded. |
0x30000019 | This event is raised when a workspace event like subscribe/update failed! |
0x3000001A | This event is raised when feed discovery succeeds |
0x3000001B | This event is raised when feed discovery failed! |
0x3000001C | This event is raised when the feed cache on the client local machine is missing icons or Rdp files due to cache corruption! |
0x3000001D | This event is raised when user has successfully updated the consent status on server side |
0x3000001E | This event is raised when user is unable to update the consent status on server! |
0x3000001F | This event is raised when the client first launches. |
0x30000020 | This event is raised when the user manually clicks the view invitations button. |
0x30000021 | This event is raised when the user starts a new cycle of feed discovery. We log the hashed UPN and timezone information here |
0x30000022 | This event is raised when all the feeds of the user have been subscribed or updated completely. We log the overall time it took to download all feeds in parallel. |
0x30000023 | This event is raised when there is a close operation which will tear down the connection. |
0x30000024 | This event is raised when protocol caps are received from the server. We log the version selected, and the client mode and AVC capability. |
0x30000025 | This event is raised when protocol caps are received from the server. We log that hardware resources are being used. |
0x30000026 | This event is raised when protocol caps are received from the server. We log that hardware resources are not being used. |
0x30000027 | This event is raised when there is error in acquiring ADAL token. |
0x30000028 | This event is raised when ADAL authentication token is successfully created. |
0x30000029 | This event is raised when ADAL authentication is cancelled. |
0x3000002C | This event is raised if a pipeline error is encountered during execution. We log the faulting component, function, and error code. |
0x3000002F | This is a generic event that may be raised by the client. |
0x30000030 | This is a generic error that may be signaled by the client. |
0x50000002 | Error |
0x50000003 | Warning |
0x50000004 | Information |
0x50000005 | Verbose |
0x70000064 | General |
0x70000065 | Connection Sequence |
0x70000066 | Automatic Reconnection Sequence |
0x70000067 | Gateway Connection Sequence |
0x70000068 | RDP State Transition |
0x70000069 | RdClient RADC workspace |
0x7000006A | RdClient Pipeline workspace |
0x90000001 | Microsoft-Windows-TerminalServices-ClientActiveXCore |
0x90000002 | Application |
0xB00000E1 | %1: Transitioned successfully from %3 to %5 in response to %7. |
0xB00000E2 | %1: An error was encountered when transitioning from %3 to %5 in response to %7 (error code %8). |
0xB00000E3 | %1: MCS Channel Join Confirmation received: ChannelID = %2, ChannelName = %3. |
0xB00003E9 | RDP ClientActiveX is trying to connect to the server (%2) |
0xB00003EA | RDP ClientActiveX has connected to the server |
0xB00003EB | RDP ClientActiveX has been disconnected (Reason= %2) |
0xB00003EC | Client has logged on to the server (SessionId = %2) |
0xB00003ED | Client failed to logon on to the server (Error = %2) |
0xB00003EE | Client machine has lost network connectivity (Reason= %2) |
0xB00003EF | DNS failed to resolve the server name (Error= %2) |
0xB00003F0 | The credentials provided are authenticated by the server |
0xB00003F1 | The credentials provided were failed to be authenticated by the server |
0xB00003F2 | RDP ClientActiveX is connecting to a gateway server (%1=%2) |
0xB00003F3 | RDP ClientActiveX succeeded in connecting to the gateway server |
0xB00003F4 | RDP ClientActiveX failed to connect to the gateway server(Error= %2) |
0xB00003F5 | RDP ClientActiveX is trying to automatically reconnect to the server (%2) |
0xB00003F6 | RDP ClientActiveX succeeded in automatically connecting to the server |
0xB00003F7 | RDP ClientActiveX failed to automatically connect to the server (Reason= %1) |
0xB00003F8 | Client has a license to connect to the server |
0xB00003F9 | Client does not have a license to connect to the server (Error= %2) |
0xB00003FA | RDP ClientActiveX failed to connect to the server (Error = %2) |
0xB00003FB | %1 |
0xB00003FC | RDP ClientActiveX has recorded the following error - %2. Check Details. |
0xB00003FD | RDP ClientActiveX's gateway transport has recorded the following error - %2. Check Details. |
0xB00003FE | %1 |
0xB00003FF | RDP Client ActiveX has started using RemoteFX for graphics decoding (decoder type = %2) |
0xB0000403 | Connected to domain (%1) with session %2. |
0xB0000404 | Server supports SSL = %1 |
0xB0000405 | Base64(SHA256(UserName)) is = %1 |
0xB0000406 | RDP Client build %1 %2 %3 %4 %5 |
0xB0000407 | Invalid format error occured when decoding packet of type %1 |
0xB0000408 | Component name:%1, :: %2 |
0xB0000409 | Component name:%1, :: %2, Error code:%3 |
0xB000040A | Component name:%1, :: %2 |
0xB000044C | The client detected the link latency is %2 milliseconds. |
0xB000044D | The client detected the bandwidth is %2 kbps/second. |
0xB000044E | The client has initiated a multi-transport connection to the server %2. |
0xB000044F | The client has established a multi-transport connection to the server. |
0xB0000450 | The client failed to establish the multi-transport connection. |
0xB0000451 | The multi-transport connection has been disconnected. |
0xB0000452 | Close event, code = %1. |
0xB0000453 | Disconnect trace:%1 "%2", Error code:%3 |
0xB00004B1 | The RdClient has been forced exit since cancelling existing workspace job took too long. |
0xB00004B2 | The user has clicked sign out on the OOB Client ribbon. |
0xB00004B3 | The user has clicked Refresh on the OOB client ribbon. |
0xB00004B4 | The user tried to login into ADAL with a different user name than the one he/she subscribed to initially. |
0xB00004B5 | %1: Workspace Event succeeded for Tenant = %2 , TotalTimeWithoutAdal = %3 ms, AdalTime = %4 ms. NumberOfResources = %5 |
0xB00004B6 | %1: Workspace Event failed for Tenant = %2. , TotalTimeWithoutAdal = %3 ms, AdalTime = %4 ms. (Error code %5) |
0xB00004B8 | Feed discovery succeeded. TotalTimeWithoutAdal = %1 ms, AdalTime = %2 ms, NumberOfFeeds = %3 |
0xB00004B9 | Feed discovery failed. TotalTimeWithoutAdal = %1 ms, AdalTime = %2 ms. (Error code = %3) |
0xB00004BA | Feed cache corruption encountered. Tenant = %1, ResourceId = %2, ResourceType = %3, (Error code %4). |
0xB00004BB | Consent status updated successfully. TotalTimeWithoutAdal = %1, AdalTime = %2. |
0xB00004BC | Consent status update failed. TotalTimeWithoutAdal = %1, AdalTime = %2. (Error code %3) |
0xB00004BD | The user has clicked view invitations on the OOB client ribbon. |
0xB00004BE | Base64(SHA256(UserName)) = %1, TimeZone Bias = %2, TimeZone Name = %3. |
0xB00004BF | Refresh Time = %1, Number of feeds = %2. |
0xB00004C0 | ADAL error code = %1, description = %2 |
0xB00004C1 | ADAL token collected successfully |
0xB00004C2 | ADAL cancelled |
0xB00004CB | %1 entering stage %2 |
0xB00004CC | %1 with http event type %2 |
0xB00004CD | %1 with http event type %2 and http status code %3 |
0xB00004CE | %1 with http event type %2 failed with xresult %3 |
0xB0000579 | The server is using version %1 of the RDP graphics protocol (client mode: %2, AVC available: %3). |
0xB000057A | The client is using hardware memory for the frame buffer. |
0xB000057B | The client is using software memory for the frame buffer. |
0xB000057C | The client encountered an issue while decoding and displaying RDP graphics (component: %1, function: %2, error code: %3) |
0xB00005DD | %1 |
0xB00005DE | %1 |
0xB00005DF | %1 |
131 entries |