Internal build system error. read the full binlog without getting a BuildFinishedMessage, while the

Hi, I´m having a problem with my unity , everytime I open a project or create a new one the error appeares and I can´t nothing about it , I have tried to unistall unity and reinstall it , I have tried to remove the library folder so the unity generates a new one , and nothing seems to work.
Where’s the error :
Internal build system error. read the full binlog without getting a BuildFinishedMessage, while the backend process is still running

How to troubleshoot build failures:

First, make a blank project with a single blank scene and prove that it builds successfully.

If the blank project does NOT build, go fix your Unity installation or your other tools, such as Android SDK, NDK, JDK, etc. It may even be necessary to change to a different version of Unity3D. It is generally best to stay with LTS versions of Unity3D.

Until you can build a blank project to the target platform, don’t fiddle with anything else.

Once you can build a blank project, now bisect the problem by bringing over parts of your current project and building it one subsystem at a time, perhaps stubbing things out that might trigger compiler errors.

Most often things that prevent building are third-party libraries such as Firebase.

Once you identify the subsystem, go to the documentation for it and make sure you are doing it correctly.

It may also be helpful to work through a tutorial or two for whatever subsystem is making the build fail.

Android build not building:

Recently (circa July 2022) there have been reports of Unity’s installer failing to install the Android Tools.

Here was how I brought up Unity2020.3.41 and the Android SDK 31 on October 30, 2022:

Android Gradle errors and other related stuff:

I´m using unity 2022.3.1f1 , now I tried to install every single module , only the language packs that I left unistalled , and then I tried to create a project 3D (core) and it didn´t fix the problem, is there another way to solve the problem , or I didn´t fix my unity in the right way?
I’m making a 3d open world just to give some information about that

1 Like

now it gave me this error

Internal build system error. Backend exited with code 2.
STDOUT:
Finished compiling graph: 333 nodes, 4019 flattened edges (4019 ToBuild, 0 ToUse), maximum node priority 123
[ 0s] Delete 94 artifact files that are no longer in use. (like Library\Bee\artifacts\mvdfrm\UnityEngine.RuntimeInitializeOnLoadManagerInitializerModule.dll_7D5347DD423F512A.mvfrm)
[ 1/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEngine.UI.AdditionalFile.txt
[ 2/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEngine.UI.rsp
[ 3/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEngine.TestRunner.rsp
[ 4/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEditor.TestRunner.AdditionalFile.txt
[ 5/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEditor.UI.rsp
[ 6/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEditor.UI.AdditionalFile.txt
[ 7/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEditor.TestRunner.rsp
[ 8/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/UnityEngine.TestRunner.AdditionalFile.txt
[ 9/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/Unity.VisualScripting.Core.AdditionalFile.txt
[ 10/332 0s] WriteText Library/Bee/artifacts/1900b0aE.dag/Unity.VisualScripting.Core.rsp
[ 11/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.OSXStandalone.Extensions.dll_C795A0A594EBE725.mvfrm
[ 12/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.iOS.Extensions.Common.dll_11A536A4613BA5CB.mvfrm
[ 13/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.LinuxStandalone.Extensions.dll_FE08B8700B3DE92A.mvfrm
[ 14/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.iOS.Extensions.dll_4654E4629C56C42A.mvfrm
[ 15/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.WindowsStandalone.Extensions.dll_F0C6748C2E6DCE7A.mvfrm
[ 16/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.iOS.Extensions.Xcode.dll_22DAA37C461428B1.mvfrm
[ 17/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.UnityTestProtocolModule.dll_8725CF7FC1724DE1.mvfrm
[ 18/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.GIModule.dll_A008152E9403D334.mvfrm
[ 19/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.WebGL.Extensions.dll_F55FCF69C85D548A.mvfrm
[ 20/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.UWP.Extensions.dll_5E9981E2ACFDCFE5.mvfrm
[ 21/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.GridModule.dll_939FBDF5F40D12A8.mvfrm
[ 22/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.GameCenterModule.dll_767FFAAFFA602EC9.mvfrm
[ 23/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.DSPGraphModule.dll_3A10D424F582C02F.mvfrm
[ 24/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.dll_D71574795C902E14.mvfrm
[ 25/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.DirectorModule.dll_34BF72BB8321EF0E.mvfrm
[ 26/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.ClusterInputModule.dll_A0BE0A572FF25602.mvfrm
[ 27/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.CrashReportingModule.dll_C4DE7659A0E568E9.mvfrm
[ 28/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.CoreModule.dll_B62EA207DBB87CB1.mvfrm
[ 29/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.ClusterRendererModule.dll_5A4A0A936BF86A9F.mvfrm
[ 30/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.ClothModule.dll_94E4158BBEF79C5C.mvfrm
[ 31/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.UnityAnalyticsModule.dll_3790306FBB1E4673.mvfrm
[ 32/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.UnityConnectModule.dll_0E81195078F283E7.mvfrm
[ 33/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.AudioModule.dll_2DFBB890E4DABD78.mvfrm
[ 34/332 0s] MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEngine.AssetBundleModule.dll_5C4CF72D539201F4.mvfrm
STDERR:
tundra: error: Couldn’t launch process with command line:
cmd.exe /c ““D:\unity version\2021.3.27f1\Editor\Data\Tools\netcorerun\netcorerun.exe” “D:/unity version/2021.3.27f1/Editor/Data/Tools/ScriptUpdater/ApiUpdater.MovedFromExtractor.exe” “Library\Bee\artifacts\mvdfrm\UnityEngine.AccessibilityModule.dll_088FF61EB8A14760.mvfrm” “D:\unity version\2021.3.27f1\Editor\Data\Managed\UnityEngine\UnityEngine.AccessibilityModule.dll””
errno: 0 (No error) GetLastError: 5 (0x00000005): Acesso negado.

Ok , I solved it , for the ones that may have this problem in the future , try installing all modules of the version you want and then restart ur pc , make sure that the unity is closed in the little arrow near the clock , and then run unity as admin and it should all be fine

2 Likes

hello.
can I give the best and simplest solution for this?
actually, I got this error many times.
I searched on many platforms and I found a simple solution which is
you can delete the Library folder and if you don’t want to do it you can Onli Delete Library/Bee folder that will work

4 Likes

Thanks, my computer switched off due to a power outage, and after rebooting the Unity project wouldn’t load, and deleting the Library folder worked!

i got he same issue on unity 2022.3.39 but i solved it by just deleting the Bee folder under library folder of you project. (Build Plateform were iOS)

1 Like