Modules Won't Tile

I’m having a problem with modules that just showed up. From all indications the modules do not do their initial tiling. When I open the module is says, “Bad Data in Module: Image not found.” I just added a internet content filter to my system so I suspect that it is the problem. I just have not yet figured out which aspect is causing the problem.

The error log shows that there was as problem during the tiling process.

I am running Vassal 3.2.2 on a Windows 7 machine. The vassal error log is as follows:

2013-03-10 14:36:59,284 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-03-10 14:36:59,287 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7
2013-03-10 14:36:59,287 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_17
2013-03-10 14:36:59,287 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.2
2013-03-10 14:36:59,319 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2013-03-10 14:37:03,609 [0-SwingWorker-pool-32688575-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\Tony\Documents\Vassal Mods\DAKII_v4_25_rc5.vmod
2013-03-10 14:37:04,290 [0-SwingWorker-pool-32688575-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files (x86)\Java\jre7\bin\java -classpath lib\Vengine.jar -Xmx129M -DVASSAL.id=2 -Duser.home=C:\Users\Tony -DVASSAL.port=51920 VASSAL.tools.image.tilecache.ZipFileImageTiler C:\Users\Tony\Documents\Vassal Mods\DAKII_v4_25_rc5.vmod C:\Users\Tony\AppData\Roaming\VASSAL\tiles\fedb9b312aca02b4f434cb390388e097b9567c65 256 256
2013-03-10 14:37:06,580 [2-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Starting
2013-03-10 14:37:06,630 [2-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/2Allied All.PNG
2013-03-10 14:37:06,633 [2-main] ERROR VASSAL.tools.image.tilecache.ZipFileImageTiler -
java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite0(Native Method) ~[na:1.7.0_17]
at java.net.SocketOutputStream.socketWrite(Unknown Source) ~[na:1.7.0_17]
at java.net.SocketOutputStream.write(Unknown Source) ~[na:1.7.0_17]
at java.io.DataOutputStream.writeByte(Unknown Source) ~[na:1.7.0_17]
at VASSAL.tools.image.tilecache.ZipFileImageTiler$3.receive(ZipFileImageTiler.java:142) ~[Vengine.jar:na]
at VASSAL.tools.image.tilecache.ZipFileImageTiler$3.receive(ZipFileImageTiler.java:140) ~[Vengine.jar:na]
at VASSAL.tools.image.tilecache.FileArchiveImageTiler.run(FileArchiveImageTiler.java:71) ~[Vengine.jar:na]
at VASSAL.tools.image.tilecache.ZipFileImageTiler.main(ZipFileImageTiler.java:167) ~[Vengine.jar:na]
2013-03-10 14:37:06,634 [2-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Exiting
2013-03-10 14:37:06,660 [0-SwingWorker-pool-32688575-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module OCS - DAK II
2013-03-10 14:37:06,663 [0-SwingWorker-pool-32688575-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files (x86)\Java\jre7\bin\java -Xms256M -Xmx512M -DVASSAL.id=1 -DVASSAL.port=51923 -Duser.home=C:\Users\Tony -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\Tony\Documents\Vassal Mods\DAKII_v4_25_rc5.vmod
2013-03-10 14:37:08,895 [1-main] INFO VASSAL.launch.StartUp - Starting
2013-03-10 14:37:08,900 [1-main] INFO VASSAL.launch.StartUp - OS Windows 7
2013-03-10 14:37:08,900 [1-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_17
2013-03-10 14:37:08,900 [1-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.2
2013-03-10 14:37:08,900 [1-main] INFO VASSAL.launch.Launcher - Player
2013-03-10 14:37:11,553 [1-AWT-EventQueue-0] WARN VASSAL.launch.BasicModule - OCS - DAK II version 4.25
2013-03-10 14:37:16,315 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 909f65731268b76ab8ca6906f8269b6f50747ce5
2013-03-10 14:37:16,316 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 3ae72065682ceb3ad49589b998a302ddb16bea5e
2013-03-10 14:37:16,316 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: dc0aeb1ac82c7e64391eedc0d5c3d5288196ab91
2013-03-10 14:37:16,317 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: f947a88edb069752c09ef9f43c684ed106655784
2013-03-10 14:37:16,317 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 155772249d489c015ee2b420b277da995f6384c4
2013-03-10 14:37:16,317 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 0e5ed0d1faee6026b54090092f6e48f91b7ed335
2013-03-10 14:37:16,318 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 56a3ff43d26dc592f05b43e2129d668995a7f84e
2013-03-10 14:37:16,318 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: c3e78ba3139aee086bc56458231caa5b9422273b
2013-03-10 14:37:16,318 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 2f9623c11852ff6a294ecd5ccc2b545e0f1f53b5
2013-03-10 14:37:16,319 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: f06092ec031532e9c54354b9815cd034ab07923c
2013-03-10 14:37:16,319 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: e1614f0994f8588dd7dffa5093c2b56dd1b57f2a
2013-03-10 14:37:16,319 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 393884c778e1aa9ce4c89f76c0dcb69b587a1d1d
2013-03-10 14:37:16,319 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 3a4aa963e9a2550e501c4ec9fcfbe3200e71351d
2013-03-10 14:37:16,320 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 851b45168b12e3f4ec7bbd07d67efe10fd0b92fe
2013-03-10 14:37:16,320 [1-AWT-EventQueue-0] WARN VASSAL.tools.ErrorDialog - Image not found: 7622fcb9254fc6cc6d4661780e19ccf713ef61e8

Thus spake TonysWar:

I’m having a problem with modules that just showed up. From all
indications the modules do not do their initial tiling. When I open the
module is says, “Bad Data in Module: Image not found.” I just added a
internet content filter to my system so I suspect that it is the
problem. I just have not yet figured out which aspect is causing the
problem.

The Module Manager talks to the Tiler over the loopback interface,
which normally has IP 127.0.0.1. Your problem appears to be that
connections over the loopback device aren’t permitted. Poorly designed
security software sometimes blocks access to the loopback device—
access which is totally safe, because the whole point of the loopback
is that your machine is both the sender and receiver of data.


J.

Thanks. That helps. I’ll check it out.