ham radio deluxe sharing logbook file mariadb

Ian is going to attempt the reinstall as well. Although, he uses Microsoft SQL Server and not Maria DB.

I have never experienced this issue myself, but a close friend recently has, and he fixed it by completely uninstalling Ham Radio Deluxe using the freeware version of Revo Uninstaller, before re-installing it.

A direct query of the database confirms the record has not been written. However, after 10 attempts at 1 second intervals, the contact cannot be found in the database. 10:45:37.9388 WARNING: Contact was not verified as logged in HRD 10:45:21.9301 Contact successfully relayed to HRD QSO Relay then tries to verify that the contact has in fact been written to the database: 10:45:21.9301 Verifying contact was logged by HRD <- NOTE HRD Logbook indicates that 31 fields will be added to the 'MI1CCU' database Ham Radio Deluxe Version Release 6.4.0.647Īdded 31 Fields to MI1CCU. Here is the conversation between QSO Relay and the HRD Logbook command line interface: The contact is relayed from QSO Relay to HRD Logbook. 10:45:18.5675 Contact successfully logged in SQLite The contact is written to QSO Relay SQLite database file: Some of the detail has been removed for clarity and replaced with 4-dot ellipses (.) Here is a snippet from a session tracing log captured by Ian, that shows the problem that both Ian and Panos are experiencing.

They are both using Maria DB as the back-end database server. I have been made aware of two QSO Relay users (Ian, MI1CCU/EI3HFB and Panos, SV8JNL) who are experiencing a problem with HRD Logbook not logging contacts.

Ham radio deluxe sharing logbook file mariadb