![]() ![]() We did not have an issue with lost licenses. You could easily see the issue in the resource monitor program. We had a similar issue in the past 6 weeks where Creo Parametric was going into a not responding mode every few seconds. ![]() You might have to call in the PTC folks to debug the problem. If you're actually having hangups of the program with "not responding" situations, it might be something more serious with your license server. In my instance it was the constant notifications that was bothering me, so I killed them with the config option: suppress_license_loss_dialog yes For example, the server expects a license request for a particular license every 120 seconds or so, but Creo is only asking for the license every 180 seconds, so the server thinks the license is no longer needed and releases it, then when the request from the client comes it gives it but triggers an alert to the user. The server is probably set to a “timeout” for the licenses that is shorter in duration than what the client programs are using. My theory was that it’s a timing thing between the server license manager and the client program (Creo). A while back I had the problem of getting a constant stream of ".Regained floating license you can resume working" messages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |