--- title: "File Transfer error with Blueprint" slug: "file-transfer-error-with-blueprint" updated: 2024-03-04T18:25:47Z published: 2024-03-04T18:25:47Z canonical: "kb.pharos.com/file-transfer-error-with-blueprint" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.pharos.com/llms.txt > Use this file to discover all available pages before exploring further. # File Transfer error with Blueprint I receive the following two errors when testing the FTP connection with the "Pharos Blueprint Enterprise Services Tester": 1. The current socket connection has been reset 2. Not logged in --- In IIS the client has set denied permission on: 1. FTP Sites 2. Default FTP Site 3. File Transfer Upload directory (The location for this setting is under the Directory Security Tab.) - Remove any particular Ip address and make sure the setting is "Granted Access" . - Apply the changes and restart IIS. ## Related - [Blueprint - ERROR: "There is no row at position 0" message and Blueprint Administrator quits](/blueprint-error-there-is-no-row-at-position-0-message-and-blueprint-administrator-quits.md) - [Pharos Blueprint Enterprise: Configuring the Print Scout or Tracker for verbose logging.](/pharos-blueprint-enterprise-configuring-the-print-scout-or-tracker-for-verbose-logging.md) - [MAC OS X Popup Client Error: "Remote host did not accept control file (54)"](/mac-os-x-popup-client-error-remote-host-did-not-accept-control-file-54.md) - [Pharos Blueprint installation fails to complete, with logged message "Error creating database: The CREATE DATABASE statement failed. The primary file must be at least "X" MB to accommodate a copy of the model database."](/pharos-blueprint-installation-fails-to-complete-with-logged-message-error-creating-database-the-create-database-statement-failed-the-primary-file-must-be-at-least-x-mb-to-accommodate-a-copy-of-the-model-database.md) - [Blueprint: Unable to run a report due to error "The configuration file section 'LogonSpecificAdminConfig could not be read."](/blueprint-unable-to-run-a-report-due-to-error-the-configuration-file-section-logonspecificadminconfig-could-not-be-read.md)