Let us examine

Error log file format

database disk image is malformed

Message text :

Error log file format
because of:
sqlite3_step failed: database disk image is malformed
db: C: \ Program Files \ 1cv8 \ srvinfo \ reg_1541 \ 34eda2fe-bcf4-485e-ab47-4f302319f59a \ 1Cv8Log \ 1Cv8.lgd
sql: SELECT severity, date, connectID , session, transactionStatus, transactionDate, transactionID, userCode,
computerCode, appCode, eventCode, comment, metadataCodes, sessionDataSplitCode, dataType, data, dataPresentation,
workServerCode, primaryPortCode, secondaryPortCode FROM EventLog WHERE date < 3155378867999999 AND eventCode IN (1,2,5,6,7,8,9,10,11,12,13,14,15,16,17,18,20,21 , 22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42) ORDER BY date DESC

Everything is sad. Logbook killed some system failure.

We learn that the platform since version 8.3.5.1068 log is stored in a SQLite database file. This file has an extension lgd. (More http://v8.1c.ru/o7/201310log/index.htm )

The forums write that it is necessary to unload and load the SQLite database, to restore its rabotosposobonost, but with possible data loss.

Download and unpack here https://www.sqlite.org/download.html the latest version of the utility for your operating system.
I went:
Precompiled Binaries for Windows sqlite-shell-win32-x86-3081101.zip (313.47 KiB)
The command-line shell program (version 3.8.11.1). (Sha1: 1640b3608784a36a113d4fcf69681503e4e9cdc3)

We take our magazine, its path can be taken from text messages

C: \ Program Files \ 1cv8 \ srvinfo \ reg_1541 \ 34eda2fe-bcf4-485e-ab47-4f302319f59a \ 1Cv8Log \ 1Cv8.lgd

and copy the folder with the utility.

Execute the command on the command line

sqlite3 1Cv8.lgd ".dump"> 1.txt

those. We do a database dump to a text file.
Waiting for completion, making recovery team

sqlite3 new.db ".read 1.txt"

At the end we get a workable database log file in new.db
Now you can put yourself in the archive and start a new log.
Or try to return to the place of damaged log.

Stay backuped