- This topic has 12 replies, 3 voices, and was last updated 20 years, 8 months ago by
.
-
Posts
-
I am trying to install 3.7RC2 on an Athlon64 machine and can’t get the installer to lunch. Is there a known compatibility issue with the 64 bit environment?
What operating system and version are you running?
WinXP Pro
What Eclipse version and build id are you using?
3.0M6
Eclipse freshly installed for MyEclipse?
yes
Are any other external plugins installed?
no
How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*
N/A
What MyEclipse version are you using?
30700RC2What JDK version are you using to run Eclipse?
1.4.2_03
What JDK version are you using to launch your application server?
N/A
What steps did you take that resulted in the issue?
Trying to launch the install.What application server are you using?
N/A
Are there any exceptions in the Eclipse log file? (<workspace>/.metadata/.log)
I have done some work with InstallAnywhere and I managed to startup the executable from the temp location. However, the exception that I got was:
java.lang.UnsatisfiedLinkError: getSpecialFolderJNI
at com.zerog.ia.platform.Sys.getSpecialFolderJNI(Native Method)
at com.zerog.ia.platform.Sys.getSpecialFolder(DashoA8113)
at ZeroGav.a(DashoA8113)
at com.zerog.ia.installer.util.magicfolders.AbstractWin32MF.b(DashoA8113)
at com.zerog.ia.installer.util.magicfolders.MagicFolder.initializeAllMagicFolderPaths(DashoA8113)
at com.zerog.ia.installer.Main.c(DashoA8113)
at com.zerog.ia.installer.Main.d(DashoA8113)
at com.zerog.ia.installer.Main.a(DashoA8113)
at com.zerog.ia.installer.Main.main(DashoA8113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.zerog.lax.LAX.launch(DashoA8113)
at com.zerog.lax.LAX.main(DashoA8113)Qaiser,
I am still looking into this, but check out this post and see if you have the DLL they talk about in the right place.Qaiser,
This looks like an incompatibility between InstallAnywhere and the version of JDK 1.4.2_03 that you’re using, based on the unsatisfied JNI link problem. Is there an older version of the JDK you can use to test this? For example JDK 1.4.1? This will let us know if the problem is with the JDK or is a 64-bit issue.
Riyad, That dll is in the location you mention on the build machine and is put in the temp location on install. It is present in my temp location when I try to launch the installer.
Scott, The last installer I made with IA bundled a 142_03 and worked fine targeting the windows platform. As for trying 141j2sdk on my system, I tried that and unfortunately it didn’t work. I did check the jdk for proper installation and everything seemed fine.
..at a loss for what to do. Also tried to install 2.7 with the same results.
-Qaiser
Qaiser,
I wasn’t able to find anything more in ZeroG’s knowledge base or even the JDK bug tracking system or Google. Can you try and set the LAX_DEBUG environment variable to ‘1’ before running the installer from the command line and pasting the output here for us to look at? I believe it will be something like this:c:\>set LAX_DEBUG=1 <installer name>.exeor
c:\>set LAX_DEBUG=1 c:\><installer name>.exec:\ just represents a prompt, I don’t think it matters where you actually execute from.
I have set the system environment variable LAX_DEBUG to 1 and also tried from the command prompt to do the same thing but can’t find the output that is supposed to come out. Please advise.
Qaiser,
Both of the suggestions I gave above are meant to be typed (copy-paste) to a windows command prompt:
Start -> Run -> type ‘cmd’ -> OKYou should see the output in the consolel. I provided both ways because I believe it should be the 2nd way I posted it, but we had a user in the forums say he was only able to see out put when he put both the set command and the executable on the same line.
I figured as much having seen the command prompt and the ‘set’ command. I tried that approach and didn’t get any output. The installer doesn’t get that far in my case, but I will try again. I am currently at work and will create a small installer with IA version 5.5.1 with 1.4.2_03 bundled. I will let you know what happens by lunch time (when I go home and try it out).
By the way, in their KB article (http://gamma.zerog.com/devnet_l/uT.jsp?page=kb/viewKB.jsp&itemID=28) IA doesn’t mention LAX_DEBUG=1, they sayd LAX_DEBUG=true and that too for the unix platform. I will try routing the output with what they suggest also at lunch time. Thanks for the time you are taking to correspond! 8)
Qaiser, thanks for the info about the LAX_DEBUG command, I will use that in the future. Also, if this still doesn’t work when you get home, you might try and redownload the installer and see if that helps. We’ve had 2 or 3 times where users had truncated installers, and the problem manifested itself in almost impossible to debug situations (like this)… very odd.
Got it to work.. through some handywork!! I am at lunch and gotta run, but I promise to fill you guys in about just what I did 🙂
Ok Riyad. At lunch time I thought I had the answer. Later when I opened MyEclipseIDE, I found that I didn’t have the necessary plugins doing what they were supposed to even though they were present in the plugins list.
Now that I had a little bit of time to look at the issue a bit closer, I was able to get the installer to work and get the desired results. I have prepared a zip file with my findings. I am a bit pooped out (long day at work) and need to just email you a zipped file of all the results or FTP it somwhere. Otherwise you can wait a day or so for me to get the results pasted on here in a meaningful way. Good news is, I am up and running and I would love to share the info with all here. Once again, thanks for your time. 🙁 🙂 😀 😛Qaiser,
Thank you for taking the time to put all that of that together. I’d really be most interested in you posting it into the forums in a meaningful way for all to see and hear. We don’t mind summarized versions either, just something to get people on the right track that might be having similar problems.
