FTP plugin problem | errorcode 123

Евгений Пикалов

Hi there. I was trying to use notepad++ ftp plugin to have access to my website files. I only can see my website. If I try to open them somehow I have the following error:
Failed to create directory C:\Users\PIikalov\AppData\Roaming\Notepad++\plugins\Config\NppFTP\Cache\odessasturgeon.com|turgeonFTP@85.238.100.83\Configs\ with errorcode 123
Download of /Configs/Counters.config failed

I tried different files to open, have installed different versions of Notepad++(the latest one x86 and x64, 7.1 x86). I`ve got Windows 7x64 on my PC.
I look through the topics here and on other forums. I can t found this “errorcode 123” nowhere.
If somebody knows how to solve this problem please tell me. Thanks.
P.S.: Sorry for my English.

Евгений Пикалов

By the way I forgot to mention that I also tried to open Notepad++ as Administrator and put on all rights for all users.

PeterJones

I did a quick search in the NppFTP GitHub repo, and found that the “Failed to create directory … with errorcode …” message comes from PathUtils.cpp PU::CreateLocalDir(), which is calling the Windows API SHCreateDirectoryEx(). MSDN’s System Error Codes shows that errorcode 123 is ERROR_INVALID_NAME: “The filename, directory name, or volume label syntax is incorrect.”

I see a vertical bar in the name you quoted (C:\Users\PIikalov\AppData\Roaming\Notepad++\plugins\Config\NppFTP\Cache\odessasturgeon.com|turgeonFTP@85.238.100.83\Configs\): when I try to create Windows filenames or foldernames with a vertical bar, Windows won’t let me. Assuming you didn’t edit the error message to hide proprietary information, I think that’s what’s causing the error. NppFTP should check for invalid characters, and possibly replace with a valid character, before trying to call SHCreateDirectoryEx.

Given that, I suggest that you create an issue at the NppFTP bugtrack on GitHub, with the full text from your initial post here, plus a link to this thread https://notepad-plus-plus.org/community/topic/15373/ftp-plugin-problem-errorcode-123.

Евгений Пикалов

@PeterJones , thank you so much. I was looking for this pathethic mistake for few days.