External Logging Issue

Question

So we had 2017 version and we installed a new 2018.2 version and restored the configuration. Everything is going fine, except for external logging. We had an external database to log data beyond a certain date. I am trying to use the same database. Is this okay to point t old database? I hoping nothing different inside the DB and it will just start inserting data. Check connection goes successful but then it fails right away. Attaching screenshots. Just to note Adaxes service account has full access to the database. Both source addaxes servers are in the same network, no firewall or thing which will cause this.

Windows Event log creates below event ID.
Softerra.Adaxes.Logger+LogMessageWrappingException: Failed to save log records to the external database. ---> Softerra.Adaxes.Logging.ExternalDatabaseException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Database: AdaxesLog (FSQL)
Username: domain\account ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out
--- End of inner exception stack trace ---

Answer 1

Hello,

We had an external database to log data beyond a certain date. I am trying to use the same database. Is this okay to point t old database?

The old and the new instances of Adaxes should write their logs into the same external MS SQL database without any issues. But starting with Adaxes 2018.1, log records are stored in UTC standard while the records created by Adaxes 2017.2 and older are stored using local time of the computer where the operations were executed. Thus, the time in log records created by another service will be shown wrong. So, we recommend using separate external MS SQL databases for Adaxes services of 2017.2 and older, and Adaxes 2018.1 and later.

Windows Event log creates below event ID.

Does the Connection failed error occur for the old instance too?
It looks like the issue is related to the settings of your SQL server. Probably, the server is not configured to handle deadlocks properly. For information on how to analyze deadlocks with SQL Server Profiler, have a look at the following help article: https://docs.microsoft.com/en-us/sql/to ... erver-2017.
Additional information about the issue can be retrieved from SQL error log. For information on how to view the SQL Server error log, have a look at the following article: https://docs.microsoft.com/en-us/sql/re ... erver-2017.