Page 1 of 1

Jet database error

Posted: Sat Dec 15, 2007 3:43 pm
by martijnj
When I start HB I get the following error. Translated to English:
The Microsoft Jet-Database-Engine has stoped the proces because you and an other user thies to change the same data.

I rebooted the system not solving the problem.

Please help :(

Martijn

Below I added the dump:
====== Begin Dump - Saturday, December 15, 2007 21:23:59 ======
Server Version = 3.01

==================================
======== House Server Thread =======
==================================
Thread Type = Main UI Thread
Thread ID = 7E8
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 00406DBC 01:00005DBC C:\Program Files\HouseBot\HouseBotServer.exe

Registers:
EAX:013B8DF4
EBX:013D7088
ECX:00000000
EDX:00000000
ESI:0012F3D0
EDI:00000007
CS:EIP:001B:00406DBC
SS:ESP:0023:0012F35C EBP:00000000
DS:0023 ES:0023 FS:003B GS:0000
Flags:00050287

Call stack:
Address Frame


====== End Dump ======

====== Begin Dump - Saturday, December 15, 2007 21:24:43 ======
Server Version = 3.01

==================================
======== House Server Thread =======
==================================
Thread Type = Main UI Thread
Thread ID = 908
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 00406DBC 01:00005DBC C:\Program Files\HouseBot\HouseBotServer.exe

Registers:
EAX:0841A3CC
EBX:013D6950
ECX:00000000
EDX:00000000
ESI:0012F3D0
EDI:00000007
CS:EIP:001B:00406DBC
SS:ESP:0023:0012F35C EBP:00000000
DS:0023 ES:0023 FS:003B GS:0000
Flags:00050287

Call stack:
Address Frame


====== End Dump ======

====== Begin Dump - Saturday, December 15, 2007 21:25:09 ======
Server Version = 3.01

==================================
======== House Server Thread =======
==================================
Thread Type = Main UI Thread
Thread ID = 90C
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 00406DBC 01:00005DBC C:\Program Files\HouseBot\HouseBotServer.exe

Registers:
EAX:013FBF9C
EBX:013D7180
ECX:00000000
EDX:00000000
ESI:0012F3D0
EDI:00000007
CS:EIP:001B:00406DBC
SS:ESP:0023:0012F35C EBP:00000000
DS:0023 ES:0023 FS:003B GS:0000
Flags:00050287

Call stack:
Address Frame


====== End Dump ======

====== Begin Dump - Saturday, December 15, 2007 21:27:09 ======
Server Version = 3.01

==================================
======== House Server Thread =======
==================================
Thread Type = Main UI Thread
Thread ID = 80C
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 00406DBC 01:00005DBC C:\Program Files\HouseBot\HouseBotServer.exe

Registers:
EAX:0141BCF4
EBX:013D7150
ECX:00000000
EDX:00000000
ESI:0012F3D0
EDI:00000007
CS:EIP:001B:00406DBC
SS:ESP:0023:0012F35C EBP:00000000
DS:0023 ES:0023 FS:003B GS:0000
Flags:00050287

Call stack:
Address Frame


====== End Dump ======

====== Begin Dump - Saturday, December 15, 2007 21:30:46 ======
Server Version = 3.01

==================================
======== House Server Thread =======
==================================
Thread Type = Main UI Thread
Thread ID = 7B4
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 00406DBC 01:00005DBC C:\Program Files\HouseBot\HouseBotServer.exe

Registers:
EAX:083F5584
EBX:013D7030
ECX:00000000
EDX:00000000
ESI:0012F3D0
EDI:00000007
CS:EIP:001B:00406DBC
SS:ESP:0023:0012F35C EBP:00000000
DS:0023 ES:0023 FS:003B GS:0000
Flags:00050287

Call stack:
Address Frame


====== End Dump ======

Posted: Sat Dec 15, 2007 11:00 pm
by ScottBot
I'd say the either another process is also writing to the HBData.mdb file, or your database is corrupt. Make sure you restart the system to and give it another try.

Replaced with backup

Posted: Sun Dec 16, 2007 3:48 am
by martijnj
Hi Scott,

The file was not in use. So I replaced it with the autobackup database.

Would you like to have a copy of the corrupted?

Martijn

Posted: Sun Dec 16, 2007 11:32 am
by ScottBot
If your backup version is working well, then there's no need to send me the corrupted version. If you need me to try and repair it, then send it to me at [email protected].

Posted: Sun Dec 16, 2007 11:55 am
by Richard Naninck
Happens all the time after a PC crash of some sort. If you have MS Access, you can fix it yourself real easy by restoring and compressing the database. Little trick, but works all the time.