Salesforce Integration Troubleshooting

This is designed to assist members of implementation and support teams who are either installing or supporting the Salesforce Integration. The items listed in this ever-growing document cover potential issues one may encounter when working with the integration, along with steps to take to investigate and alleviate those issues. Salesforce error logs refers to the Error Logs tab in Salesforce, which can be found by selecting the BeyondTrust RS Integration and then clicking the Error Logs tab. This section assumes you have a base knowledge of both Salesforce and Remote Support.

Session Key Button or Tab Displays "This Site Can’t Be Reached Error"

This error appears in Salesforce Classic when the Remote Support Web Session Key button is clicked, and in Salesforce Lightning when the Generate Session Key button under the RS Session Key tab is clicked.

Make sure the B Series Appliance hostname for the B Series Appliance Configuration record is set to a valid hostname and that it is reachable on the network.

Generate Session Key or Web Session Key Button Displays "Unauthorized Endpoint" Error

The full error may look something like:

Warning: HTTP Exception: Unauthorized endpoint, please check Setup-> Security -> Remote site settings. endpoint = https://support.example.com/oauth2/token.

This error manifests itself in Salesforce Classic when the Generate Session Key button is clicked, and in Salesforce Lightning when the RS Session Key tab is clicked.

Make sure the B Series Appliance hostname for the B Series Appliance Configuration record is set to a valid hostname and that it is reachable on the network.

Nothing Happens When The Remote Support Session Key Button Is Clicked

This button is intended to launch the Remote Support Representative Console.

Make sure the B Series Appliance hostname for the B Series Appliance Configuration record is set to a valid hostname and that it is reachable on the network.

Make sure the name of the B Series Appliance is set to Default.

Generate Session Key Button or RS Session Key Tab or RS Jump Tab Displays B Series Appliance Configuration “Default” Was Not Found Error

This error occurs whenever the default B Series Appliance is not named Default. The name field is different than the hostname field, which contains the B Series Appliance address. The name field is arbitrary, but the first or only one in the list must be set to Default.

Make sure the name of the B Series Appliance is set to Default.

'Error Validating Parameter ‘queue_ID’: The Representative Could Not Be Found"

If you get an error stating, Error validating parameter 'queue_id': The representative could not be found, this indicates that the Salesforce user who is trying to generate a session key is not mapped to a Remote Support user. Typically, an LDAP store is used for both Salesforce and Remote Support; thus usernames in each system match exactly.

If an LDAP store is not used and the usernames between Salesforce and Remote Support do not match exactly, the usernames must be manually mapped so that when a session key is generated, a Remote Support user can be found.

For more information, please see Add Remote Support Username to User Layout in this integration installation guide.

"Requested Support Representative Is Not Available at This Time"

If you get an error stating, Requested support representative is not available at this time, this indicates that the Use repRep Console for Session Keys setting is unchecked in the B Series Appliance configuration AND the representative that is mapped to the Salesforce user who generated the session key is not logged into the Remote Support Representative Console.

Have the representative log in to the Remote Support representative console OR check the Use Rep Console for Sessions Keys box and the representative console is launched if it is installed on the representative's workstation.

Support Sessions Aren’t Being Written to Salesforce

If support sessions aren't being written in Salesforce, there could be a communication issue. First check to ensure communication is open from Remote Support to Salesforce.

Login to the Remote Support /login interface and ensure Support Session End is checked on the HTTP Recipient for the Outbound Event. If Support Session End is not checked, check the box, save the HTTP Recipient, then run another support session and see if the record is written to Salesforce.

If the Outbound Event looks good, login to the Remote Support /appliance interface and run a TCP test to the hostname of the Salesforce instance on port 443. If the TCP test yields a non 200 response, recommend the network team be involved to determine if there is a network block in place, such as a firewall or network rule.

Ensure the outbound event HTTP Recipient URL is set to http://salesforce-beyondtrust-site-hostname/bomgar/BGIntegration__SessionUpdateHandler and matches the URL of the site which was created in the Salesforce Installation guide.

Data Is Missing from the Support Session in Salesforce

If data is missing from the Support Session record, it's possible the Remote Support event types have not been updated or only a subset of the event types have been set to be imported for each support session record that is written to Salesforce.

Identify which pieces of data are missing, then check the Selected Event Types field under the B Series Appliance configuration in Salesforce to see if a subset of the events are set to be imported. If you don't see any events, it's possible the Event Types were never imported into Salesforce, as outlined in the Installation guide for this integration.