Environment
NetIQ AppManager 7.0.x
Situation
AppManager returns a 1753 error message when pinging the agent using NetIQctrl
AppManager returns a 1723 error message when pinging the agent using NetIQctrl
When using the NetiQCtrl commands to troubleshoot a problem with a remote AppManager agent or Management Server service, an rpc version mismatch error may be generated.
Resolution
This error message is generated either because:
- RPC version has a different version (straightforward) RPC is busy at the time when you pinged the machine In most cases the servers is under heavy load or
- MS-RPC is under heavy load at the time that the netiqctrl ping (or other command) was issued.
Waiting a few minutes and then attempting to ping the remote agent again would work in this case. In other cases this response could indicate that the netiqmc service itself is busy or has hung. In this case you should stop and restart the netiqmc (or netiqccm or netiqms) service. If the RPC service on a particular server is in distress effecting any RPC dependant services, (check to see if you can use service control manager to access that server remotely), you may have to restart the server to regain the use of RPC.
Cause
When one of the Managed Client servers appears grayed out with a symbol that looks like -||---X- running through it in the TreeView pane of the Operator Console, use NetIQCtrl with the command ping <servername> NetIQccm , or ping <servername> NetIQmc to help diagnose the problem.
In some cases the following error message may be generated: Remote operation failed with 1723 or 1740 rpc version mismatch