We are using sql server probe 4.95v to monitor sql servers.
For some windows servers like 2003 and 2008..we are not able to make connection to the database via the probe.For some we are able to establish the connection.
Please let us know what can be the solution and how we can proceed.
Set the probe for log level 5, reproduce the problem, and see what details on the failure the log has. The sql server side can also be checked at the same time to see if it sees the connection attempt from the probe.
We are getting this connection error.
Profile: test connection profile/test connection checkpoint/Connect - COM Error: Code=0x80004002 Source=(null) Description=(null)
Based on past cases there could be a few things causing this.
The first thing to do is deploy sqlserver 5.10 and retest all the failing profiles.
There are cases where it was a failure at the OS level and resolved via installing the OS service pack for Windows 2008 R2.
The other thing known to cause the problem is a basic communication problem.
telnet can be used to test connectivity, and Wireshark is the tool for capturing network traffic.
Okay will try to deploy 5.10 and try to test.One more query ..is there any thing as such that sqlserver probe 4.95v does not support windows 2003 server or windows 2008 servers??
as such, the probe support is listed in this document:
However, as David pointed out that there could be issues for the SQL server connections specifically, if you run Win2003 or Win2008 without a Service Pack. The example he mentioned is discussed here:
CA Tech Support