If you have a version of PhonePad 5 earlier than 5.15.0 and are experiencing “freezing” issues after logging in, then you are probably getting Microsoft Windows Socket Error #10060. You can verify this by checking the PhonePad log files for the affected workstations. You can find them under this folder: C:\ProgramData\Cybercom Software\PhonePad5\Logs.
What is actually happening is that PhonePad 5 is trying to connect to the Notification and Communications servers but is getting an error back from the Windows Socket Layer. So it tries again, and keeps trying, to establish a connection. It ends up in an infinite loop if the errors keep occurring.
The immediate solution is to update to Version 5.15.0 using the PhonePad 5.15.0 Server Update. Although you will still get an error message about Microsoft Windows Socket Error #10060, PhonePad will no longer “freeze” as the number of retries has been limited. In addition to that, the connections are now done in background threads rather than the application’s main thread. As a result of this you should notice that PhonePad logs in much faster.
Unfortunately there’s nothing we can do within PhonePad to stop this error from occurring as it’s actually happening outside of PhonePad in the Microsoft Windows Socket layer. PhonePad is asking for the connections. Once a connection has been requested there’s nothing PhonePad can do about it except ask again – it’s up to Windows to provide the connection.
Initial investigations show that it is generally caused by some type of network configuration issue. We are working on finding out solutions for this. Although it’s not caused by anything we are doing we would like to find out how to resolve this error. If all goes well the solution will either be in the form of instructions, or if at all possible we will try to do it programmatically.
So what’s the downside of this error:
- PhonePad workstations with the error won’t be able to receive broadcasts from system administrators.
- Dynamic Refresh will be disabled and PhonePad will automatically revert to the polling method of new message checking.
The bottom line is you will be able to continue using PhonePad 5 as normal so it’s only a slight inconvenience.