Bukkit

What steps will reproduce the problem?
1.Try to open a Steve co. Supply Crate
3. Internal Server Error

What is the expected output? What do you see instead?
a Kick.

What version of the product are you using?
The Newest one.

Do you have an error log of what happened?
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.ThreadServerApplication.run(SourceFile:849)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.MinecraftServer.run(MinecraftServer.java:427)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.MinecraftServer.q(MinecraftServer.java:494)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.DedicatedServer.r(DedicatedServer.java:224)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.MinecraftServer.r(MinecraftServer.java:598)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.DedicatedServerConnection.b(SourceFile:30)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.ServerConnection.b(SourceFile:39)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.PlayerConnection.d(PlayerConnection.java:112)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.NetworkManager.b(NetworkManager.java:290)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.Packet102WindowClick.handle(SourceFile:31)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.PlayerConnection.a(PlayerConnection.java:1211)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.Container.clickItem(Container.java:187)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.SlotResult.a(SourceFile:58)
18.01 19:34:53 [Server] INFO at net.minecraft.server.v1_4_6.SlotResult.b(SourceFile:41)
18.01 19:34:53 [Server] INFO java.lang.NullPointerException
18.01 19:34:53 [Server] WARNING Failed to handle packet for markzunnie/85.150.56.100: java.lang.NullPointerException

Please provide any additional information below.
Just tried to open my chest after configuring the plugin (Yes i did it right. including MySQL)

Can you post your configurations? (Be sure to edit out the database passwords.) I encountered this in testing and haven't really been able to reproduce it.