Vassal-3.2.10 wont start

Hi all,

I downloaded and installed the latest version of Vassal today and nothing is happening, even when I try via the modules. SO, I made sure I installed the latest 64-bit Java (to go with my 64-bit Win7 OS), I uninstalled the old Java and then restarted… still nothing is happening and I’m outta ideas (I’ve even set the .exe to run as admin too). Below is the error report I’ve found, hopefully it will make sense to some one.

So any help would be appreciated.

2014-02-09 18:27:11,394 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-02-09 18:27:11,399 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2014-02-09 18:27:11,399 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_51
2014-02-09 18:27:11,399 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.10
2014-02-09 18:27:11,461 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-02-09 18:27:11,819 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 50850
2014-02-09 18:27:11,819 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Invalid argument: connect
2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2014-02-09 18:27:11,820 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,821 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2014-02-09 18:27:11,822 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

What antivirus and/or firewall software do you have installed?

I am having the same problem. When Vassal 3.2.10 is launched for the first time, it places a folder labelled “launch4j-tmp” in the Java/JRE6 folder under “Program Files”. With that folder in place, the program will not start. Once that folder and the files contained therein are removed, Vassal will start, but every time it starts, it replaces the “launch4j-tmp” folder, which makes it rather inconvenient to use. I’m running Windows 8.1 Pro, and Vassal 3.2.0 worked fine prior to the installation of 3.2.10.

Hi again,

I’ve only got the basic firewall windows provides and I tested Vassal again with it turned off and still no joy. I’ve got no other AV software running either.

I’ve also noticed this “launch4j-tmp” thing, but regardless what I do Vassal wont start

Unless there’s any ideas, I’m going to see if I can find an earlier version of Vassal to try out.

Thus spake sithstalker:

I am having the same problem. When Vassal 3.2.10 is launched for the
first time, it places a folder labelled “launch4j-tmp” in the Java/JRE6
folder under “Program Files”. With that folder in place, the program
will not start. Once that folder and the files contained therein are
removed, Vassal will start, but every time it starts, it replaces the
“launch4j-tmp” folder, which makes it rather inconvenient to use. I’m
running Windows 8.1 Pro, and Vassal 3.2.0 worked fine prior to the
installation of 3.2.10.

Apparently newer versions of Windows don’t support one of the options
which was in Launch4j prior to 3.1.0-beta2. I’ve updated the config
file we give to Launch4j and am now building VASSAL.exe with Launch4j
3.1.0-beta2.

Please try VASSAL 3.2.11-svn9002 and let me know if this resolves the
problem for you:

vassalengine.sourceforge.net/bui … indows.exe


J.

I am having precisely the same problem, running Windows 8.1 I tried the 3.2.11 version, and windows didn’t want to run the exe, claiming it was a threat. I ran it anyway and it didn’t launch either after isntallation.

Thus spake BSkene:

I am having precisely the same problem, running Windows 8.1 I tried the
3.2.11 version, and windows didn’t want to run the exe, claiming it was
a threat. I ran it anyway and it didn’t launch either after
isntallation.

What version of Java do you have? Have you checked that you don’t have
both Java 6 and java 7 installed at once?


J.

So, I downloaded and installed this version of Vassal. Uninstalled all the others but still nothing. I’m running it as admin, have even tried compatibility mode set to XP, I’ve allowed it through my firewall and I’m definately sure I only have Java 7 64bit. Also, I’m not getting this “launch4j” folder anymore… good or bad?

Also, may attmept with the older version of Vassal didnt work either.

Thus spake vorman87:

So, I downloaded and installed this version of Vassal. Uninstalled all
the others but still nothing. I’m running it as admin, have even tried
compatibility mode set to XP, I’ve allowed it through my firewall and
I’m definately sure I only have Java 7 64bit.

We seem to have two different problems being discussed on this thread,
which is very confusing.

Please post the errorLog after an attempt to run 3.2.11-svn9002.

Also, I’m not getting this “launch4j” folder anymore… good or bad?

That’s an intentional change.


J.

I downloaded the 3.2.11 version and installed it. It started from the checked box on the finish screen initially, but once closed, it would not restart. So, basically, the problem is the same as with the 3.2.10 installation, except that the Launch file in jre6 in no longer there. When the uninstall.exe file is used, it does not fully uninstall. The “Vassal 3.2.11…” folder remains with the “lib” folder inside. The PC must be restarted to delete that file and the parent. I’m not sure if that provides any clues, but hope that this can be resolved, as 3.2.0 was running fine and there were not any problems. Thanks for any help that you can provide…

I wonder if anyone running Windows 8.1 is able to open 3.2.10?

Thus spake sithstalker:

I downloaded the 3.2.11 version and installed it. It started from the
checked box on the finish screen initially, but once closed, it would
not restart. So, basically, the problem is the same as with the 3.2.10
installation, except that the Launch file in jre6 in no longer there.

Uninstall and reinstall, but don’t launch from the installer at the
end of the install. Do you have the same problem then?

When the uninstall.exe file is used, it does not fully uninstall. The
“Vassal 3.2.11…” folder remains with the “lib” folder inside. The PC
must be restarted to delete that file and the parent.

This could happen because something is holding open a file inside lib.
What files are in the VASSAL install folder when this happens?

I’m not sure if
that provides any clues, but hope that this can be resolved, as 3.2.0
was running fine and there were not any problems.

Please find the most recent version which doesn’t have these problems
for you. I would be very surprised if that’s 3.2.0. You can find the
release archive here:

vassalengine.org/releases/


J.

Thus spake BSkene:

I wonder if anyone running Windows 8.1 is able to open 3.2.10?

I have no idea, as I haven’t been able to get anyone else using Windows
8.1 to try it and report on the results.

Please do what I recommended to sithstalker.


J.

J.

yeah a little confusing I agree. :slight_smile:

Below however is the error report from when I last tried to run Vassal 3.2.11-svn9002:

2014-02-11 17:58:03,949 [0-main] INFO VASSAL.launch.StartUp - Starting
2014-02-11 17:58:03,953 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2014-02-11 17:58:03,953 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_51
2014-02-11 17:58:03,953 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.11-svn9002
2014-02-11 17:58:03,997 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2014-02-11 17:58:04,218 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 49222
2014-02-11 17:58:04,219 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,219 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Invalid argument: connect
2014-02-11 17:58:04,219 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,219 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2014-02-11 17:58:04,219 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,219 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2014-02-11 17:58:04,219 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,221 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2014-02-11 17:58:04,222 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

Let me know if you need anything else, system specs etc

Thanks for your help so far though.

Matt

Thus spake vorman87:

J.

yeah a little confusing I agree. :slight_smile:

Below however is the error report from when I last tried to run Vassal
3.2.11-svn9002:

2014-02-11 17:58:04,218 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on
port 49222

Something is still preventing VASSAL from connecting to a socket on
your loopback interface (127.0.0.1). This isn’t a bug in VASSAL—it’s
a problem with your particular machine.

Try running VASSAL as admin. Does that make any difference?


J.

This started when I opened 3.2.9 for the first time in Windows 8.1. It seemed to open fine, but prompted me to download 3.2.10, which was the beginning of my problems.

The last couple of days, 3.2.11 would run once per day after start-up. When it was closed after that, it would not open again.

Following your advice I installed 3.2.9 and then 3.2.8, then 3.2.7. None of them worked.

Thus spake sithstalker:

Yes, the program only starts the first time it is launched, whether after installation, or after a restart of the PC. Running as admin does not resolve this situation.

The Vassal folder, which is in “Program Files” for 3.2.10 and later, or in “Programs File (x86)” for 3.2.0 and earlier, contained the following files plus lib and doc folders:
License, Readme and Changes txt files plus Vassal and Uninst exe files.

The lib folder has many files, but those that remained after uninstall were " swing-worker-1.2.jar", “smack.jar”, “sf4j-api-1.7.6.jar”, “miglayout-core-4.2.jar”, “logback-core-1.1.1.jar”, “logback-classic-1.1.1.jar”, “java-getopt-1.0.13.jar”, “janino.jar”, “commons-lang-2.5.jar”, “commons-io-1.4.jar”, “commons-compiler.jar”.

I know that I was running Version 3.2.0, as I have played many games with it. However, it appears that once V 3.2.10 was installed, something is not being removed that is causing the “one start only” situation. I loaded 3.1.19 to test this as well, and it also had the same problem.

Please post the contents of the errorLog (vassalengine.org/wiki/Error_Logs) following a failed attempt to launch.

The likely problem is that another process is holding open a file that VASSAL needs to write (or possibly read) on launch.

This is just what you’d expect to see if these files were being held open when the uninstaller was running. Windows won’t permit open files to be deleted. Did you have any version of VASSAL running when you launched the uninstaller?

Please post the contents of the errorLog from immediately after a failed launch attempt. Also, check the task manager to see if java.exe or anything similar is already running before a failed launch attempt.

Here is my error log:

2014-02-14 21:07:39,966 [1-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_45
2014-02-14 21:07:39,966 [1-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.11
2014-02-14 21:07:39,966 [1-main] INFO VASSAL.launch.Launcher - Player
2014-02-14 21:07:41,098 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - VASSAL images folder found at jar:file:/C:/Program%20Files/VASSAL-3.2.11/lib/Vengine.jar!/images/
2014-02-14 21:07:41,103 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family go-up created for go-up.png
2014-02-14 21:07:41,103 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family go-down created for go-down.png
2014-02-14 21:07:41,103 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family calculator created for calculator.png
2014-02-14 21:07:41,103 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family network-server created for network-server.png
2014-02-14 21:07:41,103 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family yes created for yes.png
2014-02-14 21:07:41,103 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family no created for no.png
2014-02-14 21:07:41,103 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family VASSAL-jabber created for VASSAL-jabber.png
2014-02-14 21:07:41,104 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family VASSAL created for VASSAL.png
2014-02-14 21:07:41,104 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family network-idle created for network-idle.png
2014-02-14 21:07:41,104 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family jabber created for jabber.png
2014-02-14 21:07:41,104 [1-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - Icon family bug created for bug.svg
2014-02-14 21:07:42,983 [1-AWT-EventQueue-0] WARN VASSAL.launch.BasicModule - War and Peace - Edition 4.0.1 version 4.0.1
2014-02-14 21:08:17,182 [1-AWT-EventQueue-0] INFO VASSAL.build.GameModule - Exiting
2014-02-14 21:08:17,651 [0-IPC receiver for 1922722747] ERROR VASSAL.tools.ipc.IPCMessageReceiver -
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source) ~[na:1.6.0_45]
at java.net.SocketInputStream.read(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream.readObject0(Unknown Source) ~[na:1.6.0_45]
at java.io.ObjectInputStream.readObject(Unknown Source) ~[na:1.6.0_45]
at VASSAL.tools.ipc.IPCMessageReceiver.run(IPCMessageReceiver.java:34) ~[Vengine.jar:na]
at java.lang.Thread.run(Unknown Source) [na:1.6.0_45]
2014-02-14 21:08:19,212 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManagerWindow - Exiting