Product documentation
Session Recording
Current Release 2407 2402 LTSR 2311 2308 2305 2303 2212 2210 2209 2207 2206 2204 2203 LTSR 2201 2112 2110 2109 2107 2106 2104 2103 1912 LTSR 7.15 Service
View PDF

Agent cannot connect to the server

June 21, 2024
Contributed by: 
B L

When the Session Recording agent cannot connect to the Session Recording server, the Exception caught while sending poll messages to Session Recording Broker event message is logged with an exception text. The exception text provides reasons why the connection failed. The reasons include:

  • The underlying connection was closed. Could not establish a trust relationship for the SSL/TLS secure channel. This exception means that the Session Recording server is using a certificate signed by a CA that the server hosting the Session Recording agent does not trust or the server hosting the Session Recording agent does not have a CA certificate. Alternatively, the certificate might have expired or been revoked.

    Solution: Install a correct CA certificate on the server hosting the Session Recording agent. Use a CA that is trusted.

  • The remote server returned an error: (403) forbidden. This standard HTTPS error occurs when you attempt to connect using HTTP that is unsecure. The machine hosting the Session Recording server rejects the connection because it accepts only secure connections.

    Solution: Use Session Recording Agent Properties to change the Session Recording Broker protocol to HTTPS.

  • The Session Recording Broker returned an unknown error while evaluating a record policy query. Error code 5 (Access Denied). For more information, see the Event log on the Session Recording server. This error occurs when sessions are started and a request for a record policy evaluation is made. The error is a result of the Authenticated Users group (the default member) being removed from the Policy Query role of the Session Recording Authorization Console.

    Solution: Add the Authenticated Users group back to this role, or add each server hosting each Session Recording agent to the PolicyQuery role.

  • The underlying connection was closed. A connection that was expected to be kept alive was closed by the server. This error means that the Session Recording server is down or unavailable to accept requests. The IIS might be offline or restarted, or the entire server might be offline.

    Solution: Verify that the Session Recording server is started and connected to the network. Make sure that IIS is running on the server.

  • The remote server returned an error: 401 (Unauthorized). This error manifests itself in the following ways:

    • On startup of the Session Recording agent service, an error describing the 401 error is recorded in the event log.
    • Policy query fails on the Session Recording agent.
    • Session recordings are not captured on the Session Recording agent.

    Solution: Ensure that the NT AUTHORITY\Authenticated Users group is a member of the local Users group on the Session Recording agent. Local users group

Agent cannot connect to the server
June 21, 2024
Contributed by: 
B L
June 21, 2024
Contributed by: 
B L

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.