I am getting the following message when opening a newly created project:
Internal build system error. read the full binlog without getting a BuildFinishedMessage, while the backend process is still running
I’ve tried uninstalling and reinstalling 2022 LTS, among other recommended solutions from this thread, like deleting the Bee folder and the Library folder altogether:
Has anyone else gotten this immediately after starting a new project?
EDIT:
Expecting copy and paste from Kurt-Dekker, but I’m wondering if there are other possible causes solutions.
EDIT2:
The new project was just a test in 2022 LTS.
I’m currently using 2020 LTS, but I can load my main project and test projects in 2021 LTS.
Attempting to upgrade them from 2021 to 2022 (or 2020 to 2022) results in the internal build system error.
If you then get an error check the path where the project is. I can imagine two common issues: incorrect folder permissions or paths exceeding Windows‘ max path length of 260 characters (builds often create paths with additional depth such as adding the full package name as a folder name).
I got a little further. It wasn’t the project path permissions or length.
I was able to uninstall 2022 LTS, then reinstall with NO modules added.
New projects worked with no modules added.
Then, I added the WebGL module (my actual project is WebGL).
This worked fine too.
Then, I tried loading my WebGL project from 2020 LTS to 2022 LTS, and I get the internal build error.
I then tried creating a new project and it did not work, so now I’m completely hosed again.
Something about importing my 2020 WebGL project is corrupting the 2022 LTS installation.
I’ll try wiping out the Library directory before opening in 2022 LTS next.
EDIT:
And I tried reproducing this workaround, and now it doesn’t work again.
Wrong conclusion. The issue is more likely with your system, or generally with the Unity installation.
I would recommend uninstalling all editors and once you did that, uninstall the Hub. Then reinstall the Hub to its default location (don’t change install path) and then install an editor version (again, don’t change Hub settings, specifically the editor install path).
Then create a new project at its default location (Documents) and don’t change that Location path (if it’s not Documents, it must have remembered that setting so change it to your user’s Documents folder). Check if that works.
If it does, but fails to work once you move your own project to Documents, check your current project’s root folder’s permission settings. The current user should have full control permission:
Click on Advanced to verify that the Owner is your user, the user has Full control Access and the “Applies to” column reads as shown below:
I’m still considering permission issues as one of the main culprits with these kinds of errors. Particularly if you have ever edited that project on another system and just copied it over, or if it was created or moved outside the **?:\Users\<currentuser>\** path for user files, or possibly Hub or Editor was run as another user (Administrator).
Naturally, you want to choose a path below your project’s root as the target for making a build. If you point the build results to elsewhere, you also need to check that folder’s (and parent) permissions.
I’ll give it a try some time, but right now, I’ve switched to using 2021 LTS, since that works without too many immediate major changes… I can then upgrade to 2022 at a later time.
hi there, a few days ago i changed my drive permissions and when today i opened unity i got this error, so i am assuming it is because of permission issues, i tried to change permission but it didn’t work, also i couldn’t find my username in security tab
