Project import failure after database restore (attach error: project already locked to instance)

CS 4.1.2

We have had a CS database corruption (unknown reason), tried to repair it with

mongod --dbpath ./ --repair

but that failed after just a couple of seconds.
We had a backup and restored the database from that.

CS is now running and I tried to import a project that was created after the latest database backup.
I get this error in the CS GUI:

Unable to attach project: ServerError: attach error: project already locked to instance

There is a file named cs.lock in the project folder.
Is this how the project is locked to instance?
Should i manually remove this file before trying to import it?


It is okay to remove cs.lock provided it was created after the database backup that you restored (and you have not successfully attached the project in the meantime), then again try to attach.

1 Like

Worked out great!

What would you recommend in the case where the project was already present in the latest database backup but a large number of jobs (~50) was created between the latest backup and database corruption?
We can import one by one right?
But would it make more sense to make a copy of the project folder with all the jobs, delete the project from the CS interface and then reimport the ‘whole’ project again?
Both approaches are feasible, right?

Thank you again!