What are the challenges you face when working across database platforms? Take the survey
Options

Computer unreachable alert - ServerUpMonitor:COM Error

kevrileykevriley Posts: 129 Gold 1
edited June 12, 2009 12:34PM in SQL Monitor Previous Versions
Intermittently getiting a 'Computer unreachable' alert from one of my monitored servers.

It is in a different domain, however DCOM has been configured through firewall, and up until today all seemed well.

The AlertRepositoryLogFile.log file contains these entries (IP address obscured for secutiry reasons)


12:30:19.442|Error |AlertRepository |11 |The object invoked has disconnected from its clients. - query 'select FreeSpace,Size,Name,FileSystem from Win32_LogicalDisk where DriveType=3'
12:31:22.588|Error |AlertRepository |11 |The object invoked has disconnected from its clients. - query 'select Handle,Name,CreationDate,KernelModeTime,UserModeTime,WorkingSetSize,VirtualSize from Win32_Process'
12:32:04.050|Error |AlertRepository |34 |The object invoked has disconnected from its clients. - query 'select Handle,Name,CreationDate,KernelModeTime,UserModeTime,WorkingSetSize,VirtualSize from Win32_Process'
12:32:19.188|Error |AlertRepository |12 |The object invoked has disconnected from its clients. - query 'select FreeSpace,Size,Name,FileSystem from Win32_LogicalDisk where DriveType=3'
12:32:49.745|Error |AlertRepository |22 |The object invoked has disconnected from its clients. - query 'select Handle,Name,CreationDate,KernelModeTime,UserModeTime,WorkingSetSize,VirtualSize from Win32_Process'
12:33:16.328|Warn |AlertRepository |8 |ServerUpMonitor: COM Error 0x80010108 from xxx.xxx.xxx.xxx
12:38:13.417|Info |AlertRepository |26 |SqlServerInstance: xxx.xxx.xxx.xxx is now up
12:38:17.291|Info |AlertRepository |8 |Server: xxx.xxx.xxx.xxx is now up.


Any ideas of why this may be happening? Or possible causes?


Kev

SQL Response v1.2.0.219

Comments

  • Options
    kevrileykevriley Posts: 129 Gold 1
    An update...

    I changed the gateway of the alert repository pc to avoid the proxy(MS ISA Server) to see if that had any effect - it didn't.

    Put the machine back on the proxy, and since then haven't had a repeat of the issue.

    So as far as it seems, it was just a temporary issue that seems to have 'fixed' itself.



    Kev
  • Options
    kevrileykevriley Posts: 129 Gold 1
    Not sure if this is related .....

    now getting 'Computer unreachable' alerts, with the log entry of

    ServerUpMonitor: COM Error 0x800706A from xxx.xxx.xxx.xxx


    Any ideas?


    Kev
  • Options
    Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    We've had a bit of success in using Windows built-in wbemtest.exe utility to test WMI connectivity.
    Start->run: wbemtest.exe

    Click "connect". Enter \\xxx.xxx.xxx.xxx\root\CIMV2
    Click "query" (if you have not already got an error)
    Enter "select Handle,Name,CreationDate,KernelModeTime,UserModeTime,WorkingSetSize,VirtualSize from Win32_Process"

    The results for this query should come back rather quickly, if not, maybe a network latency issue is to blame. You may want to try running this query over and over again to see if it's consistent. If it doesn't work at all, try disabling any firewalls between the two machines, or follow the instructions from Microsoft:
    http://msdn.microsoft.com/en-us/library/ms809327.aspx
Sign In or Register to comment.