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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNjU4IiwiaGFzaCI6IjY4YjM2ZGJmLTM1MjQtNDM1MS1iMGVmLWZlZjU4MzgyMmRlNSJ9
1-800-691-1991 | 9am - 8pm ET
EN

No connection could be made because the target machine actively refused it

Challenge

When you try to log in to the nworks Web UI you receive the following error:

No connection could be made because the target machine actively refused it x.x.x.x:8084

See a screenshot example:


User-added image

Cause

There is a variety of reasons that can cause this issue, but the gist of the error is that you either do not have sufficient permissions, or permissions/access/settings are corrupt.

Solution

 

Troubleshooting list:

 

  • Make sure that Veeam Virtualization Extensions for System Center Service is started.

    Open the Start menu and run services.msc in the command prompt. Locate Veeam Virtualization Extensions for System Center Service in the list. If the service is not started, right-click it and choose Start from the menu.

  • Verify that the domain account that you use to access the nworks Web UI is a member of the local Veeam Virtualization Extensions Users group and a member of the local Administrators group.  

  • Verify that the local Administrators group has  Full Control access for the Veeam Virtualization Extensions UI website in IIS.  

    To check permissions, open the IIS Manager and in the Connections pane go to ServerName > Sites > Veeam Virtualization Extensions UIRight-click the Veeam Virtualization Extensions node and choose Edit Permissions from the menu. Open the Security tab and check permissions for the local Administrators group. Change permissions if necessary and propagate them to all child nodes.  These steps also apply for IIS 7. 

  • As a last resort, you can remove saved nworks data to reset any internal data sources that could contain saved credentials.  To do this, rename the vemState.db.xml file and restart Veeam Virtualization Extensions for System Center Service.  After that, you will need to add connections to VMware servers and configure monitoring settings in the Veeam Extensions UI once again.

The vemState.db.xml file is located in the following directory: 

C:\ProgramData\Veeam\Veeam Virtualization Extensions for VMware

     

     

More information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support
KB ID:
1658
Product:
Veeam Management Pack for Microsoft System Center Veeam Management Pack 9.0, Veeam Management Pack for Microsoft System Center Veeam Management Pack 8.0, Veeam Management Pack for Microsoft System Center Veeam Management Pack 7.0, Veeam Management Pack for Microsoft System Center Veeam Management Pack 6.5, Veeam Management Pack for Microsoft System Center Veeam Management Pack 6.0, Veeam Management Pack for Microsoft System Center Veeam Management Pack 5.7, Veeam Management Pack for Microsoft System Center Veeam Management Pack 5.6
Published:
2012-07-20
Last Modified:
2020-11-17
Please rate how helpful this article was to you:
3.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.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.