Ask a Question

error 2.1.0 can't start : program creates a corrupt readyapi.h2.db.

johandelaat
Occasional Contributor

error 2.1.0 can't start : program creates a corrupt readyapi.h2.db.

Just installed version 2.1.0 but can't start it as program creates corrupt readyapi.h2.db.

Delting file - as indicated in error message - doesn't fix the problem as the newly created db is corrupt again.

 

Error message : The Dashboard database is corrupted. Some tiles are disabled. Remove the file readyapi.h2.db from C:\Users\jdelaat\.readyapi\db and restart Ready! API to create a new database.
WARNING: This will delete all your test results.

14 REPLIES 14
AV
SmartBear Alumni (Retired)
SmartBear Alumni (Retired)

Hi, midhungaddipati. AFAIK now it works well and we do not have open issues about corrupted db. Please describe you use case.

I've just upgraded my ReadyAPI to the latest version (2.3.0)and I'm getting the below error popup message when ever I open the ReadyAPI.

Error message : The Dashboard database is corrupted. Some tiles are disabled. Remove the file readyapi.h2.db from C:\Users\QA\.readyapi\db and restart Ready! API to create a new database.
WARNING: This will delete all your test results.

 

When I run my test cases, they're all passing but I'm getting the error message showing the below error message from the logs. There's no change in the scripts. 

ERROR [SoapUI] An error occurred [Could not get JDBC Connection; nested exception is org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode [90020-176]], see error log for details
13:37:07,444 ERROR [errorlog] org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode [90020-176]

 

 

AV
SmartBear Alumni (Retired)
SmartBear Alumni (Retired)

Are you able to run previous version of ReadyAPI?

Are you sure that new and previous versions are not running simulataneously?

midhungaddipati
New Contributor

This error is being caused by opening multiple ReadyAPI instances at one time. This is causing the locking and corrupting of the users\.readyapi folder. Close all the instances of ReadyAPI and delete the db folder in the same folder. Now restart the ReadyAPI and it should be back to normal. 

AV
SmartBear Alumni (Retired)
SmartBear Alumni (Retired)

Thanks for heads up! Have a nice day!

cancel
Showing results for 
Search instead for 
Did you mean: