PackagingResults Error Failed to build UAT.proj

Development Programming & Scripting
1

I have a dedicated game server compiled from UE 4.22 sources (Github stable branch) and an associated game client.

Unfortunately, using the editor UE 4.22 compiled from sources (Github stable branch), upon packaging the project in UE, I get the following error:

UATHelper: Packaging (Windows (64-bit)):        WinResources.cs(10,25): warning CS1692: Invalid number [C:\Program Files\Epic Games\UE_4.22_source\Engine\Source\Programs\AutomationTool\Win\Win.Automation.csproj]
UATHelper: Packaging (Windows (64-bit)):        WinResources.cs(291,25): warning CS1692: Invalid number [C:\Program Files\Epic Games\UE_4.22_source\Engine\Source\Programs\AutomationTool\Win\Win.Automation.csproj]
UATHelper: Packaging (Windows (64-bit)):          Win.Automation -> C:\Program Files\Epic Games\UE_4.22_source\Engine\Binaries\DotNET\AutomationScripts\Win.Automation.dll
UATHelper: Packaging (Windows (64-bit)):        Project file contains ToolsVersion="12.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="4.
0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=291333.
UATHelper: Packaging (Windows (64-bit)):          Mac.Automation -> C:\Program Files\Epic Games\UE_4.22_source\Engine\Binaries\DotNET\AutomationScripts\Mac\Mac.Automation.dll
UATHelper: Packaging (Windows (64-bit)):        Project file contains ToolsVersion="12.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="4.
0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=291333.
UATHelper: Packaging (Windows (64-bit)):        Project file contains ToolsVersion="12.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="4.
0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=291333.
UATHelper: Packaging (Windows (64-bit)):          TVOS.Automation -> C:\Program Files\Epic Games\UE_4.22_source\Engine\Binaries\DotNET\AutomationScripts\TVOS\TVOS.Automation.dll
UATHelper: Packaging (Windows (64-bit)):        
UATHelper: Packaging (Windows (64-bit)):        (see C:\Program Files\Epic Games\UE_4.22_source\Engine\Programs\AutomationTool\Saved\Logs\Log.txt for full exception trace)
PackagingResults: Error: Failed to build "C:\Program Files\Epic Games\UE_4.22_source\Engine\Source\Programs\AutomationTool\Scripts\UAT.proj":
UATHelper: Packaging (Windows (64-bit)): AutomationTool exiting with ExitCode=1 (Error_Unknown)
UATHelper: Packaging (Windows (64-bit)): BUILD FAILED
PackagingResults: Error: Unknown Error

After opening the project in Visual Studio, I noticed that I am missing UWP.Automation in the Solution Explorer.

If I switch engine version to the 4.22 installed from Epic Launcher, the client packaging succeeds, however, not from 4.22 built from Github production branch source, which I need it to, in order to connect to the same version of the game’s server built from the same engine branch.

Any suggestions?

Thank you!

2

SOLUTION:
Older Visual Studio versions are known to cause problems with Unreal Engine.

Just open the project with the newest Visual Studio 2019 and you should get a message like: “Install … for Unreal Engine Automation tool” etc. just hit “install” and let Visual Studio download the missing parts.

VoilĂ , packaging works fine now.

3

Late to the party but for future reference this worked for me in VS 2022.

Another post for this issue says to resinstall the Windows SDK which I wouldn’t recommend as it may require a full rebuild of source (takes a lot of time!).

  1. Close all instances of VS down
  2. Open your UE4.sln
  3. Find the Automation tool project
  4. Right Click > clean
  5. Right Click > build
  6. Close down and restart your packaged build, it should work now.
2 Likes
4

Can confirm this works on VS 2022, UE4.27

Necro’ing for visibility.

Oculus Source Build of UE4

1 Like