We have 3 or 4 out of 28 users that while running Navisworks Manage 2014 at the same time, their license are being disconnected while currently working. They are also using Autocad at the same time. It's only Navisworks Manage which is disconnecting. If it's the network connection then both autocad and manage should be disconnected. I've already checked the LAN cables, switches, etc. and everything are good. The inactivity is set to 90 minutes in the option file. Attached is the picture of the error.
It has been ongoing for 4 months now.
Solved! Go to Solution.
Solved by TravisNave. Go to Solution.
You might post a debug.log file as it might have some insight as to the failure. Also, you might consider the FLEXLM_TIMEOUT system environment variable if it is indeed a latency issue.
Can you expand what to do and where to find the FLEXLM_TIMEOUT system environment variable? What should be the value? Also, where to find the debug.log?
Thanks!
Absolutely. The FLEXLM_TIMEOUT is a system environment variable set on the client machines. It lengthens the amount of wait time for a heartbeat. It is generally best to start at 1000000 (one-million) and move up in million increments (one second each) for additional testing.
Also, the debug log should be created by your license manager. It's location is listed in the config services tab of LMTOOLS on your license manager server.
Hope that helps.
We can get a license no problem with that. The issue is when the user is currently using NW Manage, the license is lost. It will kick him out while actively using it. See attached error window in my first post.
Thanks.
Right. Okay, so I think there might be a couple of issues going on. You might have a problem with some of your cascading because I do see some unsupported errors. That could be more related to a corrupt cascadeinfo.cas file on that client machine. Deleting it should resolve those issues.
Now, I also see the TIMEOUTALL is working because there are users that are going inactive and their license is being returned. What seems to be happening though is that you are running out of licenses. During the inactivity times, there are also -4 errors showing you are out of seats. Thus when the inactive license is returned, there are none available when the application is active again. It then closes. This is actually by design and what the TIMEOUTALL is supposed to do. That way there are no licenses being hoarded. Honestly, you might simply be short on Navis seats.
Wow! Thanks for the insight! Very informative...
Last question, where do I find the cascadeinfo.cas file on the the client machine?
Thanks again!