Menu

Discussion Forum

New Discussion
Filtern

Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.

How to Ignore Livelink Licensing Error

Posted 21.04.2020, 21:40 GMT-4 LiveLink for MATLAB 1 Reply

Denise Widdowson
Send Private Message Flag post as spam

Please login with a confirmed email address before reporting spam

Hello,

I'm using livelink with matlab to run simulations which involve opening a model. The issue I run into is that when the CAD Import licenses are used up, which my script does not require, COMSOL will throw an exception just trying to open a saved file. Interactively, when I open COMSOL and open the file myself, I get the same error, but can click "OK" on the dialog box and it opens my model. How can I effectively ignore this error in my script and continue to opening the file?

Thanks,

Denise

1 Reply Last Post 23.04.2020, 05:18 GMT-4
Lars Gregersen COMSOL Employee

Please login with a confirmed email address before reporting spam

Posted: 4 years ago 23.04.2020, 05:18 GMT-4

Hi Denise

We can have a look at the error message, but it'll take some days since some things are more complcated than usual.

If you open your model in the Comsol GUI and click on the Geometry node you can change the Geometry representation to "Comsol kernel" and save the model. After this, you shouldn't see this error message again for this model.

-------------------
Lars Gregersen
Comsol Denmark
Hi Denise We can have a look at the error message, but it'll take some days since some things are more complcated than usual. If you open your model in the Comsol GUI and click on the Geometry node you can change the Geometry representation to "Comsol kernel" and save the model. After this, you shouldn't see this error message again for this model.

Note that while COMSOL employees may participate in the discussion forum, COMSOL® software users who are on-subscription should submit their questions via the Support Center for a more comprehensive response from the Technical Support team.

Suggested Content