AdoMonitor v1.0.411 | Size: 6.01MB
Database related errors for IIS web sites has up until now been extremely difficult, if not impossible, to monitor and trace. Corrupted databases, old ODBC connection strings and connection pool overloads are just some of the errors that frequently result in IIS web server errors.
A single corrupted database is basically the only thing it takes to cause a massive CPU usage overload and/or memory consumption by the IIS web server.
With the launch of AdoMonitor this will all be a thing of the past.
AdoMonitor is the only tool built for real time monitoring of ADO-related errors. Besides these kinds of errors, it also displays connection parameters, SQL queries, descriptions, and other ADO/ODBC-related information, all in real time. It also features the possibility of reviewing all of this information from log files.
AdoMonitor detects database related errors and can execute various tasks to recover and stabilize your IIS web server.
A: AdoMonitor displays errors that occur when calling ADO functions from e.g. ASP. The monitored data can be observed in real time, and it can be logged. AdoMonitor also has the ability to perform certain actions (restart IIS, send an email, execute some commands) if some error appears frequently.
A: As ASP scripts are executed, they usually connect to some databases. You can see all the connection errors, data querying, updating to and from the databases. You can also see all regular task executions.
A: You usually access ODBC through ADO (e.g. in ASP). In that case AdoMonitor also shows all ODBC errors.
A: AdoMonitor connects to IIS and streams the information about ADO calls to the AdoMonitor service. AdoMonitor service logs this data and/or sends it to AdoMonitor windows application.
A: Yes. AdoMonitor can detect the occurrence of a particular error or errors. Upon finding these errors, AdoMonitor can inform you via email.
A:If you see "Too Many Client Tasks" error occurring frequently, then this is the cause of your problem. Also, if you see Connection.Open function with different parameters producing an error frequently, then the cause of the trouble might be that a database server became unavailable, or some other system error occurred.
A:If you have an online enterprise application, database unavailability or a database access error may be the cause of displaying a debug information dialog box on a web page, showing the implementation details of your system. With AdoMonitor you can tend to zero-tolerance for errors and never experience the same situation again.
A:You should set the AdoMonitor to watch only "Too many client tasks" error. You should also set it to restart IIS if this error occurs frequently (e.g. 10 times in 45 seconds). In this way, when IIS gets blocked by this error it is restarted and continues to work normally.
