Symptoms
Consider the following scenario:
-
You install Internet Information Services (IIS) 8.0 on a computer that is running Windows 8 or Windows Server 2012.
-
You create an FTP site by using IIS 8.0.
-
You upload files to the FTP site by using the Ftp.exe utility.
-
You run the following command to monitor the upload progress of the files:
ftp> literal size file name
In this scenario, the command does not return the current size of the file as expected. Additionally, you receive the following error message:
550-The process cannot access the file because it is being used by another process.
Win32 error: The process cannot access the file because it is being used by another process.
Error details: File system returned an error.
Cause
This issue occurs because of a sharing violation that occurs when you use the literal size command to query the current size of a file that is already open with write access.
Resolution
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a «Hotfix Download Available» section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix Download Available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have IIS8 configured to use FTP 8.0 installed on a computer that is running Windows 8 or Windows Server 2012.
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8 and Windows Server 2012 file information notes
Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages.
-
The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.2.920 0.20 xxx
Windows 8 and Windows Server 2012
RTM
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 8, and Windows Server 2012» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Ftpsvc.dll |
8.0.9200.20553 |
318,976 |
02-Nov-2012 |
05:20 |
x86 |
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Ftpsvc.dll |
8.0.9200.20553 |
369,152 |
02-Nov-2012 |
05:26 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates For more information about the issue in IIS 7.5, click the following article number to view the article in the Microsoft Knowledge Base:
2723776 «550-The process cannot access the file» error message when you run the «literal size» FTP command in Windows 7 or in Windows Server 2008 R2
Additional file information
Additional file information for Windows 8 and Windows Server 2012
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
1,796 |
|
Date (UTC) |
02-Nov-2012 |
|
Time (UTC) |
18:09 |
|
Platform |
Not applicable |
|
File name |
X86_124e38f00fc398685f3a4955857dbe9f_31bf3856ad364e35_6.2.9200.20553_none_cac8da271c10fa8f.manifest |
|
File version |
Not applicable |
|
File size |
698 |
|
Date (UTC) |
02-Nov-2012 |
|
Time (UTC) |
18:09 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft-windows-iis-ftpsvc_31bf3856ad364e35_6.2.9200.20553_none_47bf309e800dd79a.manifest |
|
File version |
Not applicable |
|
File size |
26,653 |
|
Date (UTC) |
02-Nov-2012 |
|
Time (UTC) |
05:52 |
|
Platform |
Not applicable |
|
File name |
Amd64_bb9bb6d8fbf5c83ba9c57d8440c1cc54_31bf3856ad364e35_6.2.9200.20553_none_9ecbd302d77a15bd.manifest |
|
File version |
Not applicable |
|
File size |
1,046 |
|
Date (UTC) |
02-Nov-2012 |
|
Time (UTC) |
18:09 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-iis-ftpsvc_31bf3856ad364e35_6.2.9200.20553_none_a3ddcc22386b48d0.manifest |
|
File version |
Not applicable |
|
File size |
26,659 |
|
Date (UTC) |
02-Nov-2012 |
|
Time (UTC) |
07:17 |
|
Platform |
Not applicable |
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
2,014 |
|
Date (UTC) |
02-Nov-2012 |
|
Time (UTC) |
18:09 |
|
Platform |
Not applicable |
|
File name |
Wow64_microsoft-windows-iis-ftpsvc_31bf3856ad364e35_6.2.9200.20553_none_ae3276746ccc0acb.manifest |
|
File version |
Not applicable |
|
File size |
11,542 |
|
Date (UTC) |
02-Nov-2012 |
|
Time (UTC) |
05:44 |
|
Platform |
Not applicable |
Need more help?
I have created a small windows forms application to upload the file to one of our client’s ftp site. But the problem that I’m having is that when I run this application on my local machine it uploads the file successfully. But if I run this program on our server, I get this error message;
remote server returned an error: (550) File unavailable (eg, file not found, can not access the file), on this line ‘objFTPRequest.GetRequestStream();’.
Does anybody know why? Do I need to configure the firewall or something? Here is my code;
FileInfo objFile = new FileInfo(filename);
FtpWebRequest objFTPRequest;
// Create FtpWebRequest object
objFTPRequest = (FtpWebRequest)FtpWebRequest.Create(new Uri("ftp://" + ftpServerIP + "/outbox/" + objFile.Name));
// Set Credintials
objFTPRequest.Credentials = new NetworkCredential(ftpUserName, ftpPassword);
// By default KeepAlive is true, where the control connection is
// not closed after a command is executed.
objFTPRequest.KeepAlive = false;
// Set the data transfer type.
objFTPRequest.UseBinary = true;
// Set content length
objFTPRequest.ContentLength = objFile.Length;
// Set request method
objFTPRequest.Method = WebRequestMethods.Ftp.UploadFile;
// Set buffer size
int intBufferLength = 16 * 1024;
byte[] objBuffer = new byte[intBufferLength];
// Opens a file to read
FileStream objFileStream = objFile.OpenRead();
// Get Stream of the file
Stream objStream = objFTPRequest.GetRequestStream();
int len = 0;
while ((len = objFileStream.Read(objBuffer, 0, intBufferLength)) != 0)
{
// Write file Content
objStream.Write(objBuffer, 0, len);
}
objStream.Close();
objFileStream.Close();
asked Jul 4, 2013 at 13:37
chosenOne ThabschosenOne Thabs
1,4243 gold badges20 silver badges38 bronze badges
I met the same problem, and this is what I did:
- Check the OS has the right to write. Find the ftp folder =>right
click=>properties=>security, then you must know what you should do - Check the ftp server open the write right to the user you logged. Open IIS=>click the ftp site=>ftp Authorization Rules=>add allow rules=>choose a user or group to set the rights
- Check the the dir on the ftp server, do the same thing on item 2.
I can use four pictures to show the rights to be set:




Irshad
3,0335 gold badges28 silver badges51 bronze badges
answered Jul 9, 2013 at 17:07
2
It could be more simple.
I facing similar issue and i tried all the suggested solution but no one work.
I’m figure out in simple manner like this one : take a look
Wrong code at my end
Dim request As Net.FtpWebRequest = CType(FtpWebRequest.Create("ftp://xxx.xxx.xxx.xxx/files"), FtpWebRequest)
Change it in this simple one :
Dim request As Net.FtpWebRequest = CType(FtpWebRequest.Create("ftp://xxx.xxx.xxx.xxx/files/youfilename.ext"), FtpWebRequest)
then procced with fill request and send to server 🙂
That’s all.
Make sure that all permission on server work fine and u’re using right credential.
answered Apr 3, 2014 at 20:31
1
I found the solution. The problem is the Current Working Directory of the ftp user. If you type a url like ftp:///path/test.txt it is used as a relative path ro the working directory. For example CWD is /test then the used path is /test/path/test.txt. If you want to use an absolute path, you have to type the url like ftp:////path/test.txt. Then the file is uploaded in the folder /path/test.txt, without exception.
answered Oct 1, 2018 at 7:16
shamsham
6817 silver badges25 bronze badges
In order to resolve this issue, it is required to force the System.Net.FtpWebRequest command to revert back to the old behavior of how it used to work in .Net Framework 2.0/3.5 and issue the extra CWD command before issuing the actual command.
In order to do this, the following code needs to be placed before any instance of the System.Net.FtpWebRequest class is invoked.
The code below only needs to be called once, since it changes the settings of the entire application domain.
private static void SetMethodRequiresCWD()
{
Type requestType = typeof(FtpWebRequest);
FieldInfo methodInfoField = requestType.GetField("m_MethodInfo", BindingFlags.NonPublic | BindingFlags.Instance);
Type methodInfoType = methodInfoField.FieldType;
FieldInfo knownMethodsField = methodInfoType.GetField("KnownMethodInfo", BindingFlags.Static | BindingFlags.NonPublic);
Array knownMethodsArray = (Array)knownMethodsField.GetValue(null);
FieldInfo flagsField = methodInfoType.GetField("Flags", BindingFlags.NonPublic | BindingFlags.Instance);
int MustChangeWorkingDirectoryToPath = 0x100;
foreach (object knownMethod in knownMethodsArray)
{
int flags = (int)flagsField.GetValue(knownMethod);
flags |= MustChangeWorkingDirectoryToPath;
flagsField.SetValue(knownMethod, flags);
}
}
http://support.microsoft.com/kb/2134299
answered Nov 6, 2013 at 21:44
Taras KravetsTaras Kravets
1,3534 gold badges13 silver badges15 bronze badges
Make sure target folder «outbox» exists.
That was my problem with error 550.
Simply create target directory «output» before upload.
try
{
WebRequest request = WebRequest.Create("ftp://" + ftpServerIP + "/outbox");
request.Credentials = new NetworkCredential("user", "password");
request.Method = WebRequestMethods.Ftp.MakeDirectory;
using (var resp = (FtpWebResponse)request.GetResponse())
{
Console.WriteLine(resp.StatusCode);
}
}
catch (WebException ex)
{
FtpWebResponse response = (FtpWebResponse)ex.Response;
if (response.StatusCode == FtpStatusCode.ActionNotTakenFileUnavailable)
{
response.Close();
//already exists
}
else
{
response.Close();
//doesn't exists = it's another exception
}
}
answered Jul 31, 2017 at 12:30
![]()
I had this problem. Filezilla was fine, .net wasn’t. It was to a wordpress server.
To get it working, I changed the my code from this:
ftp://XXX.XXX.XXX.XXX//folder//» + txtFile.Text
to:
ftp://[FTPNAME]@XXX.XXX.XXX.XXX//» + txtFile.Text
and it now thankfully works.
I don’t know if this is specific to WordPress FTP folders.
answered Oct 25, 2017 at 9:43
![]()
In my case, there was a root folder referenced in my ftp address that was missing.
After to create the folder the problem was solved.
ftp://xxx.xxx.xx.xx:21//rootfolder/
answered Mar 16, 2018 at 18:04
![]()
I was also having the same issue. After monitoring the traffic with WireShark I understood the problem
I had set up a new FTP site on my local IIS FTP server named ‘testftp’
The ‘testftp’ site was pointing to a folder named d:ftp on my computer’s hard disk
I was getting the ‘550’ error whenever i tried to execute the line in bold in C# code below
ftpHostURL=»ftp://127.0.0.1/testftp/test.htm»;
request = (FtpWebRequest)WebRequest.Create(ftpHostURL);
request.Proxy = new WebProxy(); //——Proxy bypassing(The requested FTP command is not supported when using HTTP proxy)
request.Method = WebRequestMethods.Ftp.UploadFile;
request.Credentials = new NetworkCredential(ftpUserName, ftpPassword);
// uploadFilePath = "d://test//tt.txt";
using (var requestStream = request.GetRequestStream())
{
using (var input = File.OpenRead(uploadFilePath))
{
input.CopyTo(requestStream);
}
}
I tried a lot of solutions mentioned in various websites but nothing helped. Then I came across a site that suggested to use WireShark to monitor the traffic.
On monitoring the traffic using the RawCap Utility I saw that the application was trying to execute the code below
STOR testftp/test.htm
Then I understood the problem. IIS was expecting a folder named ‘testftp‘ to be there under the ftp root folder which was not there.
I was considering ‘testftp‘ as the name of the virtual folder created in IIS where as IIS understood it as a folder under the FTP root
Creating a folder named ‘testftp‘ under the FTP root folder solved my issue.
Hope this is helpful to someone
Regards
Mathew
answered Nov 5, 2019 at 5:49
mjk6035mjk6035
891 silver badge9 bronze badges
Just to throw my hat in the ring, I was getting the same error. When the FTPRequest was requesting files from the FTP Service on the same computer (same IP). In the request I was using the IP address of the machine but once I changed that to 127.0.0.1 it worked. interestingly enough, requests from other IP addresses were being processed and files downloaded, just not from itself.
Hope that helped someone.
answered Nov 16, 2015 at 1:50
dellyjmdellyjm
4181 gold badge5 silver badges10 bronze badges
When i had the same issue i tried everything above and after a day later i realize that the path which i created for uri having a white space in between «/» and the folder name
string uri="192.168.1.101/ Sync/Image.jpg";
the above string should be
string uri="192.168.1.101/Sync/Image.jpg";
this small mistake also throws the same error and it’s a valid error because this is not valid path for our file if it contains any white spaces between «/» and folder/file name
answered Sep 15, 2016 at 9:14
![]()
I was having the same problem, when i compared with the ftpuri and User Name Path it is resolved
When I create ftp access i have chose the path as /directory name
in the ftpuri when i included the directory name it gave the error and when i removed the directory name it is resolved.
ftpuri with error
«ftp://www.example.com/Project/yourfilename.ds»
ftpuri resolved
«ftp://www.example.com/yourfilename.ds»
ftp access folder
«/Project»
answered Jan 11, 2017 at 15:56
I too had this problem recently. What I found is that when I use ftpUploadFile the routine is trying to put the file in the root ftp folder. Normal command line ftp worked fine. However issuing a pwd command from the command line ftp revealed that this particular server was setting a different current directory upon login. Altering my ftpUploadFile to include this folder resolved the issue.
answered Feb 1, 2017 at 13:54
user2709214user2709214
1852 silver badges12 bronze badges
I’m trying to connect to our FTP on an IIS server and I’m having issues viewing files/folders. My manager is able to connect with no issues and it’s been a long time since he set it up. We added a Windows account for me and I’m able to connect, but unable to access folders. We set the permissions on the server so I have full control, but it still doesn’t seem to want to allow me to access it. Any idea what we might be missing? We’ve tried restarting the FTP service, but that didn’t seem to work either.
FileZilla logs:
Status: Retrieving directory listing...
Command: CWD /folder_name
Response: 550 Cannot create a file when that file already exists.
Error: Failed to retrieve directory listing
CMD:
ftp> cd folder_name
550 Cannot create a file when that file already exists.
asked Nov 26, 2014 at 16:59
JeremyTJeremyT
951 gold badge2 silver badges13 bronze badges
8
I figured it out last week. In the C:WindowsSystem32inetsrvconfigapplicationHost.config file, there was an extra set of permissions for the problem sub-directory that was causing the issues. Once I removed that, it worked as expected…
answered Dec 9, 2014 at 17:50
JeremyTJeremyT
951 gold badge2 silver badges13 bronze badges
I had a similar problem, receiving the following message when logged in to an IIS 8.5 FTP server:
ftp> cd folder_name
550 Cannot create a file when that file already exists.
I believe the problem started after changing the physical path of the FTP site when FTP authorization settings had already been applied. The fix was to delete the FTP site from within IIS, point it to the correct physical path, then re-apply authorization settings via the «FTP Authorization Rules» icon.
answered Apr 21, 2015 at 14:42
There’s more than one cause for this issue. It doesn’t help that FTP doesn’t accurately report the nature of the error. First, check the obvious. Make sure your FTP user account has the correct permissions to the ftp site. Second, make sure the ftp directory or any of the files you will be replacing isn’t marked «read-only.» Finally, check the least obvious cause, is your website still running in IIS? If so, stop the site and try it again. Quite often, the application worker process has one or more of your files open.
answered Jan 6, 2022 at 17:28
user148298user148298
2912 silver badges7 bronze badges
I’m trying to setup a ftp server for one of my websites hosted with IIS 8 on Windows Server 2012.
So I set up my website, everything worked fine and the website is reachable.
Then I rightclicked the website entry -> Add FTP publishing -> no assigned ip address, port 21, chose my self signed certificate -> next -> Authentification: Standard, Allowed access for user Administrator, Read/Write permissions checked -> Finished.
Now I tried to connect to the ftp server using Filezilla.
Everything is fine but I only have read-only access.
I searched google for this problem but nothing helped so far.
I checked folder permissions of the users Administrator/IIS_IUSRS but both should have the rights for read/write access.
I’m not very experienced with Windows server 2012 so I dont really know where to look for.
Anything I missed to configure?
asked Apr 22, 2014 at 17:12
![]()
3
If I remember correctly the IIS_IUSRS account only represents anonymous IIS users, but when you publish via FTP you have to log in, therefore giving read/write permissions to IIS_IUSRS has no effect in your case.
Now this is where things tend to become a bit weird. Even though you log in as Administrator (or any administrative level user you might have) that still may not be enough, because depending on the impersonation type and level, your IIS may be accessing the web site root folder as a different user.
The most common scenarios are IIS accessing that folder as «IUSR_[computer]» or as «Network Service». Please check your directory for permissions on those accounts. Granting the proper permissions to those account should (likely) solve your problem.
answered Oct 16, 2014 at 4:59
![]()
FjodrSoFjodrSo
2941 silver badge6 bronze badges
You need to add the rights to the folder security option (shortcut from iis : edit permission on the right)
I don’t know why set user in FTP autorizations rules isn’t enought…but any way that s how it works
answered Oct 18, 2015 at 16:22
![]()
FroggizFroggiz
3,0431 gold badge18 silver badges30 bronze badges
I know this is very old thread
just add some additional tips, in my case , just like Froggiz -san suggestion
I add permission on the folder, using right click, > properties > security
I add user and allow full control
answered Feb 18, 2022 at 3:49
![]()
Hi,
we are using the FTP server integrated within IIS on Windows Server 2012, 2016 and 2019.
In some use cases the FTP server returns «550 » with a whitespace at the end but without giving a reason like «550 File not Found» or «550 Access is denied».
This happens for example if an ftp client tries to check if a folder exists on the ftp server by sending «CWD /test». Since the folder «test» does not exist on the ftp server the the IIS-FTP server rightfully replies «550 »
but omitting the reason after the white space.
Since this is not strictly RFC 959 conform, some ftp clients abort the process, because they think, that an error occured on the connection.
Is this a bug in IIS-FTP or can I fix this behaviour in IIS-FTP somehow? Can I force IIS-FTP to give a reason?
(For many commands, IIS-FTP reacts correctly for example «250 CWD command successful.» or «234 AUTH command ok. Expecting TLS Negotiation.». But for «550» there seems to be some cases, when IIS-FTP just ommits the reason)
Thanks and Greetings from Germany
Oli4
- Remove From My Forums
-
Question
-
User-117341026 posted
I have recently setup a FTP server using FTP for IIS 7.5. The server requires TLS connection. While creating new folders, renaming and deleting files are successful, uploading files result in Error «550 The supplied message is incomplete. The signature was
not verified.». This is the first time I see this error and I have no idea how to fix it. What do I need to do to fix it?Status: Connection established, waiting for welcome message... Response: 220 Microsoft FTP Service Command: AUTH TLS Response: 234 AUTH command ok. Expecting TLS Negotiation. Status: Initializing TLS... Status: Verifying certificate... Command: USER XXXX Status: TLS/SSL connection established. Response: 331 Password required for friend. Command: PASS *************** Response: 230 User logged in. Command: OPTS UTF8 ON Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON. Command: PBSZ 0 Response: 200 PBSZ command successful. Command: PROT P Response: 200 PROT command successful. Status: Connected Status: Starting upload of C:xxxFileZilla_3.3.1_win32-setup.exe Command: CWD / Response: 250 CWD command successful. Command: PWD Response: 257 "/" is current directory. Command: TYPE I Response: 200 Type set to I. Command: PASV Response: 227 Entering Passive Mode. Command: STOR FileZilla_3.3.1_win32-setup.exe Response: 125 Data connection already open; Transfer starting. Response: 550 The supplied message is incomplete. The signature was not verified. Status: Retrieving directory listing... Command: PASV Response: 227 Entering Passive Mode. Command: LIST Response: 150 Opening BINARY mode data connection. Response: 226 Transfer complete. Status: Directory listing successful
Answers
-
User-117341026 posted
The problem has been resolved, it is related to TLS 1.1 and/or TLS 1.2. After disabling TLS 1.1 and TLS 1.2, connection with FileZilla is now fine.
-
Marked as answer by
Tuesday, September 28, 2021 12:00 AM
-
Marked as answer by
So I set up the FTP server properly in IIS 6.0. Initially I was not able to create or upload files to the FTP servers due to not having the Write permission. Then I gave all the permissions properly. After that I was able to create or upload files/directory using FileZilla(FTP client for Windows). But from my C# code I am still not able to upload a file into the ftp server using the same credentials that I have used in Filezilla.
The code I am using for uploading file to the FTP server:
var request = (FtpWebRequest) WebRequest.Create(string.Format("{0}/{1}", _ftpServer, fileName));
request.Method = WebRequestMethods.Ftp.UploadFile;
request.KeepAlive = false;
request.Credentials = new NetworkCredential(_userName, _password);
//request.UsePassive = false;
var ftpStream = request.GetRequestStream();
It is giving the 505 error at the last line in the given code.
So, why I am able to create and upload file/directory using the ftp client but not by my C# code?
What I am missing?
EDIT: From code I am able to create directory but not able to upload.
So I set up the FTP server properly in IIS 6.0. Initially I was not able to create or upload files to the FTP servers due to not having the Write permission. Then I gave all the permissions properly. After that I was able to create or upload files/directory using FileZilla(FTP client for Windows). But from my C# code I am still not able to upload a file into the ftp server using the same credentials that I have used in Filezilla.
The code I am using for uploading file to the FTP server:
var request = (FtpWebRequest) WebRequest.Create(string.Format("{0}/{1}", _ftpServer, fileName));
request.Method = WebRequestMethods.Ftp.UploadFile;
request.KeepAlive = false;
request.Credentials = new NetworkCredential(_userName, _password);
//request.UsePassive = false;
var ftpStream = request.GetRequestStream();
It is giving the 505 error at the last line in the given code.
So, why I am able to create and upload file/directory using the ftp client but not by my C# code?
What I am missing?
EDIT: From code I am able to create directory but not able to upload.
Я пытаюсь подключиться к нашему FTP на сервере IIS, и у меня возникают проблемы с просмотром файлов / папок. Мой менеджер может связаться без проблем, и прошло уже много времени с тех пор, как он его настроил. Мы добавили учетную запись Windows для меня, и я могу подключиться, но не могу получить доступ к папкам. Мы установили разрешения на сервере, чтобы у меня был полный контроль, но он все еще не хочет, чтобы я получил к нему доступ. Есть идеи, что мы можем упустить? Мы попытались перезапустить службу FTP, но это тоже не сработало.
Журналы FileZilla:
Status: Retrieving directory listing...
Command: CWD /folder_name
Response: 550 Cannot create a file when that file already exists.
Error: Failed to retrieve directory listing
CMD:
ftp> cd folder_name
550 Cannot create a file when that file already exists.
Я понял это на прошлой неделе. В файле C:WindowsSystem32inetsrvconfigapplicationHost.config был дополнительный набор разрешений для подкаталога проблемы, который вызывал проблемы. Как только я удалил это, это работало как ожидалось …
У меня была похожая проблема, получая следующее сообщение при входе на FTP-сервер IIS 8.5:
ftp> cd folder_name 550 Невозможно создать файл, если этот файл уже существует.
Я считаю, что проблема началась после изменения физического пути к FTP-сайту, когда параметры авторизации FTP уже были применены. Исправление состояло в том, чтобы удалить FTP-сайт из IIS, указать правильный физический путь, а затем повторно применить параметры авторизации через значок «Правила авторизации FTP».
User-386080242 posted
Hi,
we are using the FTP server integrated within IIS on Windows Server 2012, 2016 and 2019.
In some use cases the FTP server returns «550 » with a whitespace at the end but without giving a reason like «550 File not Found» or «550 Access is denied».
This happens for example if an ftp client tries to check if a folder exists on the ftp server by sending «CWD /test». Since the folder «test» does not exist on the ftp server the the IIS-FTP server rightfully replies «550 » but omitting the reason after
the white space.
Since this is not strictly RFC 959 conform, some ftp clients abort the process, because they think, that an error occured on the connection.
Is this a bug in IIS-FTP or can I fix this behaviour in IIS-FTP somehow? Can I force IIS-FTP to give a reason?
(For many commands, IIS-FTP reacts correctly for example «250 CWD command successful.» or «234 AUTH command ok. Expecting TLS Negotiation.». But for «550» there seems to be some cases, when IIS-FTP just ommits the reason)
Thanks and Greetings from Germany
Oli4