Troubleshooting the Monitor

In addition to the recommendations listed below, Administrators can use the Message Log and Exception Reports features to troubleshoot the Monitor. See Message Log and Exception Reports.

Problem	Recommendation
When you press F5 to refresh the browser window, you are required to log in to the Monitor.	Enable JavaScript in your browser.
You receive a network communication error when you try to log in to the Monitor.	Start the Monitor. See Start the Monitor.
After upgrading to the latest version of Adobe Flash Player you continue to receive instructions to upgrade Adobe Flash Player.	Verify that the installed version Adobe Flash Player is supported by your operating system. The Monitor is backwards compatible with version 10 of Adobe Flash Player. To determine the correct version, see http://www.adobe.com/products/flashplayer/systemreqs/.
The Monitor is unable to start monitoring a SQL Anywhere database resource.	Verify that the resource's password verification functions and login procedures allow the user sa_monitor_user to connect to the resource.
You are not receiving any alert emails.	Verify that the Monitor is properly configured to send emails and send a test email. See Enable the Monitor to send alert emails. Verify that the alert emails from the Monitor are not being blocked by a virus scanner. See xp_startsmtp system procedure.
The number of unscheduled requests reported by the Monitor appears to be less than the actual number of unscheduled requests.	When collecting metrics about the number of unscheduled requests, the Monitor executes query on the resource. This query could be an unscheduled request. Unscheduled queries are processed sequentially as they arrive. Therefore, if there are unscheduled requests when the Monitor attempts to execute its query, then this query must wait for the existing unscheduled requests to complete before it can execute. As a result, when the Monitor collects the number of unscheduled requests, this number does not include the unscheduled requests that existed between the time when the Monitor issued its query and the query executed.
You are not receiving alerts when the database disk space surpasses the specified threshold.	Between Monitor collection intervals, it is possible for a database to exceed the specified disk space alert threshold and the amount of space available. In such a case, the database would stop responding before the Monitor could collect the disk usage metrics and issue an alert. If your database grows quickly, set the disk space alert threshold to a higher number so that you can receive an alert before the database runs out of space. See Alert thresholds.
You can't see the Administration window when you are logged into the Monitor.	You must be logged in to the Monitor as an administrator to have access to the Administration window. See Monitor users.
You uninstalled the Monitor before migrating your data and now you have lost your resources and metric data.	Uninstalling the Monitor removes the application, as well as the resources and collected metrics. When upgrading, you need to install the new version of the Monitor, migrate your data, and then uninstall the old version. However, if you regularly backed up your Monitor, you can use the Migrate utility to migrate the data from the backed up files to the new version of the Monitor. See Back up the Monitor.
When monitoring a database that is part of database mirroring system, you receive errors about not being able to modify a read-only database.	In the Administration window, select the mirrored database resource and click Edit. In the Other field, type NODE=PRIMARY. See NodeType (NODE) connection parameter.

Discuss this page in DocCommentXchange.