Torezu

Tried using the .jar instead? What did you add an exception for - Java or the launcher?

This means you need to add Java to your system path.

Like what? Start your own thread with your specific information.

Your bug report says Java 7, but your launcher log says Java 6. Remove all versions of Java 6 using your Control Panel. Then try again. Tekkit requires Java 7 for at least a few of its mods.

You desperately need a new version of Java. Remove all traces of Java 6 and download/install 7. Also, Technic 6.0.7 and Tekkit 2.1.0 still run on Minecraft 1.1, so that's what will show up in your Minecraft menu if you're running either of those.

Or just look for duplicate copies of the same mod .zip files in your mods folder (IC2, in this case).

Then you weren't reading. Any time downloads fail entirely (which is what happened), your antivirus/firewall is almost always to blame. So, what's yours?

ChopTree 2 does not crash the server - I can confirm.

The batch file is for servers. This is your launcher log. That's unless you're using a batch file to run the launcher .jar, in which case we really need the whole error log. Use pastebin if you can't fit it here.

This is the error that's commonly reported when someone with a newer client attempts to connect to a server running an older version. It sounds like you'll need to update your server, or go back to Tekkit 2.1.0 with all the clients. The problem with that is that it's not supported any more. Updating a 2.1.1 (server version) world to 3.0.4 (also server version), however, comes with its own set of problems. There's a thread around the Tekkit board somewhere with instructions on conversion if you'd like to try, but usually starting a new world is recommended.

You need to do a couple things: 1) Remove Java 7, 32-bit and install Java 7, 64-bit. Your Java version doesn't match your OS, and that's bad. 2) Delete your .techniclauncher\tekkit folder, go into Options after selecting Tekkit in the launcher window, and use version 3.0.3 (Recommended Build). You're likely using 3.1.0, which won't work on any server right now. 3) If those don't work, post a launcher log.

If this were Technic, you could probably just fix the block ID error with the config files and move on (except for conflicts with future versions). This being Tekkit, however, I'd consider a client reinstall to be your best option.

Why were you being sarcastic? Your launcher log shows you're using Java 6. That means either you never installed Java 7, or you didn't remove Java 6. Either way, you need to update it.

We need a launcher log. It's either that, or you're using 3.1.0 on the client.

Don't do this. Also, your problem is not related to the topic, so please post your own thread. Before you do that, though, read the stickies. They indicate how to solve this problem. It involves dedicating less RAM to your server. If the computer you're running the server on doesn't have enough to start the server from the default batch file, though, it likely won't run the server very well.

Is there still a button at the top that says NEI Subsets or something like that? If there is, click it. Left-click on anything you want to re-enable. If there isn't, but you can see other stuff, your NEI is broken and you need to reinstall.

Unless you already have 64-bit Java 7, do that ^ - otherwise, you can just remove 6 or the 32-bit version of 7.

Try clicking the Submit a Bug Report button right below the Bug Board forum title. There's another one inside the Bug Board at the top, just in case you miss the first one.

*correctly *no hyphen *semicolon ;)

How much memory do you have on the computer that's running the server? Also, what OS is it using?

You're using Multicraft. See the error message where it says: "25.06 17:32:23 [Multicraft] JAR file not found, copying from global JAR directory"? I'm betting your .jar file isn't named correctly. You need to ask your server host about this.

Install OptiFine Standard. Whatever version of OptiFine you're using doesn't like you.

Somebody probably used /reload. Don't do that. Restart the server to fix it.

Launcher/server log? Did anyone use /reload on the server?

I'm not familiar with Linux - is that a 32-bit OS? If so, you may be running out of addressing space for the RAM you're trying to use.