SSH -> Console Setting

Topics: Developer Forum, Project Management Forum, User Forum
Jun 20, 2013 at 2:46 PM
Hi,

I currently use version 3.0.1.0 (103069)

I have an issue with the Console setting for SSH connections. Terminals did not recognize my configured Rows: and Columns: settings.

I use database to store my configurations.

The only why that he gets this informations is to edit my connection and close it again.

After this I can connect to the system with my settings.
Coordinator
Jun 20, 2013 at 3:25 PM
Similar issue was reported for RDP protocol. Try latest build, it should be fixed. If not, then i have to search again.
Jun 21, 2013 at 10:57 AM
Hi,

I use 103150, now. The same issue.

regards
Coordinator
Jun 22, 2013 at 12:45 PM
That is bad, one more try to fix ...
:-(
Jun 25, 2013 at 9:25 AM
The RDP issue seems to exists still.

When I connect to a system my net drives are not mounted.

I cannot copy and past from the system to my computer.

The only why to fix it is the same as I do for SSH issue.

open the properties of the connection and close it again. (without changing anything)
Coordinator
Jun 25, 2013 at 4:27 PM
Please is there some, who is able to describe exact steps how to reproduce this issue?
I will need:
  • config file,
  • example favorite you imported/created or exported
  • log file
or any place identified in the code, which causes the issue. I am not able to reproduce!
NOTE: Test only on latest build, with database not upgraded from previous CTP.
Jun 28, 2013 at 11:22 AM
Edited Jun 28, 2013 at 12:02 PM
Hello,

I downloaded the newest official release version for testing. ( Change Set: 103236 )

The issue appears only if you have your rdp connection in the database.

If I use the local config file the issue did not appears.

For testing case a made a new database and configured one test connection.

Within the properties of the connection in tab RDP->Local Resources I use the option "DISK Drives & Plug and Play Devices..."

I checked all my devices and save everything.

After this I close the application.

When I open it again and connect to my system no device is mounted on the Remote System.

I can connect a bunch of time without any device is mounted.

The only way how I can fix this is to open the properties of the connection and close it shortly after. Click the Cancel Button is enough.

After this all devices are mounted every time I connect.

After closing the application again and start it the devices will not mounted automatically again.

I checked the log file. The only issue I see is a registry key he tries to load. This key does not exists.

regards
INFO  2013-06-28 13:10:41,013   818ms Terminals              Main               - -------------------------------Title: Terminals 3.0.2 started Version:3.0.2.41037 Date:26.06.2013 23:47:54-------------------------------
INFO  2013-06-28 13:10:41,288  1092ms Terminals              Main               - Start state 1 Complete: Unhandled exceptions
INFO  2013-06-28 13:10:41,296  1100ms Terminals              gGeneralProperties - CommandLine:"D:\terminalstest\Terminals.exe" 
INFO  2013-06-28 13:10:41,299  1103ms Terminals              gGeneralProperties - CurrentDirectory:D:\terminalstest
INFO  2013-06-28 13:10:41,301  1105ms Terminals              gGeneralProperties - MachineName:TESTSYSTEM
INFO  2013-06-28 13:10:41,302  1106ms Terminals              gGeneralProperties - OSVersion:Microsoft Windows NT 6.1.7601 Service Pack 1
INFO  2013-06-28 13:10:41,304  1108ms Terminals              gGeneralProperties - ProcessorCount:8
INFO  2013-06-28 13:10:41,305  1109ms Terminals              gGeneralProperties - UserInteractive:True
INFO  2013-06-28 13:10:41,307  1111ms Terminals              gGeneralProperties - Version:4.0.30319.17929
INFO  2013-06-28 13:10:41,308  1112ms Terminals              gGeneralProperties - WorkingSet:27320320
INFO  2013-06-28 13:10:41,309  1113ms Terminals              gGeneralProperties - Is64BitOperatingSystem:True
INFO  2013-06-28 13:10:41,310  1114ms Terminals              gGeneralProperties - Is64BitProcess:True
INFO  2013-06-28 13:10:41,311  1115ms Terminals              Main               - Start state 2 Complete: Log General properties
INFO  2013-06-28 13:10:41,315  1119ms Terminals              Main               - Start state 3 Complete: Set application properties
INFO  2013-06-28 13:10:41,496  1300ms Terminals              Main               - Start state 4 Complete: Parse command line
INFO  2013-06-28 13:10:41,502  1306ms Terminals              Main               - Start state 5 Complete: User account control
INFO  2013-06-28 13:10:41,504  1308ms Terminals              Main               - Start state 6 Complete: Set Single instance mode
INFO  2013-06-28 13:10:41,511  1315ms Terminals              Main               - Start state 7 Complete: Configuration upgrade
ERROR 2013-06-28 13:10:49,368  9172ms Terminals              Register           - Error accessing registry
System.UnauthorizedAccessException: Der Zugriff auf den Registrierungsschlüssel "HKEY_CLASSES_ROOT\TRM" wurde verweigert.
   bei Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
   bei Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions)
   bei Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck)
   bei Terminals.ProtocolHandler.CreateTrmRegistrySubKey()
   bei Terminals.ProtocolHandler.Register()
INFO  2013-06-28 13:11:06,239 26043ms Terminals              Main               - -------------------------------Terminals 3.0.2 Stopped-------------------------------
INFO  2013-06-28 13:11:11,775   829ms Terminals              Main               - -------------------------------Title: Terminals 3.0.2 started Version:3.0.2.41037 Date:26.06.2013 23:47:54-------------------------------
INFO  2013-06-28 13:11:12,039  1093ms Terminals              Main               - Start state 1 Complete: Unhandled exceptions
INFO  2013-06-28 13:11:12,047  1101ms Terminals              gGeneralProperties - CommandLine:"D:\terminalstest\Terminals.exe" 
INFO  2013-06-28 13:11:12,049  1103ms Terminals              gGeneralProperties - CurrentDirectory:D:\terminalstest
INFO  2013-06-28 13:11:12,050  1104ms Terminals              gGeneralProperties - MachineName:TESTSYSTEM
INFO  2013-06-28 13:11:12,051  1105ms Terminals              gGeneralProperties - OSVersion:Microsoft Windows NT 6.1.7601 Service Pack 1
INFO  2013-06-28 13:11:12,052  1106ms Terminals              gGeneralProperties - ProcessorCount:8
INFO  2013-06-28 13:11:12,054  1108ms Terminals              gGeneralProperties - UserInteractive:True
INFO  2013-06-28 13:11:12,055  1109ms Terminals              gGeneralProperties - Version:4.0.30319.17929
INFO  2013-06-28 13:11:12,056  1110ms Terminals              gGeneralProperties - WorkingSet:27471872
INFO  2013-06-28 13:11:12,058  1112ms Terminals              gGeneralProperties - Is64BitOperatingSystem:True
INFO  2013-06-28 13:11:12,059  1113ms Terminals              gGeneralProperties - Is64BitProcess:True
INFO  2013-06-28 13:11:12,060  1114ms Terminals              Main               - Start state 2 Complete: Log General properties
INFO  2013-06-28 13:11:12,063  1117ms Terminals              Main               - Start state 3 Complete: Set application properties
INFO  2013-06-28 13:11:12,243  1297ms Terminals              Main               - Start state 4 Complete: Parse command line
INFO  2013-06-28 13:11:12,250  1304ms Terminals              Main               - Start state 5 Complete: User account control
INFO  2013-06-28 13:11:12,252  1306ms Terminals              Main               - Start state 6 Complete: Set Single instance mode
INFO  2013-06-28 13:11:12,259  1313ms Terminals              Main               - Start state 7 Complete: Configuration upgrade
ERROR 2013-06-28 13:11:19,908  8961ms Terminals              Register           - Error accessing registry
System.UnauthorizedAccessException: Der Zugriff auf den Registrierungsschlüssel "HKEY_CLASSES_ROOT\TRM" wurde verweigert.
   bei Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
   bei Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions)
   bei Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck)
   bei Terminals.ProtocolHandler.CreateTrmRegistrySubKey()
   bei Terminals.ProtocolHandler.Register()
INFO  2013-06-28 13:11:58,648 47701ms Terminals              Main               - -------------------------------Terminals 3.0.2 Stopped-------------------------------
Coordinator
Jun 28, 2013 at 11:21 PM
Immer noch weiss ich nicht, was kann das sein. Registrierungsschlüssel hat da mit nichts zu tun.
Ich habe verstanden, das nur "DISK Drives & Plug and Play Devices..." funktionieren nicht. Ist es so?
Jul 2, 2013 at 3:01 PM
Hallo,

Ja, das ist genau das Problem.

Ohne die Properties zu öffnen sieht es so aus.
Image


Wenn man die Properties öffnen und wieder schließt sind meine lokalen Laufwerke da.
Image

An der Einstellung wurde nichts geändert.
Coordinator
Jul 2, 2013 at 6:31 PM
Edited Jul 2, 2013 at 6:32 PM
OK, danke, ich muss es uberpruffen.

Translation for others:
The resources (disk drives) are not redirected, if you don't access properties. It is relevant to database store only. I didn't identify, how to reproduce, because i didn't try to change the content of protocol specific properties.
Steps to reproduce:
  1. create RDP favorite in database store
  2. restart application
  3. Try to open connection using saved favorite
  4. The protocol specific properties are not applied
Coordinator
Jul 2, 2013 at 6:32 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.