Difference between revisions of "TUFLOW Message 0935"
(5 intermediate revisions by 3 users not shown) | |||
Line 7: | Line 7: | ||
As a background to the licencing, TUFLOW checks for a licence on model initialisation, and then periodically checks at a certain time interval, as well as at the end of the simulation. The CodeMeter licencing system used by TUFLOW will release any licences that are not in use after a period of time. This prevents the licence from being tied up forever by a force closed simulation (either closed through task manager or by clicking the red x at the top of the window). <br> | As a background to the licencing, TUFLOW checks for a licence on model initialisation, and then periodically checks at a certain time interval, as well as at the end of the simulation. The CodeMeter licencing system used by TUFLOW will release any licences that are not in use after a period of time. This prevents the licence from being tied up forever by a force closed simulation (either closed through task manager or by clicking the red x at the top of the window). <br> | ||
This message indicates either TUFLOW could not find any licence during a periodic check, or the licence has been already released between two periodic checks. | This message indicates either TUFLOW could not find any licence during a periodic check, or the licence has been already released between two periodic checks. | ||
− | |suggestions='' | + | |suggestions=''Fix connectivity issues:''<br> |
− | *TUFLOW may lose licences during a network failure or a licence server shutdown. Please make sure a modelling machine has | + | *TUFLOW may lose licences during a network failure or a licence server shutdown. Please make sure a modelling machine has stable network access to the licence server. |
*Some USB ports can lose power during a sleep mode and this can disconnect the licence dongle. Try plugging the licence dongle into a different USB port (preferably one of the USB ports on the back of the computer) as these should be much less likely to lose power / connectivity. | *Some USB ports can lose power during a sleep mode and this can disconnect the licence dongle. Try plugging the licence dongle into a different USB port (preferably one of the USB ports on the back of the computer) as these should be much less likely to lose power / connectivity. | ||
− | *Update your CodeMeter RunTime Kit, download available here: | + | *Update your CodeMeter RunTime Kit, download available here: <u>https://www.wibu.com/support/user/user-software.html</u>.<br> |
''Infrequent licence checks:''<br> | ''Infrequent licence checks:''<br> | ||
− | Prior to built 2018-03-AA the licence could get lost for HPC/GPU runs when the map output was very infrequent. | + | If you have checked all the connectivity issues and the problem still persists, this could be caused by licence being checked too infrequently. Prior to built 2018-03-AA the licence could get lost for HPC/GPU runs when the map output was very infrequent. This could cause TUFLOW to drop the licence and attempt to re-take the licence after a long period. A bug fix has been introduced for this in the 2018-03-AA build and later. But rarely, the licence can still get lost if the map output is infrequent, plus the model does not have ANY 1D or hidden 1D structures (e.g. a QT boundary). As a workaround: |
* Include more frequent map output, possibly within an small dummy output zone to avoid large outputs. | * Include more frequent map output, possibly within an small dummy output zone to avoid large outputs. | ||
* Include a dummy 1D channel to invoke the more frequent licence checks. | * Include a dummy 1D channel to invoke the more frequent licence checks. | ||
− | + | ||
− | + | ||
− | |||
− | |||
− | |||
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
− | |||
}} | }} |
Latest revision as of 14:45, 18 July 2024
TUFLOW Message
CHECK 0935 - Licence lost. Count = ",a,". Pausing for ",a," seconds.
Alternate Message
NA
Message Type
CHECK
Description
Access to the licence has been lost.
As a background to the licencing, TUFLOW checks for a licence on model initialisation, and then periodically checks at a certain time interval, as well as at the end of the simulation. The CodeMeter licencing system used by TUFLOW will release any licences that are not in use after a period of time. This prevents the licence from being tied up forever by a force closed simulation (either closed through task manager or by clicking the red x at the top of the window).
This message indicates either TUFLOW could not find any licence during a periodic check, or the licence has been already released between two periodic checks.
Suggestions
Fix connectivity issues:
- TUFLOW may lose licences during a network failure or a licence server shutdown. Please make sure a modelling machine has stable network access to the licence server.
- Some USB ports can lose power during a sleep mode and this can disconnect the licence dongle. Try plugging the licence dongle into a different USB port (preferably one of the USB ports on the back of the computer) as these should be much less likely to lose power / connectivity.
- Update your CodeMeter RunTime Kit, download available here: https://www.wibu.com/support/user/user-software.html.
Infrequent licence checks:
If you have checked all the connectivity issues and the problem still persists, this could be caused by licence being checked too infrequently. Prior to built 2018-03-AA the licence could get lost for HPC/GPU runs when the map output was very infrequent. This could cause TUFLOW to drop the licence and attempt to re-take the licence after a long period. A bug fix has been introduced for this in the 2018-03-AA build and later. But rarely, the licence can still get lost if the map output is infrequent, plus the model does not have ANY 1D or hidden 1D structures (e.g. a QT boundary). As a workaround:
- Include more frequent map output, possibly within an small dummy output zone to avoid large outputs.
- Include a dummy 1D channel to invoke the more frequent licence checks.
Up |
---|
0xxx Messages |