Sharp "s" ß errors and SharePoint
In SharePoint, sharp "s", ß, in site names, file names, and links, can present errors. To avoid errors, use characters other than ß.
SharePoint 2007/SharePoint 2010
The following characters present problems when used in site or file names. Although they may appear correctly when items are saved, they do not appear correctly in browse paths, and the server cannot read the path or find the file. If a link contains a special character, the link might not open when clicked from within Microsoft Outlook.
Note: All other characters are supported. However, supported characters work only when both CENTRAL and the Winshuttle client program are version 10.3. If any Winshuttle program is earlier than version 10.3, the following characters do not work.
SharePoint 2010
Spanish:
If the file name or site name contains the following characters, the task cannot be opened from the client.
—
’
"
"
–
Dutch:
If the file name or site name contains the following characters, the task cannot be opened from the client:
—
’
„
"
–
German:
If the file name or site name contains the following characters, the task cannot be opened from the client:
—
’
„
"
–
French:
If the file name or site name contains the following characters, the task cannot be opened from the client:
Ÿ (Caps)
Œ
œ and its uppercase
æ and its uppercase
’
"
"
–
—
Special hyphen (hyphen of French character "–")
SharePoint 2007
German:
If eszett ß is in the path of file, tasks cannot be opened from the client.
If the site name contains Ä, Ö, Ü, or ß (in caps), all the files produce the error "Der Wert darf nicht NULL sein" when opened.
If the site name contains Ä and file name is ß (in caps), the following error message is displayed: Das System kann die angegebene Datei nicht finden. (Ausnahme von HRESULT: 0x80070002)
If the site name contains Ö and file name contains Ö, no error results.
If the site name contains Ö and file name contains ß (in caps), the following error message is displayed: Das System kann die angegebene Datei nicht finden. (Ausnahme von HRESULT: 0x80070002)