none
Unable to rename folders and files on SharePoint mapped drive.

    Question

  • I just installed a fresh copy of Windows 7 and have mapped a drive to my SharePoint "Shared Documents" folder.  I am able to open, save, and delete files and folders.  However, I am unable to rename files and folders.  No matter how long of short of a name I use I get the following error:

     

    "The file name you specified is not valid or too long.  Specify a different file name."

     

    I've mapped the "S" drive to http://hostname.domain.com/Shared Documents/

     

    I am a SharePoint Admin, and have confirmed that if I do not have this problem if I log into SharePoint with IE.  I have also confirmed that others are not experiencing this issue. Also, this issue did not exist on my previous installation of Windows 7.  Therefore I assume this is a config issue.

     

    Also, in "My Computer" it shows the mapped SharePoint drive as a "FAT" filesystem.


    Wednesday, April 20, 2011 7:44 PM

Answers

  • Found the answer.  When I originally mapped the drive it I used a / at the end of the URL:

    https://hostname.domain.com/Shared Documents/

     

    When I remapped the drive without the / the error went away:

    https://hostname.domain.com/Shared Documents

     

    I've even double checked and remapped with the / at the end, the the problem is there. 

    • Marked as answer by Alex Weeks Wednesday, April 20, 2011 11:04 PM
    Wednesday, April 20, 2011 11:04 PM

All replies

  • Did some more testing. From my mapped drive, I can create new folders and files, and delete them.  I created a folder in Windows Explorer, when I tried to give a name it gave me the above error and saved the folder as "New Folder".  No matter when I try, I cannot rename this folder unless I log into the SharePoint interface.

    Next, I tried this from the command line.  I moved to my S drive, and did a "mkdir test" and was able to create a folder named test.  Next I tried to "rename test testing" and received the following error:

    The filename, directory name, or volume label syntax is incorrect.

    The full path is S:\test.  If I do a "mkdir testing" I am able to create the folder.  If I try to rename the folder in Explorer, it gives me the "file name not valid or too long".  I'm obviously well under the 260 character limit, so there has to be something wrong with the fiel name, or drive mapping.

    Also, when I "dir" the S drive it tells me the drive has no label.  "Volume in drive S has no label."

    I'm having the same issue with files. I can create a file, modify it, delete it, but can't rename it.

     

    Wednesday, April 20, 2011 10:26 PM
  • Found the answer.  When I originally mapped the drive it I used a / at the end of the URL:

    https://hostname.domain.com/Shared Documents/

     

    When I remapped the drive without the / the error went away:

    https://hostname.domain.com/Shared Documents

     

    I've even double checked and remapped with the / at the end, the the problem is there. 

    • Marked as answer by Alex Weeks Wednesday, April 20, 2011 11:04 PM
    Wednesday, April 20, 2011 11:04 PM
  • RE: Also, in "My Computer" it shows the mapped SharePoint drive as a "FAT" filesystem.

    Alex, my mapped SharePoint drive is also showing "FAT" filesystem.  Did you find any more info if this is OK or something need to be done to convert to NTFS?  Thanks for your respond.
    Wednesday, June 08, 2011 6:54 PM
  • Hi, i also have same issue, removing the / at the end does not help me.  I found that if i create a document library with no spaces or using an _ as a space the problem goes away.
    Thursday, June 30, 2011 3:16 AM
  • Can’t rename/ delete/ copy file? Please look that, LONG PATH Error Fixer helped me in this situation. Actually “Long Path Tool” is so usefully for this problem. So try it today.

    Saturday, October 20, 2012 4:52 PM
  • I had the same issue, and my drive was not mapped with a "/" at the end.

    To fix my problem, I had to re-map my drive as "https://hostname.domain.com" Previously I had not had the drive mapped beginning with "http" as opposed to "https".

    Wednesday, May 29, 2013 3:13 PM
  • Here is another solution.

    When mapping your drive, you can use UNC path and put @ssl at the end of your SharepointServerName

    Using \\

    SharepointServerName[at]ssl\sites\sitename\documents

    Unfortunately the reply box won't let me type @ssl in the UNC path. :(

    Regards,

    Wednesday, July 31, 2013 1:37 PM
  • Hello,

    This is what solved the issue for me:  

    After trying the approaches suggested in the previous posts I decided to do a re-map.

    The last portion of my path was "Shared%20Documents", in my new mapped drive path I removed "Shared%20Documents" and then I was able to rename files.

    With the old path I could create/delete documents, but I could Not move or rename them.

    I hope this helps anyone facing the reported issue.

    • Proposed as answer by Subterraneancr Friday, August 23, 2013 8:47 PM
    Friday, August 23, 2013 8:47 PM
  • Make sure that that the link does not contain converted URL characters like spaces.

    OK     net use S: "http://hostname.domain.com/Shared Documents" ; also best practice to put the quoutes around a webdav link (that contains spaces).

    NOK   net use S: "http://hostname.domain.com/Shared%20Documents" , because the %20 replacement of the space character.

    The space character becomes "%20" in the URL in your navigator. The same applies for other "special" characters ; they are in converted. This causes problems with net use and webdav. A trailing / sometimes causes problems in third party webdav clients. Trial and error (50% chance) will show you what to use.



    • Edited by Sundari-expert Tuesday, January 14, 2014 4:11 PM
    • Proposed as answer by BenB123 Friday, January 06, 2017 9:58 AM
    Tuesday, January 14, 2014 4:10 PM
  • This is what fixed it for me, thank you. I had both the / at the end of the link and the %20 as the space marker in "Shared Documents" so I removed these and the problem was solved. 

    Interestingly, I was not able to use quotation marks either side of the link, as it then reported an error of the address being unaccessible. It was happy to accept the link with the space in "Shared Documents" without the quotation marks though, and I can now rename files and folders.

    Friday, January 06, 2017 10:01 AM
  • None of the above solutions fixed it for me.
    I had the same problem with cloudstorage provider Stack (firm TransIP) in Holland.
    My connection-string look something like this: https://MyName.stackstorage.com/remote.php/webdav/
    The solution was "using only lowercase characters"... like this: https://myname.stackstorage.com/remote.php/webdav/
    You'll have to see it to believe it, but this was the fix for me ;-)


    • Edited by Gordo_S Wednesday, January 11, 2017 10:17 AM
    Wednesday, January 11, 2017 10:15 AM
  • We had the same error message in this configuration:

    Our SharePoint site (SP 2013 on Window Server 2012 R2) is available via HTTPS (let's say at URL https://YourServer )

    In IIS we have a web site for port 80 as well (like http://YourServer ) with HTTP Redirect configured (see this page for details: https://technet.microsoft.com/en-us/library/cc755042(v=ws.11).aspx ) as:

    Redirect requests to this Destination checked: https://YourServer$S$Q

    Redirect all requests to exact destination (instead of relative to destination) checked.

    In this case SharePoint Folders mapped in Windows Explorer for the HTTP site seem to work, but file renaming fails with the error message:

    "The file name you specified is not valid or too long.  Specify a different file name."

    Solution: Disconnect the mapped folder and reconnect it using HTTPS, for example:

    NET USE Y: "https://YourServer/DocLib/"

    Monday, April 24, 2017 12:48 PM
  • This worked for me!  After installing Office 365 on a users PC and then mapping the SharePoint library through Windows Explorer the user was not able to rename or copy files into folders on his directory. After adding the @ssl to the end of the SharePoint server name (sharepointserver.cloudservice.com@ssl\LibraryName) the user was able to correctly copy files into folders and rename folders. Whew!

    Christopher Valentine

    • Proposed as answer by C_Valentine Friday, June 23, 2017 5:23 PM
    Friday, June 23, 2017 5:23 PM