Here is some more info on this error:
http://support.microsoft.com/kb/155738 (http://support.microsoft.com/kb/155738)
Regards
Mark Perry
Systems & Networks Administrator
Telephonetics VIP Ltd
“making sound
business sense”
Simply dial +44 (0)1442 242 242
It seems conclusive from your description of the issue that the error is to do
with the SA code or API it uses.
The error
ERR: [10038] Socket operation on non-socket(25039)
Usually occurs when you create a TCP/IP connection object (which creates a
socket connection) and that object
Can your IP address change as a result of the failover? I think Servers Alive
caches IP addresses after the first pass. If my memory serves me correctly,
there is a setting to override that behavior.
Jim Ferrell
Senior Information Analyst
EDS, an HP company
Allison Transmis
Hi Mark,
The error is on the actual ping, not on any check that may be dependent on it.
I am able to ping the resource from a command line if SA is kicking out this
error.
Subsequent ping checks report same error once this error is generated once.
Resolution seems to be to restart SA ser
Sorry for all the questions just trying to build a picture of what is
happening:
The error is on the actual ping check and not a any check which may be
dependent on it?
e.g. Is it possible that the ping succeeds as the link is up and the link fails
over after this point?
When the fai
@Mark Perry
This does not kill SA.
Check is a ping to an external WAN interface on an internet router. I know the
service is not down. I also see this when pinging internal machines as well,
but only if my ISP failover kicks in.
Need more info?
Paul A. Mountcastle Jr., MCP 35421
There isn’t enough info here really.
Are you saying that it kills SA?
Are you able to see which check does this?
Regards
Mark Perry
Systems & Networks Administrator
Telephonetics VIP Ltd
“making sound
business sense”
Simply dial +44 (0)1442 242 242 an
