These are common errors and explanations of the possible causes that may be seen in the GNW result data.
This information can be downloaded as a Word document: GNWErrorDefinitions.doc
HTTP Error: Content Check - Accept String Not Found
- Content checking errors are common for online applications. This indicates that the web server is accessible but not serving the correct content.
- This can occur for 2 reasons, the application is failing or the content has changed due to a software release.
The web server is experiencing an error and producing a page that displays the error. A common error in the ”MyCompany” application is text related to Web Logic errors. Since the web server is just producing a page based on another error, the GNW agent software sees the “200 OK” message but the content is not correct.
In some cases, this can be due to software updates, and the Web Logic session has not formed properly. For the “MyCompany” application, this can be determined by looking at the GNW data and noticing that the transaction stops at step 7, the “Account Summary” page.
- Manually checking the application will reveal that there is either a server error occurring, or the web site has changed in some way and the script needs to be remapped.
HTTP Error : HTML parsing failed
- During the redirect process, the GNW system examines the data received from a web server. The agent is looking at the server response to see what URL is being redirected to. If the page is malformed, the agent will not be able to find the target URL for a redirect.
HTTP Error : Unable to Find the URL in Relocation
- For Company X, this error mainly affects transactions where there is a redirect (relocation) step. The GNW agent looks at the URL to find the next URL, but that URL must also exactly match the next URL in the transaction script. In other words, if the current URL in the transaction set is redirecting and the redirect target is not the same as the next step; the transaction engine will generate an error.
HTTP Error: unable to detect URLs
- This error is related to full page downloads. If the page received from the web server has no URLs, there is a problem, and the full page agent software records this error. There were no images or other URLs in the downloaded page. Therefore, the full page agent software could not download the images. This error is very similar to content checking, the agent is raising an error because the expected content, the content URLs is missing.
Local OS : Operation Not Permitted
- This is a rare error that occurs more frequently in the modem dialup data. This error indicates that a local (agent level) procedure call failed for some reason. This error is not related to the target URL.
Network : Connection Reset by Peer
- During the process of servicing a request, the web server terminated the connection to the GNW agent. The web server, for some reason, is appropriating the connection. This can occur if the server is rebooting, and the server is terminating all connections, or for some reason that server decided to service some other connection and this one had to be sacrificed.
- If this error appears with regularity, it could be an indicator that the web server is having trouble handling its traffic and it is recycling connections frequently. Users will experience partial pages or broken images.
- This error can also indicate that the network connection is set in half duplex mode and the server is having problems sending data back to the client.
Network : Failed to Connect - Connection Timed Out
- The GNW agent initiates a TCP/IP handshake with every connection. In this case, the initial attempt to establish a socket has failed because the server was unable to acknowledge the initial connection attempt. This timeout is relatively short (7 seconds) because the agent would expect the server to be able to do this operation in milliseconds.
- This error would be strongly related to the target web server – but there could be problems with intervening transport. A common cause of this error is that the ACK packets are being routed or sent to another location due to asymmetric routes and the reverse route is broken. Alternately, the load balancer system employed by the web server may be having problems routing the inbound request to a valid web server.
The GNW agent is able to connect to the load balancer but the actual socket routes internally to a physical IP address and the server at the target address is not responding. For the MyCompany transaction, this could indicate the load balancer is having problems routing to one of the 5 servers supporting www.myaccount.compx.com.
Network : Network is Unreachable
- The unreachable network error is an indicator that there is no route to the target device. Typically, if a server is down and the network interface is not on the network, the router will not publish the IP address of the server. This is the primary cause of this error.
- The secondary cause of this error is a general routing issue with a route that is in error.
Network : Transport Endpoint is Not Connected
- The error is related to the routing system stating that the target server is not connected, because there is no route at the node. This is usually seen when modem dialups have failed, or when VPN tunneling nodes have not connected.
Socket Error: Connection timed out while reading data (60 Seconds)
- This is a common error which indicates that GNW has been able to connect to the web server but the web server did not return data within the required 60 second window. If the URL being accessed is a dynamic URL, such as a Web Logic URL, this could be a Web Logic related error.
- It is also possible that this is related to a server issue, in which the server can accept connections, but the reverse path is broken, and the server cannot deliver data back to the requesting client.
SSL Error: 5 sec timeout
- If the target URL is an SSL encrypted URL, the server will be given 5 seconds to send the certificate for negotiation. If the server cannot send the certificate, the GNW agent will record a 5 seconds time out. When getting a certificate, the server should be able to respond within 0.5 seconds.
- If the server cannot send the certificate in this amount of time, there can be several causes:
- The server is overloaded and cannot send the certificate.
- The certificate is outdated. SSLv1 (Version 1) certificates are larger and slower than SSLv3 certificates.
- The cipher used in the certificate may be a slow cipher. RD4-MD5 is a very common cipher that performs very well.