.png){kind=logo}
Slate Integration - Resolving Errors
- Cause: This error is most likely caused by incorrect information entered into the "Username" field on the SFTP Configuration page in Cadence.
- Solution: Open your Slate FTP User's settings in Slate and look for the "Username" field. The username should have an "@" symbol in it. Copy that username, log into Cadence, and navigate to "Team Name" > Slate > SFTP Configuration. Enter the correct username (including the "@" symbol) into the "Username" field and click [Save]. Try running the import again.
- Cause: On the Slate FTP, the location we look for to pick up your import file does not exist. The location on the FTP must follow the correct path, and the file must be located in the "mongoose" folder under "outgoing".
- Solution: Ensure the correct path and location exists in Slate. You can use the FTP Explorer utility to search locations on the FTP. Additionally, ensure that the correct permissions are set up on the user in order for us to access that location.
- Cause: The required path restrictions, "/incoming/mongoose/", "/outgoing/mongoose/", "/incoming/mongoose/processed/", and "/outgoing/mongoose/processed/" are not properly entered in or configured, either on the Slate FTP User or on the SFTP Configuration page in Cadence.
- Solution 1: Open your Slate FTP User settings and ensure all of the required path restrictions are entered in. If they are, click to put your cursor after each path restriction entered in to ensure that there are no extra spaces. Log into Cadence and navigate to "Team Name" > Slate > SFTP Configuration and ensure the "Incoming Path" and "Outgoing Path" are entered in. If they are, click to put your cursor after each path entered in to ensure that there are no extra spaces.
- Solution 2: Open your Slate FTP User settings and ensure the path restrictions entered in are accurate and don't contain any upper case letters. Log into Cadence and navigate to "Team Name" > Slate > SFTP Configuration and ensure the "Incoming Path" and "Outgoing Path" are accurate and don't contain any upper case letters. Paths are case sensitive and must match the actual locations on the Slate FTP.
- Cause: We are able to successfully access the file path on the Slate FTP, but we were not able to find the import file.
- Solution 1: Check the naming of the file in Slate and ensure the first part of it matches the name entered in Cadence next to "File Name Prefix" on the Import Configuration page.
- Solution 2: Ensure your Slate query is successfully producing a file and placing it in the correct location on the FTP (/outgoing/mongoose/).
- Solution 3: Open your Slate FTP User settings and ensure all of the required path restrictions are entered in. If they are, click to put your cursor after each path restriction entered in to ensure that there are no extra spaces. Log into Cadence and navigate to "Team Name" > Slate > SFTP Configuration and ensure the "Incoming Path" and "Outgoing Path" are entered in. If they are, click to put your cursor after each path entered in to ensure that there are no extra spaces.
- Cause #1: There are two potential causes. One is that the file produced by your query in Slate has a prefix that does not match the one you have set up in Cadence under Slate > Import Configuration. The filename prefix must be exact, including capitalization/case.
- Solution #1: Confirm the prefix is correct and edit the filename in the query settings in Slate--or the File Name Prefix in Cadence--if needed.
- Cause #2: If the above-mentioned solution did not work, the other possible cause is that the path restrictions set up on your Slate SFTP user are incorrect. Refer to our article on Slate SFTP Configuration to confirm the paths are set up properly.
Overview
As you configure your Slate Integration, there are sometimes "errors" that will show up when you attempt to import or export data. This article will explain the most likely causes for each error and what can be done to remedy it.
FTP Errors
The following is a list of general errors related to the FTP configuration that you may encounter during the setup process. The likely cause of each and most likely solution is provided.
An error occurred while reading file from Slate SFTP server: Permission denied (publickey).
An error occurred while reading file from Slate SFTP server: Could not find a part of the path '\\technolutions.net\shared\ftp\___\outgoing\mongoose'.
Other errors related to "paths"
Errors Related to Being Unable to Find the Import File
Import Errors
If your import is configured correctly and pulling over a file from Slate, there may be errors associated with specific contact records. Please review our article on Resolving Import Errors for a list of causes and solutions.
Skipped - No file found
- Solution #2: Go into your Slate SFTP user's path restrictions and click your mouse cursor behind each path to confirm there are no trailing spaces. Additionally, confirm the capitalization matches. Slate is very specific about what is allowed, so it needs to match exactly.
- Cause: This error is most likely caused by incorrect information entered into the "Username" field on the SFTP Configuration page in Cadence.
- Solution: Open your Slate FTP User's settings in Slate and look for the "Username" field. The username should have an "@" symbol in it. Copy that username, log into Cadence, and navigate to "Team Name" > Slate > SFTP Configuration. Enter the correct username (including the "@" symbol) into the "Username" field and click [Save]. Try running the import again.
- Cause: You do not have the proper permissions set up on your Slate FTP User to allow it to create new directories on the Slate FTP.
- Solution: Ensure the correct path (/incoming/mongoose/) and location exists in Slate. You can use the FTP Explorer utility to search locations on the FTP. Additionally, ensure that the correct permissions are set up on the user in order for us to access that location.
Export Errors
If you are exporting data from Cadence to Slate via the Slate Integration, this section will help troubleshoot errors related to that file transfer.
An error occurred while sending file to Slate SFTP server: Permission denied (publickey).
Could not create directory for Mongoose export file.