gschoffstall

Geddy, I got to the point of making a ticket, but before that in my flailing about I almost bricked my pc. Fortunately, Dell Support Assist kicked in and sort of rescued my pc from the dump. They put the system back to original delivery state with Windows 10 Pro. I have to rebuild everything, so there's that. But fortunately, in rebuilding, the first thing I did was get Java and run the admin console. It worked and I'm probably going to ride Windows 10 Pro until I can't. At this point I am so frustrated with Microsoft forcing the update - and you know it's all about the money anyway. Enough from the soapbox. I'll be busy rebuilding both my i7 and my core9. Thanks for trying. FYI, I did everything possible before the thing stopped responding and wouldn't boot. I deleted the file association in the registry and let it find it again. I tried forcing the file association. I tried making sure the start file could find the executable by putting the start file in the java folder. I tried running the file from the command prompt. Microsoft reinstalled Windows 11 so many times that the original Windows 10 recovery information was gone. I might be looking for a new OS. I'm really tired if the drama and wasted time over something that should never happen. Again, Thanks to all who tried to help.

It is interesting to note that I updated two laptops to Windows 11. I just ran the same actions on the other PC, and it worked like a charm. I can tell you the one that works is an older I7 Dell, and the one giving me fits is a newer Dell with an I9, which they've now taken to calling Core 9.

Thanks for the suggestion, Geddy. Unfortunately, no joy. I uninstalled Java, rebooted, reinstalled Java from the website with the correct current version 8.441. I cleared cache again for good measure. I went to the default file setup and selected the .bin folder of Java 8.441 and selected javaws.exe. When I tried to run start.jnlp again it reverted to the same run once merry go round, never putting an icon on the desktop.

I just got communications re-established with Michel's help. This was under Windows 10. Thank you very much for helping me through it. No sooner than having this done, I reacted to Microsoft's impending shutdown of Win10 support. You guessed it, I updated to Windows 11, and it broke me again. I have another machine running Windows 10 and it still works fine. I just cannot get Win 11 to do anything. I downloaded the latest .jnlp file and tried to run it. When it didn't know how to open it, I made Java.exe the default to open those files. It keeps asking me to run it one time, and won't run the file. Any ideas? BTW, the portal does work in Win 11. It seems to be almost like the Win 10 issue, but with a twist. Thanks, George

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.

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.

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.

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.

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

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.

Sounds like a plan! Thanks again for the help.

YAY!! That worked. Thank you. When the console opened up from your supplied address, I went back to the IOX launcher. When I added the port 8080 to the launcher address, it also worked.

Yes, I checked all 3 boxes. I am running Windows 10 and the Duck Duck Go browser, but I have Chrome, Firefox, and Edge installed for options. Since I posted, I have uninstalled Java, deleted all copies of start.jnlp, re-installed Java, cleared cache (3 files) again and downloaded a new start.jnlp file. Same result.

Gentlemen, After my EISY system was up and running, it spontaneously stopped talking to me through the Admin Console. The portal works fine. All my devices do communicate. All my programs run as expected. BUT, the IOX launcher does not find the IOX. I cleared the Java cache (files) and downloaded a new start file, creating a new launcher. No good. I went on the portal, selected Maintenance> upgrade packages, rebooted. then I repeated the clear cache on Java loaded ANOTHER start file. Same result IOX Finder Not Found. Again the thing is communicating through the portal, but it won't cooperate with the Admin Console. I tried adding in the IP addresses - internal, external, and internet. It told me the addresses were invalid. I also power cycled both the PLM and EISY. Also, when I plug in the internet access to a browser, I get this: This XML file does not appear to have any style information associated with it. The document tree is shown below. What am I doing wrong?

Perfect! Also thank you Dennis C. I did not need the verbose WIKI version, but it clarified the issue. I'll save that one for the future.