Unknown Cook Failure

Development Platform & Builds
, , , , , ,
1

I have been stuck on this for a couple weeks. Every time I build it fails on UAT/cooking. I have cleared all warnings. I have created a new package and imported all content. I updated my Visual Studio Community. Also I tried building a separate package and it works. If someone could please have a look at my logs and suggest ways of debugging I would appreciate it. I have version 4.14.1 installed.

PackagingResults:Error: Error Unknown Cook Failure

UAT_Log.txt

Cook-2016.12.19-15.34.21.txt

2

Hi Brahzoo,

I did not find the text “Error Unknown Cook Failure” in either of the two logs you have posted. Please open your Output Log, right-click and select “Clear.” Then try and package your project again.

When packaging fails, cut and paste the entire newly generated data from the Output Log into a text file and post here. This should allow us to identify the cause of the packaging fail.

Lastly, please include what platform are you packaging for.

.

3

[link text][1]
[1]: 119462-outputlog.txt (472 KB)

Hi ,
I am trying to build a package for Windows 64bit (I tried 32 bit and got similar results). I have uploaded the output log as you requested. Thanks.

4

Here is the error that is currently causing your build to fail:

Error: === Critical error: ===
...Assertion failed: Result != NULL 
[File:D:\Build\++UE4+Release 4.14+Compile\Sync\Engine\Source\Runtime\Engine\Private\EdGraph\EdGraphNode.cpp] [Line: 107]

Debug “EdGraphNode.cpp” and retry packaging. Looking for the first “error” in your Output Log will reveal what needs to be corrected before moving forward.If after fixing the EdGraphNode you still need help, post a new log.

Some general steps you can take in the meantime are:

  1. After compiling and saving all, delete the Intermediate and Saved folders from the Project Folder
  2. Right-click on the Contents folder and select “Fix up redirectors in Folder”
  3. If EdGraphNode is part of a Blueprint, open the blueprint, click on Edit, and choose “Delete unused variables.”
  4. Recompile & save all.
  5. Package and save and post new log if packaging fails.

-.

5

I have never debugged a source code cpp file in Unreal. My project is fully in blueprints. I have located the EdGraphNode.cpp under: C:\Program Files\Epic Games\4.14\Engine\Source\Runtime\Engine\Private\EdGraph

I have found the line that it is complaining about: UEdGraphPin* UEdGraphNode::FindPinChecked(const FString& PinName, const EEdGraphPinDirection Direction) const { UEdGraphPin* Result = FindPin(PinName, Direction); check(Result != NULL); return Result; }

I opened up the EdNodeGraph.cpp file in VIsualStudio and tried adding some print statements. Now I saved it, and how do I compile? How do i link it with my project?

6

Since it was referencing a .cpp file and you mentioned that you updated VS Community I thought you were working on a Code Project. However, it should not make a difference: Skip the compile and recompile steps, following the remaining steps, including deleting the Intermediate and Saved folders.

Clear the output log and try to package again. If it still fails to package, cut and paste the contents from the new output log into a text file and post.

7

I did the steps as you mentioned above. I had to compile every blueprint individually, I found some new warnings got rid of the, but still that didn’t help my case. I also deleted the cache in:
C:\Users…\AppData\Local\UnrealEngine

Here is my updated output.log, it seems very similar:
link text

Thanks

8

Can you locate and post the following log: C:\Users\Brahzoo\AppData\Roaming\Unreal Engin
e\AutomationTool\Logs\C+Program+Files+Epic+Games+4.14\Cook-2016.12.22-14.13.40.txt

9

as requested:
link text

10

This log is almost identical to the Output log which is not giving me anything to go on beyond the EdGraphNode.cpp error. (If you haven’t already, remove this blueprint or node from your project).

At this point, the last thing I can suggest is to send your project as a link to a zipped project on Dropbox, Google Drive, etc to me on our and I will try to recreate the crash on our end.

11

The error log is basically saying that one of your blueprints is returning a null reference. We tried to locate the blueprint in question, unfortunately the project is too complex for us to track down without any indication on where it may be.