PxPlus User Forum

Twitter Twitter Twitter

Author Topic: winsock error  (Read 583 times)

Thomas Bock

  • Diamond Member
  • *****
  • Posts: 131
    • View Profile
winsock error
« on: July 26, 2019, 08:19:34 AM »
A customer reports a sporadic winsock error:

[TCP][Winsock]Error status:0 {-1:<UNK>}
Error #15: Operation system command failed

They are running several 24/7 PxPlus programs on a Win10Pro TS and no interactive programs. All programs run PxPlus V14 with SCS and SSL-WindX connections.
After an OK click the program continues.
As there are no new connections made by any of the programs, what can cause this?

Mike King

  • Administrator
  • Diamond Member
  • *****
  • Posts: 3416
  • Mike King
    • View Profile
    • PVX Plus Technologies
Re: winsock error
« Reply #1 on: July 26, 2019, 11:06:16 AM »
Since the output showed an Error 0, the issue is likely that a WRITE was issued and the Windows TCP drivers indicated they could not accept the data since all its internal buffers were full.

PxPlus will automatically retry the send up to the time limit set in the  WRITE directive or if no TIM= option is specified whatever is set in the 'DT' system parameter or 30 seconds if that is not set.

Generally this means you network (or server) is overloaded.

You try increasing the allowable retry interval eithe by changing the WRITE directive or changing the system 'DT' parameter. 

Mind you, if you have not specified a WRITE timeout delay and the buffers are still full after the default of 30 seconds, increasing the timeout is only going to make your end-users wonder if the system is hung and potentially cause you further trouble.