Hi all,
Had a fully working vassal until I was prompted to download the latest version. Now it just opens and closes very quickly.
I have ensured I have the lastest version of Java Runtime (1.7.0_17-bo2)
Any advice or guidance.
Cheers
Thus spake mbbelius:
Hi all,
Had a fully working vassal until I was prompted to download the latest
version. Now it just opens and closes very quickly.I have ensured I have the lastest version of Java Runtime (1.7.0_17-bo2)
Any advice or guidance.
Cheers
What OS are you using?
–
J.
Windows 7
Thus spake mbbelius:
Windows 7
Have you gone through this?
vassalengine.org/wiki/VASSAL_Does_Not_Start
What were the results?
–
J.
Tried that and here’s the error log data, many thanks for your help 
2013-05-21 22:05:27,452 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-05-21 22:05:27,455 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2013-05-21 22:05:27,455 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_17
2013-05-21 22:05:27,455 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.5
2013-05-21 22:05:27,506 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2013-05-21 22:05:28,737 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 52868
2013-05-21 22:05:28,738 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,738 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.ConnectException: Connection refused: connect
2013-05-21 22:05:28,738 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,739 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2013-05-21 22:05:28,739 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,739 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2013-05-21 22:05:28,739 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,739 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2013-05-21 22:05:28,739 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,740 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2013-05-21 22:05:28,740 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,740 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2013-05-21 22:05:28,740 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,740 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2013-05-21 22:05:28,740 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,741 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2013-05-21 22:05:28,741 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,741 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2013-05-21 22:05:28,741 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,741 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2013-05-21 22:05:28,741 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,741 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2013-05-21 22:05:28,742 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,742 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2013-05-21 22:05:28,742 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,742 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:214)
2013-05-21 22:05:28,742 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
Thus spake mbbelius:
Tried that and here’s the error log data, many thanks for your help
2013-05-21 22:05:28,737 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on
port 52868
2013-05-21 22:05:28,738 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - 2013-05-21 22:05:28,738
[0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
java.net.ConnectException: Connection refused: connect
The immediate problem is that that the Module Manager is not able to
connect to the socket on which it talks with itself.
Do you have a local firewall which is blocking connections over the
loopback device?
–
J.
I have avast security on my pc which has a firewall.
I went into the firewall settings to allow vassal access but the vassal program doesn’t appear in my current list of programs??
Does it appear under a different name?
Apols for being a bit slow but I cant understand as the previous version was working perfectly fine with avast installed before.
Cheers.
Thus spake mbbelius:
I have avast security on my pc which has a firewall.
I went into the firewall settings to allow vassal access but the vassal
program doesn’t appear in my current list of programs??Does it appear under a different name?
It might show up as “java.exe” instead.
Someting else worth trying is to rename VASSAL’s settings directory
to something else and let VASSAL create a new one. The directory
to move out of the way is the one where you found the errorLog.
–
J.