HM 5.12 on Windows XP with SP2. I want to monitor Microsoft SQL 2000 and Interbase Server 5.0.
In folder c:\windows\system32 these DLLs exists:
ntwdblib.dll, ver 2000.80.194.0
gds32.dll, ver 5.0.0.627
Login/Username and Password fields non blank.
After run test "Check MS SQL server" and "Check Interbase server" HM status "No answer".
Why? What is wrong?
MSSQL & Interbase monitor
Login/Username and Password fields non blank
Yes, username and password is Ok (three times checked). If I change these fields on wrong the status also "No answer".Does "non blank" means correct username and password? Or just some text?
For Interbase format is:
SYSDBA
password
For MS SQL format is:
DOMAIN\User
password
I checked HostMonitor's code, everything looks fine. But probably it needs better diagnostics for Database tests.
Could you check configuration on server side? Have you configured correct network protocol for Interbase server (TCP, NetBEUI...)?
BTW: How about ODBC query test method? Does it works with your servers?
Regards
Alex
Could you check configuration on server side? Have you configured correct network protocol for Interbase server (TCP, NetBEUI...)?
BTW: How about ODBC query test method? Does it works with your servers?
Regards
Alex
What I should check on server side? Access rights?
Yes, for Interbase connectivity TCP is correct protocol for me. On Hostmonitor's PC I don't have Interbase client, gds32.dll only. In test "check Intebase server" I try connect as SYSDBA. It's full rights.
About MS SQL. On Hostmonitor's PC I have Enterprise Manager and I can connect to my database and administrate this.
About ODBC. I have create user DSN with SQL Server driver, connect with Windows NT authentication and check configuration by pressing "Test Data Source..." button. Ok, test completed sucessfully.
HostMonitor's ODBC Query return status "No answer" and reply "Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'DOMAIN\MACHINEACCOUNT$'. If I try with login/password fields is blank or anyone then reply same: Login failed for user 'DOMAIN\MACHINEACCOUNT$'. Why MACHINEACCOUNT used instead of current user account or that is specified in a field login?![:(](./images/smilies/icon_frown.gif)
Yes, for Interbase connectivity TCP is correct protocol for me. On Hostmonitor's PC I don't have Interbase client, gds32.dll only. In test "check Intebase server" I try connect as SYSDBA. It's full rights.
About MS SQL. On Hostmonitor's PC I have Enterprise Manager and I can connect to my database and administrate this.
About ODBC. I have create user DSN with SQL Server driver, connect with Windows NT authentication and check configuration by pressing "Test Data Source..." button. Ok, test completed sucessfully.
HostMonitor's ODBC Query return status "No answer" and reply "Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'DOMAIN\MACHINEACCOUNT$'. If I try with login/password fields is blank or anyone then reply same: Login failed for user 'DOMAIN\MACHINEACCOUNT$'. Why MACHINEACCOUNT used instead of current user account or that is specified in a field login?
![:(](./images/smilies/icon_frown.gif)
Sorry, I don't know why Interbase test doesn't work in your case.
I think you may use ODBC test instead. If you need to start HostMonitor as service, provide admin's account on "Service" page in the Options dialog (www.ks-soft.net/hostmon.eng/mframe.htm# ... tm#Service).
Regards
Alex
I think you may use ODBC test instead. If you need to start HostMonitor as service, provide admin's account on "Service" page in the Options dialog (www.ks-soft.net/hostmon.eng/mframe.htm# ... tm#Service).
Regards
Alex