Crash loading world containing blocks with removed data values: java.lang.IllegalArgumentException: Cannot set property

How is it a duplicate of that? The log-placing crash issue throws an exception regarding ayi saying it doesn't exist. This throws one regarding ayj saying value "down" is not valid.

You're right.

Description: Exception ticking world
java.lang.IllegalArgumentException: Cannot set property ayj{name=facing, clazz=class dt, values=[north, south, west, east]} to down, it is not an allowed value
	at axy.a(SourceFile:131)
	at aqs.a(SourceFile:232)
	at ou.h(SourceFile:342)
	at ou.c(SourceFile:179)
	at net.minecraft.server.MinecraftServer.w(SourceFile:570)
	at nt.w(SourceFile:284)
	at net.minecraft.server.MinecraftServer.v(SourceFile:506)
	at net.minecraft.server.MinecraftServer.run(SourceFile:422)
	at java.lang.Thread.run(Thread.java:744)

Please check after the rollout of 14w25b if this issue is co-fixed with MC-56893

I tracked the issue down to unexpected data values. For example, chests edited into the world with data value 0 which the game assumes to mean the block is facing down (which is obviously impossible for a chest).
The crash went away after I removed all such blocks from the world, but I'm going to test 14w25b on the pre-fix world to see if the crash is still there.
Though I still think the game should react more graciously to unexpected data values (setting the values to default in such a case wouldn't be a bad idea).
Also, no block-adding/modifying mods were ever used on the world, only vanilla Minecraft, and the invalid blocks are mostly ones edited into the world by less-experienced players. I am going to make it a server rule now to pay attention to only use valid block values so such issues are avoided in the future.

I am still getting this bug in 14w25b. So it is NOT FIXED on my system.

---- Minecraft Crash Report ----
// Who set us up the TNT?

Time: 6/19/14 9:14 AM
Description: Getting block state

java.lang.IllegalArgumentException: Cannot set property ayl{name=facing, clazz=class dt, values=[north, south, west, east]} to down on block minecraft:chest, it is not an allowed value
	at aya.a(SourceFile:131)
	at aow.a(SourceFile:425)
	at ayv.h(SourceFile:446)
	at alu.q(SourceFile:699)
	at alu.a(SourceFile:989)
	at ub.d(SourceFile:475)
	at uv.g(SourceFile:1187)
	at uv.f(SourceFile:1430)
	at uw.f(SourceFile:315)
	at ty.f(SourceFile:120)
	at yo.f(SourceFile:35)
	at uv.j(SourceFile:1270)
	at uw.j(SourceFile:194)
	at alu.a(SourceFile:1425)
	at ou.a(SourceFile:549)
	at alu.g(SourceFile:1403)
	at alu.i(SourceFile:1308)
	at ou.i(SourceFile:422)
	at net.minecraft.server.MinecraftServer.w(SourceFile:578)
	at nt.w(SourceFile:284)
	at net.minecraft.server.MinecraftServer.v(SourceFile:506)
	at net.minecraft.server.MinecraftServer.run(SourceFile:422)
	at java.lang.Thread.run(Thread.java:722)

================

-- System Details --
Details:
	Minecraft Version: 14w25b
	Operating System: Mac OS X (x86_64) version 10.9.3
	Java Version: 1.7.0_11, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 3977959768 bytes (3793 MB) / 4151836672 bytes (3959 MB) up to 4151836672 bytes (3959 MB)
	JVM Flags: 2 total; -Xmx4G -Xms4G
	IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
	Profiler Position: N/A (disabled)
	Player Count: 0 / 4; []
	Is Modded: Unknown (can't tell)
	Type: Dedicated Server (map_server.txt)

Yeah, it seems it has to do with certain blocks placed before Beta 1.8.1, such as chests. It seems some data values of certain blocks were valid in Beta 1.7.3 and earlier but became invalid later, and it wasn't apparent until now.
I think they should make Minecraft behave more gracefully in this kind of situation, my suggestion would be just assuming default value in case of an unknown/unexpected/invalid value.
Until then though, I recommend loading the world with MCEdit, having it analyze the world, then compare the analysis with MCEdit's internal list of block ID's and data values (MCEdit calls them subtypes) and nothing down any combinations present in the world that are not in said list, and then using MCEdit to replace them with either sane values or air blocks, one ID:data combination by one.

Here is my crash report for what it is worth. I'll go and update to java 8 now, BTW.

---- Minecraft Crash Report ----
// Quite honestly, I wouldn't worry myself about that.

Time: 6/19/14 11:02 AM
Description: Exception ticking world

java.lang.IllegalArgumentException: Cannot set property ayl{name=facing, clazz=class dt, values=[north, south, west, east]} to down on block minecraft:chest, it is not an allowed value
	at aya.a(SourceFile:131)
	at aow.a(SourceFile:425)
	at ou.h(SourceFile:342)
	at ou.c(SourceFile:179)
	at net.minecraft.server.MinecraftServer.w(SourceFile:570)
	at net.minecraft.server.MinecraftServer.v(SourceFile:506)
	at coe.v(SourceFile:132)
	at net.minecraft.server.MinecraftServer.run(SourceFile:422)
	at java.lang.Thread.run(Unknown Source)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
	at aya.a(SourceFile:131)
	at aow.a(SourceFile:425)
	at ou.h(SourceFile:342)
	at ou.c(SourceFile:179)

-- Affected level --
Details:
	Level name: Rassilon Beta
	All players: 1 total; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-845.95, y=14.00, z=1142.53]]
	Chunk stats: ServerChunkCache: 552 Drop: 0
	Level seed: -947871334830476033
	Level generator: ID 00 - default, ver 1. Features enabled: true
	Level generator options: 
	Level spawn location: -152.00,64.00,113.00 - World: (-152,64,113), Chunk: (at 8,4,1 in -10,7; contains blocks -160,0,112 to -145,255,127), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
	Level time: 68702376 game time, 1119050 day time
	Level dimension: 0
	Level storage version: 0x04ABD - Anvil
	Level weather: Rain time: 138122 (now: false), thunder time: 50589 (now: false)
	Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
	at net.minecraft.server.MinecraftServer.w(SourceFile:570)
	at net.minecraft.server.MinecraftServer.v(SourceFile:506)
	at coe.v(SourceFile:132)
	at net.minecraft.server.MinecraftServer.run(SourceFile:422)
	at java.lang.Thread.run(Unknown Source)

-- System Details --
Details:
	Minecraft Version: 14w25b
	Operating System: Windows 7 (amd64) version 6.1
	Java Version: 1.7.0_03, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 709765208 bytes (676 MB) / 1309802496 bytes (1249 MB) up to 2673213440 bytes (2549 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2867M
	IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
	Profiler Position: N/A (disabled)
	Player Count: 1 / 8; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-845.95, y=14.00, z=1142.53]]
	Type: Integrated Server (map_client.txt)
	Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.

And here is after I updated. Fiddling with render distance seems to induce it BTW, I don't know if that's important.

---- Minecraft Crash Report ----
// Hi. I'm Minecraft, and I'm a crashaholic.

Time: 6/19/14 6:42 PM
Description: Exception ticking world

java.lang.IllegalArgumentException: Cannot set property ayl{name=facing, clazz=class dt, values=[north, south, west, east]} to down on block minecraft:chest, it is not an allowed value
	at aya.a(SourceFile:131)
	at aow.a(SourceFile:425)
	at ou.h(SourceFile:342)
	at ou.c(SourceFile:179)
	at net.minecraft.server.MinecraftServer.w(SourceFile:570)
	at net.minecraft.server.MinecraftServer.v(SourceFile:506)
	at coe.v(SourceFile:132)
	at net.minecraft.server.MinecraftServer.run(SourceFile:422)
	at java.lang.Thread.run(Unknown Source)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
	at aya.a(SourceFile:131)
	at aow.a(SourceFile:425)
	at ou.h(SourceFile:342)
	at ou.c(SourceFile:179)

-- Affected level --
Details:
	Level name: Rassilon Beta
	All players: 1 total; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-887.47, y=78.00, z=1852.25]]
	Chunk stats: ServerChunkCache: 647 Drop: 0
	Level seed: -947871334830476033
	Level generator: ID 00 - default, ver 1. Features enabled: true
	Level generator options: 
	Level spawn location: -152.00,64.00,113.00 - World: (-152,64,113), Chunk: (at 8,4,1 in -10,7; contains blocks -160,0,112 to -145,255,127), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
	Level time: 68716122 game time, 1135559 day time
	Level dimension: 0
	Level storage version: 0x04ABD - Anvil
	Level weather: Rain time: 90321 (now: false), thunder time: 72242 (now: false)
	Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
	at net.minecraft.server.MinecraftServer.w(SourceFile:570)
	at net.minecraft.server.MinecraftServer.v(SourceFile:506)
	at coe.v(SourceFile:132)
	at net.minecraft.server.MinecraftServer.run(SourceFile:422)
	at java.lang.Thread.run(Unknown Source)

-- System Details --
Details:
	Minecraft Version: 14w25b
	Operating System: Windows 7 (amd64) version 6.1
	Java Version: 1.8.0_05, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 211241712 bytes (201 MB) / 835190784 bytes (796 MB) up to 2673344512 bytes (2549 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2867M
	IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
	Profiler Position: N/A (disabled)
	Player Count: 1 / 8; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-887.47, y=78.00, z=1852.25]]
	Type: Integrated Server (map_client.txt)
	Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.

Since my bug was a duplicate posting my servers crash file here

Also this is happening with pistons on my server, not chests.

Confirmed for 14w25b. Is this fixable if you replace the chests in the new snapshot?

The crash seems to be induced by trying to render chests having the data value 0, as João de Camões commented earlier. However, all the chests in my world seem to have data value 0, so how do the previous versions of Minecraft know which way the chests are facing?

This issue is corrected by removing the chests in 14w21b and then placing them in 14w25b

The problem is... was an chest placed by me or is from some dungeons... someone knows in wich version of mc appeared dungeons?
:/ yah i cheked and the problem is on the dugeon... ive replaced then by air, works but now i have empty dungeons. Anyway i keep a backup of my map who knows maybe they fix that.

All chest with data value 0 in my world are dungeon chests, so removing and replacing all those chests just takes to long if I have to locate all of them.

Confirmed for 14w25b ,not only chest and piston, ladder also have problem in my old world.

---- Minecraft Crash Report ----
// Everything's going to plan. No, really, that was supposed to happen.

Time: 6/24/14 3:26 PM
Description: Exception ticking world

java.lang.IllegalArgumentException: Cannot set property ayl{name=facing, clazz=class dt, values=[north, south, west, east]} to down on block minecraft:ladder, it is not an allowed value
	at aya.a(SourceFile:131)
	at arn.a(SourceFile:127)
	at ou.h(SourceFile:342)
	at ou.c(SourceFile:179)
	at net.minecraft.server.MinecraftServer.w(SourceFile:570)
	at net.minecraft.server.MinecraftServer.v(SourceFile:506)
	at coe.v(SourceFile:132)
	at net.minecraft.server.MinecraftServer.run(SourceFile:422)
	at java.lang.Thread.run(Unknown Source)

I have the same issue, but with item frames. I have removed most of them, but there is one left and I can't figure out where it is... I wonder how likely this is to be fixed any time soon, if at all.

Has anyone any suggestions on how to locate problematic objects?

• Christopher Martin: Use MCEdit. Just have it replace all blocks with invalid data values with eg. air. But of course, do it one block/data combination by one.

João de Camões: I can see what you're saying, but I just want to be sure. You're talking about using the Fill/Replace tool in MCedit?

If the crash was:
java.lang.IllegalArgumentException: Cannot set property ayl {name=facing, clazz=class dt, values=[north, south, west, east]} to down on block minecraft:wall_sign, it is not an allowed value

What is the code for a wall sign with the down orientation? 68:something? 68:0? I'm a bit wary about using replace tools and not quite knowing what I'm doing.

Replacing chest blocks with, for example, data value 0 in mcedit replaces chests with all data types, so that wouldn't work.

My single player world is crashing shortly after loading with a similar error. This started happening with the latest snapshot 14w27a. With previous version the world loaded normally.

Description: Rendering entity in world

java.lang.IllegalArgumentException: Cannot set property azi{name=facing, clazz=class dw, values=[north, south, west, east]} to down on block minecraft:chest, it is not an allowed value
	at ayx.a(SourceFile:132)
	at apr.b(SourceFile:425)
	at cfb.a(SourceFile:85)
	at cfb.a(SourceFile:113)
	at cjg.a(SourceFile:116)
	at cjg.a(SourceFile:95)
	at cjg.a(SourceFile:15)
	at cic.a(SourceFile:272)
	at cic.a(SourceFile:237)
	at cic.a(SourceFile:204)
	at cei.a(SourceFile:501)
	at cdo.a(SourceFile:1194)
	at cdo.a(SourceFile:1121)
	at cdo.b(SourceFile:971)
	at bmi.ap(SourceFile:886)
	at bmi.a(SourceFile:303)
	at net.minecraft.client.main.Main.main(SourceFile:120)

Is this still an issue in 14w28b ?

I'm not sure if MC-61495 which is a ticking entity crash has anything to do with this. However MC-58437 which was related to this one was fixed by Mog

The issue with Minecart Chests has been resolved

MC-61495 and MC-58437 are completely different to this crash.