Folder names cannot include any of the following characters что делать
Folder names cannot include any of the following characters что делать
This forum is closed. Thank you for your contributions.
Asked by:
Question
I’m trying to install a pc game but for some reason at the end before the installation after choosing the file path, the above error comes up.
HOW DO I GET AROUND THIS?
All replies
It sounds like that error means that you, or the game, is creating a folder with an invalid character in the name of the folder. You need to contact support for whoever makes the game. unfortunately, the MSDN Subscriptions team doesn’t make any video games, so your post here is off topic.
Please review the topic of the forum you’re posting in before posting your question. Moving your post to the off topic forum.
MSDN and TechNet Subscriptions Support
Read the Subscriptions Blog!
Folder names cannot include any of the following characters что делать
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Hi, I am trying to upload the file in SharePoint library, and that filename contains some special character, so I am getting below message:
After removing special character able to upload.
Answers
It’s by-default or you can call it’s a design behavior of the SharePoint.
Request you to have a look at following articles for better clarity:
Information about the characters that you cannot use in site names, folder names, and file names in SharePoint: http://support.microsoft.com/kb/905231
Error Message: Filename is Invalid or Cannot Contain Any of the Following Characters: http://support.microsoft.com/kb/177506
Hi, I am trying to upload the file in SharePoint library, and that filename contains some special character, so I am getting below message:
After removing special character able to upload.
I’m not sure what O/S you are using or how you were able to load filenames with special characters onto your filesystem but for Win 7, 64 Bit O/S these are characters not allowed for file and path names (though the path characters list left some out I think). Although you can search on the net for what characters are not authorized for your O/S and possibly disk format (i.e. fat32 or NTFS) if that matters which I would not think it does.
Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I’ve been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become «unstable» or something to that effect. 🙂 I can only surmise that is due to Global Warming of the threads.
Folder names cannot include any of the following characters что делать
Gianny J. Sabattino S. wrote on 12-Mar-2009:
Hello
I’m entering this newsgroup for first time, and my native languaje is
spanish. sorry for my english.
I’m recently migrate from Inno 5.0.7 to 5.2.23
The setup generated with this new version generates the following message
Markus Wolf replied on 12-Mar-2009:
Gianny J. Sabattino S. wrote:
(snip)
You AppName contains invalid characters (‘/’). See the error message
you’re getting.
This is a Windows restriction.
If it really worked with an older version of Inno Setup (which I doubt)
Dean Earley replied on 12-Mar-2009:
Markus Wolf wrote:
(snip)But that isn’t used in any of the paths is it? (Except maybe the
uninstall key name via AppID)
—
Dean Earley (✉icode.co.uk)
Gavin Lambert replied on 12-Mar-2009:
Quoth Gianny J. Sabattino S.:
(snip)
I doubt this could work. The group name needs to be a relative path,
andis an absolute path.
If you want to install an icon in the startup location, do that with an
[Icons] entry that refers toinstead of to .
Gianny J. Sabattino S. replied on 13-Mar-2009:
Ok. I comment DefaultGroupName=
line and setup works.
I’ll have to read the help file again because i see Inno 5.2.3 have
incompatibility with scripts thah work in earlier versions.
Thans for Help.
«Gavin Lambert» escribi? en el mensaje de
Gavin Lambert replied on 13-Mar-2009:
Quoth Gianny J. Sabattino S.:
(snip)This isn’t a new thing. If it worked in the past, it was by
coincidence, not design.
Ed Dressel replied on 09-Apr-2009:
(snip)
why isn’t this a compile time error, not a runtime error?
Ed Dressel replied on 09-Apr-2009:
(snip)
doubt away—it worked for me (see new post)
why isn’t this a compile time error, rather than a runtime error?
Ed Dressel replied on 10-Apr-2009:
(snip)
FWIW, my code worked fine in the preivous version, just not the new version.
Gavin Lambert replied on 13-Apr-2009:
Quoth Ed Dressel:
(snip)
Because AppName may include constants, and thus evaluation is deferred
until runtime.
Помогоите с пачем ПЛЗ!
TheSiD Хм. Интересная проблема. Остаётся предположить, что испорчена запись об игре в реестре. Проверь. До пропатчивания должно быть следующее:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Ascaron Entertainment\Sacred Underworld]
@=»Release»
«InstallLocation»=»C:\\Program Files\\Ascaron Entertainment\\Sacred Underworld»
«Language»=»ENG»
«Version»=»2.0.2.21»
«InstallKey»=»
«Updated»=»NONE»
По большому счёту, на эту проблему можно забить и распаковать содержимое патча непосредственно в папку с игрой при помощи Inno Setup Unpacker`а. Я давал ссылку в одной из недавних тем пару дней назад.
«InstallLocation»=»C:\\Program Files\\Ascaron Entertainment\\Sacred Underworld» и тут не все понятно, у меня: «C:\\PROGRA
1″, это DOS имя, надеюсь это немешает мне пачицца, или.
мля. пошел по тупому, но всеравно не помогло.
в «InstallLocation» поменял у себя с «C:\\PROGRA
1″ на «C:\\Program Files\\Ascaron Entertainment\\Sacred Underworld» но легче не стало.
в «Version» с «2.0.2.20» на «2.0.2.21». теже. только в профиль!
хм. ну кто такой стар форс я знаю, (еще на космических рейнджерах и принсе персии в него вляпался) но у меня на сакреде его нет, оригинальный 2.21 был вабше без всякой защиты и шел ны 2-х дисках. точнее болванках, ну типа коробку я невидел, мне его просто записали. и всетаки вопрос открыт, куда сд кей писать?
ЗЫ
или «http://download.ascaron.com/sacreduw/retail_patch_2.0.2.4_RUS.exe» им защищен?
ЗЫ
если у кого есть вопросы по сакреду. и не только, то бращацца только к ним! 😉
Ща все будете до-о-олго смеяться =)
Неуспел я сказать спс, как уже нашел новую траблу. Пставил я пач (http://download.ascaron.com/sacreduw/retail_patch_2.0.2.4_RUS.exe), и с СД кеем (http://sacred.net.ru/uploads/SacredUWTrue_akella.rar) все гуд, но сакред начал жутко тупить! При старте игры, в меню, при загрузке, в игре. кароче везде! Причем просто подвисает на долю сек, но постоянно. и эта лажа появилась именно после пача, до этого гама работала практически идеально.
А теперь мой, уже любимый вопрос, ЧТО ДЕЛАТЬ? КАК БЫТЬ. у когонить такое еще было?
ЗЫ
отрубаю звук становится немнооого лехче, а остальные настроики вашше ниче не дают.
спасибо, но у меня винда настроена хорошо, без всякой лишней хрени, с дровами уже тож порулил. кароч есть еще одна идея. просто поставлю сакред с пачем на другую машину и поюзаю, или просто на другую винду.
ЗЫ
слышал XP SP3 вышел..
помогите распаковать архив выдает такую хрень
P.S. Сам я играю в английскую версию игры с записанной болванки, имитирующей лицензионный диск.
начала 2004 года) драйверы для своей видюшки и попробуй с ними.
2. Певеди игру в оконный режим (где-то в конфиге должна быть такая опция), при разрешении 1024×768 игра всё равно будет идти на полный экран, но проблема может исчезнуть. В оконном режиме игра совсем по другому работает с видеодрайвером.
3. Попробуй (если есть такая возможность) временно поменять себе видюшку на nVidia и поиграть с ней. Или найди другой комп с видюшкой nVidia и попробуй на нём. По крайней мере станет 100% ясно, виновата ли в этой проблеме игра или же видеокарта.
Folder names cannot include any of the following characters что делать
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I have found reports of this error being generated if the file path is too long, but all users are accessing this from a shared drive, and even if the share name is taken into account the file path and name are easily under 100 characters.
I have 3 users on 3 different systems reporting this issue, so I don’t think it is user error.
The workstations are running Windows 7 Pro, SP1. The server is Windows Server 2003 R2 Enterprise, Service Pack 2.
The users are located at a remote site, and accessing the share over a site to site VPN. There are XP workstations at the site as well, that do not appear to be having the issue.
Any help, suggestions, or guidance is greatly appreciated!
All replies
This error should occurs when the name contain invalid characters. Please simply rename the folder just contain normal letter like “aaa” to see if the same issue occurs.
Furthermore, please create another share folder to these users and let them try renaming for test.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Neither the new or the old files or folder name contain invalid characters. If the user tries again with the same filename, they are able to rename the file without an issue, so the error does not actually seem to be being triggered by invalid characters in the filename.
Thank you for your update.
That’s seems quite odd. Another question: could these folders renamed on local server with administrators?
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
One interesting thing is that the error is a pop-up message box, rather than a alert balloon like it would be if you actually tried to rename a file with invalid characters. I have attached a screenshot (sanitized to remove identifying information).
I am trying to involve someone familiar with this topic to further look at this issue.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Thanks for your help, I would really like to try to get this resolved as soon as possible.
As you noted with the pop-up, this is definitely not the default behavior of Windows7. It is expected to be a non intrusive balloon.
The wording is also different from the general Windows error i.e. «cant» in place of «cannot» expected in windows errors.
I’d suggest you to look for 3rd party software on the PCs.
Does this happen in safe mode with networking?
Does it happen when you do clean boot using msconfig?
Can you replicate this error with a share on another server?
As an update, it is looking like the issue may potentially be due to the realtime scanning portion of the ESET antivirus. I am still in the process of try to confirm this, as users are still reporting getting it, but I have not gotten the error with realtime scanning disabled (of course, I also have had issues replicating it in the first place).
I will give another update if I determine this has resolved the issue, or if I have further troubleshooting.
Download process explorer from technet.
When the error window pops up again, run process explorer as Administrator and then drag the ‘find windows process'(sniper marker) icon on to this popup.
If its a user mode process, it should point you to the process throwing the error.
check the DLLs loaded in explorer.
Use shellexview.exe to disable the 3rd party shell extensions.
I have captured the log file as the issue happened. There are a couple of attempts here, the one where the issue happened is near the end of the file; I was trying to rename «2 3 45» to «4 5 6 2». No file extension on either of them, makes it easier to do multiple renames quickly that way.
I was doing a clean boot to minimize the noise from other applications, the only allowed items are the antivirus and the software I use to access this system remotely.
I have attached the same file as both a ZIP and the PML, just in case one or the other is blocked.
Thanks for your continued help on this issue!
Can you try installing the 3rd party softwares on a test system that has the issue?
I still believe it is caused by one of the 3rd party software installed on these systems.
I was able to test most of these softwares inside my test system to try and reproduce the issue.
However I could not manage to test the Dell(wave) encryption/drive protection software as it seems like hardware dependent.
So i’d suggest choosing a test system, then start uninstalling the 3rd party softwares one by one starting with the Dell drive protection.
Or you can go the other way around and take a vanilla system and install the standard softwares in your environment till the error occurs.
Based on my test i’d put my money on the drive protection s/w, however that is just an educated guess.
Outside of this approach it would take a lot of debugging to figure out who is throwing the error and requires direct access to these machines as well which requires to be worked through a paid support incident.
Sorry to intrude but i have precisely the same problem with the same setup. Did you find a solution to the problem?
I am getting this error frequently as well. The system here is running MSE and have very little third party software on it. It has been doing it since it was first installed. I think is is an x64 version issue as I have not experienced it on an x32 system I use at work.
I’m also getting this error from a Window 7 computer naming folders on a network share
Did anyone find a fix for this yet? I have 45 new Windows 7 pro x64 machines exhibiting this behavior on network shares that reside on ALL types of server operating systems: NT4 Server sp6a, Windows 2000 Server, Windows 2003 Server, Windows 2008 Server and even on Windows 7 x64 pro workstation shares.
I does not appear to happen when renaming files/folders on XP shares or Linux shares. Its only on Windows server shares and Win7 shares. Have not tested Vista shares (don’t have Vista).
I am now hesitant to rollout the rest of the 200+ workstations due to this annoying «feature».
This problem happens on Linux servers as well. Users will not find a fix for this as it’s a coding error in the operating system.
Don’t know if I would stop a rollout however as it isn’t a show stopper.
Mircosoft is very well known for ignoring theses sorts of problems so you will left in limbo.
I get this problem quite regularly and now highlight my change and press ^c if the rename is extensive before pressing enter.
When/if the message pops up I then rename (f2) again using ^v
Did anyone find a fix for this yet? I have 45 new Windows 7 pro x64 machines exhibiting this behavior on network shares that reside on ALL types of server operating systems: NT4 Server sp6a, Windows 2000 Server, Windows 2003 Server, Windows 2008 Server and even on Windows 7 x64 pro workstation shares.
I does not appear to happen when renaming files/folders on XP shares or Linux shares. Its only on Windows server shares and Win7 shares. Have not tested Vista shares (don’t have Vista).
I am now hesitant to rollout the rest of the 200+ workstations due to this annoying «feature».
I’d put my bottom dollar on that this is an issue within windows.
Normally, the error appears as a bubble in windows 7, but for some reason it comes up as a standard error message in this instance. I have a user on my network who is having the same issue.
Also, the standard windows 7 ‘bubble’ error uses the word can’t in the place of cannot (Tested on my unaffected machine).
More and more people are having the issue, Microsoft don’t appear to be doing jack about it. Meh.
Should also add that this is happening on my network when a particular user attempts to amend the name of a file hosted on a Windows Server 2008 R2 server from a Windows 7 machine running SP2 and all updates.
Considering rebuilding his machine and seeing if the error happens again.
Same exact issue here. We have Win 2008 R2 Server, remote user connect via Cisco AnyConnect VPN and uses Vista PC with PGP Encryption on it. Anyone got a solution for this? I would appreciate any help. Thanks in advance.
I’d like to throw my hat into the ring regarding this problem. Judging by what I’ve been reading and comparing it to my issue (Same renaming problem), I’d have to say it’s not a server problem and I’m not 100% sure it’s just a windows 7 problem. I have a NAS setup on a router and I have the renaming issue running from my Dell laptop running 7 pro x64. It didn’t happen when I had XP pro on another Dell laptop but now it happens quite frequently. It doesn’t happen, however, from any work machine running Windows 7 pro x64 and going to our work NAS, Server 2003 or any other server version that we run (we have 4 servers).
I have noticed that it SEEMS to happen more frequently when the laptop is running very slowly do to file transfers or other background activity. That COULD be my imagination but I don’t think so. I’m starting to think it may be a background process (maybe a pre-installed DELL utility) or even a virus/spyware/malware intrusion. I have run several virus/malware utilities and have more yet to run but I would have thought that I’d have found it by now if it was that.
I hope that someone out there is still on the case as I’m sure some bright guy or gal will eventually come up with the answer and I’d love to know what it is.