0
|
Site responded normally to all tests
Site responded normally to all tests
Your test has run successfully. Congratulations.
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
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
|
Test timed out
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 will need to increase your timeout interval.
|
3
|
Invalid response from server
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
|
Validation failed
Validation failed
Your monitoring test requires a specific text keyword, image, or
JavaScript result that was not found. This error generally indicates
that your site is not responding with the expected page content and
should be checked. If everything looks OK, you should review the
validation(s) that you have specified for the page.
|
6
|
No response from server
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
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, click here
|
8
|
Web site is redirected (warning)
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.
|
9
|
Ping failed (site is not responding)
Ping failed (site is not responding)
After your site has returned a status code of 1 or 2, we will perform
a "last-ditch" ping request if you have selected that option. "Ping"
is a low-level test to determine if your server is "reachable" and
the results indicate that there is a problem connecting to your site.
|
20
|
Selenium Specific Error
Selenium Specific Error
Selenium script finished with an exit code other than 0. Depending
on how your script is designed, this could mean that some specific
text or element was not found on a page, a page could not be loaded,
or an assertion failed. Look for any errors in the Selenium run log.
If everything looks OK, review your Selenium script to make sure it
works as intended.
|
21
|
Selenium Startup Error
Selenium Startup Error
Selenium script could not be started. Possible reasons:
- The JAR file is not runnable (does not contain a manifest with
Main-Class).
- The JAR file does not have Selenium libraries or other required
libraries embedded in it.
- The script uses an unsupported browser. AlertSite only supports
Firefox and Chrome browsers. Selenium 1.0 and Selenium Grid are not
supported.
|
51
|
Unable to resolve IP address
|
99
|
Unable to ping from location
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.
|
80
|
Browser event timeout encountered
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 will need to re-record
your transaction.
|
82
|
Page took too long to load
Page took too long to load
While running a multi-step transaction, the event time limit
was exceeded. The browser informs DejaClick 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. DejaClick compares these notifications
with those encountered during recording in order to determine if
the page has finished loading. If the browser does not notify DejaClick
that the page load was complete, then DejaClick will report that
the page took too long to load.
|
83
|
Firefox event notification did not occur
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 will
need to re-record your transaction.
|
84
|
Page location did not change when expected
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 will need to re-record your transaction.
|
85
|
Expected page updates did not occur
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 will need to
re-record your transaction.
|
86
|
Network activity did not stop
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 will need to re-record your transaction.
|
89
|
Internal Browser timeout
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.
|
81
|
Maximum transaction time was exceeded
Maximum transaction time was exceeded
While running a multi-step transaction on your site, the overall
time limit was exceeded. You will need to re-record your transaction
with fewer actions/events.
|
90
|
Unexpected processing exception occurred
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
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 will need to re-record your transaction.
|
92
|
Maximum number of skipped events exceeded
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 will need to re-record your transaction.
|
93
|
Missing instruction for dialog prompt
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 will need to add or modify instructions for handling the dialog in the
recorder using the Event Properties panel and re-upload your transaction.
You will need to re-record your transaction to add the missing prompt
instructions automatically.
|
94
|
Maximum transaction steps exceeded
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
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
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
|
Target page element was not found
Target page element was not found
The target page element (such as a button, textbox, image, link, or
iframe) could not be found in the content. For a TrueScreen event,
this could also mean that the target element was present but the
target coordinates were not within the visible bounds of the page
(missing or out-of-bounds). This error generally indicates that
your site is not responding with the expected page content. If
your site's content has changed significantly, you will need to
re-record your transaction.
|
988
|
Unplanned Maintenance
Unplanned Maintenance
A keyword was detected that indicates the monitored site is in
a maintenance state.
|
HIGH
|
High-risk Vulnerabilities detected
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 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
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.
|