Launcher doesn't open modpack when launch button is pressed.

[Kaniva]

Launcher Version: 285 - 322

Operating System: Windows 7 64-bit

Java Version: Version 7 Update 45

Antivirus Program: avast! antivirus

Description of Problem:

When I press the launch button after logging into the launcher, it tries to extract or something (progress bar seems to do something), but abruptly stops and does nothing. Repeated tries, as well as multiple clean installs of the launcher, java, Minecraft, and antivirus has done nothing. Antivirus and firewalls have been turned off. Tried different memory amounts, different versions of modpack and launcher, as well as logging in with a Mojang email account as well as a Minecraft username account. I also have both the 32 and 64-bit versions of java installed.

The packs seem to install fine, but afterwards never lets me launch them. The only pack I have noticed that lets me launch is Tekkit Classic.

It's also worth noting that last time I used the launcher (Summer 2013) it worked flawlessly, problem has arisen since then.

Error Messages:

No error messages given, just doesn't do anything after launch is pressed.

Technic Launcher Console:

Analytics Response [installModpack]: 200



Starting download of http://mirror.technicpack.net/Technic/version/1.5.2/1.5.2.json, with 3 tries remaining

 

 

Error Log:

2013/10/30 00:37:00 [iNFO] ------------------------------------------

2013/10/30 00:37:00 [iNFO] Technic Launcher is starting....

2013/10/30 00:37:00 [iNFO] Launcher Build: 322

2013/10/30 00:37:00 [iNFO] ------------ Startup Parameters ------------

2013/10/30 00:37:00 [iNFO] --------- End of Startup Parameters ---------

2013/10/30 00:37:00 [iNFO] Analytics Response [runLauncher]: 200

2013/10/30 00:37:02 [iNFO] Starting download of http://skins.technicpack.net/helm/Kaniva/100, with 3 tries remaining

2013/10/30 00:37:02 [iNFO] Valid:

2013/10/30 00:37:02 [iNFO] {"accessToken":"e2c46c727ed24518a25feb4ea86f8c6e","clientToken":"a15f8fbb-e0d9-49bf-9a9a-c27de580d07b","selectedProfile":{"id":"f203f9a1566c41739ad346a64a6eb629","name":"Kaniva"}}

2013/10/30 00:37:02 [iNFO] Launcher took: 3476ms to start

2013/10/30 00:37:05 [iNFO] Analytics Response [installModpack]: 200

2013/10/30 00:37:07 [WARNING] File version.json not found in C:\Users\Windows\AppData\Roaming\.technic\modpacks\hexxit\bin\modpack.jar

2013/10/30 00:37:07 [iNFO] Starting download of http://mirror.technicpack.net/Technic/version/1.5.2/1.5.2.json, with 3 tries remaining

2013/10/30 00:37:07 [sEVERE] Unhandled Exception in Thread[installThread,6,main]

com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1

at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)

at com.google.gson.Gson.fromJson(Gson.java:803)

at com.google.gson.Gson.fromJson(Gson.java:768)

at com.google.gson.Gson.fromJson(Gson.java:717)

at com.google.gson.Gson.fromJson(Gson.java:689)

at net.technicpack.launchercore.install.ModpackInstaller.getMinecraftVersion(ModpackInstaller.java:186)

at net.technicpack.launchercore.install.ModpackInstaller.installPack(ModpackInstaller.java:80)

at org.spoutcraft.launcher.InstallThread.run(InstallThread.java:54)

Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1

at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:374)

at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:165)

... 7 more

[Granja]

I have the same problem. Help?

[Virolite]

Same problem, what's going on! I also downgraded to Java 6 and it still does not work!

[CanVox]

Post your version.json from the pack you tried to run. It's located in the modpack's bin directory.

[Kaniva]

Here is the version.json from the Hexxit modpack.

https://www.dropbox.com/s/n32zdx54cmustlk/version.json

[CanVox]

Hi Kaniva, that is not a valid version.json. It looks like something weird happened when we tried to download it- instead we got a page that your local router served up. Delete version.json and see if restarting hexxit works ok.

[CanVox]

Actually kaniva, it looks like your local network is providing a situation where when your router receives a 404 from a remote webpage, it serves you a search page instead. This sucks for us, because we check to see if the technic site has a version.json before we try to use the mojang one. What's going on is your router tells the launcher that there IS a version.json at the remote site, and then we download the search page your router serves up and try to parse it as json. We'll probably need to make some changes to the way we do things to work around this, but it'd be better if you could get your router to stop doing this craziness.

[Kaniva]

Thank you. I'm just glad to finally see a proper response after reading countless forum posts on the matter. Any advice on how I could work around this with my router?

[CanVox]

Hi, Kaniva, I'm not familiar with your setup, but this thread offers some suggestions for turning off this "feature": http://www.dslreports.com/forum/r24249322-?hilite=routers

[Kaniva]

Thank you for your help CanVox, appreciate it.

[Kaniva]

It turns out with my specific router this feature cannot be turned off. Is there a version.json that I could download and add manually? Or does my computer specifically need to generate it?

Either that or I buy a new router.

[CanVox]

Hi, we moved a lot of version.json files to our hosting last night to help people with this issue. I think if you delete your version.json file, you should start working ok.

[Kaniva]

This seems to have fixed the problem entirely. Thank you for your help.

[lee beringer]

im having the same problem what can i do?>

[xXsapperayXx]

EYY i just search for find help and the same problem u guys talking about happening with me anyone have a tip. btw i tryed reinstall and use other modpacks nothing works.

[xXsapperayXx]

yah and the modpack i want 2  work is attack of the b-team

[Munaus]

you should have read the pinned threads '?do=embed' frameborder='0' data-embedContent>>

 

Don't jump in on someone elses report and say "me too!" "I have the same problem", because in most cases I have seen, users don't have the same issue and/or need a different fix to solve it.