Salesforce Troubleshooting
Overview
This article covers the common errors seen when installing the ScreenMeet managed package or creating a session from within Salesforce. Each entry lists the error text, its root cause, and the resolution. Most session-creation errors trace back to permission set or object settings on the ScreenMeet service account, so verify those first.
Package Installation Error: feedLayout is not supported for this layout
You see Case-Case Layout: feedLayout is not supported for this layout when installing the ScreenMeet package.
Root cause: Chatter is not enabled in your Salesforce org.
Resolution: Enable Chatter, then reinstall the package. In Salesforce, go to Setup > Customize > Chatter > Settings and turn on Turn on Chatter and Global Search features.
TypeError: Failed to fetch
You see TypeError: Failed to fetch when starting a ScreenMeet session.
Root cause: The ScreenMeet domain is missing from your Content Security Policy (CSP) Trusted Sites.
Resolution: Add https://*.screenmeet.com as a CSP Trusted Site. See Add ScreenMeet to CSP Trusted Sites.
Error 400: INVALID_FIELD
You see 400: INVALID_FIELD when creating a session.
Root cause: Incorrect object settings on the service account permission set.
Resolution: On the ScreenMeet Live Sessions object, confirm the Host URL field permissions have both Read and Edit access. See Service Account Setup.
Error 400: INVALID_FIELD_FOR_INSERT_UPDATE
You see 400: INVALID_FIELD_FOR_INSERT_UPDATE when creating a session.
Root cause: Incorrect object settings on the service account permission set.
Resolution: Verify the object settings on the permission set as described in Service Account Setup.
Error 404: NOT_FOUND
You see 404: NOT_FOUND when creating a session.
Root cause: Incorrect object settings on the service account permission set.
Resolution: Verify the service account object settings as described in Service Account Setup.
Error 404: NO_ACCESS
You see 404: NO_ACCESS when creating a session, either in the ScreenMeet widget or in the console network error log.
Root cause: IP-based session validation settings are enabled and are blocking the session.
Resolution: In the ScreenMeet Console, confirm that Lock sessions to the IP address from which they originated and Enforce login IP ranges on every request are both unchecked. These settings must be off for sessions to validate correctly.
No Option to Reset Security Token
After signing in to Salesforce with the service account, the Reset Security Token option is not available.
Root cause: A Login IP Range is set on the service account profile. When a profile is restricted to specific IP ranges, Salesforce hides the security token reset option.
Resolution: Remove the Login IP Range from the service account profile so the reset option reappears. See Salesforce: Unable to see the Reset Security Token option.
If the Issue Persists
If an error continues after applying the resolution above, collect the error text, the ScreenMeet session ID if one was generated, and the ScreenMeet package version, then contact ScreenMeet support. Most session-creation errors come from the service account permission set, so re-running Service Account Setup end to end resolves the majority of cases.