- Veeam Support Knowledge Base
- nworks "Failed to Login" or "Cannot Complete Login" troubleshooting
nworks "Failed to Login" or "Cannot Complete Login" troubleshooting
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Purpose
Cause
Solution
Check whether the vCenter Server complies with the minimum requirements.
The account used to connect to VMware systems should have at minimum the Read-only privilege. Other instructions described below are task-oriented.
To enable gathering of host hardware data directly from ESX(i) hosts, the CIM interaction privilege should also be assigned. To assign CIM interaction to the user role, edit the role settings: go to All Privileges > Host > CIM and enable CIM interaction. The firewall on ESX hosts by default allows incoming connections on port 5989 for CIM data collection.
CIM interaction privilege is required for collecting hardware sensor data directly from ESX hosts using CIM over XML. Alternatively, you can disable CIM-XML hardware data gathering and use an account with the read-only permissions. In this case, hardware monitoring data will be collected from vCenter.Note: This method will initiate “Hardware Refresh” events (one per Host), visible in the vSphere Client.
Note: If MP Tasks in the context of virtual machine or ESX host are required, the account used to connect to a VMware server must be assigned the required elevated privileges to run the task (Power On/Off VM, put ESX host in Maintenance Mode etc.).
To create an appropriate user role and assign specific permissions, use the vSphere Client, as described in VMware documentation.
Access should be provided to the complete vSphere hierarchy and not only to particular objects. You cannot use ‘“No Access” or other restricted permissions to any part of the vCenter hierarchy to configure monitoring visibility. To define which ESX clusters and hosts are monitored, use the nworks Enterprise Manager Web UI and check/uncheck clusters and hosts as required.
The next thing to check is the Collector Service Account. This account is the Windows service on which the Collector relies. The nworks Collector Service account should be:
-
An administrative account on the server where the Collector is running.
-
A member of the local nworks Enterprise Manager Accounts group on the server where the nworks Enterprise Manager is running.
Finally, check the nworks Enterprise Manager Web UI access account. If you do not have access to the Web UI, you will not be able to open up the GUI (Web UI).
To access the nworks Enterprise Manager Web UI (to add/remove vCenter Server connections, configure Collector settings and so on), users must be included in the local group named nworks Enterprise Manager accounts. This local group is created during nworks Enterprise Manager installation.
If you change username information with windows services or accounts, restart the service/computer to verify the change has been applied.
More Information
All this information can be found in nworks guides:
http://www.veeam.com/vmware-esx-monitoring-hp-operations/resources.html
http://www.veeam.com/vmware-microsoft-esx-monitoring/resources.html
If you have any trouble, feel free to contact support.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.