---

Back to index

AlertSite Status Codes

You have landed on a page that is obsolete. Please go to AlertSite Status Codes for the most up to date list of Error Codes.

AlertSite Status Codes, displayed in the Dashboard, Status tab, and Reports, indicate that your monitored device was experiencing some kind of error condition. Every failed check is retried to verify that the device really is in error. Some monitoring types also perform remote verification from an alternate location. See Monitor-Verify-Notify for more information on monitoring types and what functions they perform.

The error codes are categorized in the table below. Click on the specific code for more information about the error.

General Status Codes:	Browser Timeouts (Transaction devices):
0 - Site responded normally to all tests 1 - TCP connection failed 2 - No response from server -- test timed out 3 - Invalid response from server 5 - Keyword verification error within returned page 6 - No response from server 7 - HTTP error from web server 8 - Web site is redirected (warning) 51 - Unable to resolve IP address 99 - Unable to ping from location	80 - Browser event timeout encountered 82 - Page took too long to load 83 - Firefox event notification did not occur 84 - Page location did not change when expected 85 - Expected page updates did not occur 86 - Network activity did not stop 89 - Internal Browser timeout
Notification and Verification Status:	Other Transaction Errors:
70 - Remote verification did not detect an error. No error alert is generated 71 - Remote verification has confirmed an error. Alert is generated 72 - Remote verification response was not received. Alert is generated 73 - Remote verification response was invalid. Alert is generated 79 - Remote verification was unavailable. No alert is generated 98 - Notification (alert) was generated	81 - Maximum transaction time was exceeded 90 - Unexpected processing exception occurred 91 - Minimum match score not met 92 - Maximum number of skipped events exceeded 93 - Missing instruction for dialog prompt 94 - Maximum transaction steps exceeded 95 - Unable to monitor from chosen station 96 - Unable to parse transaction XML 97 - Response does not contain expected target page item
Fullpage Monitoring Errors:	SLA, Round Robin or Rotated Locations Code:
70XX - Page object error where XX corresponds to General Status Codes 7121 - Object length changed 7122 - Missing object 7123 - New object found 7130 - No fullpage objects found 7202 - Fullpage Timeout	9095 - Unable to run test from chosen monitoring location
ServerAgent Errors:	Security Device Errors:
4030 - Warning threshold exceeded for monitored item 4040 - Error threshold exceeded for monitored item 4050 - Reported results were not received when expected	HIGH - High-risk Vulnerabilities detected MEDIUM - Medium-risk Vulnerabilities detected INFO - Informational messages

General Status Codes

0 - Site responded normally to all tests

Your test ran successfully. Note: The displayed console status is adjusted to 0 when remote verification of an error returns success. The status shown in reports is not similarly adjusted.

1 - TCP connection failed

We were unable to establish an internet connection to your site. You will see this message appear when your firewall is blocking traffic to your site, or if your site is just not accepting any TCP/IP traffic. You can check the following:
   •  Your site may be overloaded.
   •  Your site may not be running.
   •  A firewall may be preventing connections to your site.

2 - No response from server -- test timed out

There was no response from your server within your selected timeout interval. This usually indicates that your system is very busy and experiencing a slow down. If things look normal, you may just need to increase your timeout interval.

3 - Invalid response from server

This is a protocol error. The server did not provide an appropriate response. This generally indicates a system problem with your server.

5 - Keyword verification error within returned page

Keyword verification looks for a particular keyword or phrase within the retrieved page and raises an alert if it finds (or cannot find, depending on settings) the word(s). This error generally indicates that your site is not responding as expected and should be immediately checked. If everything looks OK, you should review the keyword(s) that you have specified for the page.

6 - No response from server

While attempting to communicate with your site, we received no response at all. This usually indicates that your site is down.

7 - HTTP error from web server

While communicating with your site, we received an HTTP status code from your web server that indicates some unexpected event. To see more information about these codes, go to HTTP Status Codes help.

8 - Web site is redirected (warning)

Many web pages are redirected to an alternate page or to another site altogether. In this case, however, you specified that AlertSite should Report redirects (HTTP 301/302) as errors and your site is now redirecting users to a different page. You should find out why the redirect is happening. If this is OK, you can turn off the option to report these as errors.

51 - Unable to resolve IP address

DNS resolution failed. You've selected to Resolve DNS for every test and our DNS servers failed to resolve your domain name to an IP address.

99 - Unable to ping from location

One of your AlertSite monitoring locations is experiencing temporary network issues and is unable to run ping tests. If the problem persists, please contact your AlertSite Performance Advisor.

Back to top

Browser Timeouts (Transaction devices)

The following transaction status codes pertain to browser timeouts.

80 - Browser event timeout encountered

While running a multi-step transaction on your site, a non-network event timeout interval was reached. This message appears if browser-related events are not received when expected and the transaction step has timed out. Such timeouts may occur while waiting for:
   •  the overall page to load.
   •  an expected URL location change.
   •  a response to a replayed browser event.
   •  start or completion of dynamic page content changes.
Event timeouts could indicate significant site content changes. You should download and replay your transaction to examine the results. You should also review your transaction's step timeout setting on the AlertSite Edit Transaction page. If your site's content has changed significantly, you may need to re-record your transaction.

82 - Page took too long to load

While running a multi-step transaction, the event time limit was exceeded. Firefox informs DéjàClick about Page Load progress with different notifications, for example, base page has been transferred, all objects have been transferred, Ajax activity is in progress, and so on. DéjàClick compares these notifications with those encountered during recording in order to determine if the page has finished loading. If Firefox does not notify DéjàClick that the page load was complete and the configured Browser timeout and HTTP step timeout thresholds expired, DéjàClick reports that the page took too long to load.

83 - Firefox event notification did not occur

While running a multi-step transaction on your site, an event was injected into the browser, but we could not verify that the event was successfully replayed. This could indicate significant site content changes. You should download and replay your transaction to examine the results. You should also review your transaction's step timeout setting on the AlertSite Manage Transaction page. If your site's content has changed significantly, you may need to re-record your transaction.

84 - Page location did not change when expected

While running a multi-step transaction on your site, a location/URL change was expected but did not occur. This could indicate significant site content changes. You should download and replay your transaction to examine the results. You should also review your transaction's timeout settings on the AlertSite Manage Transaction page. If your site's content has changed significantly, you may need to re-record your transaction.

85 - Expected page updates did not occur

While running a multi-step transaction on your site, dynamic page changes (e.g., through AJAX, JavaScript, etc.) were expected but did not occur. This could indicate significant site content changes. You should download and replay your transaction to examine the results. You should also review your transaction's timeout settings on the AlertSite Manage Transaction page. If your site's content has changed significantly, you may need to re-record your transaction.

86 - Network activity did not stop

While running a multi-step transaction on your site, network activity did not stop after the page was loaded. This could indicate significant site content changes. You should download and replay your transaction to examine the results. You should also review your transaction's timeout settings on the AlertSite Manage Transaction page. If your site's content has changed significantly, you may need to re-record your transaction.

89 - Internal Browser timeout

While running a multi-step transaction on your site, we encountered an internal browser timeout. Please report this incident to your AlertSite Performance Advisor.

Back to top

Notification and Verification Status

The following codes are displayed to show verify and notification status.

70 - Remote verification did not detect an error. No alert is generated

An error was detected at your site, but the test was successful from a different internet monitoring location. This generally indicates that the problem is due to isolated internet traffic problems, rather than anything at your site.

71 - Remote verification has confirmed an error. Alert is generated

An error was detected at your site and the same test is also failing from different internet monitoring location(s). This generally indicates that there is a problem at your site. This error message will include another status code indicating the precise problem.

72 - Remote verification response was not received. Alert is generated

An error was detected at your site but AlertSite was not able to perform the same test from a different internet monitoring location. This generally indicates a problem with internet traffic. To see if there is a known problem, you can contact your AlertSite Performance Advisor or check out the Network Notifications area of the Alertsite User Forum by clicking here.

73 - Remote verification response was invalid. Alert is generated

An error was detected at your site but AlertSite was not able to perform the same test from a different internet monitoring location. This generally indicates a problem with internet traffic. To see if there is a known problem, you can contact your AlertSite Performance Advisor or check out the Network Notifications area of the Alertsite User Forum by clicking here.

79 - Remote verification was unavailable. No alert is generated

An error was detected at your site but AlertSite was not able to perform the same test from a different internet monitoring location. This generally indicates a problem with internet traffic. To see if there is a known problem, you can contact your AlertSite Performance Advisor or check out the Network Notifications area of the Alertsite User Forum by clicking here.

98 - Notification (alert) was generated

This status code is used to record the fact that an alert was actually sent to one of your registered notifiers.

Back to top

Other Transaction Errors

The following are additional transaction status codes.

81 - Maximum transaction time was exceeded

While running a multi-step transaction on your site, the overall time limit was exceeded. You may need to re-record your transaction with fewer actions/events.

90 - Unexpected processing exception occurred

While running a multi-step transaction on your site, an unexpected processing exception has occurred. Please report this incident to your AlertSite Performance Advisor.

91 - Minimum match score not met

While running a multi-step transaction on your site, the minimum match score you specified for use when searching for target page elements was not met. Generally, low match scores may indicate significant site content changes. You should download and replay your transaction to examine the results. If the results are OK, you can edit or disable the minimum match score in the recorder using the Script or Event Properties panels and re-upload your transaction. If your site's content has changed significantly, you may need to re-record your transaction.

92 - Maximum number of skipped events exceeded

While running a multi-step transaction on your site, the number of skipped events encountered has reached the limit you specified. This may indicate significant site content changes. You should download and replay your transaction to examine the results. If the results are OK, you can edit or disable the maximum number of skipped events in the recorder using the Script Properties panel and re-upload your transaction. If your site's content has changed significantly, you may need to re-record your transaction.

93 - Missing instruction for dialog prompt

While running a multi-step transaction on your site, a dialog prompt was encountered for which there were no instructions available to use as a response. This may indicate that your site has encountered an error condition or it has changed. You should download and replay your transaction to examine results. If the new dialog prompt is OK, you may add or modify instructions for handling the dialog in the recorder using the Event Properties panel and re-upload your transaction. You may also re-record your transaction to add the missing prompt instructions automatically.

94 - Maximum transaction steps exceeded

While running a multi-step transaction on your site, we used more steps than are allowed by your billing plan. You can either record a new transaction or contact your Performance Advisor to purchase more steps.

95 - Unable to monitor from chosen station

While attempting to run a multi-step transaction on your site, one of your monitoring locations was temporarily out of resources. This condition should clear up shortly. This status does not indicate an error with your transaction.

96 - Unable to parse transaction XML

An internal system error has prevented us from testing a multi-step business transaction at your site. Please contact your AlertSite Performance Advisor for assistance.

97 - Response does not contain expected target page item

This can be interpreted similarly to a keyword error (Status 5). The difference is, rather than a keyword/phrase not being found, the target page item (such as a button, image, link, or frameset) that AlertSite expected to find could not be found in the content.

Back to top

Fullpage Monitoring Errors

Additionally, devices with optional Fullpage Monitoring may see alert statuses in their Detail Report or Fullpage Report with 4 digit status codes beginning with "7".

70XX - Page object error where XX corresponds to the codes above

Certain status codes have the format 70XX. The 70 indicates it is an error that occurred while loading a page object (image, javascript, css, etc.). The last two digits (XX) are interpreted using the General Status Codes. For example, 7002 would indicate a timeout error while loading an image.

7121 - Object length changed

You have chosen to be notified if any object on your internet page has changed size.

7122 - Missing object

You have chosen to be notified if any object on your internet page has been removed since the last test.

7123 - New object found

You have chosen to be notified if any object has been added to your internet page.

7130 - No fullpage objects found

You have chosen Fullpage monitoring for your site, but our tests indicate there are no additional objects (image, javascript, css, etc.) to be retrieved for the page.

7202 - Fullpage Timeout

While retrieving the objects for your Fullpage Monitoring test, the specified timeout for the entire page was exceeded.

SLA, Round Robin or Rotated Locations Code

The following code applies to devices set to SLA (MultiPOP) or Round Robin Monitoring Type, or if rotated locations are set.

9095 - Unable to run test from chosen monitoring location

One of your AlertSite monitoring locations is not available but should be shortly. If the problem persists, please contact your AlertSite Performance Advisor.

Back to top

ServerAgent Errors

ServerAgent produces its own unique set of status codes to alert users to potential issues requiring attention.

4030 - Warning threshold exceeded for monitored item

One of the items being measured by your ServerAgent has passed the level you specified as a Warning.

4040 - Error threshold exceeded for monitored item

One of the items being measured by your ServerAgent has passed the level you specified as an Error.

4050 - Reported results were not received when expected

Your ServerAgent has been set up with a specified Reporting Interval, such as 5 minutes. This error indicates that more time has passed than your Reporting Interval and your ServerAgent has not sent any data to AlertSite. Most likely, your ServerAgent is not running and should be restarted.

Back to top

Security Device Errors

Security Devices produce three types of results.

HIGH - High-risk Vulnerabilities detected

High-risk vulnerabilities represent the most severe security threats. High-risk vulnerabilities provide remote intruders with remote root or remote administrator capabilities. With this level of vulnerability, attackers can compromise the entire host. High-risk includes vulnerabilities that provide remote hackers full file-system read and write capabilities, remote execution of commands as a root or administrator user. The presence of back doors and Trojan horses also qualify as High-risk vulnerabilities. High-risk vulnerabilities also include remote user capabilities and/or partial access to file-systems.

MEDIUM - Medium-risk Vulnerabilities detected

Medium-risk vulnerabilities represent less critical security threats. Limited exploit of read, directory browsing and Denial of Service (DoS). Medium-risk vulnerabilities provide hackers with access to specific information stored on the host, including security settings. This level of vulnerabilities could result in potential misuse of the host by intruders. Examples of Medium-risk vulnerabilities include partial disclosure of file contents, access to certain files on the host, directory browsing, disclosure of filtering rules and security mechanisms, susceptibility to denial of service (DoS) attacks, and unauthorized use of services (for example, mail relaying).

INFO - Informational messages

Informational messages are scan results that do not represent an immediate threat. Informational messages contain information can be obtained by attackers regarding the specific host configuration. This information may include a list of responsive ports as well as the precise versions of responding services. With this information, attackers could research potential attacks to try against the host.

Back to top
Back to index