Rtcrsv.exe stops working when you add a TCP-enabled trusted application to a trusted application pool


You create a trusted application pool and publish the topology. Then, you add a TCP-enabled trusted application and run Enable-CsTopology. In this situation, the Rtcsrv.exe process stops running on the front-end servers. This issue occurs in a Skype for Business 2015 and Lync Server 2013 environment.


This issue may occur if you are using for the trusted application a trusted application pool with different Outbound Only settings and the same IP as another trusted application or service from the pool.

When the application is enabled for TCP, the application endpoint is identified by IP address and port instead of by FQDN and port. If the IP address that's used by the trusted application pool is not explicitly specified in the topology, it defaults to (any IP), which can match any server. This causes a configuration conflict.

When this issue occurs, the following events are logged in the event log when you try to start the Rtcsrv.exe process:


To fix this problem, use one of the following methods:
  • Use TLS instead of TCP for the trusted application.
  • Make sure that trusted application pools have the same Outbound Only settings.
  • Specify the IP address of the trusted application pool by using the Limit service usage to selected IP addresses option in the topology. This option is not available when you create the trusted application pool. However, it becomes available after you associate a trusted application with the trusted application pool.

文章識別碼:3175719 - 最後檢閱時間:2016年7月8日 - 修訂: 1