POI never registered crash not fixed

Can confirm, added another crash report

Similarly to MC-145694, breaking the affected block entity instead of using it will just print the error without crashing the server.

An example (it says "FATAL" but doesn't actually crash in this situation):

[15:53:25] [Server thread/FATAL]: Error executing task on Server
java.lang.IllegalStateException: POI never registered at eu{x=890, y=71, z=-829}
	at apa.a(SourceFile:72) ~[server_19w11b.jar:?]
	at aoy.a(SourceFile:37) ~[server_19w11b.jar:?]
	at vc.b(SourceFile:1271) ~[server_19w11b.jar:?]
	at re.run(SourceFile:18) ~[server_19w11b.jar:?]
	at afy.g(SourceFile:122) [server_19w11b.jar:?]
	at agc.g(SourceFile:23) [server_19w11b.jar:?]
	at afy.p(SourceFile:101) [server_19w11b.jar:?]
	at net.minecraft.server.MinecraftServer.p(SourceFile:693) [server_19w11b.jar:?]
	at afy.c(SourceFile:110) [server_19w11b.jar:?]
	at net.minecraft.server.MinecraftServer.o(SourceFile:678) [server_19w11b.jar:?]
	at net.minecraft.server.MinecraftServer.run(SourceFile:632) [server_19w11b.jar:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]

Can also confirm this is still happening.

This one is from opening a barrel, it crashed once, then crashes again when you start the world again, and then the third time will load.

(Will crash again if you open the barrel again, and repeat the above)

1: Opening the barrel

Time: 3/15/19 10:44 AM
Description: Ticking block entity

java.lang.IllegalStateException: POI never registered at eu\{x=495, y=60, z=-69}
 at apa.a(SourceFile:72)
 at aoy.a(SourceFile:37)
 at vc.b(SourceFile:1271)
 at vc$$Lambda$2937/1750173533.run(Unknown Source)
 at afy.execute(SourceFile:77)
 at vc.b(SourceFile:1270)
 at vc$$Lambda$2934/1024619627.accept(Unknown Source)
 at java.util.Optional.ifPresent(Optional.java:159)
 at vc.a(SourceFile:1270)
 at bfx.a(SourceFile:252)
 at brt.a(SourceFile:156)
 at brt.g(SourceFile:150)
 at bfx.K(SourceFile:620)
 at vc.a(SourceFile:400)
 at net.minecraft.server.MinecraftServer.b(SourceFile:816)
 at net.minecraft.server.MinecraftServer.a(SourceFile:755)
 at dwb.a(SourceFile:128)
 at net.minecraft.server.MinecraftServer.run(SourceFile:630)
 at java.lang.Thread.run(Thread.java:745)

2: Re-opening the world after the first crash

Time: 3/15/19 10:45 AM
Description: Ticking block entity

java.lang.IllegalStateException: POI never registered at eu{x=495, y=60, z=-69}
at apa.a(SourceFile:72)
at aoy.a(SourceFile:37)
at vc.b(SourceFile:1271)
at vc$$Lambda$2917/1373698956.run(Unknown Source)
at afy.execute(SourceFile:77)
at vc.b(SourceFile:1270)
at vc$$Lambda$2916/1126487179.accept(Unknown Source)
at java.util.Optional.ifPresent(Optional.java:159)
at vc.a(SourceFile:1270)
at bfx.a(SourceFile:252)
at brt.a(SourceFile:156)
at brt.g(SourceFile:150)
at bfx.K(SourceFile:620)
at vc.a(SourceFile:400)
at net.minecraft.server.MinecraftServer.b(SourceFile:816)
at net.minecraft.server.MinecraftServer.a(SourceFile:755)
at dwb.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:630)
at java.lang.Thread.run(Thread.java:745)

Smokers and Blast Furnaces cause the above mentioned crash

a) when putting items in (

)

b) when the last item has finished processing (

)

[17:45:46] [Server thread/FATAL]: Error executing task on Server
java.lang.IllegalStateException: POI never registered at eu{x=5, y=86, z=-517}
        at apa.a(SourceFile:72) ~[server.jar:?]
        at aoy.a(SourceFile:37) ~[server.jar:?]
        at vc.b(SourceFile:1271) ~[server.jar:?]
        at re.run(SourceFile:18) ~[server.jar:?]
        at afy.g(SourceFile:122) [server.jar:?]
        at agc.g(SourceFile:23) [server.jar:?]
        at afy.p(SourceFile:101) [server.jar:?]
        at net.minecraft.server.MinecraftServer.p(SourceFile:693) [server.jar:?]
        at afy.c(SourceFile:110) [server.jar:?]
        at net.minecraft.server.MinecraftServer.o(SourceFile:678) [server.jar:?]
        at net.minecraft.server.MinecraftServer.run(SourceFile:632) [server.jar:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]

Got something similar to this with the bell entity. Adding crash report. Personally unsure what actually happened as I was not on the server at the time, but the above happened after the restart.

Crash report: 

There is no need to keep adding crash reports to this ticket. One is enough. Thanks.

Confirmed happening with barrels. Breaking them also seems to cause the same problem. I have also had this happen with hoppers. Unfortunately I wasn't around to see the event itself, but it caused the server to go into a constant crash loop (probably because it's trying to modify its inventory).

Happened again. This time with hoppers putting items into composters. Setup: Chest->Hopper->Composter->Hopper->Chest

Happened when I opened a barrel while walking sideways

Happened while filling a composter with a hopper.

Me too. "IllegalStateException: POI never registered" crash when trying to open a barrel. 

Happened on two different barrels. 

After a crash, the game will crash once or twice again when loading the world on startup. 

So I'm having the same issue. POI never registered.... Don't know if this is much help but a workaround for the issue for me was to just break the block(barrel) before opening it and before it causes the server to crash again.

I encounter this when opening a barrel as well. Server crashes. I relaunch the server, and it crashes on load.

If I restart the server a second time, it launches stably (obviously I avoid the barrel now until GA).

Currently playing in 19w11b - Any interaction with blast furnace crashed the game. The furnace occasionally does this as well.

The crash report is as follows:

 
The game crashed whilst ticking block entity
Error: java.lang.IllegalStateException: POI never registered at eu{x=-143, y=72, z=-112}

I have no more problems opening barrels in 19w12a.

a map from 19w09a to 19w12a,

The barrels don't crash, but le error message ("POI never registered") is see into console.

and the barrel is empty (it have some stuff inside)

Can also confirm that this is fixed, in the sense that the game no longer crashes. The "POI data mismatched" error is now MC-146279.