2011-02-05, 09:56
Matsutake Wrote:Maybe this will help ... here's what the errorlog.txt file is showing.
Code:Title: Error
Message: Data Source cannot be empty. Use :memory: to open an in-memory database
StackTrace: at System.Data.SQLite.SQLiteConnection.Open()
at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at EmberAPI.Database.FillDataTable(DataTable& dTable, String Command)
Date/Time: 2/4/2011 5:01:30 PM
===========================================================================================
OK, wild guess here... the ember code is not specifying the connection string in a truly conforming manner that perhaps Win 7 64 bit has some exposure to.
A quick google suggests the sqlite .net connector requires filename and version to be indicated in the connection string. The ember source suggests it is only providing the filename. I don't claim to be an expert in this area - it does work fine for most users. Maybe this is somehow exposed when you open other internet connections which the .net security profile is interacting with.... Maybe Tuscani has a view on this?
Only other possible tip is that for some reason your system is refusing to give a correct path to where the application is located, so when ember attempts to open media.emm it has some issue. Simple thing you can do to maybe check is see if when you scan something new do you see the media.emm file get updated (eg file size change, new date time etc).