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

KB ID: 1658
Product: Veeam Management Pack for Microsoft System Center | Veeam Management Pack 5.6 | Veeam Management Pack 5.7 | Veeam Management Pack 6.0 | Veeam Management Pack 6.5 | Veeam Management Pack 7.0 | Veeam Management Pack 8.0 | Veeam Management Pack 9.0
Published: 2012-07-20
Last Modified: 2020-11-17
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

Oops! Something went wrong.

Please try again later.

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
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.