Build failure during package, AutomationToolnot found

Development Programming & Scripting
1

Windows 10, 64 bit, Visual Studio 2015 (without update 3)

Happens in latest release and 4.11 release from github. Build fails instantly with

MainFrameActions: Packaging (Windows (64-bit)): Running AutomationTool...
MainFrameActions: Packaging (Windows (64-bit)): Could not load file or assembly 'AutomationTool, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the path specified.
MainFrameActions: Packaging (Windows (64-bit)):    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolea
MainFrameActions: Packaging (Windows (64-bit)): n suppressSecurityChecks)
MainFrameActions: Packaging (Windows (64-bit)):    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
MainFrameActions: Packaging (Windows (64-bit)):    at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
MainFrameActions: Packaging (Windows (64-bit)):    at System.Reflection.Assembly.LoadFrom(String assemblyFile)
MainFrameActions: Packaging (Windows (64-bit)):    at System.AppDomain.ExecuteAssembly(String assemblyFile, String[] args)
MainFrameActions: Packaging (Windows (64-bit)):    at System.AppDomain.ExecuteAssembly(String assemblyFile, String[] args)
MainFrameActions: Packaging (Windows (64-bit)):    at AutomationToolLauncher.Launcher.Main() in F:\411UnrealEngine\Engine\Source\Programs\AutomationToolLauncher\Launcher.cs:line 30
MainFrameActions: Packaging (Windows (64-bit)): AutomationToolLauncher exiting with ExitCode=193
MainFrameActions: Packaging (Windows (64-bit)): copying UAT log files...
MainFrameActions: Packaging (Windows (64-bit)): BUILD FAILED

I confirmed that AutomationTool.exe is in that location,

2

Hello Dahak,

Does this happen in your project only or does it also happen in blank C++ projects? It would be useful to know if it’s contained only to one project or if it’s something wrong across the board.

Could you upload the full log from the packaging attempt as well?

3

Absolutely. I just tried with a brand new blank project, exact same error.
Here’s the full log

4

This could be related to the file path that you’re using for your engine’s installation. Could you please try removing/moving the “411” in your “411UnrealEngine” folder? Having numbers at the beginning of a filename/folder name can cause some issues when it comes to UE4’s systems. If this makes no difference, can you open your engine’s solution and attempt to build the Automation Tool directly to see if it is indeed building correctly?

5

We haven’t heard from you in a while, Dahak. Are you still experiencing this issue? If so, could you refer to the question in my previous post? In the meantime, I’ll be marking this as resolved for tracking reasons.

6

Built it again without the 411, end result is that it now does not show the newly built version in the dropdown of engine sources. I managed to get it working on another computer in the house, though - nothing at all different in the way I did it.
Apologies for the late reply, wife has been in hospital.

7

“end result is that it now does not show the newly built version in the dropdown of engine sources.” Which dropdown is this that you’re mentioning?

8

The dropdown to select an engine when launching or converting a project file.

9

Ah, that’s what I assumed. After compiling an engine, be sure you’ve opened it once, via opening the UE4Editor.exe in the Engine/Binaries/Windows folder. After it’s opened once, it should show up in that list.

10

OK, launched the newly compiled editor, created a new blank project with no starter content to test, started compile - Exact same error.
Log

11

I’m not sure why this didn’t come up when I searched before, but take a look at this post where someone was having a similar issue. It seems like it may be a security problem with Windows.