BESClient postresults.exe error

Usage and Config Platform
1

I am facing issue to one client where i did new agent install , but getting below error message even though firewall is disable and i can telnet the application server port.

Client : windows 2012R2

Error posting report to: ‘http: // <>:52311/cgi-bin/bfenterprise/PostResults.exe’ (General transport failure.
SOCKET RECEIVE (winsock error -10))

2

Winsock 10 according to this article:

http://www-01.ibm.com/support/docview.wss?uid=swg21505977

indicates a problem receiving something (like a response or http confirmation from the parent relay).

This operation is the client posting a report to the parent relay.

Is anything blocking b-directional communication between the client and parent relay on the network for TCP on port 52311?

  • Firewall (network or host based on either end)?
  • Content filtering proxy between client and parent relay?
  • Is the relay currently overloaded with clients (network connections)?
  • Quality of the link, is the line reduced in bandwidth or jittery?

Try putting a Wireshark on the endpoints and see if a networking issue can be determined.

Try restarting the BES services on the relay (BES Relay and then BES Client) to see if a service restart makes the parent relay more responsive.

3

As the error is a SOCKET_RECEIVE it was able to connect to the socket on the relay, and to send something but got an error receiving from the relay through the socket ( or you would have gotten a SOCKET_CONNECT or SOCKET_SEND ).

I’d check the BESRelay.log on this relay and see if there are some issues with sockets occurring.

4

Hi, I am getting below error in BESrelay.log

Tue, 03 May 2016 11:12:58 -0500 - /cgi-bin/bfenterprise/PostResults.exe (9700) - Uncaught exception in plugin PostResults with client IP-address: Socket Error: Windows Error 0x2746: An existing connection was forcibly closed by the remote host.

5

can you please try to open below url from the client machine browser.

http://relay_dns_name:52311/rd

note: repalce relay_dns_name with the relay name which client is currently reporting too.

check if complete page loading or not?

6

yes , mentioned link is opened correctly.

7

This is suggesting that perhaps the relay is having some problems with sockets or is overused. I’d suggest opening a PMR so someone can help from support and get more details

8

Yes opened PMR for this. Thanks

9

Do you have any other server in same subnet of problematic client which is reporting fine in IEM console? we need to compare “route print” command output from problematic and working endpoint. Looks like either you have teaming or NAT ip address on problematic server.

11

No NAT or teaming found , and route print is almost same on other server which is working fine.

12

@mail2vij did you found any solution for this post

13

found firewall issue into it