https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNTM3IiwiaGFzaCI6IjZhMzhlODFmLWEzYmQtNDc5OC05YzljLWFkMGEwN2Q1NDU0ZSJ9
1-800-691-1991 | 9am - 8pm ET
EN

nworks "Failed to Login" or "Cannot Complete Login" troubleshooting

Purpose

The following errors occur: Login failed or Cannot complete login.

Cause

You may see the following event in the nworks logs or receive a similar notification:
ERROR IMon  Quering (IP or VC Name) failed:
Veeam.LicenseServer.LsException: Soap login to '(IP or VC Name)' failed, port 443, user 'YourUserName', proxy srv:, proxy port: 0, proxy user: '' ---> System.Web.Services.Protocols.SoapException: Cannot complete login due to an incorrect user name or password.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at VimApi.VimService.Login(ManagedObjectReference _this, String userName, String password, String locale)
   at Veeam.LicenseServer.ViSoap.ServiceSession.Create(ServiceConnSpec connSpec)
   --- End of inner exception stack trace ---
   at Veeam.LicenseServer.ViSoap.ServiceSession.Create(ServiceConnSpec connSpec)
   at Veeam.LicenseServer.InfrastructureMonitor.go(Object data)
ERROR CM    Monitor object: 'Veeam.LicenseServer.InfrastructureMonitor', Error: 'Soap login to '(IP or VC Name)' failed, port 443, user 'YourUserName', proxy srv:, proxy port: 0, proxy user: '''.

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.

KB ID:
1537
Product:
Veeam Management Pack for Microsoft System Center
Version:
5.x
Published:
2012-07-06
Last Modified:
2020-08-28
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later