We have a licensed installation of teleflow 2005 (24 port, on enGenic hardware) that was working “rock solid” for four months (until a week ago.) <br> <br>It is now, intermittently giving an error that we are not licensed to use Teleflow (though we are.) <br> <br>The portion of the log indicating the problem is listed below. <br> <br> <br> <br>Mar 24 11:08:07.31: Main<==LoadSystem <br> <br>Mar 24 11:08:07.31: [55] Wait for Call <br> <br>Mar 24 11:08:07.31: WARNING: TIMEOUT '0' evaluates to 0 and is interpreted as no timeout <br> <br>Mar 24 11:08:08.81: Wait for 0 rings and then pickup <br> <br>Mar 24 11:08:08.81: Open port 4, protocol 'ops0' <br> <br>Mar 24 11:08:08.81: Port requested exceeds number of ports installed in the system <br> <br>Mar 24 11:08:08.81: ERROR: WaitForCall failed to open port <br> <br>Mar 24 11:08:08.81: FAILURE <br> <br>Mar 24 11:08:08.81: ERROR: Missing next step <br> <br>Mar 24 11:08:08.81: FATAL <br> <br>Mar 24 11:08:08.81: Attempting to jump to Fatal Error Global Event label: 'APPLICATION_ERROR' <br> <br>Mar 24 11:08:08.81: [19] Label <br> <br>Mar 24 11:08:08.81: Label: APPLICATION_ERROR <br> <br>Mar 24 11:08:08.81: [105] Run Flowchart <br> <br>Mar 24 11:08:08.81: Flowchart: 'Exit' <br> <br> <br>What can be done to correct this problem??

This is not a licensing issue. Unlicensed ports will operate in an unlicensed state, which will allow your application to run, but play an advertisement message. <br> <br>The error you are getting actually means that the port requested is greater than the number of ports available in the system. You would get this message if, for example, you tried to run an application on port 25 of a single T1 system (either 23 or 24 ports depending on protocol). <br> <br>The other reason why this could occur, and likely why it is happening in your case, is that the telephony board has not been started. In that case, the available port count is zero. Every application will report that the port requested is out of range (ie: port 4 > 0). <br> <br>To correct the problem, ensure that TeleFlow Server (TFServer.exe) is not running, and re-boot the boards with OAMSYS. <br> <br>If you are running TeleFlow Server as a service, you will want to configure your cards to start with Windows. This is covered in the help file at the topic TeleFlow Server -> TeleFlow Server as a Service.

Thanks Tim. <br> <br>The system was actually booted up (oamsys running, etc.) -- it is licensed on 24 ports. Ports 1-3 were executing our Teleflow application correctly. out of nowhere port 4 gave this issue. <br> <br>Note: ports 5-24 were is a wait for call state when this happenned. <br> <br>With that said I don't think any of the conditions you mention were the case - but I'll keep them in mind.

Only port 4?! That is bizarre. <br> <br>Save a copy of all the files in your log directory(as defined with TFConfig), in case they are needed for reference later. <br> <br>Please do a full system restart to see if this corrects the problem, and gets all ports functioning again.

Yep .. did a full system restart -- all working well since then. <br> <br>Will save the files and let you know if we "catch" another similar issue.