- Remove From My Forums
-
Question
-
Hi
I am attempting to replace our Citrix XenApp with TS now that packaged applications are available. I have added an application to the RemoteApp programs list and then created the .rdp from that. However, if I click on the .rdp file from a client PC I get the error: «Access is Denied. This initial program cannot be started: C:windowssystem32rdpinit.exe.»
If I change the setting on the Terminal Server to «Allow users to start both listed and unlisted programs on initial connection» then it works. I can’t understand why if I turn it back to «Do not allow users to run unlisted apps» it fails to start, even though my application IS listed.
I don’t have to list rdpinit.exe and rdpshell.exe as listed apps too??
Thanks for any help.
Answers
-
Hi,
Based on out database, this was a bug of Windows Server 2008 Beta. Please help to collect more information for research.
1. Open IE, visit http://TSSERVERNAME/TS, try to launch RemoteApp, is there any error?
2. If so, please help to collect MPS For research.
1) Download proper MPS Report tool from the website below.
Microsoft Product Support Reports
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-88B7-F9C79B7306C0&displaylang=en
2) Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the «Select the diagnostics you want to run» page appears, select «General», «Server Components», click Next.
3) After collecting all log files, choose «Save the results», choose a folder to save <Computername>MPSReports.cab file. Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give us the download address.
Thanks
This posting is provided «AS IS» with no warranties, and confers no rights.
-
Marked as answer by
Wednesday, September 2, 2009 7:59 AM
-
Marked as answer by
Symptoms
Consider the following scenario:
-
You run a Windows Embedded Compact 7-based image on a touch screen device.
-
You use Remote Desktop Protocol (RDP) to connect the device to a remote computer.
-
You double-tap the icon of an application on the remote computer in the RDP session.
In this scenario, the application does not start.
Cause
This issue occurs because consecutive taps are not recognized as double-taps or double-clicks by the remote computer. Specifically, the tap coordinates that are sent from the Windows Embedded Compact 7-based RDP client are not close enough to qualify as double-taps or double-clicks.
Note This issue occurs almost exclusively on touch screen devices on which the precision of touch is less accurate.
Resolution
To resolve this issue, apply the following update.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
By default, this update is disabled after you apply it. To enable the update, set the DWORD value of the EnableDoubleClickDetect registry entry to 1. By default, the EnableDoubleClickDetect DWORD value does not exist, and you must create it in the following registry subkey:
HKEY_LOCAL_MACHINESoftwareMicrosoftTerminal Server Client
This update uses the values of the DblTapDist and DblTapTime settings. These values specify the time and space threshold settings that define consecutive taps or clicks as double-taps or double-clicks. The default value for the DblTapDist setting is 20 pixels, and the default value for the DblTapTime setting is 600 milliseconds. You can optimize these settings for platforms that require more accurate tap or click precision. To optimize these settings, change the DWORD value of the following two registry entries:
-
HKEY_CURRENT_USERControlPanelPendblTapDist
-
HKEY_CURRENT_USERControlPanelPendblTapTime
Note By default, these registry entries are not present, and you must create them.
Known issue
After you enable this update, consecutive taps or clicks still do not work as intended in an application if the following conditions are true:
-
The application is running on the RDP server.
-
You want to perform consecutive taps or clicks that are within the values of the DblTapDist andDblTapTime settings in the application.
-
You do not want the consecutive taps or clicks to be considered as a double-click.
For example, you want to click two times (such as when you draw two dots in a Microsoft Paint application). The distance between these clicks is less than the value of the DblTapDist setting, and the time between the clicks is less than the value of the DblTapTime setting. In this case, when the EnableDoubleClickDetect value is set, the two clicks are considered as a double-click (or a drag motion in the Microsoft Paint application), instead of the two single clicks that you intended.
Software update information
Download information
The Windows Embedded Compact 7 Monthly Update (February 2013) is now available from Microsoft. To download this Windows Embedded Compact 7 Monthly Update, go to the following Microsoft Download Center website:
Windows Embedded Compact 7 updatesThe kind of processor that each file applies to is visible in the name of each file in the «File information» section.
Prerequisites
This update is supported only if all previously issued updates for this product have also been installed.
Restart requirement
After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
-
On the Build menu, click Clean Solution, and then click Build Solution.
-
On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.
Update replacement information
This update does not replace any other updates.
The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Files that are included in this hotfix package
File name |
File size |
Date |
Time |
Path |
---|---|---|---|---|
Tscaxctrl.lib |
33,719,550 |
13-Feb-2013 |
22:35 |
PublicRdpOakLibArmv5Checked |
Tscaxctrl.lib |
34,558,602 |
13-Feb-2013 |
22:33 |
PublicRdpOakLibArmv5Debug |
Tscaxctrl.lib |
25,346,982 |
13-Feb-2013 |
22:32 |
PublicRdpOakLibArmv5Retail |
Tscaxctrl.lib |
33,720,170 |
13-Feb-2013 |
22:50 |
PublicRdpOakLibArmv6Checked |
Tscaxctrl.lib |
34,552,978 |
13-Feb-2013 |
22:49 |
PublicRdpOakLibArmv6Debug |
Tscaxctrl.lib |
25,347,802 |
13-Feb-2013 |
22:47 |
PublicRdpOakLibArmv6Retail |
Tscaxctrl.lib |
33,609,328 |
13-Feb-2013 |
23:06 |
PublicRdpOakLibArmv7Checked |
Tscaxctrl.lib |
34,439,052 |
13-Feb-2013 |
23:04 |
PublicRdpOakLibArmv7Debug |
Tscaxctrl.lib |
25,273,014 |
13-Feb-2013 |
23:03 |
PublicRdpOakLibArmv7Retail |
Tscaxctrl.lib |
32,119,828 |
13-Feb-2013 |
23:21 |
PublicRdpOakLibMipsiiChecked |
Tscaxctrl.lib |
34,273,494 |
13-Feb-2013 |
23:20 |
PublicRdpOakLibMipsiiDebug |
Tscaxctrl.lib |
24,413,776 |
13-Feb-2013 |
23:18 |
PublicRdpOakLibMipsiiRetail |
Tscaxctrl.lib |
32,135,642 |
13-Feb-2013 |
23:36 |
PublicRdpOakLibMipsii_fpChecked |
Tscaxctrl.lib |
34,288,886 |
13-Feb-2013 |
23:35 |
PublicRdpOakLibMipsii_fpDebug |
Tscaxctrl.lib |
24,429,452 |
13-Feb-2013 |
23:33 |
PublicRdpOakLibMipsii_fpRetail |
Tscaxctrl.lib |
30,053,252 |
13-Feb-2013 |
23:51 |
PublicRdpOakLibSh4Checked |
Tscaxctrl.lib |
31,872,952 |
13-Feb-2013 |
23:50 |
PublicRdpOakLibSh4Debug |
Tscaxctrl.lib |
23,203,526 |
13-Feb-2013 |
23:48 |
PublicRdpOakLibSh4Retail |
Tscaxctrl.lib |
29,789,612 |
14-Feb-2013 |
00:06 |
PublicRdpOakLibX86Checked |
Tscaxctrl.lib |
29,706,690 |
14-Feb-2013 |
00:04 |
PublicRdpOakLibX86Debug |
Tscaxctrl.lib |
22,500,614 |
14-Feb-2013 |
00:03 |
PublicRdpOakLibX86Retail |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
References
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Need more help?
- Status
- Not open for further replies.
-
#1
-
- Aug 6, 2016
-
- 236
-
- 0
-
- 1,910
- 50
-
#3
-
- Jul 2, 2006
-
- 1,621
-
- 0
-
- 21,960
- 368
-
#2
-
- Aug 6, 2016
-
- 236
-
- 0
-
- 1,910
- 50
-
#3
-
- May 26, 2009
-
- 419
-
- 1
-
- 19,010
- 63
-
#4
-
#5
-
- Jan 2, 2014
-
- 106
-
- 0
-
- 10,710
- 25
-
#6
Question from GatorChomp21 : «Can’t open games with Remote Desktop Connection»
Did you tell FM17 to open in a window? or is it doing it on it’s own?
It’s hard for remote software to capture full-screen applications.
So you ideally want to make FM17 open in a Window on the PC it’s running from, and then when you launch it remotely it should work better.
- Status
- Not open for further replies.
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
|
Question Old Game on new pc crashing | Apps General Discussion | 0 | Sep 21, 2022 |
|
Question Do I have to do relational databases and database creation and management for game development ? | Apps General Discussion | 2 | Aug 3, 2022 |
|
Question Steam games not opening | Apps General Discussion | 5 | Mar 13, 2022 |
|
Question Epic games wants me to install the game again | Apps General Discussion | 1 | Feb 1, 2022 |
|
Question Can’t find game I played as a kid | Apps General Discussion | 0 | Dec 25, 2021 |
|
Question Fps drops/stuttering only on Epic games | Apps General Discussion | 0 | Feb 24, 2021 |
C
|
Question Logitech Gaming Software: Trying to set a TAB key toggle | Apps General Discussion | 0 | Sep 3, 2019 |
|
Question PUBG Lite launcher error | Apps General Discussion | 2 | Jul 1, 2019 |
S
|
Question What Wi-Fi router is good for a large home WITHOUT gaming? For seniors | Apps General Discussion | 1 | May 19, 2019 |
C
|
Question Are there any recommendations for relaxing games on google play? | Apps General Discussion | 3 | May 14, 2019 |
|
Help, icue won’t stop repeating macro. | Apps General Discussion | 1 | Jan 19, 2019 |
J
|
Most games get error message | Apps General Discussion | 4 | Jan 1, 2019 |
G |
10 Upcoming Video Game Movies (And When You Can Watch Them) | Apps General Discussion | 1 | Dec 16, 2018 |
C
|
how can i use archive manager to install apps and games | Apps General Discussion | 1 | Dec 12, 2018 |
I
|
Solved! When im playing free fire…automatically it stop and come to home screen during the game..plz help me soon.. | Apps General Discussion | 2 | Dec 10, 2018 |
G |
Epic Games Store has launched: Massive Rival to Steam Revealed | Apps General Discussion | 1 | Dec 7, 2018 |
N
|
How do i transfer any PC game to another PC? (friend`s) | Apps General Discussion | 2 | Nov 27, 2018 |
F
|
I need feedback | Apps General Discussion | 2 | Nov 13, 2018 |
P
|
Solved! Vm software for Gaming | Apps General Discussion | 18 | Nov 7, 2018 |
N
|
Solved! Download Flash Games From Boomerang.co.uk | Apps General Discussion | 4 | Nov 6, 2018 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
Code | Reason |
0 | No error |
1 | User-initiated client disconnect. |
2 | User-initiated client logoff. |
3 | Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred. For help solving the problem, see «Remote Desktop» in Help and Support. |
260 | Remote Desktop can’t find the computer «». This might mean that «» does not belong to the specified network. Verify the computer name and domain that you are trying to connect to. |
262 | This computer can’t connect to the remote computer. Your computer does not have enough virtual memory available. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
264 | This computer can’t connect to the remote computer. The two computers couldn’t connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. |
266 | The smart card service is not running. Please start the smart card service and try again. |
516 | Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. |
522 | A smart card reader was not detected. Please attach a smart card reader and try again. |
772 | This computer can’t connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support. |
778 | There is no card inserted in the smart card reader. Please insert your smart card and try again. |
1030 | Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again. |
1032 | The specified computer name contains invalid characters. Please verify the name and try again. |
1034 | An error has occurred in the smart card subsystem. Please contact your helpdesk about this error. |
1796 | This computer can’t connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
1800 | Your computer could not connect to another console session on the remote computer because you already have a console session in progress. |
2056 | The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. |
2308 | Your Remote Desktop Services session has ended. The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. |
2311 | The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
2312 | A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again. |
2567 | The specified username does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support. |
2820 | This computer can’t connect to the remote computer. An error occurred that prevented the connection. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
2822 | Because of an error in data encryption, this session will end. Please try connecting to the remote computer again. |
2823 | The user account is currently disabled and cannot be used. For assistance, contact your system administrator or technical support. |
2825 | The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support. |
3079 | A user account restriction (for example, a time-of-day restriction) is preventing you from logging on. For assistance, contact your system administrator or technical support. |
3080 | The remote session was disconnected because of a decompression failure at the client side. Please try connecting to the remote computer again. |
3335 | As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support. |
3337 | The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support. |
3590 | The client can’t connect because it doesn’t support FIPS encryption level. Please lower the server side required security level Policy, or contact your network administrator for assistance |
3591 | This user account has expired. For assistance, contact your system administrator or technical support. |
3592 | Failed to reconnect to your remote session. Please try to connect again. |
3593 | The remote PC doesn’t support Restricted Administration mode. |
3847 | This user account’s password has expired. The password must change in order to logon. Please update the password or contact your system administrator or technical support. |
3848 | A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator. |
4103 | The system administrator has restricted the times during which you may log in. Try logging in later. If the problem continues, contact your system administrator or technical support. |
4104 | The remote session was disconnected because your computer is running low on video resources. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
4359 | The system administrator has limited the computers you can log on with. Try logging on at a different computer. If the problem continues, contact your system administrator or technical support. |
4615 | You must change your password before logging on the first time. Please update your password or contact your system administrator or technical support. |
4871 | The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support. |
5127 | The Kerberos sub-protocol User2User is required. For assistance, contact your system administrator or technical support. |
6919 | Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid. In some cases, this error might also be caused by a large time discrepancy between the client and server computers. |
7431 | Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer. |
8711 | Your computer can’t connect to the remote computer because your smart card is locked out. Contact your network administrator about unlocking your smart card or resetting your PIN. |
9479 | Could not auto-reconnect to your applications,please re-launch your applications |
9732 | Client and server versions do not match. Please upgrade your client software and then try connecting again. |
33554433 | Failed to reconnect to the remote program. Please restart the remote program. |
33554434 | The remote computer does not support RemoteApp. For assistance, contact your system administrator. |
50331649 | Your computer can’t connect to the remote computer because the username or password is not valid. Type a valid user name and password. |
50331650 | Your computer can’t connect to the remote computer because it can’t verify the certificate revocation list. Contact your network administrator for assistance. |
50331651 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) The requested Remote Desktop Gateway server address and the server SSL certificate subject name do not match. 2) The certificate is expired or revoked. 3) The certificate root authority does not trust the certificate. Contact your network administrator for assistance. |
50331652 | Your computer can’t connect to the remote computer because the SSL certificate was revoked by the certification authority. Contact your network administrator for assistance. |
50331653 | This computer can’t verify the identity of the RD Gateway «». It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance. |
50331654 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance. |
50331655 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance. |
50331656 | Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance. |
50331657 | An error occurred while sending data to the Remote Desktop Gateway server. The server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
50331658 | An error occurred while receiving data from the Remote Desktop Gateway server. Either the server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
50331659 | Your computer can’t connect to the remote computer because an alternate logon method is required. Contact your network administrator for assistance. |
50331660 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address. |
50331661 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
50331662 | Your computer can’t connect to the remote computer because the Remote Desktop Services client component is missing or is an incorrect version. Verify that setup was completed successfully, and then try reconnecting later. |
50331663 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is running low on server resources and is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
50331664 | Your computer can’t connect to the remote computer because an incorrect version of rpcrt4.dll has been detected. Verify that all components for Remote Desktop Gateway client were installed correctly. |
50331665 | Your computer can’t connect to the remote computer because no smart card service is installed. Install a smart card service and then try again, or contact your network administrator for assistance. |
50331666 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Try again using a valid smart card, or contact your network administrator for assistance. |
50331667 | Your computer can’t connect to the remote computer because no smart card is available. Try again using a smart card. |
50331668 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Reinsert the smart card and then try again. |
50331669 | Your computer can’t connect to the remote computer because the user name or password is not valid. Please type a valid user name and password. |
50331671 | Your computer can’t connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance. |
50331672 | The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
50331673 | The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
50331674 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) Your credentials (the combination of user name, domain, and password) were incorrect. 2) Your smart card was not recognized. |
50331675 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not listed in the RD Gateway’s permission list 2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1). Contact your network administrator for assistance. |
50331676 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not authorized to access the RD Gateway «» 2) Your computer is not authorized to access the RD Gateway «» 3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password) Contact your network administrator for assistance. |
50331679 | Your computer can’t connect to the remote computer because your network administrator has restricted access to this RD Gateway server. Contact your network administrator for assistance. |
50331680 | Your computer can’t connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator. |
50331681 | Your computer can’t connect to the remote computer because your password has expired or you must change the password. Please change the password or contact your network administrator or technical support for assistance. |
50331682 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance. |
50331683 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server does not support the request. Contact your network administrator for assistance. |
50331684 | Your computer can’t connect to the remote computer because the client does not support one of the Remote Desktop Gateway’s capabilities. Contact your network administrator for assistance. |
50331685 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server and this computer are incompatible. Contact your network administrator for assistance. |
50331686 | Your computer can’t connect to the remote computer because the credentials used are not valid. Insert a valid smart card and type a PIN or password, and then try connecting again. |
50331687 | Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Contact your network administrator for assistance. |
50331688 | Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance. |
50331689 | Your computer can’t connect to the remote computer because the RD Gateway server that you are trying to connect to is not allowed by your computer administrator. If you are the administrator, add this Remote Desktop Gateway server name to the trusted Remote Desktop Gateway server list on your computer and then try connecting again. |
50331690 | Your computer can’t connect to the remote computer because your computer or device did not meet the Network Access Protection requirements set by your network administrator, for one of the following reasons: 1) The Remote Desktop Gateway server name and the server’s public key certificate subject name do not match. 2) The certificate has expired or has been revoked. 3) The certificate root authority does not trust the certificate. 4) The certificate key extension does not support encryption. 5) Your computer cannot verify the certificate revocation list. Contact your network administrator for assistance. |
50331691 | Your computer can’t connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials. |
50331692 | Your computer can’t connect to the remote computer because smart card credentials are required to authenticate to the Remote Desktop Gateway server instead of a user name and password. |
50331693 | Your computer can’t connect to the remote computer because no smart card reader is detected. Connect a smart card reader and then try again, or contact your network administrator for assistance. |
50331695 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to missing firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
50331696 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to invalid firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
50331698 | Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you. |
50331699 | The connection has been disconnected because the session timeout limit was reached. |
50331700 | Your computer can’t connect to the remote computer because an invalid cookie was sent to the Remote Desktop Gateway server. Contact your network administrator for assistance. |
50331701 | Your computer can’t connect to the remote computer because the cookie was rejected by the Remote Desktop Gateway server. Contact your network administrator for assistance. |
50331703 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is expecting an authentication method different from the one attempted. Contact your network administrator for assistance. |
50331704 | The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
50331705 | The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
50331707 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway and the remote computer are unable to exchange policies. This could happen due to one of the following reasons: 1. The remote computer is not capable of exchanging policies with the Remote Desktop Gateway. 2. The remote computer’s configuration does not permit a new connection. 3. The connection between the Remote Desktop Gateway and the remote computer ended. Contact your network administrator for assistance. |
50331708 | Your computer can’t connect to the remote computer, possibly because the smart card is not valid, the smart card certificate was not found in the certificate store, or the Certificate Propagation service is not running. Contact your network administrator for assistance. |
50331709 | To use this program or computer, first log on to the following website: <a href=»»></a>. |
50331710 | To use this program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
50331711 | Your session has ended. To continue using the program or computer, first log on to the following website: <a href=»»></a>. |
50331712 | Your session has ended. To continue using the program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
50331713 | The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn’t pass the Network Access Protection (NAP) requirements set by your network administrator. Contact your network administrator for assistance. |
50331714 | Your computer can’t connect to the remote computer because the size of the cookie exceeded the supported size. Contact your network administrator for assistance. |
50331716 | Your computer can’t connect to the remote computer using the specified forward proxy configuration. Contact your network administrator for assistance. |
50331717 | This computer cannot connect to the remote resource because you do not have permission to this resource. Contact your network administrator for assistance. |
50331718 | There are currently no resources available to connect to. Retry the connection or contact your network administrator. |
50331719 | An error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator. |
50331721 | Your Remote Desktop Client needs to be updated to the newest version. Contact your system administrator for help installing the update, and then try again. |
50331722 | Your network configuration doesn’t allow the necessary HTTPS ports. Contact your network administrator for help allowing those ports or disabling the web proxy, and then try connecting again. |
50331723 | We’re setting up more resources, and it might take a few minutes. Please try again later. |
50331724 | The user name you entered does not match the user name used to subscribe to your applications. If you wish to sign in as a different user please choose Sign Out from the Home menu. |
50331725 | Looks like there are too many users trying out the Azure RemoteApp service at the moment. Please wait a few minutes and then try again. |
50331726 | Maximum user limit has been reached. Please contact your administrator for further assistance. |
50331727 | Your trial period for Azure RemoteApp has expired. Ask your admin or tech support for help. |
50331728 | You no longer have access to Azure RemoteApp. Ask your admin or tech support for help. |