"Exception loading structure piece" and "No key" error spam after upgrading a world to 1.17 and exploring chunks

OK while playing in my world I encountered the errors again, except this time I wasn't loading new chunks or even exploring and was in pre-existing chunks (far far away from areas where I haven't explored). Since I'm not sure if I encountered a freak accident I won't update the bug report to avoid putting potentially false information, but I'll post the errors that came up in this comment. If I should update the bug report to include me possibly encountering the errors in pre-existing chunks as well please let me know,

[23:47:44] [Server thread/ERROR]: No key dirt_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]; No key sapling_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]; No key foliage_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]
[23:47:44] [Server thread/ERROR]: Exception loading structure piece with id minecraft:jigsaw
java.lang.IllegalStateException: Invalid pool element found
	at dbf.k(SourceFile:54) ~[minecraft-1.17-client.jar:?]
	at java.util.Optional.orElseThrow(Optional.java:403) ~[?:?]
	at dbf.<init>(SourceFile:54) ~[minecraft-1.17-client.jar:?]
	at cuc.a(SourceFile:151) ~[minecraft-1.17-client.jar:?]
	at cni.a(SourceFile:415) ~[minecraft-1.17-client.jar:?]
	at cni.a(SourceFile:175) ~[minecraft-1.17-client.jar:?]
	at abe.l(SourceFile:511) ~[minecraft-1.17-client.jar:?]
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1764) ~[?:?]
	at aqu.c(SourceFile:151) ~[minecraft-1.17-client.jar:?]
	at abp$a.c(SourceFile:527) ~[minecraft-1.17-client.jar:?]
	at aqu.z(SourceFile:125) ~[minecraft-1.17-client.jar:?]
	at abp$a.z(SourceFile:536) ~[minecraft-1.17-client.jar:?]
	at abp.d(SourceFile:279) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.bg(SourceFile:771) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.z(SourceFile:759) ~[minecraft-1.17-client.jar:?]
	at aqu.bq(SourceFile:110) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.y(SourceFile:743) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.x(SourceFile:696) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.a(SourceFile:274) ~[minecraft-1.17-client.jar:?]
	at java.lang.Thread.run(Thread.java:831) [?:?]
[23:47:44] [Server thread/ERROR]: No key dirt_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]; No key sapling_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]; No key foliage_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]
[23:47:44] [Server thread/ERROR]: Exception loading structure piece with id minecraft:jigsaw
java.lang.IllegalStateException: Invalid pool element found
	at dbf.k(SourceFile:54) ~[minecraft-1.17-client.jar:?]
	at java.util.Optional.orElseThrow(Optional.java:403) ~[?:?]
	at dbf.<init>(SourceFile:54) ~[minecraft-1.17-client.jar:?]
	at cuc.a(SourceFile:151) ~[minecraft-1.17-client.jar:?]
	at cni.a(SourceFile:415) ~[minecraft-1.17-client.jar:?]
	at cni.a(SourceFile:175) ~[minecraft-1.17-client.jar:?]
	at abe.l(SourceFile:511) ~[minecraft-1.17-client.jar:?]
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1764) ~[?:?]
	at aqu.c(SourceFile:151) ~[minecraft-1.17-client.jar:?]
	at abp$a.c(SourceFile:527) ~[minecraft-1.17-client.jar:?]
	at aqu.z(SourceFile:125) ~[minecraft-1.17-client.jar:?]
	at abp$a.z(SourceFile:536) ~[minecraft-1.17-client.jar:?]
	at abp.d(SourceFile:279) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.bg(SourceFile:771) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.z(SourceFile:759) ~[minecraft-1.17-client.jar:?]
	at aqu.bq(SourceFile:110) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.y(SourceFile:743) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.x(SourceFile:696) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.a(SourceFile:274) ~[minecraft-1.17-client.jar:?]
	at java.lang.Thread.run(Thread.java:831) [?:?]
[23:47:44] [Server thread/ERROR]: No key dirt_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]; No key sapling_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]; No key foliage_provider in MapLike[{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},heightmap:"OCEAN_FLOOR",ignore_vines:1b,leaves_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},max_water_depth:0,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}}]
[23:47:44] [Server thread/ERROR]: Exception loading structure piece with id minecraft:jigsaw
java.lang.IllegalStateException: Invalid pool element found
	at dbf.k(SourceFile:54) ~[minecraft-1.17-client.jar:?]
	at java.util.Optional.orElseThrow(Optional.java:403) ~[?:?]
	at dbf.<init>(SourceFile:54) ~[minecraft-1.17-client.jar:?]
	at cuc.a(SourceFile:151) ~[minecraft-1.17-client.jar:?]
	at cni.a(SourceFile:415) ~[minecraft-1.17-client.jar:?]
	at cni.a(SourceFile:175) ~[minecraft-1.17-client.jar:?]
	at abe.l(SourceFile:511) ~[minecraft-1.17-client.jar:?]
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1764) ~[?:?]
	at aqu.c(SourceFile:151) ~[minecraft-1.17-client.jar:?]
	at abp$a.c(SourceFile:527) ~[minecraft-1.17-client.jar:?]
	at aqu.z(SourceFile:125) ~[minecraft-1.17-client.jar:?]
	at abp$a.z(SourceFile:536) ~[minecraft-1.17-client.jar:?]
	at abp.d(SourceFile:279) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.bg(SourceFile:771) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.z(SourceFile:759) ~[minecraft-1.17-client.jar:?]
	at aqu.bq(SourceFile:110) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.y(SourceFile:743) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.x(SourceFile:696) ~[minecraft-1.17-client.jar:?]
	at net.minecraft.server.MinecraftServer.a(SourceFile:274) ~[minecraft-1.17-client.jar:?]
	at java.lang.Thread.run(Thread.java:831) [?:?]

I would recommend not to explore new chunks as they will most likely have broken generation. The error can occur in any chunk if the game tries to get that key. It's supposed to have a value but the dfus have appeared to have done something bad to them. So it's the same problem, but the error is just showing up in different places.

I already knew not to generate anymore new chunks when I first saw the errors upon exploring the very small amount of new chunks conveniently unexplored/not generated. Will encountering the errors in pre-existing chunks have any negative side-effects though (I found out a few pre-existing chunks near my underground railway also throw the errors)?

I'll also update the bug report to mention the errors come up in pre-existing chunks as well.

The only negative effect should be errors in the log and maybe some performance degeneration. Since it appears to be a problem with values used with world gen nothing should happen to the chunks. If you are worried about the chunks having broken values stored in them that should be fixed when the dfu is working properly again since it will replace the problem with the proper value.

OK thanks for telling me.

I think the confirmation status should be changed to "Community Consensus".

Question, do you have any data packs in the world? If so, could you check if there are new versions for them specifically for 1.17 and if so, if using those instead solves the issue?

I'm not the reporter, but I have the same issue and I have no data packs.

Sorry for the late reply but I never used any data packs in my world. I don't even have the option to toggle data packs or view them for my world.

I'm experiencing the same errors as well. No data packs, vanilla server. 

Can also confirm, I get the same error entries on my 1.17 server running on linux including the performance impacts. No data packs are used.

If it's of any help, here's some info on my server:

Linux mineos-tkldev 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64

Attempting to run vanilla 1.17.jar file after previously generating / running world on vanilla 1.16.5

Seed: [-7657594132119525537]

No data packs or modifications of any kind.

Can confirm it happened to me too. I updated from Paper 1.16.5 to Spigot 1.17. I thought it might be a Spigot issue, but the other commenters did it on vanilla.

Just switching the jar from 1.16.5 to 1.17 and starting the world will throw the errors every launch:

Can confirm in 1.17.1 Pre-release 1.

Can confirm, the same issue from older versions too.

Should I upgrade my world and ignore these error messages. 

I would recommend staying in 1.16.5 until this issue is fixed.

Ok Thank you. Ampolive.

Also occurs on Ubuntu 18+.

BTW is "Status" really still "Open" or is it "In Progress"?

Yeah I am interested in this too as it's been quite a long while since this gamebreaking bug was reported

Edit: I can confirm this is reproducible for new maps too as randomly the exact same errors will be thrown. In my case however I have also seen a spike in CPU usage when this happens.

Please attach a world where this can be reproduced.

We have the same issue with our 1.17 server, also in chunks generated in earlier versions 1.16.x. The performance gets so bad from time to time that it causes the entire server to crash. Needs to be fixed as soon as possible.

Hey Thommy, This is as clean as I could manage getting my world. https://drive.google.com/file/d/1snaKn8LxyDSEoQ_FGx1cRl7W-bfrFx7v/view?usp=sharing Thanks for your help!

As much as I would like to upload a world where the issue is reproducible, I sadly can't for the following reasons:

1) My world where the issue is easily reproducible is far too large to upload (over 6GB uncompressed; 3.5GB compressed).

2) I don't have access to a cloud storage provider account where they allow uploads that large to be public without strict limitations.

3) Even if I could get a world where the issue always happens to a manageable size, sadly I'm stuck with 768kbps DSL and my ISP (Frontier Communications) seemingly limits file uploads to around 1MB. If I upload anything larger, the file becomes corrupted and my connection becomes unusable until the next day.

Someone else has uploaded a world file though so hopefully my horrible internet situation won't impact solving this bug.

It also might be worth trying to generate a new world with the same seed on 1.16.5 and then upgrade it to 1.17.x to see if the issue can be recreated at the same spots. If so people with affected world files just need to provide the seed and coordinates to a location where the issue occurs rather than uploading the world file it's self for people with cases like yours. The only thing we have to be careful of is that the issue may behave differently at particular spots depending on if they are old chunks, newly generated chunks, or up to date chunks.

Yeah I can also confirm his happens in my Minecraft server which was upgraded from 1.16.5 every once in a while my console will get filled with these error messages but thankfully haven’t experienced a server crash yet. 

Thanks. This was definitely reproducable using the attached world.

Thommy, if you need another world to check, please let me know and I'll post mine as well.

Can confirm in 1.17.1 Pre-release 3.

Can confirm in 1.17.1 Release Candidate 1.

Can confirm in 1.17.1 Release Candidate 2.

I'm not sure if this will help as I'm working on a PaperMC server with various plugins but just in case it's of any use...

I was having this issue with testing a 1.16.5 world that I'm preparing to upgrade to 1.17.1. As part of my preparation I ran up the server with the --eraseCache option and it seems to have fixed the problem.

Edit: Or maybe not. It appeared to fix the issue when I first tried it but rerunning the upgrade from scratch with --eraseCache hasn't worked. Sorry if this is a red herring.

Can someone with a test or backup world check if it works with the --forceupgrade flag?

I tried with forceupgrade and there's errors too

Can confirm, when updating 1.16.5 to 1.17.1, only on new chunks.
Is it safe to play this way?, or might better to load the 1.16.5 backup.

@Karim Rivera Load a backup, the bug decreased my TPS to 1.5 within 10 minutes, then the server crashed.

Restarting didn't help, so I had to load a backup.

@Til Weimann 
Thanks for the advice!, will wait until this bug has been fixed.
Now loading the backup

I have also been running into this on two of our 1.17.1 servers (Paper).  On one, we have experienced two crashes caused by this. The first crash was on the 8th of July and the second crash was on the 10th of July. Still seeing the occasional MapLike spam since then but it doesn't seem to be affecting performance too much. The other server doesn't seem to be running into this bug as much but i still see a fair bit of MapLike spam...

This happens to me to, whenever I log in to my server. It is quite annoying and there doesn't seem to be a fix that I can see ( When I generated a new world, it was fine, soooo). Maybe try making a new world, then teleporting players on join to the normal world? This seems to work.

I also moved my player data folder (???). Not sure why this worked, but it did.

I am also experiencing this issue on our server. The MapLike error message gets spammed ca 20 times a second. 1.17.1 is unplayable for us.

I don't know if this is related, but today I've changed sync-chunk-writes=false to sync-chunk-writes=true within my server.properties file to try and solve an unrelated issue we had (minecarts getting jammed after unloading the chunks they are in).

Surprisingly, this completely fixed the massive spam of these errors in the console. After this, I turned it back to false and loaded/walked into an area in the world that would always spam a bunch of errors. I could reliably get the errors to be spammed when sync-chunk-writes was turned to false, and then not get a single error with sync-chunk-writes turned to true. I have also ran the server with sync-chunk-writes turned to true for about a day now, and haven't gotten an error since.

It was not related, please read my later comment. The below error might still be interesting though, I can reliably reproduce that one in my world too.

Something else interesting, besides the MapLike error, we also frequently got spammed a slightly different error:

[00:53:05] [Server thread/ERROR]: Invalid bounding box data, inverted bounds for: dar{minX=2147483647, minY=2147483647, minZ=2147483647, maxX=-2147483648, maxY=-2147483648, maxZ=-2147483648}
[00:53:05] [Server thread/ERROR]: Exception loading structure piece with id minecraft:jigsaw
java.lang.IllegalStateException: Invalid call to EmtyPoolElement.getBoundingBox, filter me!
	at cxt.a(SourceFile:39) ~[server.jar:?]
	at dbg.<init>(SourceFile:57) ~[server.jar:?]
	at cud.a(SourceFile:151) ~[server.jar:?]
	at cnj.a(SourceFile:415) ~[server.jar:?]
	at cnj.a(SourceFile:175) ~[server.jar:?]
	at abe.l(SourceFile:512) ~[server.jar:?]
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(Unknown Source) ~[?:?]
	at aqv.c(SourceFile:151) ~[server.jar:?]
	at abp$a.c(SourceFile:528) ~[server.jar:?]
	at aqv.z(SourceFile:125) ~[server.jar:?]
	at abp$a.z(SourceFile:537) ~[server.jar:?]
	at abp.d(SourceFile:280) ~[server.jar:?]
	at net.minecraft.server.MinecraftServer.bf(SourceFile:776) ~[server.jar:?]
	at net.minecraft.server.MinecraftServer.z(SourceFile:764) ~[server.jar:?]
	at aqv.bp(SourceFile:110) ~[server.jar:?]
	at net.minecraft.server.MinecraftServer.y(SourceFile:748) ~[server.jar:?]
	at net.minecraft.server.MinecraftServer.x(SourceFile:701) ~[server.jar:?]
	at net.minecraft.server.MinecraftServer.a(SourceFile:270) ~[server.jar:?]
	at java.lang.Thread.run(Unknown Source) [?:?]

By the way, EmtyPoolElement is not a typo, that's actually what it says in the logs.
I hope all this information helps somehow.

Jeroen45: Would this work in singleplayer? Because as far as I know sync-chunk-writes is true by default in singleplayer, and I still have the issue.

@ampolive I have just tested this in singleplayer, and have gotten the same errors. After this, I restarted the whole pc my server was running on, after which the error started showing up again on the server too, even though sync-chunk-writes turned to true. I have no idea what caused the errors to disappear earlier now, I'm sorry for causing any confusion. I have edited my earlier comment to reflect this new knowledge. The different error that also showed up a lot for me might still be interesting though, so I'll leave that up. Please let me know if I can still do anything else to help.

I have the same issue, but it does not happen on the whole map. Basically our spawn and the chunks where most player-bases are located, do work or at least do not crash. The error does come up a few times, but not very often.

Then I wanted to look if everything still works in 1.17.1 on one of my projects, but teleported to the wrong cooordinates (missing minus), which still worked. But just after teleporting to the correct coordinates, it crashed and did also crash everytime I logged in at that place. I managed to send another teleport command on logging in just before the next crash to get away right in the middle of an ocean (mixed up coordinates again), where it also crashed but this time so fast, that I could not get any command out on logging in. Therefore I had to edit my NBT to get myself back to our spawn/bases.
All of this happened in a part of the map, where there should not be any newly generated chunk. Also both places were it crashed do have way less changed blocks then our spawn/bases chunks.

Hello, I am experiencing the same issue after upgrading my multiplayer server from 1.16.5 to 1.17.1. I am using paper spigot 1.17.1 (build #103).
I am enclosing the whole log file. I hope it helps.

There is a few other unrelated error messages from some plugins, but this is the largest one.

If you are playing on Paper or a fork of it like Tuinity or Purpur, you might be able to stop the symptoms of the bug by disabling the "async chunks" feature in paper.yml.

The bug message still appeared a couple of times, but there weren't any problems like extreme lag and the server crashing for me (which was the case before).

But I would still advise you to make a backup in case it doesn't work for you and you need to go back to 1.16.

Cannot really understand how this is not a priority, have seen minor bugs being solved prior to developing a solution for this one. Am i missing something? I cannot upgrade because of this bug, am I the only one waiting for a solution?

@TechRoot

Mojang being Mojang. Their attention to the server community has really been lacking in the past years. The only reason people can run bigger servers is third party software that optimizes vanillas horrible server performance and fixes bugs Mojang won't touch allthough they have been known to be an issue for months or even years (dupes etc.).

As I already said, if you are on Paper (or a fork of it), try to disable the async chunks thing. Otherwise, you will probably have to wait until either Mojang fixes it or a different solution is found.

@TechRoot
Unfortunately you are not the only one waiting for this solution. We are experiencing this issue while trying to upgrade to 1.17 and 1.17.1 in our vanilla 1.16.5 server and also can not upgrade because of this bug.

@Thommy Siverman  I noticed the status was flipped between "Fixed" and "Reopened." Was a fix merged that you'd like us to test, either in the current 1.17 snapshot or an unofficial build?

@Til Weimann  This bug affects single-player, too, it seems. Every software accumulates technical debt, and has limited people-power. PMs have to balance priorities. That includes finishing new features in Caves & Cliffs. So we can't assume that Mojang lacks "attention to the server community"... But yes, it will be nice to finally get our hands on the :yellow_star: so shiny:yellow_star: 1.17 stuff.

Are there any workarounds in the meantime? I have not been able to launch up my server for weeks due to this issue.

Our workaround is keeping the affected servers on 1.16.5. It (obviously) works well but without any new features of 1.17. But if the other choice is no server...

Indeed, we are still on 1.16.5, its a shame, because it doesnt feel like devs are even taking care of this issue. We dont know what to expect.

Hello!

I just came to say that I run into this issue too. Is there any progress with this bug?

Also having the same issue, interested in any work-arounds folks know about. Thanks!

Hello!
Is there any work going on to implement the patch in future versions 17.+? Our server has this problem too, Players want to upgrade with new features... but we can't do anything because of this bug.

Have simular issues as all other, having a server with a lot of players eager to play the new update.

Hello,

same here. This is really a big problem for our server. Unable to upgrade from version 1.16.5 to version 1.17.1 because of this.

So any progress? I had downgrade my server back to 1.16.5 to be able to run it.

It seems that current versions of Paper MC fixed it.

Thanks for info, I will try it on test server soon.

I follow Paper development and I have seen nothing indicating that this has been fixed there. Please add some source for the "seems" statement, like which build added the fix.

Hello, 

I confirm that I've upgraded with success from 1.16.5.788 to 1.17.1.249 with no errors in any world on my server. 

The server seems to be fully functionnal at the moment and with my team we are checking if all is OK in our worlds 

First checks in production show that there is a WARNING "Ignored advancement in progress file" with certains Recipes, and some ERRORS indicating that some recipes are not found "Tried to load unrecognized recipe: minecraft:iron_ingot_from_blasting removed now." and repeat the message for others. 

Don't know if it's linked to this bug or refear to another bug of 1.17.1 version.

@unknown: That is another bug which was marked as "Won't Fix" (MC-228367).

@ampolive : Thank you for this element. 

I can confirm that converting my
1.16.5-788 (Paper)
to
1.17.1-259 (Paper)

No longer has the errors.

I have multiverse with about 10 worlds, and about 14 plugins running.

All previous attempts resulted in a flood of the above errors and required me to roll back my snapshot.

I don't know if this can be applied to vanilla.

Updated to the latest paper version seems to have fixed the issue for us.

This could be the result of the new Data Converter system included in Paper in builds #232 and later. (This was a feature of Tuinity that got added in the merge) Data Converters are a replacement for Data Fixer Uppers (DFU) which is the system which updates older chunk data to newer formats. The issue described here supposedly is caused by DFU upgrading chunks with faulty data which when read causes the errors to appear in the log. Since Data Converter is an entire replacement of DFUs there is a chance that the bug is not present with it's world conversion meaning chunks have the proper data. (No errors in log) If my theory is correct the issue should be fixed in Paper and all of it's downstreams if they have been updated to build #232 or later. Though there will be no fix available for Vanilla and modded servers as this is not a copy and paste solution even though that's not necessary possible anyways due to potential licensing issues. For those who are interested in learning about Data Converters from a technical standpoint you can read about it on the GitHub repo: https://github.com/PaperMC/DataConverter. Do note that the repo contains a Fabric mod that implements Data Converter but it should never be used. While you could compile it your self it if they got it working outside of a dev environment it should not be used unless you fully understand what it is doing or are testing a contribution to the project. I nor the PaperMC team are responsible for any damage caused to your save file if you use this modification.

TLDR

For users of PaperMC or a downstream (Airplane, Purpur, etc) you should upgrade to a build that contains the changes in Paper build #232. This should fix the issue but no promises. For users of the Vanilla server or a modded one (Forge, Fabric, Quilt) a fix is not available and you will have to wait for Mojang to fix the issue unless if the community creates another solution.

After testing with a newer Paper 1.17.1 build I agree with the posters above. Switched to the latest build 263 and the problem seems gone. No idea if it leads to other problems under the hood though? Running with this for testing now and keeping my backups close. 🙂

I'm running Paper build #279 and still getting the error on a 1.16.5 world that I updated with --forceUpgrade to 1.17.1, however it doesn't appear to be crashing the server (yet) just generating the console error.

Can confirm in 21w39a for the "Exception loading structure piece with id minecraft:jigsaw". The "No key" error seems to no longer be present.

Can confirm in 21w40a.

Can confirm in 21w41a.

At this point I've lost any hope Mojang is interested in resolving this and I'm honestly very disappointed that such a critical issue has been neglected and left to the community to make guesswork fixes for.

Can confirm in 21w42a.

Can confirm in 21w43a.

Can confirm in 21w43a.

@@unknown @@unknown Are there any other methods for bringing this issue into Mojang's visibility?  I'm not on Twitter, but is that somewhere people could bring this issue to Mojang's attention, for example?

@unknown This ticket was already assigned a Mojang Priority, meaning that a Mojang developer/employee has triaged this issue, so the developers are already aware of it. All we can do is vote for this ticket and provide new information when available.

Can confirm in 21w44a.

Can confirm for servers upgrading to 1.18 pre-release 1.
Also spams error about hay_block.

Can also confirm in 1.18 Pre-release 1. The "No key" error is present once again.

Can confirm in 1.18 Pre-release 4.

I tried to upgrade to 1.17.1 again, and, while the upgrade itself succeeded (finally), I think I'm getting some lag due to this bug.  I posted about it on Spigot's forum too, but I guess no one there knows what's going on with it.
https://www.spigotmc.org/threads/invalid-call-to-emtypoolelement-getboundingbox-filter-me.534979/

This issue did not happen for me after I optimized a previous backup of the world that was not loaded in 1.17.1.

How does one optimize a world? Is this a possible fix?

No working, after optimalizing 1.16.2 and run on 1.18 still the same

I had this same error when upgrading from 1.16 to 1.17. I'm not sure what got rid of it, but now that I'm upgrading from 1.17 to 1.18, I'm getting the error again - this time it's so much longer though.

Hi,

Happy new year to all, hope that 2k22 will be better than 2k21 \o/

I use Paper Minecraft Server.

Recently I updated with success from 1.16.5 to 1.17.1.249 with no errors, but today when I want to update from 1.17.1.407 to 1.18.1.132, i've got the error again. (I've already post here)

The ForceUpgrade of World, Nether and End seems to be OK, but when server is ready, few seconds later i've messages like this one : 

[17:57:17] [Paper Async Chunk Urgent Task Thread/ERROR]: No key placement in MapLike[{config:{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},foliage_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},force_dirt:0b,ignore_vines:1b,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}},type:"minecraft:tree"}]; No key feature in MapLike[{config:{decorators:[],foliage_placer:{height:3,offset:0,radius:2,type:"minecraft:blob_foliage_placer"},foliage_provider:{state:{Name:"minecraft:oak_leaves",Properties:{distance:"7",persistent:"false"}},type:"minecraft:simple_state_provider"},force_dirt:0b,ignore_vines:1b,minimum_size:{limit:1,lower_size:0,type:"minecraft:two_layers_feature_size",upper_size:1},trunk_placer:{base_height:4,height_rand_a:2,height_rand_b:0,type:"minecraft:straight_trunk_placer"},trunk_provider:{state:{Name:"minecraft:oak_log",Properties:{axis:"y"}},type:"minecraft:simple_state_provider"}},type:"minecraft:tree"}]

And the famous :

[17:57:17] [Paper Async Chunk Urgent Task Thread/ERROR]: Exception loading structure piece with id minecraft:jigsaw

I've decided to rollback in 1.17.1.407, waiting for new version that I hope without bug.

Thanks for your returns.

As can  be seen from comments above in September 2021 I had this problem with early Paper 1.17.1 builds (and also with Vanilla) and it was fixed by later builds.  No problems after that while keeping regularly updated Paper 1.17.1 builds.

Now when testing upgrading a Paper 1.17.1 build 408 to Paper 1.18.1 build 133 (with --forceUpgrade done) the same type of error messages appears again. On server load, on player join and on exploration. It's impossible for me to tell if the decreased server performance is connected to the errors or due to other changes with the upgrade.

Got this error back when we moved from 1.16 to 1.17, a later version of Paper fixed it but now it's back again as we've just moved to 1.18.

Just a reminder people, Paper is a Fork. does the same bug happen with the vanilla server jar?

yes. this started to pop up for me on 1.18.1, and this happens with the vanilla server jar (btw still happens with Paper's --forceUpgrade flag)

I should have also tested this on Fabric and Fabric doesn't produce the errors as shown above