RunUAT.bat error retries not enabled

Development Platform & Builds
, ,
1

Hi,

I downloaded the source for 12.5 from Epic servers, UE4_QA 12.5 hotfix and compiled it in VS and opened the UE4 editor.

I want to distribute this to our team and when I try to build it with :

RunUAT.bat GUBP -Node=GatherRocket -TargetPlatforms=Win32+Win64 -NoDDC -CleanLocal -NoSign , I keep getting this error :

retries not enabled.

Below is log :

ParallelExecutor.Execute: OnlineSubsystemSteam.generated.cpp
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\steamclientpublic.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\steamuniverse.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\isteamutils.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\matchmakingtypes.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\isteamuserstats.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\isteamremotestorage.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\isteamscreenshots.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
ParallelExecutor.Execute: c:\users\su-pc\perforce\ue4_warrenwin_dico\ue4-qa\engine\source\thirdparty\steamworks\steamv132\sdk\public\steam\isteamunifiedmessages.h: error C4819: The file contains a character that cannot be represented in the current code page (932). Save the file in Unicode format to prevent data loss
GUBP.ExecuteNode: AutomationTool.AutomationException: BUILD FAILED: failed, retries not enabled:
at AutomationTool.UE4Build.Build(BuildAgenda Agenda, Nullable1 InDeleteBuildProducts, Boolean InUpdateVersionFiles, Boolean InForceNoXGE, Boolean InUseParallelExecutor, Boolean InForceNonUnity, Boolean InForceUnity, Boolean InShowProgress, Dictionary2 PlatformEnvVars, Nullable1 InChangelistNumberOverride, Dictionary2 InTargetToManifest) in C:\Users\SU-PC\Perforce\UE4_WarrenWin_DICO\UE4-QA\Engine\Source\Programs\AutomationTool\AutomationUtils\UE4Build.cs:line 1417
at GUBP.CompileNode.DoBuild(GUBP bp) in c:\Users\SU-PC\Perforce\UE4_WarrenWin_DICO\UE4-QA\Engine\Source\Programs\AutomationTool\GUBP\LegacyNodes.cs:line 329
at GUBP.GamePlatformMonolithicsNode.DoBuild(GUBP bp) in c:\Users\SU-PC\Perforce\UE4_WarrenWin_DICO\UE4-QA\Engine\Source\Programs\AutomationTool\GUBP\LegacyNodes.cs:line 1274
at AutomationTool.LegacyNode.DoBuild() in c:\Users\SU-PC\Perforce\UE4_WarrenWin_DICO\UE4-QA\Engine\Source\Programs\AutomationTool\GUBP\Nodes\LegacyNode.cs:line 81
at GUBP.ExecuteNode(BuildNode NodeToDo, Boolean bFake) in c:\Users\SU-PC\Perforce\UE4_WarrenWin_DICO\UE4-QA\Engine\Source\Programs\AutomationTool\GUBP\GUBP.cs:line 1506
Program.Main: AutomationTool exiting with ExitCode=1 (Error_Unknown)
Domain_ProcessExit
AutomationToolLauncher exiting with ExitCode=1
copying UAT log files…
BUILD FAILED

2

link text

3

I fixed it thanks. It was a system language setting for me was the problem, I had to change it to English.

In case anyone needs it :

Control Panel >Clock, Language, Region > Region > Adminsitrative > Language for non Unicode programs > Change system locale button.

4

If you receive this error nowadays, and correcting your clock isn’t fixing it, this is related to licensing verification called upon by msbuild and use of the MSVC build toolchain and Windows SDKs for Visual Studio. This issue occurs on or after December 2020 updates to the operating system, during Microsoft’s initial Windows 11 Insider Preview rollout. Unfortunately, if you have updated, which you most likely have automatically, license verification for use of Microsoft’s build tools and SDK is now mandatory. Thankfully, this is free for Community Edition users with a valid Microsoft Account. But if you’re a business with a Professional license to Visual Studio, a license will need to be purchased for your build server, specifically, and included in turnkey.

The changes have now propagated into Windows 10, and a valid Microsoft account is required to use the command-line build tools and Windows software development kit. This will result in the error “Retries failed:” due to templates from the Windows SDK and MSVC development headers that will fail to import if your machine is not correctly licensed to use the toolchain and SDK:

Many businesses using AutoSDK ran into this issue on in-house servers with CO/CI continuous delivery pipelines configured. Our easy solution was turnkey (which will come with UE5), which allows us to provide licensing files for Microsoft Products (as well as others) that will automatically inject the registry and configure the system correctly with the business license and account details. But may not be yours.

  1. Verify that Visual Studio is correctly logged into the Microsoft account associated with your installation, by starting the IDE and checking on that. Re-login if you are asked to reauthenticate, do so.
  2. Be sure to use the Visual Studio Developer Command Prompt to kick off the BuildGraph to ensure the correct environment.
1 Like
5

OMG. I was about ready to throw my computer out the window. Signing into VS (even though it’s community) and then going through their dev tools fixed it.

Day wasted of trying to get this thing to build, thinking it was everything else but this. Thankyou.