Create account / Log in

Can't launch Vassal

Issues with the Vassal engine.

Moderators: uckelman, Tim M

Can't launch Vassal

Postby tiffman » July 16th, 2014, 1:10 am

Trying to join my friends in a game but can't seem to get Vassal Running. Trying to launch nothing seems to happen but I do see Java launch in processes for a second before quitting. I have uninstalled all Java, reinstalled, restarted, tried 64 vs 32 Java, tried java 6 and 7, as well as reinstalling Vassal in between all this. I have AVG but have it disabled when trying all this.

OS: Windows 7 x64
CPU: Intel i7 2600k
Memory: 16GB
Video: GeForce 780 GTX
VASSAL: 3.2.12
Java: 7.0.650

ErrorLog:

2014-07-15 18:08:45,060 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-07-15 18:08:45,062 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2014-07-15 18:08:45,062 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_65
2014-07-15 18:08:45,062 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.12
2014-07-15 18:08:45,079 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-07-15 18:08:45,269 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 50923
2014-07-15 18:08:45,269 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,269 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Invalid argument: connect
2014-07-15 18:08:45,269 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,269 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2014-07-15 18:08:45,269 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2014-07-15 18:08:45,270 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.<init>(Unknown Source)
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.<init>(Unknown Source)
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2014-07-15 18:08:45,271 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -



Thanks for the help!
tiffman
 
Posts: 4
Joined: July 16th, 2014, 12:57 am

Re: Can't launch Vassal

Postby uckelman » July 16th, 2014, 7:23 am

Thus spake tiffman:
> Trying to join my friends in a game but can't seem to get Vassal
> Running. Trying to launch nothing seems to happen but I do see Java
> launch in processes for a second before quitting. I have uninstalled
> all Java, reinstalled, restarted, tried 64 vs 32 Java, tried java 6 and
> 7, as well as reinstalling Vassal in between all this. I have AVG but
> have it disabled when trying all this.
>
> OS: Windows 7 x64
> CPU: Intel i7 2600k
> Memory: 16GB
> Video: GeForce 780 GTX
> VASSAL: 3.2.12
> Java: 7.0.650
>
> ErrorLog:
>
> 2014-07-15 18:08:45,060 [0-main] INFO VASSAL.launch.StartUp - Starting
> 2014-07-15 18:08:45,062 [0-main] INFO VASSAL.launch.StartUp - OS
> Windows 7 6.1
> 2014-07-15 18:08:45,062 [0-main] INFO VASSAL.launch.StartUp - Java
> version 1.7.0_65
> 2014-07-15 18:08:45,062 [0-main] INFO VASSAL.launch.StartUp - VASSAL
> version 3.2.12
> 2014-07-15 18:08:45,079 [0-AWT-EventQueue-0] INFO
> VASSAL.launch.ModuleManager - Manager
> 2014-07-15 18:08:45,269 [0-main] WARN
> VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on
> port 50923

This is what you see when VASSAL can't connect to your loopback device
(127.0.0.1). Something is blocking it. No amount of uninstalling or
reinstalling Java or VASSAL will help.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8839
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Can't launch Vassal

Postby tiffman » July 16th, 2014, 7:00 pm

Any way that I can fix this or get around it? Never dealt with loopback device before
tiffman
 
Posts: 4
Joined: July 16th, 2014, 12:57 am

Re: Can't launch Vassal

Postby JoelCFC25 » July 16th, 2014, 7:26 pm

Do you have any firewall software (beyond the one built into Windows) running? Most times I've seen this problem, it's been from people with hyper-restrictive firewall software--e.g., Norton Internet Security.
JoelCFC25
 
Posts: 727
Joined: October 12th, 2010, 5:15 pm
Location: Minnetrista, MN

Re: Can't launch Vassal

Postby uckelman » July 16th, 2014, 7:27 pm

Thus spake tiffman:
> Any way that I can fix this or get around it? Never dealt with loopback
> device before

All I can tell you is what the problem is. I'm not a Windows user; I
don't have any advice about what specifically you need to do. But it's
not a problem with VASSAL---the problem is how you have Windows or a
local firewall or AV program configured. Maybe someone who uses Windows
can offer some advice about how to proceed.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8839
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Can't launch Vassal

Postby tiffman » July 16th, 2014, 10:17 pm

The only thing I have is AVG, but I've tried disabling AVG (including the firewall) with no luck.

The issue is all on my computer for this correct? Nothing to do with router set up or anything?
tiffman
 
Posts: 4
Joined: July 16th, 2014, 12:57 am

Re: Can't launch Vassal

Postby uckelman » July 17th, 2014, 9:48 am

Thus spake tiffman:
>
> The issue is all on my computer for this correct? Nothing to do with
> router set up or anything?

Yes, it's all local to your machine. The loopback interface is a network
interface where both ends are on to your machine (hence the name
"loopback").

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8839
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Can't launch Vassal

Postby tiffman » August 28th, 2014, 12:21 am

Been really trying to figure this out. I even found a way to create a new connection "Microsoft Loopback Adapter". Still having trouble.

Latest log:

2014-08-27 17:17:06,915 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-08-27 17:17:06,918 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2014-08-27 17:17:06,918 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_67
2014-08-27 17:17:06,918 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.13
2014-08-27 17:17:06,950 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-08-27 17:17:07,198 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 55118
2014-08-27 17:17:07,198 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,199 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Invalid argument: connect
2014-08-27 17:17:07,199 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,199 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2014-08-27 17:17:07,199 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,199 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-08-27 17:17:07,200 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.<init>(Unknown Source)
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.<init>(Unknown Source)
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2014-08-27 17:17:07,201 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

I'm guessing this still has something to do with loopback?
tiffman
 
Posts: 4
Joined: July 16th, 2014, 12:57 am

Re: Can't launch Vassal

Postby uckelman » August 30th, 2014, 9:49 pm

Thus spake tiffman:
> Been really trying to figure this out. I even found a way to create a
> new connection "Microsoft Loopback Adapter". Still having trouble.
>

Try the test build 3.2.14-svn9156, available here:

http://vassalengine.sourceforge.net/builds/

Does this change the results you get?

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8839
Joined: December 10th, 2007, 9:48 am
Location: Durham, England


Return to Technical Support & Bugs

Who is online

Users browsing this forum: No registered users and 6 guests