msra.exe
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x3 | 78.11011 | Application will terminate, a critical error was detected in %1 Line %2 Function %3 |
| 0x30000000 | 78.11011 | Info |
| 0x30000002 | 78.11011 | Stop |
| 0x50000001 | 78.11011 | Critical |
| 0x50000002 | 78.11011 | Error |
| 0x50000005 | 78.11011 | Verbose |
| 0x90000001 | 78.11011 | Microsoft-Windows-RemoteAssistance |
| 0x90000002 | 78.11011 | Application |
| 0xb0000001 | 78.11011 | Entering function %1 |
| 0xb0000002 | 78.11011 | Leaving function %1 |
| 0xb0000004 | 78.11011 | Hit exception block of code at %1 Line %2 in function %3 |
| 0xb0000005 | 78.11011 | Branching on Line:%2 File:%1 with the string %3 |
| 0xb0000006 | 78.11011 | Switching on Line:%2 File:%1 with the value %3 |
| 0xb0000007 | 78.11011 | Entering conditional block at Line:%1 File:%2 |
| 0xb0000008 | 78.11011 | Exiting conditional block at Line:%1 File:%2 |
| 0xb0000009 | 78.11011 | There was a problem interacting with COM object %1. An outdated version might be installed, or the component might not be installed at all. |
| 0xb000000a | 8.11011 | A user tried to use Remote Assistance and send an invitation for help through their default email client, but Remote Assistance failed to successfully send the invitation. It is possible the email client configured as the default client does not support SMAPI calls, or that the email client is improperly configured. It is also possible that the user closed the email client without sending the message. |
| 0xb000000b | 78.11011 | A user opened a Remote Assistance invitation, but the invitation was closed due to too many bad password attempts to connect to the machine. |
| 0xb000000c | 78.11011 | A user tried to use Remote Assistance, group policy requires a session log to be maintained, and a session log couldn't be created. Remote Assistance was terminated. Check the disk to see if there are problems with the disk or if it is full. |
| 0xb000000d | 78.11011 | Remote Assistance started with: %1 as the command line parameters. |
| 0xb000000e | 78.11011 | A Remote Assistance Invitation was successfully opened. |
| 0xb000000f | 78.11011 | An RDP connection was successfully made. |
| 0xb0000010 | 78.11011 | The Remote Assistance password was verified. The Remote Assistance session has begun. |
| 0xb0000011 | 78.11011 | The Remote Assistance password provided was incorrect. The RDP session was terminated. |
| 0xb0000012 | 78.11011 | The Remote Assistance session was disconnected remotely. |
| 0xb0000013 | 78.11011 | The Remote Assistance session was disconnected locally. |
| 0xb0000014 | 78.11011 | The Remote Assistance invitation was closed, any information concerning it given out is now invalid. |
| 0xb0000015 | 78.11011 | The helper is sharing control. |
| 0xb0000016 | 78.11011 | The helper can now view the screen. |
| 0xb0000017 | 78.11011 | Remote Assistance detected that it didn't restore the background and screen settings before shutting down. An attempt was made to restore these settings. |
| 0xb0000018 | 78.11011 | The time limit of offered invitations has been reached. |
| 0xb0000019 | 78.11011 | User setting value currently applied is %1 |
| 0xb000001a | 78.11011 | The system or GP settings do not allow an Remote Assistance invitation to be created. This action has been blocked by the application. |
| 0xb000001b | 78.11011 | The system or GP settings do not allow a helper to share control. This action has been blocked by the application. |
| 0xb000001c | 78.11011 | The Windows firewall has been checked and it appears that it is configured so that it will stop Remote Assistance from working. |
| 0xb000001d | 78.11011 | The error message: %1 has been shown to the user. |
| 0xb000001e | 78.11011 | Remote Assistance has ended. |
| 0xb000001f | 78.11011 | Remote Assistance COM server has started. |
| 0xb0000020 | 78.11011 | Remote Assistance COM server has ended. |
| 0xb0000021 | 78.11011 | The Remote Assistance ticket contained the following IP addresses: %1 |
| 0xb0000022 | 78.11011 | A PNRP Node was created at the following address: %1 |
| 0xb0000023 | 78.11011 | The following PNRP clouds were detected: %1 |
| 0xb0000024 | 78.11011 | A PNRP Node was released at the following address: %1 |
| 0xb0000025 | 78.11011 | Started looking for PNRP node with the following address: %1 |
| 0xb0000026 | 78.11011 | Stopped looking for PNRP node, address: %1 |
| 0xb0000027 | 78.11011 | There was a problem interacting with the PNRP service. This component might not be installed correctly. The error code received was: %1 |
| 0xb0000028 | 78.11011 | Diagnosis Repro Attempt resulted in a success. |
| 0xb0000029 | 78.11011 | Diagnosis Repro Attempt resulted in a failure. |
| 0xb000002a | 78.11011 | Current time on NTP Server: %1 |
| 0xb000002b | 78.11011 | Remote Assistance troubleshooting rejected problem %1. |
| 0xb000002c | 78.11011 | Remote Assistance troubleshooting has confirmed the problem: %1. |
| 0xb000002d | 78.11011 | Remote Assistance troubleshooting is starting to repair the identified problem: %1. |
| 0xb000002e | 78.11011 | Remote Assistance troubleshooting successfully repaired the problem: %1. |
| 0xb000002f | 78.11011 | Remote Assistance troubleshooting failed to repair the problem: %1. |
| 0xb0000064 | 78.11011 | Remote OS Type : %1. |
| 0xb0000065 | 78.11011 | Remote Assistance connection attempt failed with error code: %1. |
| 0xb0000066 | 78.11011 | Remote Assistance reproduced the problem and created following ticket to verify the problem: %1. |
| 0xb0010011 | 78.11011 | The Remote Assistance password provided was incorrect. The RDP session was terminated, IP address of the connecting machine is %1 |
| 0xb000000a | 7 | A user tried to use Remote Assistance and send an invitation for help through their default e-mail client, but Remote Assistance failed to successfully send the invitation. It is possible the e-mail client configured as the default client does not support SMAPI calls, or that the e-mail client is improperly configured. It is also possible that the user closed the e-mail client without sending the message. |
| 59 entries | ||