# SFTP unable to handle "control.ini" **URL:** \ **Category:** Bugs\ **Created:** [February 22, 2019, 12:15pm UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430 "2019-02-22T12:15:42Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![mjones](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/m/439d5e/32.png) [@mjones](https://www.finalbuilder.com/forums/u/mjones)\ **Post date:** [February 22, 2019, 12:15pm UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/1 "2019-02-22T12:15:43Z")
I use a file called “control.ini” on a web server. I’ve changed the server to a synology NAS, and updated the script. FinalBuilder is now unable to do anything with a file called “control.ini” on the server. It reports “Connection to the SFTP server has been lost.” if I try to upload it. Renaming the destination file in the action has it work fine. Any combination of “controlnew.ini” or “controlini” works. So I figured I’d upload it and rename it. But SFTP delete doesn’t remove a file with that name. Any other name seems fine. And rename of the file to the “control.ini” fails too. Now, it used to work on another server. But I can do anything on the file from another client. And I can’t see anything relevant on the web regarding the file name and SFTP or Synology. Is there anything “significant” in FinalBuilder with that name? Any clues really very welcome! ---
**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\ **Post date:** [February 22, 2019, 10:17pm UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/2 "2019-02-22T22:17:29Z")
No, FinalBuilder doesn’t know anything about specific filenames. I will test this on Monday as we have a Synology nas in the office. If the file was there before, my guess is permissions with the existing file? ---
**Author:** ![mjones](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/m/439d5e/32.png) [@mjones](https://www.finalbuilder.com/forums/u/mjones)\ **Post date:** [February 23, 2019, 10:53am UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/3 "2019-02-23T10:53:26Z")
There was no previous file, and I could create one, rename one, delete one from other client. And FB was working fine with other files - ironically the control.ini is the last, so I thought it must be local. But it can upload the same file with another name. Totally bizarre! ---
**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\ **Post date:** [February 25, 2019, 12:55am UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/4 "2019-02-25T00:55:15Z")
What version of FinalBuilder are you using? ---
**Author:** ![mjones](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/m/439d5e/32.png) [@mjones](https://www.finalbuilder.com/forums/u/mjones)\ **Post date:** [February 25, 2019, 9:13am UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/5 "2019-02-25T09:13:26Z")
I was originally on an older version, then reported as per version 8.0.0.2508 and have no installed build 2516. Incidentally, the check for updates returns an error saying it didn’t understand `

` Below is the log - it seems to me that there is something “tripping up” the SFTP component. Oh wow, done some experimentation and it is failing with any 7.3 file name. A simple 1234567.123 fails too, but add an 8 and it works. Take the 6, it works. No idea where to go from that, but any 7 letter name and 3 letter extension seems to fail guaranteed. I hope this helps! Matthew * * * Action Messages: Connecting to ‘[myserver.com](http://myserver.com)’ on port 4422. Connecting… Setting Authtypes to keyboard and password Received Server Key [77c092c20e05fbd66373d2b418c28e40]. Starting Authentication… Attempting Authentication type: [4] Authenticated OK. Server public key cached: 77c092c20e05fbd66373d2b418c28e40 Connected to [myserver.com](http://myserver.com) Server Software : OpenSSH\_7.4 Server SFTP Protocol Version : 3 SFTP Upload File - Myfile.exe Action Messages: Acquiring connection object Uploading c:\src\MyFolder\Distribution\Server\Myfile.exe Uploaded [c:\src\MyFolder\Distribution\Server\Myfile.exe] to [MyFolder/updates/Myfile-50.exe] Releasing connection object SFTP Upload File - control.ini Action Messages: Acquiring connection object Uploading C:\src\MyFolder\Controller\control.ini Upload of ‘C:\src\MyFolder\Controller\control.ini’ to ‘MyFolder/updates/control.ini’ failed: SFTP component not connected Releasing connection object ---- Retry with upload under other name, delete name and then rename to proper. Connect skipped for brevity. Action Messages: Acquiring connection object Uploading C:\src\MyFolder\Controller\control.ini Uploaded [C:\src\MyFolder\Controller\control.ini] to [MyFolder/updates/controlnew.ini] Releasing connection object SFTP Remove File - [LocalTest] Action Messages: Acquiring connection object Removing MyFolder/updates/control.ini File removed. Releasing connection object SFTP Rename File - [LocalTest] Action Messages: Acquiring connection object Connection to the SFTP server has been lost. Releasing connection object ---

**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\ **Post date:** [February 25, 2019, 10:37pm UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/6 "2019-02-25T22:37:18Z")
> [@mjones](#): > > Oh wow, done some experimentation and it is failing with any 7.3 file name. A simple 1234567.123 fails too, but add an 8 and it works. Take the 6, it works. > No idea where to go from that, but any 7 letter name and 3 letter extension seems to fail guaranteed. I hope this helps! Hmmm… must be something in secureblackbox, as I checked our code and we don’t do anything with filenames other than pass them into the library code. I’ll look into this. ---
**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\ **Post date:** [February 26, 2019, 2:07am UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/7 "2019-02-26T02:07:41Z")
I just tested this here with the latest FinalBuilder on our synology nas running DSM 6.2.1-23824 Update 4 (installing update 6 now) and it worked fine with any filenames of any length. what version of DSM are you running? I didn’t change any settings on the nas other than to turn on sftp. ---
**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\ **Post date:** [February 26, 2019, 2:11am UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/8 "2019-02-26T02:11:51Z")
Tested with update 6 with the same result. Not sure where to go from here. ---
**Author:** ![mjones](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/m/439d5e/32.png) [@mjones](https://www.finalbuilder.com/forums/u/mjones)\ **Post date:** [February 26, 2019, 9:24am UTC](https://www.finalbuilder.com/forums/t/sftp-unable-to-handle-control-ini/6430/9 "2019-02-26T09:24:09Z")
Well, I can’t explain it either - nothing in the Synology logs, was pretty up to date with only one more update to apply. Certainly not “out of date”. Just in case it adds to a future resolution, I’m running in a VMWare Fusion VM, and I tried with the Windows Firewall turned off. Nothing I can see to get in the way of such. And particularly SFTP I’d expect to be hard to intercept at a firewall level anyway. The Synology logs the good transfers, but nothing on the failed ones. Ah well, not critical to me right now, so I will leave it. Thanks for looking. If someone else has this, I hope we can work out the common factor and solve it. For now, let’s not dig further.