Hy,
since 3 days we have the yellow message no answer from _Service - RMAService with the reply "Win32 error #1722".
We have reinstalled the service but no affect.
What can we do?
regards
Franki
Win32 error #1722
According to Microsoft manual error 1722 means "The RPC server is unavailable".
What test method displays such error? What system you are checking? Where this system located (in the same or foreign domain)? What account do you use to perform this test? What account you are using to start HostMonitor (or RMA if this test is performed by agent)? Does RPC service run on that system?
Regards
Alex
What test method displays such error? What system you are checking? Where this system located (in the same or foreign domain)? What account do you use to perform this test? What account you are using to start HostMonitor (or RMA if this test is performed by agent)? Does RPC service run on that system?
Regards
Alex
According to Microsoft manual error 1722 means "The RPC server is unavailable".
What test method displays such error?
_Service - RMAService (method: check service)
What system you are checking?
W2K Menber Server
Where this system located (in the same or foreign domain)?
Same domain
What account do you use to perform this test?
special admin account for the domain
What account you are using to start HostMonitor (or RMA if this test is performed by agent)?
same admin account for the domain
Does RPC service run on that system?
Yes
Regards
Frank
What test method displays such error?
_Service - RMAService (method: check service)
What system you are checking?
W2K Menber Server
Where this system located (in the same or foreign domain)?
Same domain
What account do you use to perform this test?
special admin account for the domain
What account you are using to start HostMonitor (or RMA if this test is performed by agent)?
same admin account for the domain
Does RPC service run on that system?
Yes
Regards
Frank
Could you check some more parameters:
1) Is the "Service" service running on target system as well?
2) Is the “Server” service bounded to the interface on which target system is being polled? You may open network connection properties dialog (Start->Settings->Network and dial-up connections->...); in the list marked "Components checked are used by this connection" make sure the entry "File and Print Sharing for Microsoft Networks" is present and checked.
3) Is the "Workstation" service running on monitoring system (system where HostMonitor is running)?
4) Is the “Workstation” service bounded to the interface which is used for monitoring? Use the same network connection dialog (Start->Settings->Network and dial-up connections->...) on HostMonitor's system; in the list marked "Components checked are used by this connection" make sure the entry "Client for Microsoft Networks" is present and checked
5) Also Microsoft recommends to use Netdiag and Netdom tools for diagnostic: http://support.microsoft.com/default.as ... us;Q224370
6) May be some TPC ports (e.g. 445) are blocked on some router between monitoring system and target server?
7) Could you try to configure test item using IP address instead of hostname? E.g. \\192.168.10.15
Regards
Alex
1) Is the "Service" service running on target system as well?
2) Is the “Server” service bounded to the interface on which target system is being polled? You may open network connection properties dialog (Start->Settings->Network and dial-up connections->...); in the list marked "Components checked are used by this connection" make sure the entry "File and Print Sharing for Microsoft Networks" is present and checked.
3) Is the "Workstation" service running on monitoring system (system where HostMonitor is running)?
4) Is the “Workstation” service bounded to the interface which is used for monitoring? Use the same network connection dialog (Start->Settings->Network and dial-up connections->...) on HostMonitor's system; in the list marked "Components checked are used by this connection" make sure the entry "Client for Microsoft Networks" is present and checked
5) Also Microsoft recommends to use Netdiag and Netdom tools for diagnostic: http://support.microsoft.com/default.as ... us;Q224370
6) May be some TPC ports (e.g. 445) are blocked on some router between monitoring system and target server?
7) Could you try to configure test item using IP address instead of hostname? E.g. \\192.168.10.15
Regards
Alex
Could you check some more parameters:
1) Is the "Service" service running on target system as well?
2) Is the “Server” service bounded to the interface on which target system is being polled? You may open network connection properties dialog (Start->Settings->Network and dial-up connections->...); in the list marked "Components checked are used by this connection" make sure the entry "File and Print Sharing for Microsoft Networks" is present and checked.
3) Is the "Workstation" service running on monitoring system (system where HostMonitor is running)?
4) Is the “Workstation” service bounded to the interface which is used for monitoring? Use the same network connection dialog (Start->Settings->Network and dial-up connections->...) on HostMonitor's system; in the list marked "Components checked are used by this connection" make sure the entry "Client for Microsoft Networks" is present and checked
The same configuration of RMA Service runs successful on further 51 server without a problem
5) Also Microsoft recommends to use Netdiag and Netdom tools for diagnostic: http://support.microsoft.com/default.as ... us;Q224370
all tested, no errors.
6) May be some TPC ports (e.g. 445) are blocked on some router between monitoring system and target server?
We have an open MPLS network for all servers and clients
7) Could you try to configure test item using IP address instead of hostname? E.g. \\192.168.10.15
we had tested it, but no effect
very strange!
Regards
Frank
1) Is the "Service" service running on target system as well?
2) Is the “Server” service bounded to the interface on which target system is being polled? You may open network connection properties dialog (Start->Settings->Network and dial-up connections->...); in the list marked "Components checked are used by this connection" make sure the entry "File and Print Sharing for Microsoft Networks" is present and checked.
3) Is the "Workstation" service running on monitoring system (system where HostMonitor is running)?
4) Is the “Workstation” service bounded to the interface which is used for monitoring? Use the same network connection dialog (Start->Settings->Network and dial-up connections->...) on HostMonitor's system; in the list marked "Components checked are used by this connection" make sure the entry "Client for Microsoft Networks" is present and checked
The same configuration of RMA Service runs successful on further 51 server without a problem
5) Also Microsoft recommends to use Netdiag and Netdom tools for diagnostic: http://support.microsoft.com/default.as ... us;Q224370
all tested, no errors.
6) May be some TPC ports (e.g. 445) are blocked on some router between monitoring system and target server?
We have an open MPLS network for all servers and clients
7) Could you try to configure test item using IP address instead of hostname? E.g. \\192.168.10.15
we had tested it, but no effect
very strange!
Regards
Frank
Sounds like the 1722 error isn't new; however it just started happening for us in December and we've been running 5.12 since June 2005. It happens on the Service monitor, primarily on the Norton or Symantec service (although I've seen it on iisadmin and w3svc monitors a couple times). The problem is intermittent...meaning it's OK, then unknown, then OK again. We have a special service acct the HM service runs under that is an admin on all monitored servers, all in the same domain, and happens on both IP and (FQN) hostname.KS-Soft wrote:Yeah, very strangeSorry, I don't have any other idea what can be wrong... If I find something, I let you know
Regards
Alex
I wanted to see if you've gotten any further before escalating to our network folks (which could take years
)Intermittent problems - the worst problems to discover. It can be related to some Windows timeout... I have checked our database, found one solution that works for some customers (but does not help others) - specify target host using IP address instead of hostname. Unfortunately we cannot say for sure why such problem happens 
this question should be directed to Microsoft.
Regards
Alex
this question should be directed to Microsoft.Regards
Alex
Unfortunately, it happens using the IP as well, and yesterday I saw the error on a Windows Event monitor. Our network security is ever-changing with upgrades, patches, and lock downs so who knows if/when they will come up with anything. I'll probably end up unchecking "treat unknown as bad" on these types of monitors to at least stop the email alerts.
I'll keep watching this topic so please reply if you come up with any suggestions. I'll do the same if we come up with a solution.
Regards,
Rhonda
I'll keep watching this topic so please reply if you come up with any suggestions. I'll do the same if we come up with a solution.
Regards,
Rhonda
-
david.matthewson
- Posts: 94
- Joined: Tue Oct 24, 2006 12:45 pm
1722 error
We to see this and also find it is intermittant.
Really difficult to track down exactly what is going on. Sometimes a reboot of the target server fixes it but it then returns many days later. Sometimes a manual refresh of hostmon causes a retest and it then comes up good.
The real issue is the false positive one - you get to ignore the error and of course when it really really means what it says you also ignore it.
This happens on Win2003 servers with 5.x & 6.x versions of KS. (Which is great product)
Brgds
David
Really difficult to track down exactly what is going on. Sometimes a reboot of the target server fixes it but it then returns many days later. Sometimes a manual refresh of hostmon causes a retest and it then comes up good.
The real issue is the false positive one - you get to ignore the error and of course when it really really means what it says you also ignore it.
This happens on Win2003 servers with 5.x & 6.x versions of KS. (Which is great product)
Brgds
David
This will happen with any version of HostMonitor. There is some problem with Windows RPC service, its not our fault.This happens on Win2003 servers with 5.x & 6.x versions of KS
If this problem appears on single server, simply install RMA on that server and use RMA to check "local" system (local to the agent of course). This always works fine because HostMonitor<->RMA uses our own protocol built over TCP/IP stack.
Regards
Alex
-
david.matthewson
- Posts: 94
- Joined: Tue Oct 24, 2006 12:45 pm