UG-106181 C-WCS Forcing Additional Wavelink Licenses
Aptean
Forcing Additional Wavelink Licenses
WCS - 3.4
30th April 2025 - 1.0
Reference: UG 106181
Forcing Additional Wavelink Licenses
Preparation
Ensure that all RDT users are logged off the system.
Re-start WCS-Server application
Log on the WCS Server machine and locate the WCS-Server application:
To stop, click the 'X' in the corner:
Enter the password.
Click 'OK'
If any RDT users are connected, you will be prompted how long to wait before logging them off:
If you enter 0, the WCS-Server application will exit immediately without informing any connected RF users.
If you leave a positive number of minutes in here, the WCS-Server will commence a countdown on the screen, and will send each connected RF user a message, to exit the system immediately.
To restart the WCS-Server application, choose the application from the Start menu/Programs/Warehouse Control Server/WCS Server shortcut.
When the server restarts, the WCS will reconnect to any RDT users when they next press a key:
Stop and Start the Wavelink Services
Note: Restarting the Wavelink services will forcibly disconnect any users currently connected. Any users disconnected in this way may require their locks clearing through the WCS Maintenance application (if they were performing a task when forcibly disconnected). It is also possible that RF applications that have been forcibly disconnected in this way may not be killed efficiently by the operating system. Therefore these orphaned or 'spinning' processes may need to be killed manually – see Appendix A
Start the Services control panel by clicking on Start/Settings/Control Panel/Administrative Tools/Services.
Stop the WavelinkServer and WavelinkStartupSrvc by selecting the services and clicking the 'Stop' button on the toolbar:
Start the WavelinkStartupSrvc Service by selecting the service and pressing the 'Start' (play) button on the toolbar.
Start WavelinkStartupSrvc Service by selecting the service and pressing the 'Start' (play) button on the toolbar.
Note: At this point, you may want to enable extra diagnostic messages in Wavelink, to help resolve the problem. If so, do not start the process this way, but right-click on the Wavelink service and choose Properties from the pop-up menu.
Enter -D4 in the Start parameters, then click 'Start':
Note: The Debug levels for Wavelink Server are:
| Debug Level | Purpose |
| 0 | No debug messaging at all |
| 1 | Notifies the event log and the WaveLink log files of the WaveLink server start-up and termination. |
| 2 | Level 1 messages plus major application errors |
| 3 | Level 2 messages plus minor application errors and warnings |
| 4* | Level 3 messages plus current action messages. |
*Level 4 debugging also enables the WaveLink API debug messaging.
Appendix A: Killing Orphaned RDT Processes
Run Windows Task Manager:
Orphaned processes will be named 'RDTMenu1.exe' and will be constantly taking a large amount of CPU. Once these have been identified, click on the RDTMenu1 processes taking the CPU and click 'End Process'.
Click 'Yes' – this will kill the process.
If necessary, repeat this process to kill all the orphaned RDTMenu1 processes.
