Error-Code 642 - Unable to receive data

2 posts / 0 new
Last post
MatzeR
Error-Code 642 - Unable to receive data

Hi Support-Community,

I have a RPM Version 5.1.1.99 installed and licensed. On this servers are at this moment two printing queues, they work fine. Now, I have an VPN to our branche-office. When the branche-office, try to print to their queue I always get the error 642. I already tested many firewall settings, this should be fine. The queue of the branch-office is enabled, no transforms choosen, and Action is "Archive to folder" (at this moment Admin-Desktop for testing purposes)

Why this queue is not working? Is this a missing setting in RPM or is there something wrong on the branch-office side?

Hopefully someone can help me.

Kind regards Matthias

 

RPM-Log:
103,Info,'2018-02-22 11:01:09.487,Closing LPD socket for 1468
107,Info,'2018-02-22 11:01:09.487,Transfer is done for 1468
112,Info,'2018-02-22 11:01:09.471,Client closed connection on 1468
133,Info,'2018-02-22 11:01:09.471,Accepted connection from on port 35220
197,Info,'2018-02-22 11:00:00.015,Remove job 14362
197,Info,'2018-02-22 10:59:00.013,Remove job 14361
197,Info,'2018-02-22 10:57:00.007,Remove job 14360
197,Info,'2018-02-22 10:56:00.004,Remove job 14359
197,Info,'2018-02-22 10:55:00.017,Remove job 14358
197,Info,'2018-02-22 10:54:00.015,Remove job 14357
197,Info,'2018-02-22 10:53:00.012,Remove job 14356
104,Info,'2018-02-22 10:52:00.962,"Received data on socket 1428, 5 bytes"
133,Info,'2018-02-22 10:51:57.415,Accepted connection from on port 59057
197,Info,'2018-02-22 10:51:00.007,Remove job 14355
197,Info,'2018-02-22 10:50:00.004,Remove job 14354
197,Info,'2018-02-22 10:49:00.017,Remove job 14353
197,Info,'2018-02-22 10:48:00.014,Remove job 14352
103,Info,'2018-02-22 10:46:07.212,Closing LPD socket for 1112
107,Info,'2018-02-22 10:46:07.212,Transfer is done for 1112
112,Info,'2018-02-22 10:46:07.212,Client closed connection on 1112
642,Error,'2018-02-22 10:46:07.212,"Network error on close: (10053, Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer abgebrochen.)"
113,Info,'2018-02-22 10:45:48.258,Acknowledge for 1112
118,Info,'2018-02-22 10:45:48.258,Receive print job on queue
186,Info,'2018-02-22 10:45:48.258,Verifying queue
124,Info,'2018-02-22 10:45:48.243,Command 2 text
104,Info,'2018-02-22 10:45:48.243,"Received data on socket 1112, 13 bytes"
133,Info,'2018-02-22 10:45:48.243,Accepted connection from on port 15535
103,Info,'2018-02-22 10:45:48.227,Closing LPD socket for 1356
107,Info,'2018-02-22 10:45:48.211,Transfer is done for 1356
112,Info,'2018-02-22 10:45:48.211,Client closed connection on 1356
642,Error,'2018-02-22 10:45:48.211,"Network error on close: (10053, Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer abgebrochen.)"
103,Info,'2018-02-22 10:45:48.211,Closing LPD socket for 1088
107,Info,'2018-02-22 10:45:48.211,Transfer is done for 1088
112,Info,'2018-02-22 10:45:48.211,Client closed connection on 1088
642,Error,'2018-02-22 10:45:48.211,"Network error on close: (10053, Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer abgebrochen.)"
113,Info,'2018-02-22 10:45:29.226,Acknowledge for 1088
118,Info,'2018-02-22 10:45:29.226,Receive print job on queue
186,Info,'2018-02-22 10:45:29.226,Verifying queue
124,Info,'2018-02-22 10:45:29.226,Command 2 text
104,Info,'2018-02-22 10:45:29.226,"Received data on socket 1088, 13 bytes"
113,Info,'2018-02-22 10:45:29.226,Acknowledge for 1356
118,Info,'2018-02-22 10:45:29.226,Receive print job on queue
186,Info,'2018-02-22 10:45:29.226,Verifying queue
124,Info,'2018-02-22 10:45:29.226,Command 2 text
104,Info,'2018-02-22 10:45:29.226,"Received data on socket 1356, 13 bytes"
133,Info,'2018-02-22 10:45:29.226,Accepted connection from on port 37548
133,Info,'2018-02-22 10:45:29.226,Accepted connection from on port 59561

Leroy Powell
Error 10053 is very generic

Error 10053 is very generic and it is nearly always impossible to determine a network issue by this error alone. All it means is that the connection was closed by the print client. However, the print client may have closed the connection for very valid reasons.

For instance, if the client opens a connection and issues a request to print a job, and it does not get an acknowledgement back, it would close the connection. However, RPM definitely sends an acknowledgement in that case, so it might mean that the route back to the client is failing somehow and could indicate the VPN connection is not configured correctly for two-way communication.