Windows Errors
From ServersCheck Wiki
Make sure that the Windows checks minimum requirements are met in respect to the account settings of the monitoring service and firewall requirements.
Contents |
Error: Access is denied
If you have made sure that all settings are correct in terms of admin rights for the service, then the issue can be related to the fact that DCOM is not running. The error message Windows returns is misleading and creates confusion.
To solve the DCOM issue, proceed as follows:
1) Go to your Start Menu and select Run
2) Type DCOMCNFG in the Open textbox and hit the Go button
3) In Windows you have direct access to a window with several tabs in it.
4) Go to the tab Default Properties and check the option Enable Distributed COM on this computer (on computer running ServersCheck and target computer)
Try now to run the check again.
When using Windows based checks (CPU, Drivespace, Process, Memory, ...) the computer running ServersCheck connects by using WMI and RPC to connect to the remote computer and execute the task. Due to the complexity of networks, several items could cause the issue.
Try to the steps outlined below. If the error message changes from 'RPC is unavailable' to 'Access Denied', then the RPC issue is resolved and it has become an issue of security settings.
1. Is the "Server" service running on the remote host?
2. Is the "Server" service tied to the interface (network card) on which the requests arrive from ServersCheck? In Windows you can check this by verifying if the "Client for Microsoft Networks" is available for that network connection. If not, then click the Install button to add it.
3. Is TCP/UDP Port 139 open between ServersCheck and remote host?
4. Is TCP Port 445 open between ServersCheck and remote host?
5. Is NETBIOS enabled on computer running ServersCheck?
6. Is NETBIOS enabled on remote host?
7. Does the remote host have more than one IP address? The IP address being called by ServersCheck needs to be the first one configured on the remote host. See http://support.microsoft.com/default.aspx?scid=kb;en-us;Q131641 for more information.
8. If the above do not resolve the issue, then try following article from Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224370
Please note that depending on your configuration, the remote host's RPC dynamic port allocation will instruct the RPC program to use a particular random port above 1024.
More information on this topic can be found in following Microsoft Knowledge Base article on configuring RPC through firewalls: http://support.microsoft.com/?kbid=154596
Remote calls are not allowed for this process
This error occurs if the ServersCheck and/or target computer does not have Distributed COM (DCOM) enabled.
To resolve this problem, enable DCOM on the client computer.
1) Click Start, and then click Control Panel.
2 Double-click Administrative Tools, and then double-click Component Services to open the Component Services Microsoft Management Console (MMC).
3) Expand the Component Services and the Computers nodes.
4) Right-click My Computer, and then click Properties.
5) On the Default Properties tab, click to select the Enable Distributed COM on this computer check box, and then click OK.
6) Close the Component Services MMC.
7) Reboot the system
Call was rejected by callee
1) Go to your Start Menu and select Run
2) Type regedit in the Open textbox and hit the Go button
3) Navigate down the tree to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLE\
4) Double click in the Enable DCOM name to view its properties.
5) Change the value to Y even if it is already set to Y.
6) Reboot the system
Now try to run the check again.
