Could not connect to http://localhost:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:5725.

Question

when trying to Debug TImer job getting below error

Could not connect to http://localhost:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:5725.

Answer 1

This is the User Profile Service Application. Is one provisioned and/or is UPSS running?

---

Trevor Seward

Office Servers and Services MVP

Author, Deploying SharePoint 2016

This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Answer 2

Upss is running without any issue

Answer 3

Hi Veeralaxminarayana I,

If you could share the solution, your solution will benefit many other users.

Best Regards,

Lisa Chen

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [e-mail]

Answer 4

Hello all,

The solution is the below: 

1)

In SharePoint timer job history I have noticed that there's the error in starting User Profile synchronization:

Could not connect to http://spsrv:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it <ip-adress:port>.

2)

In EventViewer there were some records like this:

Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.

And apply the below solution:

Solution.

Open services.msc. Be sure that both Forefront Identity Manager Service and Forefront Identity Manager Synchronization Service are started. Start them if they are stopped. The above endpoint refers to these services.

Answer 5

Confirmed. This worked for me. One of the services was stopped event startup is set to automatic. Time to update the monitoring software.