"No answer" for MS SQL tests

[netnetnet]

I've configured a few MS SQL servers and they all give me "no answer". Here's how I've configured them:

1) Installed RMA on server, enabled all tests and responses. Confirmed that RMA Manager connects okay.
2) Setup test for MS SQL, "master" db, sa and password (also tried domain administrator)

No matter how I tweak things I can only get "No answer" for these tests. There isn't anything helpful in the logs, different databases are the same, starting the RMA under different usernames is the same. I'm at a loss.

Both Windows Server 2003, SQL 2000, no firewalls.

Thanks.

[KS-Soft]

What version of the agent (RMA) do you use?
Have you installed SQL client library on system where agent is running?
Old versions of the agent may show "No answer" status when client library cannot be load. New version displays "Unknown" status.

Regards
Alex

[netnetnet]

(BTW, our other staff member was the one that installed the RMA, so I'm rather unfamiliar with this situation)

We're using Host Monitor ver 5.38... would this be the same ver for the RMA? If not, how can I check it?

Don't know if we've installed the SQL client library: how can I verify this?

thanks

[KS-Soft]

We're using Host Monitor ver 5.38... would this be the same ver for the RMA? If not, how can I check it?

Agent can be older. Dialog windows that allows you to choose agent also shows information about agent - version, platform, comment.
Or use RMA Manager to see agent list.
http://www.ks-soft.net/hostmon.eng/rma- ... /index.htm

Don't know if we've installed the SQL client library: how can I verify this?

Do you have ntwdblib.dll on the system?

Regards
Alex

[netnetnet]

Within RMA manager: 'version' column shows 3.14 (status shows 'operable').
Yes, we've got 'ntwdblib.dll' in the system directory.

[KS-Soft]

Version 3.14 shows "no answer" status when library is loaded but it cannot connect to database.

Could you try command line (console) utility www.ks-soft.net/download/mssqltest.exe ?
It has 4 command line parameters: ServerName Database UserName Password. It should display error description that may help resolve the problem.

BTW: Have you tried ODBC Query test method to connect to your server?

Regards
Alex

[netnetnet]

Thanks for the info. I've downloaded mssqltest, & will try to connect. Don't know if our other staff had tried ODBC test, will also try that.

I'll let you know what results I get from mssqltest, etc.

thanks Alex...

[netnetnet]

Thank you sir, that program got me where I needed to be.

For the curious members of the audience, it turns out that the sa password I had written down is not correct!

[KS-Soft]

I am glad it works now

Regards
Alex