[Server] Crash on startup, ticking tile entity, Ultimate 1.1.2

[Shizzle T]

I placed a tesseract on the side of a diamond pipe and then my server crashed. Is there a way to fix this with out losing the world? FTB ultimate 1.1.2.

<spoiler> ---- Minecraft Crash Report ----
// There are four lights!

Time: 6/4/13 12:46 PM
Description: Ticking tile entity

java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:839)
at java.util.HashMap$ValueIterator.next(HashMap.java:868)
at buildcraft.transport.PipeTransportItems.moveSolids(PipeTransportItems.java:261)
at buildcraft.transport.PipeTransportItems.updateEntity(PipeTransportItems.java:225)
at buildcraft.transport.Pipe.updateEntity(Pipe.java:166)
at buildcraft.transport.TileGenericPipe.g(TileGenericPipe.java:189)
at yc.h(World.java:2153)
at in.h(WorldServer.java:516)
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:680)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:599)
at bdz.q(IntegratedServer.java:123)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
at fy.run(SourceFile:849)


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

-- Head --
Stacktrace:
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:839)
at java.util.HashMap$ValueIterator.next(HashMap.java:868)
at buildcraft.transport.PipeTransportItems.moveSolids(PipeTransportItems.java:261)
at buildcraft.transport.PipeTransportItems.updateEntity(PipeTransportItems.java:225)
at buildcraft.transport.Pipe.updateEntity(Pipe.java:166)
at buildcraft.transport.TileGenericPipe.g(TileGenericPipe.java:189)

-- Tile entity being ticked --
Details:
Name: net.minecraft.src.buildcraft.transport.GenericPipe // buildcraft.transport.TileGenericPipe
Block type: ID #0
Block data value: Unknown? (Got -1)
Block location: World: (-118,65,104), Chunk: (at 10,4,8 in -8,6; contains blocks -128,0,96 to -113,255,111), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Stacktrace:
at yc.h(World.java:2153)
at in.h(WorldServer.java:516)

-- Affected level --
Details:
Level name: world
All players: 1 total; [iq['ShizzleT'/540, l='world', x=-122.07, y=65.00, z=98.85]]
Chunk stats: ServerChunkCache: 1056 Drop: 0
Level seed: -1929209582496932372
Level generator: ID 00 - default, ver 1. Features enabled: true
Level generator options:
Level spawn location: World: (224,64,256), Chunk: (at 0,4,0 in 14,16; contains blocks 224,0,256 to 239,255,271), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 66347670 game time, 71299766 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 37785 (now: false), thunder time: 70682 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:680)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:599)
at bdz.q(IntegratedServer.java:123)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:497)
at fy.run(SourceFile:849)

-- System Details --
Details:
Minecraft Version: 1.4.7
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: 420452184 bytes (400 MB) / 825196544 bytes (786 MB) up to 4225236992 bytes (4029 MB)
Mod Pack: CWW256 forgot to change this.
LiteLoader Mods: 4 loaded mod(s)
- VoxelPacket version 2.0.2
- VoxelPlayer version 0.9.6
- VoxelMenu version 1.4.7_05
- VoxelMap version 1.0.0
JVM Flags: 7 total; -Xms256M -Xmx4096M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+AggressiveOpts -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=128m
AABB Pool Size: 8768 (491008 bytes; 0 MB) allocated, 8366 (468496 bytes; 0 MB) used
Suspicious classes: FML and Forge are installed
IntCache: cache: 0, tcache: 0, allocated: 3, tallocated: 63
FML:
mcp [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available->Available->Available->Available
FML [Forge Mod Loader] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available->Available->Available->Available
Forge [Minecraft Forge] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available->Available->Available->Available

(all mods where listed as available)

Profiler Position: N/A (disabled)
Vec3 Pool Size: 1879 (105224 bytes; 0 MB) allocated, 1790 (100240 bytes; 0 MB) used
Player Count: 1 / 8; [iq['ShizzleT'/540, l='world', x=-122.07, y=65.00, z=98.85]]
Type: Integrated Server (map_client.txt)
Is Modded: Definitely; Client brand changed to 'forge,fml' </spoiler>

 

[Quantax]

Thanks to the detailed Forge crash report there's a way to solve this (and similar errors) without reseting or reverting the whole world but it requires some manual work.

What you need to do is manually remove the offending block/tile entity. Here's a quick guide on how to do it:

1. Get NBTexplorer or similar program which allows you to view Minecraft region files.
2. Take a look at the "Block Location" line in the crash report. In your case "Block location: World: (-118,65,104), Chunk: (at 10,4,8 in -8,6; contains blocks -128,0,96 to -113,255,111), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)"
3. Get the region file indicated by the error (bolded). In this case you want the file called r.-1.0.mca
4. Open the file in NBTexplorer (or your program of choice)
5. Find the chunk at location indicated by the crash report (underlined). In this case -8,6. You'll have to manually find the index tag where the chunk in question is. Just look inside the "Chunk [nn,mm]" ->"Level" for x and z coordinates
6. Once you find the chunk, search through its TileEntities list for a TE at the coordinates indicated by the error report (italic) and remove it.
7. Save and replace the old region with the modified one

Remember to backup before editing!


P.S. Sorry for the late response but I thought I'd share this trick for fixing crashing worlds. This method has saved me many times from reverting to backups or even trashing the whole map. All this is possible thanks to the awesome detail of Forge crash reports. Kudos to Forge team for that!

 

[Ashzification]

Add:

Spoiler

Please follow these steps exactly: http://desk.feed-the-beast.com/index.php?/Knowledgebase/Article/View/9/0/basic-troubleshooting

Your Java is REALLY out of date. In the guide is the link to oracle downloads for you to update Java.

 

[brail]

Thanks to the detailed Forge crash report there's a way to solve this (and similar errors) without reseting or reverting the whole world but it requires some manual work.

What you need to do is manually remove the offending block/tile entity. Here's a quick guide on how to do it:

1. Get NBTexplorer or similar program which allows you to view Minecraft region files.
2. Take a look at the "Block Location" line in the crash report. In your case "Block location: World: (-118,65,104), Chunk: (at 10,4,8 in -8,6; contains blocks -128,0,96 to -113,255,111), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)"
3. Get the region file indicated by the error (bolded). In this case you want the file called r.-1.0.mca
4. Open the file in NBTexplorer (or your program of choice)
5. Find the chunk at location indicated by the crash report (underlined). In this case -8,6. You'll have to manually find the index tag where the chunk in question is. Just look inside the "Chunk [nn,mm]" ->"Level" for x and z coordinates
6. Once you find the chunk, search through its TileEntities list for a TE at the coordinates indicated by the error report (italic) and remove it.
7. Save and replace the old region with the modified one

Remember to backup before editing!



P.S. Sorry for the late response but I thought I'd share this trick for fixing crashing worlds. This method has saved me many times from reverting to backups or even trashing the whole map. All this is possible thanks to the awesome detail of Forge crash reports. Kudos to Forge team for that!

Not OP but THANKS! This just saved my servers map :]