CODEWITHSUNDEEP
unity-game-engineunity-editor
Lanthanum
Lanthanum

Reputation: 43

Internal build system error. read the full binlog without getting a BuildFinishedMessage, while the backend process is still running

I just can't use Unity! Every time when I want to open my project I have an error and Unity reccomends me to open project in Safe Mode. When the project's opening is finished (doesn't matter if I open it Safe Mode or not) I can do litteraly NOTHING - there's no objects on the scene, I can't open prefab, etc. There's error in the console "Internal build system error. read the full binlog without getting a BuildFinishedMessage, while the backend process is still running"

And when I try to create a new project it seems like it's gonna open, but i see this error. This project appears in the Unity Hub, but when I click on it, there's another problem.

I tried a lot of things, that I saw on the internet, for example: deleting "Library" folder or deleting "Cache" folder. I also tried to reinstall Unity Editor and Hub - nothing happened.

So, StackOverflow is my last hope. 😟

Edit: Sometimes when I try to open project I can see this.

Upvotes: 3

Views: 8416

Answers (7)

Sri-harish.k
Sri-harish.k

Reputation: 11

Closing and reopening the Unity editor works for me!

Upvotes: 0

Tadikus
Tadikus

Reputation: 1

I found that my problem was at the level of my command prompt. the cmd.exe was moved I repaired it and it works perfectly

Upvotes: 0

Zeinna Mochammad Farella
Zeinna Mochammad Farella

Reputation: 1

  1. remove any using namespace that calls "UnityEditor.Callbacks"
  2. save projects
  3. close unity
  4. rename your project folders the same name as the .sln file name (you probably changed your folders name)
  5. run unity with administrator

hopefully this would fix your issue

Upvotes: 0

Kenneth Rougeau
Kenneth Rougeau

Reputation: 1

Just a quick "me, too" post: Encountered the same error w/ the project stored on an external SSD. Moved the project to another drive & it cleared up. No idea why that drive hates Unity so much, but it's a constant pain in the rump.

Upvotes: -1

tstorm
tstorm

Reputation: 33

I got this error right after I created a new C# script. Hadn't even opened the script yet. So I closed out of the project, reopened it, and the error was gone. For a while. Then it came back. No solution, except I think I'll go back to Godot. This is about my third time to try to use Unity. I like the way it works, but I don't trust it at all.

Upvotes: 0

Mirror
Mirror

Reputation: 51

maybe you missed some modules to install, if you want to build in windows, then except windows support, you also need to install universal windows build support.

Upvotes: 0

Saphirah
Saphirah

Reputation: 23

This happened to me recently.

If it’s a project specific error, try to delete the Library and the Logs folder in your project. Then restart your PC. After this, start Unity Hub/Unity as administrator. For some users this fixed the issue.

But it looks like this is a Unity issue for you. Same for me! In my case the issue was installing Unity on a secondary hard drive with insufficient file permissions. For some reason windows would always reset my permission overrides and Unity would not be able to read/write from it‘s editor directory.

So the solution was to install Unity on my C:/ drive under C:/users/[USERNAME]/Unity/… Also try moving the Project to the same Hard Drive as the Unity install.

Upvotes: 1

Related Questions