Azure Authentication Errors
You may experience one of the following errors if your Auth. Provider is improperly configured.
You may experience one of the following errors if your Auth. Provider is improperly configured.
When authenticating with SharePoint Online, you get an error: "AADSTS165000: Invalid Request: The request tokens do not match the user context." This error usually indicates a mismatched OAuth 2.0 endpoint url. This error will interrupt the set up wizard flow.
When attempting to initialize the sFiles internal component, the user gets the error, "Authentication Error: Please contact your Salesforce administrator to initiate authentication."
When loading the sFiles component, you get the error, "Either the Site, Document Library, or root folder no longer exists, or you might not have access to it."
An error appears when trying to upload a file: "Error uploading file: <filename>". This issue is typically caused by your Salesforce's CSP policies blocking your SharePoint domain.
When a user attempts to initialize sFiles on a Salesforce record, you get the error "Failed to find folder by Id. Proceeded to load folder by name instead of Id."
When loading the sFiles component, you get the error, "Parent object is not set up. Please set the parent up before setting up this record. Additionally, the SharePoint Folder Id specified on the record no longer exists."
When loading the sFiles component, you get the following error message: "Parent object is not set up. Please set the parent up before setting up this record."
When attempting to setup a folder, you get the error, "Please check if SharePoint columns specified in SharePoint Object Settings exist in this Document Library / Site."
When loading a record, the sFiles browser shows an error that says "Root_Folder_Id__c in Sharepoint Object Settings for [object] is incorrect." This indicates that either the root folder SharePoint Id is incorrect or that it isn't available in the document library.
When attempting to use the sFiles Admin Panel, you get the error, "sFiles not set up. sFiles is not yet set up, please run the sFiles Setup Wizard to view sFiles Settings."
This error can occur in the case that a single user's auth token has expired, or the application client secret has expired.
When attempting to setup a folder, you get the error, "The folder cannot be created because the folder name field is blank."
When authenticating with SharePoint Online, you get an error: "Unable to Access Page: The value of the "ErrorDescription" parameter contains a character that is not allowed or the value exceeds the maximum allowed length. Remove the character from the parameter value or reduce the value length and resubmit. If the error still persists, report it to our Customer Support team. Provide the URL of the page you were requesting as well as any other related information."
When loading the sFiles component, you get the following error message: "Unable to update record with folder Id." This record means the sFiles component cannot update the SharePoint Folder Id field on the record."
When a user attempts to authorize with Microsoft, you get the error "User Auth Failed"
This article explains possible causes and resolutions for this authentication error.
With the release of Salesforce Winter 2021, apex class security has been tightened which may cause an error to appear. This article walks you through how to resolve this error.
Upon attempting to email a file link on a case, the modal spins continuously and does not provide an error mesage.
When trying to upload a file larger than 3MB, sFiles spins continuously with a message, "Preparing files for upload..."
Reference this article for guidance on how to troubleshoot errors from the sFiles API.
Here are some common issues that can cause errors when setting up sFiles in Experience Cloud.