you could try to start Spark with Spark.cmd start script and set the Direct 3D parameters. Do you get a Javacore file (located somewhere in the Spark directory) when Spark crashes? It should contain some useful information.
I run the cmd script and tested all 3 parameters (-Dsun.java2d.ddoffscreen=false -Dsun.java2d.d3d=false -Dsun.java2d.noddraw=true) but it crashs again.
I run the cmd script with the debug funktion (“C:\Program Files (x86)\Java\jre1.6.0_05\bin\java.exe” -Xms16m -Xmx16m -XX:NewSize=4m -XX:MaxNewSize=4m -XX:PermSize=16m -XX:MaxPermSize=16m -XX:+PrintGCDetails org.jivesoftware.launcher.Startup %autologin%)
in Attachment the Screen dump.
And i think i found the core file in Spark directory. In Attachment too
As you are using JRE 1.6.0_05 you should update the JRE to 1.6.0_06 or 1.6.0_10-beta and try to reproduce the issue. If this happens again you can submit a bug report to Sun.
Did you ever get this resolved? Did LG’s last suggestion work? I have the same problem so I’d like to know what your fix turned out to be (if you found one). Thanks!
I would like to know this as well. I’ve got it happening on a Win 2k3 x64 Terminal Server. Here’s the kicker. If I login to the account as the local machine admin, I can bring up that ADVANCED window. However, if I login with any domain accounts, it crashes when I press ADVANCED.
In my case, my ultimate goal is to just pre-enable the autofind server and SSO options so users can just run the program w/o needing to initially configure it.
it may be more easy to create the configuration files (and if needed registry entries) for every Spark user than strarting and configuring it for every user manually. Running it on a terminal server may be a bad idea as Spark needs about 64 MB memory.
Normally I’d agree, but I’m a noob, so not entirely sure how to. And for the terminal server part, not too worried about it, 32 GB server for 16 users. Pleanty of room/ram.
Likely a problem with the used dll. Anyhow Spark does usually not run on servers - so I have no idea whether this is a win2003 problem or a problem with your setup.