Share via


ESENT QmgrDatabaseInstance Errors

Question

Monday, October 2, 2017 7:40 PM

A while back I looked at the Application Log and there where the following events (Source ESENT):

- qmgr.dll (6784) QmgrDatabaseInstance: De database-engine heeft een sessie (0) met fout (-1090) stopgezet.

- qmgr.dll (6784) QmgrDatabaseInstance: Kan geen nieuw logboekbestand maken, omdat de database niet naar het logboekstation kan schrijven. Het station heeft mogelijk te weinig schijfruimte of is alleen-lezen, is onjuist geconfigureerd of beschadigd. Fout -1032.

- qmgr.dll (6784) QmgrDatabaseInstance: Kan bewerking #-39 op database C:\ProgramData\Microsoft\Network\Downloader\qmgr.db niet terugdraaien. Fout: -510. Alle toekomstige database-updates worden geweigerd.

- qmgr.dll (6784) QmgrDatabaseInstance: Een poging het bestand C:\ProgramData\Microsoft\Network\Downloader\edbtmp.log te maken is mislukt. Systeemfout 80 (0x00000050): Het bestand bestaat. . Tijdens het maken van het bestand treedt fout -1814 (0xfffff8ea) op.qmgr.dll (6784)

- QmgrDatabaseInstance: De volgorde van de logboekbestanden in C:\ProgramData\Microsoft\Network\Downloader\ is gestopt vanwege een onherstelbare fout. Er kunnen geen updates meer worden uitgevoerd voor de databases die deze logboekbestandsvolgorde gebruiken. Los het probleem op en start het systeem opnieuw op, of voer een herstelbewerking uit vanuit de back-up.

Google Translate:

- qmgr.dll (6784) QmgrDatabaseInstance: The database engine has stopped a session (0) with error (-1090)

- qmgr.dll (6784) QmgrDatabaseInstance: Unable to create a new log file because the database can not write to the logger. The drive may not have enough disk space or is read-only, incorrectly configured or corrupted. Error -1032.

- qmgr.dll (6784) QmgrDatabaseInstance: Can not reverse operation # -39 on database C: \ ProgramData \ Microsoft \ Network \ Downloader \ qmgr.db. Error: -510. All future database updates are denied.

- qmgr.dll (6784) QmgrDatabaseInstance: An attempt failed to create the C: \ ProgramData \ Microsoft \ Network \ Downloader \ edbtmp.log file. System Error 80 (0x00000050): The file exists. . While creating the file, error -1814 (0xfffff8ea) occurs. Qmgr.dll (6784)

- QmgrDatabaseInstance: The order of log files in C: \ ProgramData \ Microsoft \ Network \ Downloader \ has stopped due to an irreversible error. No updates can be performed for the databases that use this log file order. Fix the problem and restart the system, or perform a recovery operation from the backup.

I would like to know if this is a serious problem and if so, what I can do about it.

I use:

Editie: Windows 10 Home
Versie: 1703
Build : 15063.608

And there has been a update:

- 13-09-2017 KB4038788 2017-09 Cumulatieve update voor op Windows 10 Version 1703 for x64 gebaseerde systemen

- 13-09-2017 KB4038806 2017-09 Beveilingsupdate voor Adobe Flash Player voor op Windows 10 Version 1703 voor x64 gebaseerde systemen

- 13-09-2017 KB890830 Windows-programma voor verwijderen van schadelijke software voor Windows 8, 8.1, 10 en Windows Server 2012,2012 R2, 2016 x64-editie - september 2017

The reports, as far as I can see, have been once. But because it looks like a notification stating that "" All future database updates are denied "and" No updates can be performed for the databases that use this log file order "I wondered whether this will be a problem in the future with windows updates.

All replies (2)

Tuesday, October 3, 2017 3:09 AM

Hi,

According to the error, it seems to be referring to Event ID: 104 Source : ESE.

http://www.eventid.net/display-eventid-104-source-ESE-eventno-10524-phase-1.htm

Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

It also prompts that the drive may not have enough disk space or is read-only, incorrectly configured or corrupted.

Meanwhile, I suppose that you could delete the edb.log. Then it could not related to the Windows Update.

Hope it will be helpful to you

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Wednesday, October 4, 2017 7:18 PM

Hi, thank you for your reply.

I've viewed the link you posted, but there is not much information about the problem and more information is only available to EventID.Net subscribers.

About the drive:

- There is more than enough space available on the drive.

- I do not think the drive is read-only because I can save files on it.

- As far as I know, the drive is not configured incorrectly, among other things because in device management it says "This device is working properly".

- However, I do not know if the drive is corrupted. Do you know a way I can test that?

I wanted to delete the edb.log, but I don't know how to do that (also I did a search for the edb.log and there were 43 edb.log files. And there were 12 edbtmp.log files). Is there perhaps a built-in feature in windows that can delete the edb.log? Do you know how I can delete the edb.log?