FSQL Crash

Archived Topics
1

This has me puzzled: I have been using FSQL for about 1.5 years and it has never crashed unexpectedly like this before. Here is what I see in the event log. I have been working in the designer from a remote computer this week and did not see any problems. There is one client running at all times (this started this week). Take a look at the attached dump from the log viewer. There are more errors than I am able to figure out. Some of the errors there I have seen before but nothing like this.

I tried to post the file but “The extension xml is not allowed.” I will email it.

[code]Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 4/14/2010
Time: 5:11:07 PM
User: N/A
Computer: FACTORYPMI
Description:
EventType clr20r3, P1 factorysql service.exe, P2 4.2.11.0, P3 4a79aa85, P4 system.data.sqlite, P5 1.0.46.0, P6 47005c70, P7 218, P8 0, P9 system.data.sqlite.sqlite, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 66 00 61 00 63 00 .f.a.c.
0018: 74 00 6f 00 72 00 79 00 t.o.r.y.
0020: 73 00 71 00 6c 00 20 00 s.q.l. .
0028: 73 00 65 00 72 00 76 00 s.e.r.v.
0030: 69 00 63 00 65 00 2e 00 i.c.e…
0038: 65 00 78 00 65 00 2c 00 e.x.e.,.
0040: 20 00 34 00 2e 00 32 00 .4…2.
0048: 2e 00 31 00 31 00 2e 00 …1.1…
0050: 30 00 2c 00 20 00 34 00 0.,. .4.
0058: 61 00 37 00 39 00 61 00 a.7.9.a.
0060: 61 00 38 00 35 00 2c 00 a.8.5.,.
0068: 20 00 73 00 79 00 73 00 .s.y.s.
0070: 74 00 65 00 6d 00 2e 00 t.e.m…
0078: 64 00 61 00 74 00 61 00 d.a.t.a.
0080: 2e 00 73 00 71 00 6c 00 …s.q.l.
0088: 69 00 74 00 65 00 2c 00 i.t.e.,.
0090: 20 00 31 00 2e 00 30 00 .1…0.
0098: 2e 00 34 00 36 00 2e 00 …4.6…
00a0: 30 00 2c 00 20 00 34 00 0.,. .4.
00a8: 37 00 30 00 30 00 35 00 7.0.0.5.
00b0: 63 00 37 00 30 00 2c 00 c.7.0.,.
00b8: 20 00 32 00 31 00 38 00 .2.1.8.
00c0: 2c 00 20 00 30 00 2c 00 ,. .0.,.
00c8: 20 00 73 00 79 00 73 00 .s.y.s.
00d0: 74 00 65 00 6d 00 2e 00 t.e.m…
00d8: 64 00 61 00 74 00 61 00 d.a.t.a.
00e0: 2e 00 73 00 71 00 6c 00 …s.q.l.
00e8: 69 00 74 00 65 00 2e 00 i.t.e…
00f0: 73 00 71 00 6c 00 69 00 s.q.l.i.
00f8: 74 00 65 00 20 00 4e 00 t.e. .N.
0100: 49 00 4c 00 0d 00 0a 00 I.L…

Event Type: Error
Event Source: FSQLSrc
Event Category: None
Event ID: 0
Date: 4/14/2010
Time: 5:11:05 PM
User: N/A
Computer: FACTORYPMI
Description:
Unhandled system exception: System.Data.SQLite.SQLiteException: The database file is locked
Unable to close due to unfinalised statements
at System.Data.SQLite.SQLiteConnectionHandle.ReleaseHandle()
at System.Runtime.InteropServices.CriticalHandle.Cleanup()
at System.Runtime.InteropServices.CriticalHandle.Dispose(Boolean disposing)
at System.Runtime.InteropServices.CriticalHandle.Dispose()
at System.Data.SQLite.SQLite3.Close()
at System.Data.SQLite.SQLiteConnection.Close()
at FactorySQL.DataCacheSystem.RefreshSystemStatus()
at FactorySQL.DataCacheSystem.VacuumDB()
at FactorySQL.DataCacheSystem.LoadThreadWork()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 4/14/2010
Time: 5:11:17 PM
User: N/A
Computer: FACTORYPMI
Description:
The FactorySQL service terminated unexpectedly. It has done this 1 time(s).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.[/code]

2

Yikes, that is indeed a strange/rare event. Luckily though it has a lot of information.

Basically, an error occurred in the data cache system and wasn’t handled properly. It’s possible, since the error refers to the file being locked, that restarting FactorySQL resolved the problem and it won’t happen again. However, since I’ve never seen this before, either it was a heavy alpha-particle day, or there’s something unique about the file in question, the datacache db.

That file is “data_cache_db.fdb” in the install directory. Take a look at it- is it abnormally large? If so, there could be a lot of cached data backed up, or a lot of quarantined data. If it’s not big it could have just been a fluke. Either way, you may want to shut down FSQL, rename that file, and start it up again in order to create a new DB file.

Let me know how the file looks.

Regards,

3

The filesize was 694K. I renamed the file like you requested and the new file it created is 4K in size.
The crash has not happened again, but I will keep you posted.