I have repeatedly been getting this error for some time now it happens randomly when optimization is running. It happens during NEMO and it also happens if using OSeMOSYS, and it happens with any solver. I tried different computers and it still happens and it also happens with different models. It also happens with any versions of LEAP. I write programs in VBA to control LEAP and run many scenarios in a row, changing variables, and extracting results, then running more scenarios. I have tried many workarounds but found nothing to circumvent the error. Any fix would be great appreciated as this greatly slows down progress when executing programs and running many scenarios, especially overnight.

Thanks,

Matt

Debug information:

Academic license - for non-commercial use only - expires 2024-04-19

2023-22-Jul 03:25:12.571 Started modeling scenario.

2023-22-Jul 03:25:12.571 Validated run-time arguments.

2023-22-Jul 03:25:12.571 Connected to scenario database. Path = C:\Users\mbdavis\DOCUME~1\LEAPAR~1\_SETTI~1\_Work\0\NEMO_2~2.SQL.

2023-22-Jul 03:25:12.596 Dropped pre-existing result tables from database.

2023-22-Jul 03:25:12.596 Verified that transmission modeling is not enabled.

2023-22-Jul 03:25:12.842 Created parameter views and indices.

2023-22-Jul 03:25:12.843 Created temporary tables.

NEMO encountered an error with the following message: TaskFailedException

nested task error: SQLite.SQLiteException("database is locked")

Stacktrace:

[1] sqliteerror(handle::Ptr{Nothing})

@ SQLite c:\users\jason\.julia\packages\SQLite\wpQeE\src\SQLite.jl:29

[2] sqliteerror(db::SQLite.DB)

@ SQLite c:\users\jason\.julia\packages\SQLite\wpQeE\src\SQLite.jl:124

[3] macro expansion

@ c:\users\jason\.julia\packages\SQLite\wpQeE\src\consts.jl:24 [inlined]

[4] sqliteprepare

@ c:\users\jason\.julia\packages\SQLite\wpQeE\src\SQLite.jl:204 [inlined]

[5] SQLite._Stmt(db::SQLite.DB, sql::String)

@ SQLite c:\users\jason\.julia\packages\SQLite\wpQeE\src\SQLite.jl:132

[6] Stmt

@ c:\users\jason\.julia\packages\SQLite\wpQeE\src\SQLite.jl:162 [inlined]

[7] prepare

@ c:\users\jason\.julia\packages\SQLite\wpQeE\src\tables.jl:117 [inlined]

[8] execute(conn::SQLite.DB, sql::String, params::NamedTuple{(), Tuple{}})

@ DBInterface C:\Users\Jason\.julia\packages\DBInterface\1Gmxx\src\DBInterface.jl:130

[9] #execute#2

@ C:\Users\Jason\.julia\packages\DBInterface\1Gmxx\src\DBInterface.jl:152 [inlined]

[10] execute

@ C:\Users\Jason\.julia\packages\DBInterface\1Gmxx\src\DBInterface.jl:152 [inlined]

[11] run_qry

@ c:\users\jason\.julia\packages\NemoMod\cfWKn\src\other_functions.jl:1158 [inlined]

[12] macro expansion

@ c:\users\jason\.julia\packages\NemoMod\cfWKn\src\other_functions.jl:1134 [inlined]

[13] (::NemoMod.var"#121#threadsfor_fun#25"{Dict{String, Tuple{String, String}}, ReentrantLock, Dict{String, DataFrames.DataFrame}, Vector{String}})(onethread::Bool)

@ NemoMod .\threadingconstructs.jl:85

[14] (::NemoMod.var"#121#threadsfor_fun#25"{Dict{String, Tuple{String, String}}, ReentrantLock, Dict{String, DataFrames.DataFrame}, Vector{String}})()

@ NemoMod .\threadingconstructs.jl:52.

To report this issue to the NEMO team, please submit an error report at https://leap.sei.org/support/. Please include in the report a list of steps to reproduce the error and the error message.

nothing

I've encountered this problem as well. Errors have always happened when turning the Analysis Module to the Results Module.

"NEMO optimization failed with error: the Gurobi solver failed but did not report any error" or "NEMO optimization failed with error: Gurobi Solver Reports Problem is Infeasible" popped up.

And they occurred in the branch: Transformation/Electricity Generation

Version:2020.1.106

Thank you in advance!

【Debug Information for Gurobi solver failed but did not report any error】

【Debug Information for Gurobi Solver Reports Problem is Infeasible】

Hi, Matthew -

I'm sorry it's taken a while to respond to your message. We've noticed this problem too and have implemented a fix in NEMO 2.0, which we plan to release soon. In the meantime, if the issue is still blocking your work, please email me, and I can share a pre-release version of NEMO 2.0 for you to use.

Thanks,