Create account / Log in

Vassal-3.2.10 wont start

Issues with the Vassal engine.

Moderators: uckelman, Tim M

Vassal-3.2.10 wont start

Postby vorman87 » February 9th, 2014, 6:29 pm

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.<init>(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.<init>(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 -
vorman87
 
Posts: 4
Joined: February 9th, 2014, 6:23 pm

Re: Vassal-3.2.10 wont start

Postby JoelCFC25 » February 10th, 2014, 1:34 am

What antivirus and/or firewall software do you have installed?
JoelCFC25
 
Posts: 730
Joined: October 12th, 2010, 5:15 pm
Location: Minnetrista, MN

Re: Vassal-3.2.10 wont start

Postby sithstalker » February 10th, 2014, 7:51 pm

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.
sithstalker
 
Posts: 14
Joined: April 16th, 2013, 8:56 pm

Re: Vassal-3.2.10 wont start

Postby vorman87 » February 10th, 2014, 8:51 pm

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.
vorman87
 
Posts: 4
Joined: February 9th, 2014, 6:23 pm

Re: Vassal-3.2.10 wont start

Postby uckelman » February 10th, 2014, 9:04 pm

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:

http://vassalengine.sourceforge.net/bui ... indows.exe

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

Re: Vassal-3.2.10 wont start

Postby BSkene » February 11th, 2014, 12:17 am

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.
BSkene
 
Posts: 11
Joined: February 11th, 2014, 12:15 am

Re: Vassal-3.2.10 wont start

Postby uckelman » February 11th, 2014, 8:09 am

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.
User avatar
uckelman
Site Admin
 
Posts: 8848
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Vassal-3.2.10 wont start

Postby vorman87 » February 11th, 2014, 5:47 pm

uckelman wrote: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:

http://vassalengine.sourceforge.net/bui ... indows.exe

--
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.
vorman87
 
Posts: 4
Joined: February 9th, 2014, 6:23 pm

Re: Vassal-3.2.10 wont start

Postby uckelman » February 11th, 2014, 6:25 pm

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.
User avatar
uckelman
Site Admin
 
Posts: 8848
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Vassal-3.2.10 wont start

Postby sithstalker » February 12th, 2014, 12:36 am

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....
sithstalker
 
Posts: 14
Joined: April 16th, 2013, 8:56 pm

Re: Vassal-3.2.10 wont start

Postby BSkene » February 12th, 2014, 3:29 am

I wonder if anyone running Windows 8.1 is able to open 3.2.10?
BSkene
 
Posts: 11
Joined: February 11th, 2014, 12:15 am

Re: Vassal-3.2.10 wont start

Postby uckelman » February 12th, 2014, 8:30 am

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:

http://www.vassalengine.org/releases/

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

Re: Vassal-3.2.10 wont start

Postby uckelman » February 12th, 2014, 9:32 am

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.
User avatar
uckelman
Site Admin
 
Posts: 8848
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Vassal-3.2.10 wont start

Postby vorman87 » February 12th, 2014, 10:56 pm

J.

yeah a little confusing I agree. :)

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.<init>(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.<init>(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
vorman87
 
Posts: 4
Joined: February 9th, 2014, 6:23 pm

Re: Vassal-3.2.10 wont start

Postby uckelman » February 12th, 2014, 11:46 pm

Thus spake vorman87:
> J.
>
> yeah a little confusing I agree. :)
>
> 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.
User avatar
uckelman
Site Admin
 
Posts: 8848
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Next

Return to Technical Support & Bugs

Who is online

Users browsing this forum: No registered users and 8 guests