Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License Error when Running Wolfram Engine 14 with WLJS #162

Closed
pyreymo opened this issue May 14, 2024 · 8 comments
Closed

License Error when Running Wolfram Engine 14 with WLJS #162

pyreymo opened this issue May 14, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@pyreymo
Copy link

pyreymo commented May 14, 2024

I am encountering an issue when trying to run Wolfram Engine 14.0 with WLJS. Despite having successfully activated WE locally, I am receiving a license error. Here are the details of the error message:

image

WLJS laucher paused because of a license error.

Steps I have taken to resolve the issue:

  1. Verified that the license is correctly activated locally.
    image
  2. Attempted to run the application as an administrator.

Unfortunately, these steps have not resolved the issue. I suspect there may be an issue with how the license is being verified or with the integration between WLJS and Wolfram Engine 14.0.

I am relatively new to Wolfram Engine and this project, so I apologize in advance if this issue is due to any basic mistakes on my part. Any guidance or suggestions would be greatly appreciated.

@pyreymo pyreymo added the bug Something isn't working label May 14, 2024
@pyreymo
Copy link
Author

pyreymo commented May 14, 2024

2minutesLog.txt

Windows 11
WLJS.Notebook.Setup.2.3.5.exe

@JerryI
Copy link
Owner

JerryI commented May 14, 2024

Hello @pyreymo,
We are sorry about that, it looks like a bug. We have seen before, that sometimes Wolfram Engine does not allow to run 2 instances on the same machine for no reason (WLJS requires exactly 2), but quite rare.

We will prepare a test script for you to diagnose a problem and will try our best to help you :)

PS: thank you for log file

@JerryI
Copy link
Owner

JerryI commented May 14, 2024

Could you, please, try to download this repo and run the following demo (just directly by double-click) ?

Examples/Balls/Balls.wls

And after it finishes an installation, open http://127.0.0.1:8010 page in the browser.

@pyreymo
Copy link
Author

pyreymo commented May 15, 2024

It seems to work without any errors, the ball follows the mouse to create and then moves normally after I checked "Gravity".

image

This file Balls.log shows all the displays after I run Examples/Balls/Balls.wls.

@JerryI
Copy link
Owner

JerryI commented May 15, 2024

Looks great! One branch less..
Could you, please, locate a folder C:\\Users\<YourName>\AppData\Roaming\wljs-notebook

then you need to copy a file _settings.wl (here is a Gist link) there. It will disable second Wolfram Kernel on the startup, if it causes the crash.

Check if it crashes again and if possible, we would be appreciated for a log file as well.

@pyreymo
Copy link
Author

pyreymo commented May 16, 2024

I edited my _settings.wl to <|"Autostart" -> False|> and restarted the WLJS launcher. However, I am still encountering the license error, though it appears slightly different this time.

image

Here is the full log:
Launcher.log

@JerryI
Copy link
Owner

JerryI commented May 16, 2024

If you still have motivation, I would like to ask you to do a few more tricks. You are helping us a lot and other users, who could face similar issues.

If not - it is fine, we don't want to steal your time. Thank you again.

Tricks (just in case)
Since it fails at Autotest, could you please edit the file

C:\\Users\<YourName>\AppData\Roaming\wljs-notebook\Scripts\start.wls

and delete following lines

Screenshot 2024-05-16 at 18 43 55

It will bypass an autotest and we might see some reasonable answer and which part of a stack is malfunctioning.

@JerryI
Copy link
Owner

JerryI commented Jun 28, 2024

stale

@JerryI JerryI closed this as not planned Won't fix, can't repro, duplicate, stale Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants