gschoffstall Posted March 17 Posted March 17 I haven't talked to my Eisy in a while. I tried connecting to track down an issue, but it wouldn't connect. I tried all the usual suspects - clear cache, uninstall Java, reinstall, clear cache, reset Eisy and the PLM - twice. It recognizes the device if I use the online portal tool with web access and sees the program and devices. It just will not recognize the Eisy for the console. I can see the device on my network, but when I go to add it to the admin console, it just can't find it. I get IoX Not Found. Windows 10 22H2, Eisy firmware 5.8.4 Seems I get myself into these problems because it just works mostly and I lose familiarity. This may just be a red herring, but I just installed a Synology NAS on my network. Any ideas would be greatly appreciated. Quote
Solution gschoffstall Posted March 17 Author Solution Posted March 17 Don't know if this helps, but here's a Java log: Java Web Start 11.441.2.07 Using JRE version 1.8.0_441-b07 Java HotSpot(TM) 64-Bit Server VM JRE expiration date: 6/15/25 12:00 AM console.user.home = C:\Users\gscho ---------------------------------------------------- c: clear console window f: finalize objects on finalization queue g: garbage collect h: display this help message m: print memory usage o: trigger logging p: reload proxy configuration q: hide console r: reload policy configuration s: dump system and deployment properties t: dump thread list v: dump thread stack 0-5: set trace level to <n> ---------------------------------------------------- Missing Application-Name manifest attribute for: https://isy.universal-devices.com/launcher/isyfinder-3.6.jar Running query on George/100.122.107.49 java.io.FileNotFoundException: C:\Users\gscho\AppData\Local\Temp\udi_launcher.state (The system cannot find the file specified) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(Unknown Source) at java.io.FileInputStream.<init>(Unknown Source) at java.io.FileInputStream.<init>(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.restoreState(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.restoreState(Unknown Source) at com.universaldevices.isyfinder.ISYFinder$9.run(Unknown Source) Server is not yet listening Server is not yet listening Server is not yet listening Listening for responses... Asking question Question{qName=_https._tcp.local., qType=PTR, qClass=IN} Asking question Question{qName=_https._tcp.local., qType=PTR, qClass=IN} Response received! Response was not a mDNS response packet, ignoring it Listening for responses... Response received! Response was not a mDNS response packet, ignoring it Listening for responses... No instances of type _https._tcp found Quote
Guy Lavoie Posted March 17 Posted March 17 Have you tried manually adding it to the IoX finder with it's IP address? Click on "add" and enter the URL with the IP address (for example, 192.168.0.99): https://192.168.0.99:8443/desc Quote
Geddy Posted March 17 Posted March 17 13 hours ago, gschoffstall said: Missing Application-Name manifest attribute for: https://isy.universal-devices.com/launcher/isyfinder-3.6.jar Running query on George/100.122.107.49 java.io.FileNotFoundException: C:\Users\gscho\AppData\Local\Temp\udi_launcher.state (The system cannot find the file specified) Something seems odd with this process. I just ran the IoX Launcher and compared my console and it never had the manifest line. Have you downloaded a fresh start.jnlp from the UD website lately? Make sure you're not using an old downloaded file! Seems that you've got the current Java version installed (8_411). When you're clearing the Java Cache are you checking all 3 boxes? It's looking for a .state file that says it cannot find. That's usually added with a successful launch of the IoX Launcher applet. Are you running any antivirus or firewall software that might have removed .state files in the referenced directory? Typically they'll be recreated, but for this to be looking for it and not being there is a concern. Quote
gschoffstall Posted March 17 Author Posted March 17 The Java app is new because I uninstalled and reinstalled the current version. I also went to UD and got the latest Start.jnlp file. I always check all 3 boxes and run the finder again. I do run the Brave browser instead of Edge or something else. I don't have a specific firewall configured that I set up. I did just installed a NAS on my network. No idea if it did something on the install, but again, I didn't configure a firewall on the install. Quote
gschoffstall Posted March 17 Author Posted March 17 Michel messaged me through a series of SSI scripts that pointed him to the port that I was missing to add to the IP with the ADD function to the launcher. Until I added the port to the Eisy IP address it was returning "Not Found". It works now, but I am confused as to why the Java app or Eisy "forgets its address and/or port". I can always go fishing to find the IP, but the port, if I forget it, is a problem. Quote
tlightne Posted March 17 Posted March 17 Do you save the ISY Finder file?? If you do you can just reload it when the Java app resets the IP and port number.. Quote
gschoffstall Posted March 18 Author Posted March 18 I always save the start.jnlp file. Problem is, when it forgets its IP, it also forgets its port. Finder doesn't find the device without the port. So it's a vicious cycle unless you have the port memorized or recorded somewhere. then knowing the IP along with the port redirect lets finder actually find the EISY. Quote
Guy Lavoie Posted March 18 Posted March 18 When you click on "Save" in the IoX Finder screen, it saves everything you see in the URL box. Ip address, port, directory. then if it ever comes up blank, I click on "Load" and it loads back the settings. Quote
Geddy Posted March 18 Posted March 18 15 hours ago, gschoffstall said: I can always go fishing to find the IP, but the port, if I forget it, is a problem. Can always read the wiki troubleshooting: https://wiki.universal-devices.com/Eisy:User_Guide#Can't_Find_eisy Quote
gschoffstall Posted March 18 Author Posted March 18 Thanks to everyone for all the help, especially Michel K. for babysitting me. I really appreciate it The operative word in my case is "Normally 8443" for the port. My system, for whatever reason, decided it should like to be port 8080. Thanks again. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.