Troubleshooting 'NLB is not configured in this Server' issue
The following conditions must be met before you can proceed to troubleshoot NLB nodes:
1. The node has successfully been added via WMI.
2.WMI is working properly on the remote server.
Using wbemtest.exe to troubleshoot WMI:
1. Open wbemtest.exe, usually located at C:\Windows\System32\wbem\wbemtest.exe
2. From the Applications Manager server, open wbemtest.exe and click Connect.
3. In the Namespace field enter: \\RemoteServerIpAddress\root\MicrosoftNLB
4. Provide Credentials then Click Connect. If 'Invalid Namespace' error appears, then the NLB feature is not installed in that Server. Install the NLB feature from the Server Manager, then configure the NLB Cluster.
5. Once connected, click Query. The Query dialog appears.
6. Run a Query for specific information.
SELECT Name FROM MicrosoftNLB_Node
If the test was successful and still not able to get the NLB details in the Applications Manager web console, then follow the below steps.
1. Go to AppManagerHome\working\conf\application\scripts\ folder in command prompt and execute the below script:
cscript serverNLB.vbs <RemoteHost> <UserName> <Password> > serverNlb.txt
2. Send the serverNlb.txt file to appmanager-support@manageengine.com along with the Support Information File from Applications Manager.
New to ADSelfService Plus?
Related Articles
Troubleshooting 'NLB is not configured in this Server' error
The following conditions must be met before you can proceed to troubleshoot WMI nodes: 1. The node should have been successfully added via WMI. 2. WMI should be working properly on the remote server. Using wbemtest.exe to troubleshoot WMI: 1. Open ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshooting Server error responses
Server error responses Internal Server Error, Bad Gateway, Service Unavailable and Gateway Timeout are the most common server error messages. Seeing any one among these errors generally indicates an issue with the URL's server. Troubleshooting for ...Troubleshooting Bad Request and Internal Server error
Bad Request & Internal Server error When the server of URL cannot understand the request it has received it responds with a Bad request or a malformed syntax error message. If there is an error in processing the request received by the server, it ...Troubleshooting - Apache Server
Condition to determine, if it is 'Apache Server':- Open Command Prompt in Applications Manager machine and execute the following commands and check for the specified outputs. telnet <Apache_Hostname> <Apache_Portnumber> Then a blank screen appears, ...