problem logging to sql

iis5_rulez · Post by **iis5_rulez** » Fri Dec 05, 2003 4:04 am

Hello,

we've setup hostmonitor to log all tests to a sql db. but since a few days we see errors in the hostmon application. unfortunatly the errormessage is too long to be displayed in the application and the error doesnt seem to be logged in the hostmonitor "syslog". the failure is probably due to a config error in a test, but since we've over 4000 tests it's not an option to check them all. is there anyway to increase logging so we can see the full error message and hopefully identify the error source?

since it's a odbc error we've already turned on odbc logging. but nothing yet so far...

KS-Soft · Post by **KS-Soft** » Fri Dec 05, 2003 1:11 pm

we see errors in the hostmon application.

Where did you see that error? In the popup window? HostMonitor cannot log this kind of errors, its unexpected errror

You should send screen shot to us... If it appears again, please, send screen shot
BTW: what version of HostMonitor do you use?

Regards
Alex

iis5_rulez · Post by **iis5_rulez** » Mon Dec 08, 2003 6:53 am

we are using 4.10. the error appears in the bottom of the hostmonitor application.

www.datacrash.net/rob/ss_067.jpg

KS-Soft · Post by **KS-Soft** » Mon Dec 08, 2003 2:05 pm

I found information about this problem on www.microsoft.com
Microsoft says "To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000".
Article information available at http://support.microsoft.com/default.as ... -US;318606

Regards
Alex

Marcus · Post by **Marcus** » Tue Dec 09, 2003 4:56 am

The problem here is not SQL or service packs or HostMonitor.

There is one or more test configurations that are not correct (we depend a great deal on comment lines for logging and reporting). The problem however is that you have to check all tests before you know what's wrong and you can overlook the error (otherwise you wouldn't make it in the first place

). It could be as simple as placing a comma instead of a dot.

If hostmonitor can display this error in its status bar, it must be possible to create a log entry in the system log, which states the test name and the error code returned from the odbc driver.

It will save a lot of time searching for this human made error.

KS-Soft · Post by **KS-Soft** » Tue Dec 09, 2003 10:06 pm

There is update at www.ks-soft.net/download/hm415.zip
There are 2 modifications:

1) HostMonitor records information about ODBC error into <system log> when ODBC Query fails (if "record info about failed acions" option enabled)

2) if there are more than 20 consecutive ODBC errors occur, HostMonitor suspends ODBC logging for 10 min. If you correct problem (e.g. restart SQL Server or fix error in SQL Query), you may resume ODBC logging manually using Options dialog (just open dialog and click "save" button).

Regards
Alex

Marcus · Post by **Marcus** » Wed Dec 10, 2003 4:39 am

It worked, thanks again for the great support, but .....

The testname was not included in the logging, which resulted in me scrolling through 4000+ test to find the right time. So if the testname could be included, it would be even better.

And with consecutive you mean that 19 failures, 1 ok, 19 failures, 1 ok wil not stop HostMonitor??

KS-Soft · Post by **KS-Soft** » Wed Dec 10, 2003 1:29 pm

Ok, now you will see name of the test. Update available at the same place.

And with consecutive you mean that 19 failures, 1 ok, 19 failures, 1 ok wil not stop HostMonitor??

Correct.

Regards
Alex

Marcus · Post by **Marcus** » Thu Dec 11, 2003 2:36 am

It works perfectly. Thanks again!