There are multiple symptoms that can arise when there is no root site in a SharePoint Web Application.
When checking out an Office file from SharePoint 2010 using the drop down (Edit Control Block) the following error shows: "This document could not be checked out. You may not have permission to check out the document or it is already checked out or locked for editing by another user"
In an Office application when you choose File | Save As and attempt to navigate to the SharePoint Site the following errors may occur: “File Path Not Found” or “Document Not Saved”
Users open Word documents from a MOSS 2007 server using Word 2010 running on Windows 7. Once the document opens in Word, File | Save As points to the Libraries\Documents folder on the C: drive. It should point to the location it was opened from which is the SharePoint Document Library. This means that the file cannot be saved directly back to the server. Users must instead save it locally and re-upload it to the MOSS 2007 document library.
Open a OneNote 2010 file from a SharePoint 2010 document library and type in the section or new page. Manually sync or wait for the automatic sync. Close the OneNote file and reopen it from the SharePoint 2010 site. The changes made initially are not synchronized to the OneNote 2010 file within the SharePoint document library.
These errors are caused by not having a root site in the SharePoint web application.
This happens because the above-mentioned scenarios (and many others) depend on web service or other RPC calls that get made to the root of the web application. If there is no root site, these calls cannot succeed.
Create a root site for the web application:
1. Go to Central Administration | Application Management | Create Site Collections. 2. Select the problem Web Application (Example: SharePoint-80) 3. For the URL, set it to http://<YourHostName>/ (Example: http://www.contoso.com) 4. Make the other site collection settings as needed and click ok.
In a network trace, a WebDAV OPTIONS request on the root site ("/") was sent from the client's WebClient (UserAgent: Microsoft-WebDAV-MiniRedir/6.1.7601) to the server: WEBDAV:Request, OPTIONS /
The server responds with a 404 (Not found): WEBDAV:Response, HTTP/1.1, Status: Not found, URL: /