Error exporting results to sqlite via experimenter

Question

question

Lucas Matheus asked Apr 4, '23 Jeanette F commented Apr 7, '23

Error exporting results to sqlite via experimenter

While my model is running on Experimenter, an error appears in the system console " exception: query Error cannot commit - no transaction is active". In some models, some results were exported to sqlite. When the error occurs, the task hangs in "recording" status.

What could be causing this error?

Software Version:

FlexSim 23.0.3

experimenter results sqlite

1680611438832.png (17.1 KiB)

· 3

Jordan Johnson ♦♦ commented · Apr 04, 2023 at 03:10 PM

That does seem like an issue. I have some follow-up questions:

Is there a model where this happens consistently? If so, can you share it?
If you open a new model and run the experiment job, does this error occur? Normally, it doesn't make sense to run an experiment on an empty model like that, but it is a good test.
Is that the very first error you see? It feels like this error would come because of a previous error.
Is there anything special about your database file? Is it on a network drive, or is some other application attempting to read it at the same time?

0 ·

Lucas Matheus Jordan Johnson ♦♦ commented · Apr 04, 2023 at 04:12 PM

Hi @Jordan Johnson,

I was unable to replicate the error in a simplified model. Sorry.
This error doesn't occur in a new model.
Yes, it is the first error in the console.
Yes, the database it is on Onedrive.

0 ·

Jeanette F ♦♦ commented · Apr 07, 2023 at 04:37 PM

Hi @Lucas Matheus, was Jordan Johnson's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 ·

Answer 1 · 2023-04-04T16:30:42Z

Jordan Johnson answered Apr 4, '23

I suspect having the file in a OneDrive folder is the issue. My theory is that queries that read the database work just fine, but that queries that attempt to write to the database fail. For example, beginning a transaction would require write permission, and that fails quietly. But then finishing the transaction fails loudly for some reason. In any case, I think the answer is to move the database file to somewhere besides the OneDrive folder. You can use a custom path for the file with these options:

1680625828112.png (14.8 KiB)

question