The property database "Library/Search/propertyDatabase.db" is already opened.

[orville_redenbacher]

Lately I’ve been getting this error when I exit play mode. Does anyone know how to fix it? Deleting the Library folder didn’t work.

[Kurt-Dekker]

Perhaps some antivirus solution scanning it?

[madhoe]

I have this as well. Every time I edit any property,

The property database “Library/Search/propertyDatabase.db” is already opened.
UnityEditor.EditorApplication:Internal_InvokeTickEvents ()

The property database “Library/Search/propertyAliases.db” is already opened.
UnityEditor.EditorApplication:Internal_InvokeTickEvents ()

Very annoying

EDIT: Nvm, found out there were stray Unitys open for some reason

[orville_redenbacher]

@madhoe

I have this as well. Every time I edit any property,

The property database “Library/Search/propertyDatabase.db” is already opened.
UnityEditor.EditorApplication:Internal_InvokeTickEvents ()

The property database “Library/Search/propertyAliases.db” is already opened.
UnityEditor.EditorApplication:Internal_InvokeTickEvents ()

Very annoying

EDIT: Nvm, found out there were stray Unitys open for some reason

Was hoping this was the fix but I only have one instance of Unity open

[Kurt-Dekker]

@orville_redenbacher

but I only have one instance of Unity open

Then try reboot your computer… there might be sooper-seekrit headless processes that Unity fires off holding onto this.

[orville_redenbacher]

@Kurt-Dekker

Then try reboot your computer… there might be sooper-seekrit headless processes that Unity fires off holding onto this.

It seems to come back no matter what I do

[sebastiengrenier]

@orville_redenbacher

It seems to come back no matter what I do

Hi. Can you check your project’s Temp folder if you have any “PropertyDatabase_XXXXXXXXXX” files and delete those (without Unity opened). These are the lockfiles for the property databases. We can’t open a property database multiple times on a single file, so we use those lockfiles to manage that. However, “Library/Search/propertyDatabase.db” and “Library/Search/propertyAliases.db” are handled by Search and should not have multiple instances. I suspect the lockfiles were not properly during domain reload, and now you are stuck in a weird state. If there is no Temp folder or it does not contain any “PropertyDatabase_XXXXXXXXXX” files, please log a bug and we will investigate.

[eeprom]

@sebastiengrenier

Hi. Can you check your project’s Temp folder if you have any “PropertyDatabase_XXXXXXXXXX” files and delete those (without Unity opened).

That worked. Thanks.

Had my project crash a few times, which left some of these files hanging around.

[yagizdeneri]

@sebastiengrenier

Hi. Can you check your project’s Temp folder if you have any “PropertyDatabase_XXXXXXXXXX” files and delete those (without Unity opened).

works thank you

[FoodFish_1]

I have deleted the PropertyDatabase_xxxxx files and temporarily solves the problem. However the files quickly come back after regular usage and the errors resume.

[sebastiengrenier]

@FoodFish_1

I have deleted the PropertyDatabase_xxxxx files and temporarily solves the problem. However the files quickly come back after regular usage and the errors resume.

I’m sorry to hear that. Are the errors appearing during a single session after you’ve cleaned the files, or do you need to close the Editor and reopen it to see the errors again?
I’m asking because those files should get cleaned after Unity is closed, since they are in the temp folder. So if the error appears only after reopening Unity a second time, maybe the temp folder does not get cleaned up properly, but if they appear in the first session after you deleted them, then the problem is elsewhere.

In any case, if you are able to reproduce the issue with a sample project, could you file a bug report?

[TheVirtualMunk1]

I had this issue due to a hanging unity process in the Task Manager - so check if you have one as well and then close it completely.

[orville_redenbacher]

I suspect the reason for this was my constant forceful shutdowns of Unity when it hangs. It seems that if the Unity editor is not in focus, it has a higher chance of hanging while reloading, importing, etc. Bit of a pain to be unable to switch to another window while Unity works.

[recaremo01]

Thanks to Sebastian - this tip fixed my errors well.

[CodeSmile]

I also had this issue, due to me having to force-close Unity earlier and some process got stuck.

Ending the zombie process and deleting Temp folder fixed it.

[hadtofall]

I have this problem on 2021.3.5f1 LTS as well

[Noha_Morte]

@sebastiengrenier

Hi. Can you check your project’s Temp folder if you have any “PropertyDatabase_XXXXXXXXXX” files and delete those (without Unity opened). These are the lockfiles for the property databases. We can’t open a property database multiple times on a single file, so we use those lockfiles to manage that. However, “Library/Search/propertyDatabase.db” and “Library/Search/propertyAliases.db” are handled by Search and should not have multiple instances. I suspect the lockfiles were not properly during domain reload, and now you are stuck in a weird state. If there is no Temp folder or it does not contain any “PropertyDatabase_XXXXXXXXXX” files, please log a bug and we will investigate.

One up from me too, issue seems to be related to me shutting down the Unity Editor from the Task Manager after becoming non responsive. Restarting the editor or the system has no effect. Deleting the files with name starting with “PropertyDatabase_” with the Editor is closed worked just fine.

[iamarugin]

Same problem here. Any news on a fix?

[yengNami]

@sebastiengrenier

Hi. Can you check your project’s Temp folder if you have any “PropertyDatabase_XXXXXXXXXX” files and delete those (without Unity opened). These are the lockfiles for the property databases. We can’t open a property database multiple times on a single file, so we use those lockfiles to manage that. However, “Library/Search/propertyDatabase.db” and “Library/Search/propertyAliases.db” are handled by Search and should not have multiple instances. I suspect the lockfiles were not properly during domain reload, and now you are stuck in a weird state. If there is no Temp folder or it does not contain any “PropertyDatabase_XXXXXXXXXX” files, please log a bug and we will investigate.

This solved my issue. Thank you.

[Thatila]

@sebastiengrenier

Hi. Can you check your project’s Temp folder if you have any “PropertyDatabase_XXXXXXXXXX” files and delete those (without Unity opened). These are the lockfiles for the property databases. We can’t open a property database multiple times on a single file, so we use those lockfiles to manage that. However, “Library/Search/propertyDatabase.db” and “Library/Search/propertyAliases.db” are handled by Search and should not have multiple instances. I suspect the lockfiles were not properly during domain reload, and now you are stuck in a weird state. If there is no Temp folder or it does not contain any “PropertyDatabase_XXXXXXXXXX” files, please log a bug and we will investigate.

you got it thank you