Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ASG2017 constant crashing
#21
I have just experienced the application hang & crash issue I originally reported (although not sure this one is associated with the DLL issue above). I am running 2017 patch 2, and there do seem to be a load of events in the Application Event log. Here's the first 3:

############################################################################################

The program ASGRD.exe version 10.1.5713.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1cd8
Start Time: 01d3892aae2adbf9
Termination Time: 412
Application Path: C:\Program Files (x86)\ASG-Remote Desktop 2017\ASGRD.exe
Report Id: 4562160a-fadc-11e7-81f3-e006e6b64447

############################################################################################

An error occured on executing an sql statement
LogsGet
 
An error occured on executing an sql statement
LogsGet
Transaction (Process ID 98) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
 
---------------------------
 
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at CloudAdminDataAccess.SqlDataAccessor.LogsGet(LogTypes logType, Guid itemId, DateTime startDate, DateTime endDate, String itemName, String username, String computer)

############################################################################################

An error occured on executing an sql statement
LogsAdd
 
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& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at CloudAdminDataAccess.SqlDataAccessor.LogsAdd(LogItem logItem)
Reply
#22
We have implemented some code for the next release (planned for next week) that should help us identify these calls / errors - it seems to be that 2 threads are trying to use a database connection - but the only background thread should be reading information for session information - but this make no sense - so currently unable to verify the position where the error occurred but hopefully better logs with the next release...
Regards/Gruss
Oliver
Reply
#23
(Yesterday, 08:48 AM)DevOma Wrote: We have implemented some code for the next release (planned for next week) that should help us identify these calls / errors - it seems to be that 2 threads are trying to use a database connection - but the only background thread should be reading information for session information - but this make no sense - so currently unable to verify the position where the error occurred but hopefully better logs with the next release...

I wondered whether these logs would be useful, as from my perspective this appeared to be more logging than the previous release, however thanks for the info - I will wait for the next release.
Reply




Users browsing this thread: 1 Guest(s)