- Veeam Support Knowledge Base
- No connection could be made because the target machine actively refused it
No connection could be made because the target machine actively refused it
| KB ID: | 1658 |
| Product: | Veeam Management Pack | 5.6 | 5.7 | 6.0 | 6.5 | 7.0 | 8.0 | 9.0 | 9a | 13 |
| Published: | 2012-07-20 |
| Last Modified: | 2025-06-18 |
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
Oops! Something went wrong.
Please, try again later.
This article specifically concerns a communication issue between Veeam Management Pack for Microsoft System Center components.
The core error message, "No connection could be made because the target machine actively refused it" is a generic error that occurs anytime a connection to a service fails, either because the port mentioned in the error is blocked or the service that should be listening on that port on the destination machine is not running.
Challenge
When you try to log in to the Veeam Management Pack for Microsoft System Center Web UI you receive the following error:
No connection could be made because the target machine actively refused it x.x.x.x:8084
Cause
Solution
Recommended Troubleshooting
- Ensure that Veeam Virtualization Extensions for System Center Service service is running.
- Verify that the domain account that you use to access the Veeam Management Pack for Microsoft System Center 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.
- Open the IIS Manager.
- In the Connections pane go to ServerName > Sites > Veeam Virtualization Extensions UI.
- Right-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.
- 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 service.
The vemState.db.xml file is located in the following directory:
C:\ProgramData\Veeam\Veeam Virtualization Extensions for VMware - After that, you will need to add connections to VMware servers and configure monitoring settings in the Veeam Extensions UI once again.
- To do this, rename the vemState.db.xml file and restart Veeam Virtualization Extensions for System Center Service service.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
