Manage Remote Node Login page not available
|
This error may occur if the Managed System Login preference is disabled. To enable, login to the local system with administrator privileges and enable the Managed System Login in
Preferences > General Settings
> Webserver
> Properties
> Managed System Login
If the Managed system login in the preference page is disabled you would not be able to login into webserver.
|
Could not resolve hostname
|
This error may occur when the Web server cannot resolve the hostname you have entered.
|
Connection error
|
The error may occur due to any of the following reasons:
- The managed system you are trying to log in to is unreachable.
- The Web Services for Management (WS-Man) server on the managed system is not running.
- The port number you entered is incorrect.
- The WS-Man server is running but not configured for HTTPS. For more information, see the
Server Administrator Installation Guide.
- The system running Server Administrator Web server has default proxy settings (not the browser proxy settings), the managed system login may fail. To fix this problem, the managed system should be accessed directly or by bypassing the proxy. For more information about configuring the proxy settings, see your operating system documentation.
|
Certificate error
|
The error may occur due to any of the following reasons:
- The managed system certificate has expired.
- The Certificate Authority (CA) of the managed system certificate is not trusted by Server Administrator web server.
- The Common Name (CN) name of the managed system certificate does not match the hostname entered in the Hostname/IP address field.
- The managed system certificate is not revoked.
|
Authentication Failure
|
This error may occur due to any of the following reasons:
- You have either entered an incorrect
User Name or
Password.
- The Windows Remote Management Authorization feature (Remote Enablement) is not configured in the managed system. For information about installing and configuring Remote Enablement, see the
Server Administrator Installation Guide and for information about User Configuration, see the
Server Administrator User's Guide.
- The managed node is running Windows 2008 R2 and WinRM's (Windows Remote Management) "CbtHardeningLevel" setting is configured to "Strict." To resolve this issue, change the CbtHardeningLevel setting to either "Relaxed" or "None." See the WinRM documentation for details.
- The lockdown mode is enabled while you are logged into Server Administrator on VMware ESXi operating system. For more information about lockdown mode, see VMware documentation.
|
Connection timeout
|
This error may occur if the managed system you are trying to access is unreachable or taking too long to respond. This may be because the dependent service(s) on the managed system are processing other requests.
|
Internal error occurred
|
This error may occur due to any of the following reasons:
- The dependent service(s) on the managed system are not running. For information about dependent service(s), see the
Server Administrator Installation Guide.
- The WS-Man server is running but not configured for HTTPS.
- The remote enablement is not installed. For information about how to install remote enablement, see the
Server Administrator Installation Guide.
|
Out of Memory
|
This error is an operating system error. See the operating system documentation of the managed system and fix the issue and login again.
|
CRL file not present or bad
|
This error may occur if you have not specified a valid CRL (Certificate Revocation List) file.
|
Lockdown mode is enabled in the managed node
|
This error may occur if the lockdown mode is enabled on a VMware ESXi managed node. For more information about lockdown mode, see VMware documentation.
|