Warning: call_user_func_array() expects parameter 1 to be a valid callback, class '' not found in /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php on line 324

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/cybercom/public_html/blog/wp-includes/class-wp-hook.php:324) in /home/cybercom/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":1375,"date":"2017-01-09T23:38:14","date_gmt":"2017-01-09T23:38:14","guid":{"rendered":"http:\/\/cybercom-software.com\/blog\/?p=1375"},"modified":"2017-01-09T23:41:23","modified_gmt":"2017-01-09T23:41:23","slug":"phonepad-5-freezing-after-login-microsoft-windows-socket-error-10060","status":"publish","type":"post","link":"https:\/\/cybercom-software.com\/blog\/index.php\/2017\/01\/phonepad-5-freezing-after-login-microsoft-windows-socket-error-10060\/","title":{"rendered":"PhonePad 5 Freezing After Login – Microsoft Windows Socket Error #10060."},"content":{"rendered":"

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.\u00a0 You can verify this by checking the PhonePad log files for the affected workstations.\u00a0 You can find them under this folder: C:\\ProgramData\\Cybercom Software\\PhonePad5\\Logs<\/em>.<\/p>\n

What is actually happening is that PhonePad 5 is trying to connect to the Notification and Communications servers<\/em> but is getting an error back from the Windows Socket Layer.\u00a0 So it tries again, and keeps trying, to establish a connection.\u00a0 It ends up in an infinite loop if the errors keep occurring.<\/p>\n\"error<\/a>\n

The immediate solution is to update to Version 5.15.0 using the PhonePad 5.15.0 Server Update<\/strong>.\u00a0 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.\u00a0 In addition to that, the connections are now done in background threads rather than the application’s main thread.\u00a0 As a result of this you should notice that PhonePad logs in much faster.<\/p>\n

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.\u00a0 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.<\/p>\n

Initial investigations show that it is generally caused by some type of network configuration issue.\u00a0 We are working on finding out solutions for this.\u00a0 Although it’s not caused by anything we are doing we would like to find out how to resolve this error.\u00a0 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.<\/p>\n

So what’s the downside of this error:<\/p>\n