Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ASG-RD 2014 - RC5
#1
Hi all,

we provide Release Candiate 5 (RC5).

This version will be supported by this forum - upgrade to final RTM version will be supported.

The following ReleaseNotes describes the known issues - we try to fix all the issues as soon as possible.

If you want to migrate your data from 2012 version you can do inside a new environment in 2014 - so you could not connect to an old environment (as in the past) - you need to create a new environment and select "Environment=>Upgrade from 2012".

ASG-RD 2014 RC5
ASG-RD 2014 RC5 (incl. SQL Express)

Main fixes of RC5:
- Security issues
- Export/Import issues
- some minor issues...

For any feedback please use this sub forum.


Data from previous RC versions must be migrated if you use database mode - will be done automatically by migration wizard
Regards/Gruss
Oliver
#2
Hallo Allerseits,

mit dem RC 5 scheint der Migrationsassistent nicht mehr zu funktionieren. Die Konfig der 2012 Version wird nicht mehr eingelesen/erkannt.

MfG

Heinrich


Attached Files Thumbnail(s)
       
#3
Hallo,

bei mir wurde beim Aktualisieren von RC4 auf RC5 die RC4-Datenbank erfolgreich migriert und auch eine erneute Migration der RD 2012 DB in eine neue DB war erfolgreich (beide Male aber eben mit einer Datenbank als Quelle).

Update: Eine Kleinigkeit: Der RC5 meldet sich als 8.0.4675.1 (Release Candidate 4)

Schöne Grüße,

Klaus
#4
We're experiencing crashes of RC5 when people try to initiate remote desktop connections:

From the error log:
An error occured on executing an sql statement
LogsAdd
There is already an open DataReader associated with this Command which must be closed first.

---------------------------

at System.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
at System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String method, SqlCommand command)
at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at CloudAdminDataAccess.SqlDataAccessor.LogsAdd(LogItem logItem)

this causes the application to crash
#5
Changing the Icon on a folder to the 'person' totally breaks your ability to edit that item. Context options like 'Properties' become inoperable. I am therefore unable to undo this change... Very annoying.

I have admin permissions and I am using this in Database Mode

The Icon:
[Image: 2RGqDnp.png]

The context options:
[Image: 7CSXJyF.png]

The correct options:
[Image: Mlx8SP9.png]
#6
@hmcs: Sollte an einem Bug in der vorherigen Versionen liegen - da wurden nicht nur die Umgebungen des angegebenen Pfades ausgelesen, sondern auch immer zusätzlich die Umgebungen aus dem "All Users"-Verzeichnis

@r4pt012: Using of the "user"-icon will be fixed with the next binaries

@morthj: I will have a look at this issue...
Regards/Gruss
Oliver
#7
After upgrading to RC5 i get this,,,k, Why???


Attached Files Thumbnail(s)
   
#8
When did you get that message? On upgrading process? Login? Could you create a new environment and set up this environment with the same database settings as before (only a new name) and try with this connection?
Regards/Gruss
Oliver
#9
Work if i changed name.....but why....
#10
I never seen this before - and I do not understand :-) You could compare the 2 connection strings in your environments.xml file (for databases usally in AllUsers\AppData\ASG-RemoteDektop\8.0) - looks like the connection string was modified and perhaps I could see which part if you compare it...
Regards/Gruss
Oliver
#11
Hi,

I'm wondering what happened to the logbook in this version. We have been using VisionApp since 20110 and version 2012 since it came (Country License). We are using the logbook button and modified stored procedures to log changes to our objects to a central database. I was prepared for some changes, but the new logbook doesn't seem to be related to the objects at all, and I cannot find the stored procedures either.

When I click Logbook in 2014RC5 i get the opportunity to post a log entry to Current Item which is "Credentials". Is this a bug?
#12
No - logbook is now available for all objects - data structure was completely modified - there only objects that are stored in datasource - for all log types this is the table "Logs" - StoredProc "LogsAdd" - but the data is serialized so it can be used for different logs without changing the data structure...
Regards/Gruss
Oliver
#13
I am working with 2011 but want to upgrade to 2014. Can I migratr? If not out of the box, is there maybe a tool?
#14
Is there a hard date for the ASG 2014 release yet?
#15
We started a last complete test this week - and if there are no major bugs we plan to release it end of next week :-)
Regards/Gruss
Oliver
#16
@Morgenstern72: You need to upgrade to 2012 before - only 2012 data can be migrated inside a 2014 environment
Regards/Gruss
Oliver
#17
Bei einer Verbindung zu einem Windows 7 PC, der als RDP-Host auf das RDP-Protokoll 8.0 umgestellt wurde, funktioniert nicht die Darstellungsoption: "Fensterinhalt beim Ziehen anzeigen".

Das "Ziehen anzeigen" funktioniert dagegen problemlos, wenn ich eine native RDP-Verbindung via RDP-Client 6.3.9600 herstelle.

Dieser Darstellungsfehler existierte bereits unter vRD2011 und 2012; ich hatte sehr darauf gehofft, dass der Fehler mittlerweile beseitigt ist.

Ergänzung:
Die Verbindungen zu Windows 8 oder Server 2012 mit vmtl. RDP-Protokoll 8.1 klappen dagegen problemlos mit "Fensterinhalt beim Ziehen anzeigen"; selbst mit dem alten vRDP 2011. Nur das Protokoll 8.0 i. V. m. Windows 7 funktioniert nicht mit dieser Darstellungsoption.
#18
Quick Connect is still badly broken and buggy. specifically, when you try reconnecting a connection you did quickconnect from.
It makes the product almost unusable..
AK
#19
It's fixed already - and we plan to publish the RTM end of this week...
Regards/Gruss
Oliver
#20
Great! Looking forward to testing!!
AK




Users browsing this thread: 1 Guest(s)