ASG-RD 2019 Patch 2 - Crash now SQL errors

[ICTSystemsAdministration]

We've been running ASG 2019 since it was released and every so often it just stops responding (like it has on multiple version on multiple machines over the years) with a grey title bar and the only way to continue is to kill it then load it up again.

Today it happened again, and now when I try to open it I get multiple SQL pop up errors (Pasted one below), it tries to reconnect to my saved sessions then dies without me being able to do anything. I've tried removing it and reinstalling with no change (both 32 and 64 bit versions). I tried updating from 2019 Patch 1 to Patch 2, no change. I've ran the optimisations via a patch 2 client on a different account and no change. Other users are working fine, so this appears to be the status of my last session before the crash is in the DB but corrupt and the app is trying to load it back in again.

Please advise how I can fix this.

Thanks
Michael

An error occured on executing an sql statement
BaseItemGet
Invalid attempt to call Read when reader is closed.

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

   at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
   at System.Data.SqlClient.SqlDataReader.Read()
   at CloudAdminDataAccess.SqlDataAccessor.BaseItemGet(Guid itemId, Guid userId)

[DevOma]

Could you try to solve the problem by the following command line

ASGRD.EXE /resetlayout

[ICTSystemsAdministration]

Could you try to solve the problem by the following command line

ASGRD.EXE /resetlayout

Hi Oliver,

  I tried that and got the errors:

An error occured on executing an sql statement
LogsAdd

An error occured on executing an sql statement
PropertiesSet

  It then let me in enough to logoff the existing RDP sessions. The toolbar was grayed out so none of the menus could be clicked. After logging off the sessions I quit and ran it again with the same command and got the SQL errors again and tried to double click one of my connections which caused the app to crash again (spinning circle). After it eventually quit, I ran it without the switch and it seems to be working again now (no errors and I can click the menus and open rdp connections). Fingers crossed this is fixed as I live in this thing on a daily basis.

Thanks for your help so far.
Michael

[ICTSystemsAdministration]

Could you try to solve the problem by the following command line

ASGRD.EXE /resetlayout

Hi Oliver,

  I tried that and got the errors:

An error occured on executing an sql statement
LogsAdd

An error occured on executing an sql statement
PropertiesSet

  It then let me in enough to logoff the existing RDP sessions. The toolbar was grayed out so none of the menus could be clicked. After logging off the sessions I quit and ran it again with the same command and got the SQL errors again and tried to double click one of my connections which caused the app to crash again (spinning circle). After it eventually quit, I ran it without the switch and it seems to be working again now (no errors and I can click the menus and open rdp connections). Fingers crossed this is fixed as I live in this thing on a daily basis.

Thanks for your help so far.
Michael

I spoke too soon. After quitting and running it again, I get the SQL errors, gray toolbar and I can do nothing. Please advise.

Thanks
Michael

[Michael Scholz]

Hi Michael,

Do you havs logs enabled in the Settings and did you restrict them ? It's advisable to limit the logs to a couple hundreds or limit of 30days or so. If Logsize has increased too much that could lead to such errors as "LogsAdd" and some others.. ; So if you are able to open ASG-RD and reach to the settings then limit the Logs please, close and restart and hopefully that will solve the problems. Otherwise open SQL Management Studio and look for your database and then you can see how big is the log-section under "Tables" "dbo.Logs" -> Properties. Whats the logsize and Row count ?

best regards,
Michael

[ICTSystemsAdministration]

Hi Michael,

Do you havs logs enabled in the Settings and did you restrict them ?  It's advisable to limit the logs to a couple hundreds or limit of 30days or so.  If Logsize has increased too much that could lead to such errors as "LogsAdd" and some others.. ; So if you are able to open ASG-RD and reach to the settings then limit the Logs please,  close and restart and hopefully that will solve the problems. Otherwise open SQL Management Studio and look for your database and then you can see how big is the log-section under "Tables" "dbo.Logs"  -> Properties.  Whats the logsize and Row count ?  

best regards,
Michael

Hi Michael,

  The logs were default, so I unticked them all, quit out with open sessions and opened again and I get the SQL errors "propertiesSet" and "BaseItemGet" alternating four times, Then the "connection could not be established" dialog box - OK or Retry. In the dialog box it states "Last Command: PropertiesSet - Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or (The rest I can't see as the dialog box isn't big enough". Clicking Retry gives the dialog box "Error saving 'Quick-Connect' item - The source was not found, but some or all event logs could not be searched. To create the source, you need permission to read all event logs to make sure that the new source name is unique. Inaccessible logs: Security.State. Clicking OK takes me in and I can use the product,

  There are 768 rows in the dbo.logs table.

Thanks
Michael

[Michael Scholz]

Ok thanks for the input ! 768 Rows is not so much that i would lead to any errors. So thats ok. I wonder about those massive other errors occuring. Sounds like a corrupt database.
Before getting those errors have you started with a new and empty 2019 dataase or migrated from 2018 ? Is it possible to export all your settings in an rde file for you, create a new environment with a new database and import that just for testing after clean restart with a new database for testing purposes ?

best regards,
Michael

[ICTSystemsAdministration]

Ok thanks for the input !  768 Rows is not so much that i would lead to any errors. So thats ok. I wonder about those massive other errors occuring. Sounds like a corrupt database.
Before getting those errors have you started with a new and empty 2019 dataase or migrated from 2018 ? Is it possible to export all your settings in an rde file for you, create a new environment with a new database and import that just for testing after clean restart with a new database for testing purposes ?

best regards,
Michael

Hi Michael,

  We've been using this for a few years now and we just backup then upgrade the database when needed. We've been successfully using the 2019 version for a few weeks now, and this only started when my session crashed and only for me, so I definitely agree that it looks like my session info in the DB is corrupt.

  If I do an export, is that just for me or will it include all the users?

Thanks
Michael

[ICTSystemsAdministration]

Ok thanks for the input !  768 Rows is not so much that i would lead to any errors. So thats ok. I wonder about those massive other errors occuring. Sounds like a corrupt database.
Before getting those errors have you started with a new and empty 2019 dataase or migrated from 2018 ? Is it possible to export all your settings in an rde file for you, create a new environment with a new database and import that just for testing after clean restart with a new database for testing purposes ?

best regards,
Michael

Hi Michael,

  We've been using this for a few years now and we just backup then upgrade the database when needed. We've been successfully using the 2019 version for a few weeks now, and this only started when my session crashed and only for me, so I definitely agree that it looks like my session info in the DB is corrupt.

  If I do an export, is that just for me or will it include all the users?

Thanks
Michael

I took a chance and exported the settings and it appears as though they are just mine. I got one of the other administrators to delete my account from ASG, then I logged back in and restored my settings. I can now open/close and connect without error. The only problem I have now is I cannot set a "Personal" credential on any object even though I have personal credentials created. I tried deleting and creating one again in case the import/export didn't work for those and it still doesn't work. When I go to the "Personal Values" tab on a connection or folder, I am unable to use the drop down. Any ideas?

Regards
Michael

[ICTSystemsAdministration]

Ok thanks for the input !  768 Rows is not so much that i would lead to any errors. So thats ok. I wonder about those massive other errors occuring. Sounds like a corrupt database.
Before getting those errors have you started with a new and empty 2019 dataase or migrated from 2018 ? Is it possible to export all your settings in an rde file for you, create a new environment with a new database and import that just for testing after clean restart with a new database for testing purposes ?

best regards,
Michael

Hi Michael,

  We've been using this for a few years now and we just backup then upgrade the database when needed. We've been successfully using the 2019 version for a few weeks now, and this only started when my session crashed and only for me, so I definitely agree that it looks like my session info in the DB is corrupt.

  If I do an export, is that just for me or will it include all the users?

Thanks
Michael

I took a chance and exported the settings and it appears as though they are just mine. I got one of the other administrators to delete my account from ASG, then I logged back in and restored my settings. I can now open/close and connect without error. The only problem I have now is I cannot set a "Personal" credential on any object even though I have personal credentials created. I tried deleting and creating one again in case the import/export didn't work for those and it still doesn't work. When I go to the "Personal Values" tab on a connection or folder, I am unable to use the drop down. Any ideas?

Regards
Michael

I created a brand new database, deleted my connection to the other database and imported my settings (This fixed my private credential issues) and when I quit out of ASG and open it again, I still get the SQL errors when loading up. Could the corruption have come across with my export/import? Could there be files left behind on a client remove which are causing this issue (If so where)? I've already removed and reinstall the software multiple times on my PC?

Thanks
Michael

[Michael Scholz]

Hi Michael,

thanks for your extensive testing ! Have you tried the data Optimizer from the setings menu (Administration-Data Optimizer) ? If there are corrupt or redundant informations in that should eliminate them. But normally it should not be possible to export or import erraneous data. Also local files should not cause such SQL-errors. Do you have any error logs ( must be activated in settings first ) that you could provide ?

Best regards,
Michael

[DevOma]

Step by step - could you send me a backup of your database - best would be to get the database after your session crashed and you couldn't log in again? If so please send the backup file (from MS SQL Management Studio) to asg.rd@asg.com - add a link to this thread, and let me know your user name - then I can update the data to login with your account (but I won't be able to decrypt your creds, just to have the same data loaded as you)

[ICTSystemsAdministration]

Hi Michael,

thanks for your extensive testing ! Have you tried the data Optimizer from the setings menu (Administration-Data Optimizer) ? If there are corrupt or redundant informations in that should eliminate them. But normally it should not be possible to export or import erraneous data. Also local files should not cause such SQL-errors. Do you have any error logs ( must be activated in settings first ) that you could provide ?

Best regards,
Michael

Sorry about the delay in replying, we've been dealing with some critical issues. The following logs are ticked (default for the install as I haven't changed them):

Activate error log
Activate change log
Activate connection history

  If these would be useful, let me know where they are and how to get them to you.

  I've already ran through the data optimizer and there is still no difference.

[ICTSystemsAdministration]

Step by step - could you send me a backup of your database - best would be to get the database after your session crashed and you couldn't log in again? If so please send the backup file (from MS SQL Management Studio) to asg.rd@asg.com - add a link to this thread, and let me know your user name - then I can update the data to login with your account (but I won't be able to decrypt your creds, just to have the same data loaded as you)

I've backed up/zipped and sent my DB as requested.

Thanks
Michael

[DevOma]

I got the file and will check that asap...

[DevOma]

I can run your database with your user without any issues - did you restart your SQL server to test if there is any open connection blocking your access?

[ICTSystemsAdministration]

I can run your database with your user without any issues - did you restart your SQL server to test if there is any open connection blocking your access?

Yes, the SQL server has been restarted and I even restored the database to a different SQL instance when testing with the same result. This is why I was wondering if there is something local being left behind on my machine even after a remove/re-install of the client.

Thanks
Michael

[DevOma]

You can rename the profile.xml file in your AppData\Roaming\ASG-RemoteDesktop\12.0 directory - it will be created a new one when starting again

If you can login you can deactivate options for automated reconnect at startup and delete your layout settings (Tools=>Reset Layout)

But I'm wondering why I don't get the same error - I updated your userID with my account - so I log in with the same settings like you...

[ICTSystemsAdministration]

You can rename the profile.xml file in your AppData\Roaming\ASG-RemoteDesktop\12.0 directory - it will be created a new one when starting again

If you can login you can deactivate options for automated reconnect at startup and delete your layout settings (Tools=>Reset Layout)

But I'm wondering why I don't get the same error - I updated your userID with my account - so I log in with the same settings like you...

I removed the app again. Delete any entries for ASG under my current user registry hive, deleted the AppData\Roaming\ASG-RemoteDesktop folder completely, then reinstalled it. I then ran it, connected using the environment which was still configured, then did a Tools -> Reset Layout. Same problem.

I then went through and disabled every option which may save a log file/session etc. and enabled them one-by-one and the error came back when the "Restore sessions on program start without prompt" is ticked (This has always been ticked before the crash). If I un-tick this, it saves my sessions and when I reload it asks me if I want to reconnect. If I click yes, it loads the sessions up without error. As soon as I tick this box, it gives me the SQL errors when I reload the app.

I've also noticed that I am unable to set "Personal Values" on the credential tab for folders/connections (The drop downs are grayed out). I can change the Default Values without issue. I do have working personal credentials configured as I can right click a connection and select them from the options list.

Regards
Michael

[ICTSystemsAdministration]

You can rename the profile.xml file in your AppData\Roaming\ASG-RemoteDesktop\12.0 directory - it will be created a new one when starting again

If you can login you can deactivate options for automated reconnect at startup and delete your layout settings (Tools=>Reset Layout)

But I'm wondering why I don't get the same error - I updated your userID with my account - so I log in with the same settings like you...

I removed the app again. Delete any entries for ASG under my current user registry hive, deleted the AppData\Roaming\ASG-RemoteDesktop folder completely, then reinstalled it. I then ran it, connected using the environment which was still configured, then did a Tools -> Reset Layout. Same problem.

I then went through and disabled every option which may save a log file/session etc. and enabled them one-by-one and the error came back when the "Restore sessions on program start without prompt" is ticked (This has always been ticked before the crash). If I un-tick this, it saves my sessions and when I reload it asks me if I want to reconnect. If I click yes, it loads the sessions up without error. As soon as I tick this box, it gives me the SQL errors when I reload the app.

I've also noticed that I am unable to set "Personal Values" on the credential tab for folders/connections (The drop downs are grayed out). I can change the Default Values without issue. I do have working personal credentials configured as I can right click a connection and select them from the options list.

Regards
Michael

I've fixed the "Personal Values" issue by adding my account into the "Administrators" security group, rather than the AD group we have added in with all the options selected. Is this a change in this version or just another bit of weirdness caused by my crash, as this was working before?

Regards
Michael