RBAC - w3wp.exe Connection Leak detected

Question

_{Saturday, March 21, 2015 8:33 PM}

Hello,

I'm receiving this error on our Exchange 2013 server and was wondering if anybody has encountered it before, what is it caused by and what is the fix?

Log Name: Application
Source: MSExchange RBAC
Event ID: 74
Task Category: RBAC

(Process w3wp.exe, PID 11616) Connection leak detected for key domain.local/OU/User Accounts/Admin-Exchange in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.

Cheers,

Rob

All replies (4)

_{Monday, March 23, 2015 7:09 AM ✅Answered}

Hi Rob,

From your description, the issue is related to insufficient permission. I recommend you check if there is any task running without enough permission in your Exchange server. If yes, please add the necessary permission and check the result.

Hope this can be helpful to you.

Best regards,

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Amy Wang
TechNet Community Support

_{Monday, March 30, 2015 1:28 AM}

Hi,

Any update?

Best regards,

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Amy Wang
TechNet Community Support

_{Monday, May 21, 2018 5:15 PM}

Hi Belinda

Can you shed some light on what permissions are insufficient? I have seen this happen on almost every CU of Exchange 2013 and 2016. servers with wildcard certs, without them, with AV and no AV, the only tasks running on a "vanilla" server is the exchange performance logs and the time the "leak" event id 74 logs is once a day at random times, it is not consistent. 

I thought i had it figured out to do something with PowerShell but cannot replicate it. I can open the EMS up and close it and sometimes it will log this error but who is to say it is that?

Can this be escalated to the product team at all to shed some light where it is coming from and what to look at or to suppress this error if it is no harm to the server.

Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

_{Wednesday, September 12, 2018 3:15 PM}

Have the issue from time to time. Anyone has the solution? Hey Microsoft what is the problem?