Project crashes on startup - LogLinker:Error: Bad name index

Hi,

Since a few days, my project (1100+ hours) won’t open. Crashes everytime on startup.

It seems to be some asset naming issue (see excerpt of logs below). But I cant explain what could have caused this in the pst few days (my last stable version is from Saturday). Have not really done much of renaming / relocating lately (and I am always careful to fix up all redirectors).

I hope somebody can help me figure out how to locate the “wrong” asset. A few days of work is at stake!

What does this number, for instance mean?
Bad name index 1701080677/139

Also, I get this: [2018.06.28-19.59.51:565][ 0]LogLinker:Warning: Can’t find file ‘/Script/EnvironmentQueryEditor’
[2018.06.28-19.59.51:565][ 0]LogLinker:Warning: Can’t find file for asset ‘/Script/EnvironmentQueryEditor’ while loading F:/UE4ProjectsSamsung/MatrixProject/Content/Blueprints/AI_character/EQS/EQS_FindRangedShootLocation.uasset.
[2018.06.28-19.59.51:565][ 0]LoadErrors:Error: Error /Game/Blueprints/AI_character/EQS/EQS_FindRangedShootLocation : Can’t find file for asset. /Script/EnvironmentQueryEditor
[2018.06.28-19.59.51:565][ 0]LogLinker:Warning: Can’t find file ‘/Script/EnvironmentQueryEditor’

This is totally weird because I wrote this task months ago and there never was a problem. Also I am pretty sure that EQS was enabled in project settings. (could it have been disabled somehow?) Anyhow I cannot access the project to go into editor preferences.

Thanks for any hints!

2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1701080677/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1918985326/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1953064005/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 735349937/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1918985543/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1936482665/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1129469554/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1701604463/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index -99155860/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1194262528/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1632448338/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1918985543/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1869771886/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1702125901/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1129469554/139
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1207961/139
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 2652103/139
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1450336613/139
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1634027311/139
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1699151872/139
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogLinker:Error: Bad name index 1936028277/139
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:899][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.28-20.00.14:904][ 0]LogWindows: Windows GetLastError: Der Vorgang wurde erfolgreich beendet. (0)

I have found a solution. A single asset has been corrupted, no idea why, but it was one that was placed in my scene. Here are my learnings in case anybody else stumbles upon the same problem.

  1. Make sure you have the engine debugging symbols installed, that way you can learn a bit more about the nature of the problem when the editor crashes.
  2. Delete your intermediary folder and see if the problem goes away (did not work for me but many people with similar problems suggested it.)
  3. Update your project to a newer version and see if the problem goes away (did not work for me but many people with similar problems suggested it.
  4. If that still does not help, open your project folder in explorer and start deleting your assets in a controlled fashion. So for example start by deleting half of your assets while keeping the other half and see what happens. Use the same method to narrow down to single assets. Using this method I could pinpoint the one (!) asset out of 15 000 that caused the issue.

I hope this is helpful to you!

I would like to say I am quite dissappointed about the fact that nobody every seems to respond on AnswerHub. My five questions since summer 2016 have not received a response and eventually I have returned to answer them myself. Maybe it is just me but honestly I have seen more badly formulated questions getting a response on the UE4 Answerhub. I would also think that I am an active member helping others so it kinda sucks that I never get back anything.

That was my last post on answerhub! Cheers.

Thank you for writing this up. I have a slightly different problem but these steps helped me.