Недопустимое имя файла или номер (ошибка 52) Bad file name or number (Error 52)

При попытке доступа к заданному файлу возникла ошибка. An error occurred trying to access the specified file. Эта ошибка имеет следующие причины и способы решения: This error has the following causes and solutions:

Оператор ссылается на файл с номером файла или именем файла, которые: A statement refers to a file with a file number or file name that is:

Не определены в операторе Open либо был определен в операторе Open, но с тех пор закрыт. Not specified in the Open statement or was specified in an Open statement, but has since been closed. Укажите имя файла в операторе Open. Specify the file name in an Open statement. Обратите внимание, что если оператор Close выполнить без аргументов, возможно, все открытые в текущий момент файлы будут ненамеренно закрыты, тем самым сделав недействительными все номера файлов. Note that if you invoked the Close statement withoutarguments, you may have inadvertently closed all currently open files, invalidating all file numbers.

За пределами диапазона номеров файлов (1–511). Out of the range of file numbers (1 — 511). Если кодом генерируются номера файлов по алгоритму, убедитесь, что номера являются допустимыми. If your code is generating file numbers algorithmically, make sure the numbers are valid.

Существует недопустимое имя или недействительный номер. There is an invalid name or number.

Имена файлов должны соответствовать соглашениям, принятым в операционной системе, а также соглашениям по именованию файлов в языке Basic. File names must conform to operating system conventions as well as Basic file-naming conventions.

В Microsoft Windows используются следующие соглашения по именованию файлов и каталогов: In Microsoft Windows, use the following conventions for naming files and directories:

Имя файла или каталога может состоять из двух частей: имени и необязательного расширения. The name of a file or directory can have two parts: a name and an optional extension. Две части разделяются точкой, например, myfile.new. The two parts are separated by a period, for example, myfile.new.

Имя может содержать до 255 знаков включительно. The name can contain up to 255 characters.

Имя должно начинаться с буквы или цифры. The name must start with either a letter or number. Оно может содержать любые прописные или строчные знаки (имена файлов не чувствительны к регистру клавиатуры): кавычки («), апостроф (‘), косую черту (/), обратную косую черту (**), двоеточие (:) и вертикальную черту (|**). It can contain any uppercase or lowercase characters (file names aren’t case-sensitive) except the following characters: quotation mark («), apostrophe (‘), slash (/), backslash (**), colon (:), and vertical bar (|**).

Имя может содержать пробелы. The name can contain spaces.

Следующие имена зарезервированы и не могут использоваться для файлов и каталогов: CON, AUX, COM1, COM2, COM3, COM4, LPT1, LPT2, LPT3, PRN и NUL. The following names are reserved and can’t be used for files or directories: CON, AUX, COM1, COM2, COM3, COM4, LPT1, LPT2, LPT3, PRN, and NUL. Например, если попытаться присвоить файлу имя PRN в операторе Open, принтер по умолчанию просто станет адресатом для операторов Print # и Write #, направляемых в номер файла, который указывается в операторе Open. For example, if you try to name a file PRN in an Open statement, the default printer will simply become the destination for Print # and Write # statements directed to the file number specified in the Open statement.

На компьютерах Macintosh имя файла может включать любой знак за исключением двоеточия (:), а также может содержать пробелы. On the Macintosh, a file name can include any character except the colon (:), and can contain spaces. Использование символов Null (Chr(0)) в именах файлов не допускается. Null characters (Chr(0)) aren’t allowed in any file names.

Для получения дополнительной информации выберите необходимый элемент и нажмите клавишу F1 (для Windows) или HELP (для Macintosh). For additional information, select the item in question and press F1 (in Windows) or HELP (on the Macintosh).

Поддержка и обратная связь Support and feedback

Есть вопросы или отзывы, касающиеся Office VBA или этой статьи? Have questions or feedback about Office VBA or this documentation? Руководство по другим способам получения поддержки и отправки отзывов см. в статье Поддержка Office VBA и обратная связь. Please see Office VBA support and feedback for guidance about the ways you can receive support and provide feedback.

Fixing invalid characters and colliding file names

When you try to create, rename or save files, two common errors might occur that will prevent your file from syncing: invalid characters and colliding filenames.

Colliding filenames

This error happens when you try to create, rename or save a file to a folder that already contains a file with the same name.

There are two rules to watch out for when you name your files:

• Tresorit filenames are case insensitive, which means that A.txt and a.txt are considered the same.
• Filenames with the same Unicode normalization are considered the same.

Invalid characters and filenames

You can upload all files to the cloud with a filename that doesn’t contain any control characters or a / (forward slash). Also, the filename can’t be any of the filenames reserved by Tresorit application (. and ..).

Invalid filenames on Windows

If you wish to download your files to a Windows Operation System, there are additional rules the filename needs to comply with.

• The filename doesn’t contain any of the following characters: » (double quote), * (asterisk), (greater than), ? (question mark), \ (backslash), | (pipe), / (forward slash), : (colon)
• The filename can’t end with a space or a period
• The filename can’t contain any of the names reserved by Windows

How to fix invalid filenames

Validation rules are stricter on Windows than on any other devices, that’s why in some cases you will need to rename files when you download them from the cloud. When a file contains invalid characters, you will see a notification in orange in your Tresorit client.

📝 Note: If you don’t use Tresorit on a Windows PC, you can ignore this notification. However, we advise you to review your filenames before you share your files with others — invalid filenames won’t sync on Windows devices.

1. Click the notification arrow.
2. A list of filename conflicts will appear on a pop-up. You can either choose to rename all files using the suggestions or edit filenames one-by-one.

Click on a conflict file, then click Rename.

Click Rename to confirm.

Invalid Filename

The name specified for at least one of the files in the archive is not a valid Windows filename. It may include characters that are not allowed in Windows filenames, it may be too long, or it may contain a name that is reserved for a system device such as the printer. WinZip ® will not be able to extract the file using the name as it is specified in the archive.

WinZip does not list files with invalid names in the main window because it cannot predict what will happen if you attempt to extract the file: the result depends on the filename, the archive format (Zip, LZH, etc.), and other factors. Therefore if you were to attempt to (for example) view the file, WinZip would not know the name under which the file had been stored and could not successfully open the extracted file or delete it after viewing.

Although WinZip will not automatically extract the file for operations such as viewing, you may be able to extract it manually. Just be aware that the extraction might not be successful and that, if it is, the filename on disk will probably not be the same as the filename specified in the archive. With Windows 8, Windows 7, or Windows Vista; either click the Unzip to drop down arrow in the Actions pane or choose Unzip to My PC or Cloud on the 1-click Unzip drop down menu in the Unzip/Share tab. To try this in Windows XP, simply extract from the archive using the Extract dialog box, making sure that you choose All files/folders in archive in the Files area.

Note: If no files display in the WinZip window, because all of them have invalid file names, you will have to add a file to the Zip file before trying to extract files.

Invalid file names windows

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Executing the command wmic LogicalDisk where DriveType=3 get DeviceId,Size,FreeSpace /Format:csv returns the error Invalid XSL format (or) file name.

I have windows 7 64 bit.

Answers

>>returns the error Invalid XSL format (or) file name

In my experience, it’s a known issue, here are some workarounds:

(1) Change the International setings to English (United States), reboot

(2) Specify the csv path, try this command:

The «en-us» will be different for different locales, please change it based on your system.

Because this issue is more related to the product issue, so I think this forum should be more appropriate: http://social.technet.microsoft.com/Forums/en-US/home?forum=w7itprogeneral

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Git pull invalid Windows file names

I’m working a shared project using git for version control. I’m on windows while my partner is on Unix.

My partner has named some files with .txt . When I try to pull these files they are not accepted as the and > are invalid characters for Windows. This is fine, I don’t need to touch the files. However, they are added to my commit as deleted. So, if I push then I’ll delete these files which I don’t want to do.

I can’t use git reset —hard as it finds an invalid path for each of these «deleted» files.

Is there a way to exclude these files from my commits? I’ve tried adding to my .git/info/exclude but that didn’t work.

2 Answers 2

Ignoring doesn’t help if the files are tracked already.

Use Sparse checkout to skip those files.

You would need to get your partner to change the names to be something that is also valid on Windows. After they have renamed them, what I’d do is this:

1. Backup any changes that you only have locally (both uncommitted AND committed but not pushed).
2. Run git reset —hard where is any commit from before the files were added.
3. Run git pull to get all the way to the latest revision (where the files are renamed).
4. Restore your backed up changes from 1.

This should then get the newer revision where the files aren’t named in this, to Windows, illegal way, and they won’t be deleted (or ever created) from under git by the OS 🙂

P.S. I know this is an old question, but I’ve been getting this issue recently, so hopefully the solution I’ve arrived at can help others as well.

EDIT:

To avoid this happening again, your partner can add a pre-commit hook that will stop them from committing files with names that would not be allowed on Windows. There’s a sample/example often in pre-commit.sample. I’ve changed the bit a little in the past and end up with something like:

]\0′ bit is the important part that I’ve changed a little. It defines all the allowed ranges of characters, and the example one only disallows «non-ascii» characters (which is what the comment at the top says), but there are also ascii characters that are not allowed in file names on Windows (such as ? and : ).

All the allowed characters are removed, and if there’s anything left ( wc -c != 0 ) it errors. It can be a bit difficult to read, as you can’t see any of the disallowed characters. It helps if you have a list of the char ranges to look at when reading or editing it.