Cooking fails - stack for UAT, UnknownCookFailure

Cant package my game without getting UnknownCookFailure during “stack for UAT”. Cant find any clues in logs what could cause it. When packing empty Project with the same used plugins, it works right. But something in my Project is blocking packaging to work. Any tips how to find the cause are welcome. :slight_smile: Using 4.16.3

In UAT_log.txt
Cook: LogWindows:Error: begin: stack for UAT
Cook: LogWindows:Error: === Critical error: ===
Cook: LogWindows:Error:
Cook: LogWindows:Error: Fatal error!
Cook: LogWindows:Error:
Cook: LogWindows:Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000000

Cook: LogWindows:Error: end: stack for UAT
CommandUtils.Run: Run: Took 82,0398045s to run UE4Editor-Cmd.exe, ExitCode=3

Program.Main: ERROR: AutomationTool terminated with exception:…

Program.Main: AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)

Attached all related logs.

Packing settings (nativization method is disable out of screen)

[link text][2]

With 4.17.1 got same but with:
UATHelper: Packaging (Windows (64-bit)): Cook: LogWindows: Error: Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\Build++UE4+Release-4.17+Compile\Sync\Engine\Source\Runtime\Core\Public\Containers/Array.h] [Line: 596]
UATHelper: Packaging (Windows (64-bit)): Cook: LogWindows: Error: Array index out of bounds: 6 from an array of size 6

Going to go blueprints beter through, having some errors. Not sure if those were with 4.16.3, but checking all and seeing if the stack for UAT fail would go away.

After fixing all errors and warnings, getting still the same fail in 4.17.1. Going to wait 4.17.2 since its having some GetWorldFromContextObject error fix. Getting that error if having compilation manager enabled in Project settings.

link text

Got this one solved after deleting few object pool blueprints that had no class assigned or something similar. Project could be now packaged, even the packaged Project start during start up. But will make another ticket for that if not finding the bug during next week or few.