I take it you're using SolidWorks Network License Manager?
I had a similar problem the other day where another using logging in pinched the only sim license we have whilst I was trying to use it. I solved the issue (with the help of my VAR) by creating an "options file" on the license server.
I used the guide linked below (and others as additional reference) to reserve the Premium license for myself.
I'm not sure if this is best practice if the "reserved for" user changes on a regular basis...
Thank you for the reply.
Hmmm, not sure I'll be able to get our I.T. to manage this on a daily basis, and the '...first come, first served' doesn't explain why once a license is in use, it can be seconded by another user initiating a simulation on a different workstation. Maybe if the first sim goes into a 'pause' or 'hold' state, it gets relinquished by another process seeking the same license.
Still, good info, thank you.
If you use the LM you can 'check-out' a license for a period of time and then they (probably) can't 'take' it from you. I use this feature on my laptop b/c I run some FEAs over the w/e.
simple and obvious....I don't know why the users aren't doing that, or why I didn't think of it.......Was looking for something more complex, but.......
You are most welcome.
borrow feature is definitely the way to resolve the issue here
the network license manager is at the mercy of your network
if your network times out, so does your license, so it goes back to the pool
if someone else snags it and the user that was using it doesn't get it in time, that causes the issue you describe
by borrowing, you guarantee the license doesn't go back to the pool, even if the network goes down
i don't really see any improvements that could be made except maybe a grace period that simulation users get...but that could easily lead to abuse.
Jared, yes, thank you. Of course.
Staring us in the face all of the time. I've been here less than a year, but users have been suffering this on and off for several years...wow!
What a numpty. I've sent out the necessary email to them all.
I don't think BORROW is a viable solution here;
It is cumbersome. You shouldn't be bothered by that, and
It is not a mechanized process - it requires human intervention, and most humans are imperfect.
They will not communicate or forget to return the license on time or be sick and OOO the morning after.
This will eminently lead to poor license availability and utilization.
I would check why the license was returned:
1. Network down issue ?
2. Check the FlexLM debug log for information.
3. Check the Options file: was license retrieval caused by a TIMEOUT parameter ?
4. Check what processes are running during your simulation.
5. Check for windows' events etc.
I think that sweeping the problem under the BORROW rug will eventually bite you back.
In OpenLM we have been working on methods for clever conditional license retrieval.
I'll be happy to discuss this with you offline (firstname.lastname@example.org).
All the best,