Here is another message I just recieved when reinstalling and trying to load database from last week. It said Unhandled exception has occurred????? This just keeps getting worse. By the way I have no problem running these files on my XP machine.
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text ************** System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Server stack trace: at Philips.Pronto.SQLiteClient.SQLiteInterOp.sqlite3_exec(IntPtr dbHandle, String strSql, IntPtr pvCallback, IntPtr pvParam, String& strErrMsg) at Philips.Pronto.SQLiteClient.SQLiteInterOp.SqliteExecute(IntPtr dbHandle, String strSql, IntPtr pvCallback, IntPtr pvParam, String& strErrMsg) at Philips.Pronto.SQLiteClient.SQLiteImplementation.ExecuteCommand(String strQuery) at Philips.Pronto.SQLiteClient.SQLiteCommand.ExecuteNonQuery() at Philips.Pronto.DatabaseServer.EditorDbServer.RestoreDatabase(String strRestoreDBName, DatabaseType eDBType) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Philips.Pronto.DatabaseServer.EditorDbServer.RestoreDatabase(String strRestoreDBName, DatabaseType eDBType) at Philips.Pronto.Editor.DatabaseAccess.RestoreMyDatabase(IWin32Window owner) at Philips.Pronto.Editor.MainForm.OnFileRestoreMyDatabase(MenuCommand command) at Philips.Pronto.Common.MenuCommand.Execute() at Philips.Pronto.Common.MenuStripCommandExecutor.menuItem_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
