We are bumping up against our maximum limit of network NavisWorks licenses, prompting some users to run the program and do nothing with it (even leaving their computer on overnight) - just to have a license "in case they need it". I've added a TIMEOUT line to the options file with a half-hour delay, but after a couple of days I can still see licenses that were pulled several days back. Shouldn't the TIMEOUT feature yank the license if the software is just sitting there without doing anything, or is there something else that I can do?
Solved! Go to Solution.
Solved by DouglasLauritsen. Go to Solution.
Try the TIMEOUTALL 900 option. That will force the return after 15 minutes of idle, which is the minimum setting. To define idle is sometimes difficult when it comes to the return of the license to the NLM. After rereading in the adskflex.opt options file, the debug log should show that activity timeout for all features is 900 seconds. Any licenses that are returned due to idle will show IN (Inactive) in the log file.
Keep in mind that all products do not support the TIMEOUT options of the NLM. I have not verified yet if Navisworks allows this. I know that AutoCAD does, but Inventor does not.
Thanks. The debug log file IN/OUT and TIMEOUT statements seem to confirm its working, even though the server status read-out is showing otherwise. I think a more practical test is in order once enough folks have left for the day.
Bugger. Left the program on but minimized and the manager kept the license signed out...
Currently NavisWorks does not have an idle state for license usage. A request to add this to a future release has been submitted to the developers. You can add to the business case on this by making a direct request yourself by filling out the feedback form at this Autodesk web page.
Thanks for the confirmation on this product's support of TIMEOUT, Doug. I had not tested it yet.
Thanks for the update. I did see a couple of (INACTIVE) markers in the debug log file, but not as many as I think there should be.
As mentioned in the first post, this feature is important when businesses start hitting that upper limit of current licenses. Users get frustrated and start opening the program first thing in the morning with no actual intention of using it, making the problem worse. Management techniques can only get you so far, after that its like herding wet cats (and not the household variety...).
I can understand the frustration and why engineers will hoard a license even when they don't need it. There are other Options that you can set in the file that would always reseve a group of engineers licenses so they can open the product anytime -- assuming there is a priority of use at your company. If you need any help with that, let me know. Otherwise, it may simply be beneficial to pick up a few more seats.
Yeah, I've considered user groups and used them in the past. The trouble in doing that is it reduces the overall number of licenses available to the general population and we end up in the same place, except those doing the complaining don't have as much influence with management. So we are getting more licenses - once they get past the IT solutions cost approval *and* they get the service moved to the new server.
When it rains it pours!