Hello,
I have been unable to open the latest installment of Vassal, namely version 3.1.19
Whenever I try to access my Vassal program,
a message pops up,
stating that the socket of the Module Manager
is not operational and urges me to restart Vassal.
This does not seem to work and I also have tried installing/reinstalling the application to no noticeable effect.
I will add that I have never experienced problems with previous
versions of Vassal.
The specs of my computer are the following:
Acer Aspire 8930
OS: Windows Vista
RAM: 4 Mega
CPU: Intel (R) Core ™ 2 QuadQ9000 @2.00 GHz
System : 32 bits
Video card
NVIDIA® GeForce® 9600M GT
And yes, I have updated my Java parameters…
Any help would be greatly appreciated
TIA
Thus spake Coryphodon:
Whenever I try to access my Vassal program,
a message pops up,
stating that the socket of the Module Manager
is not operational and urges me to restart Vassal.
What is the exact error message?
–
J.
Thank you Uckelman for your concern,
The main text of the message is the following:
“The socket over which the Module Manager communicates has had a fault Please restart Vassal”
a more detailed message says :
java.net. Socket. exception: Socket closed
at java.net Plain Socketlmpl.socketAccept (Native Method)
at java.net Plain Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at Vassallaunch Command Server.run (Command ServerJava 62)
atjavalang.Thread run (Unknown Source)
Cheers
Thus spake Coryphodon:
Thank you Uckelman for your concern,
The main text of the message is the following:
“The socket over which the Module Manager communicates has had a fault
Please restart Vassal”
a more detailed message says :
java.net. Socket. exception: Socket closed
at java.net Plain Socketlmpl.socketAccept (Native Method)
at java.net Plain Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at java.net Server Socketlmpl.socketAccept (Unknown Source)
at Vassallaunch Command Server.run (Command ServerJava 62)
atjavalang.Thread run (Unknown Source)
Cheers
Does this problem persist after you reboot?
–
J.
Sorry Uckelman, I tried rebooting the computer but the problem persists.
Cheers
Thus spake Coryphodon:
Sorry Uckelman, I tried rebooting the computer but the problem persists.
Then it’s likely that you have a stale lock file. Look in
%APPDATA%\VASSAL. What files do you see there?
–
J.
Hello again,
OK, it seems that you are in the right path to diagnose my problem…
I took a look at my folder and the lock file is empty (0 Ko)
The error file and the key file both have 1 Ko, the preferences file has 12 Ko
What should be my next step?
Anyways,
Thanks a lot, Uckelman
OK, lock file deleted
Should I reinstall the program?
Thanks
Thus spake Coryphodon:
OK, lock file deleted
Should I reinstall the program?
No. Deleting the lock file should be sufficient.
–
J.
Sorry Uckelman to bother
but upon
clicking on the Vassal icon, I receive a message
from the Java virtual Machine launcher
stating that it cannot find the Vassal Module Manager
so, the program fails to open
Thus spake Coryphodon:
Sorry Uckelman to bother
but upon
clicking on the Vassal icon, I receive a message
from the Java virtual Machine launcher
stating that it cannot find the Vassal Module Manager
so, the program fails to open
This is a different problem.
What is the shortcut set to run when you click it? (Check its
Properties.)
–
J.
Hello Uckelman,
The Vassal application is set to
“C:\Program Files\VASSAL\VASSAL.exe”
However it opens at
“C:\Program Files\VASSAL”
Window of execution is normal
Thus spake Coryphodon:
Hello Uckelman,
The Vassal application is set to
“C:\Program Files\VASSAL\VASSAL.exe”
However it opens at
“C:\Program Files\VASSAL”
Window of execution is normal
What’s the exact error message you see?
–
J.
Sorry Uckelman for having been unclear,
the Java Virtual Machine Launcher announces:
“could not find the main class
VASSAL.launch.ModuleManager
Program will exit”
Cheers
Beats me,
I only downloaded the newest version of Vassal (3.1.19) and the Case Blue / Guderian 's Blitzkrieg II
Module
Until then I haven’t experienced problems with the application
All the best
Thus spake Coryphodon:
Beats me,
When you installed, did you choose a Standard install, or a Custom
install?
–
J.
Hello
Sorry, I forgot to mention that this was a standard installation (as always whenever I install a new application)
Thanks
Thus spake Coryphodon:
Hello
Sorry, I forgot to mention that this was a standard installation (as
always whenever I install a new application)
Let’s keep narrowing down the possible causes.
What files and directories are in C:\Program Files\VASSAL?
Does C:\Program Files\VASSAL\lib\Vengine.jar exist?
–
J.