Fix SharePoint 2013 File Not Found Error When Creating a Web Application
Question details
The user encounters a 'File not found' error while attempting to create a new web application in SharePoint 2013 Central Administration.
- Product
- SharePoint 2013 Server
- Device & OS
- not provided
- Scenario
- Creating a new web application via the SharePoint Central Administration interface.
- Observed behavior
- The web application populates in the Central Administration list, but underlying IIS configuration files, sites, and virtual directories fail to be created due to the 'File not found' error.
Ensure you are logged into the SharePoint Server as a Farm Administrator and have full access to the Internet Information Services (IIS) Manager.
Verify IIS Path Accessibility and Permissions
A missing or inaccessible physical path during IIS provisioning often triggers the file not found error.
When Central Administration attempts to create a web application, it provisions IIS configuration files and virtual directories. If the target path is missing or restricted, the provisioning process will fail even though the web app appears in the database.
Press Win + R on your server keyboard, type 'inetmgr', and press Enter to open the Internet Information Services (IIS) Manager.
In the Connections pane on the left, expand your server node and click on Sites. Check if the newly created web application site is listed but lacking proper physical path configurations.
Right-click the site (if visible) and select Manage Website > Advanced Settings. Note the Physical Path directory and ensure it actually exists on your server's drive.
Navigate to the physical path in File Explorer, right-click the folder, select Properties, and go to the Security tab. Ensure the WSS_WPG and WSS_ADMIN_WPG groups have appropriate read/write permissions.
Provision Web Application using SharePoint Management Shell
Use PowerShell to bypass Central Administration UI glitches and capture more detailed error output during web application creation.
Consult Microsoft Q&A for SharePoint Server Issues
Escalate the issue to the specialized Microsoft Q&A community, as this is an on-premises SharePoint Server error rather than a general SharePoint Online issue.
Switch to a Simpler Document Solution with WPS Office
Managing on-premises SharePoint servers and troubleshooting IIS provisioning can be complex and error-prone. If you are looking for a straightforward, lightweight alternative for document management, creation, and collaboration, consider WPS Office. It provides powerful productivity tools without the heavy server configuration.
- 1. Download the installer: Visit the official WPS Office website and click the Free Download button.
- 2. Install the suite: Run the downloaded executable file and follow the on-screen prompts to complete the installation.
- 3. Start collaborating: Open WPS Office, sign in to your cloud account, and instantly begin creating and sharing documents with your team.
Frequently Asked Questions
Why does the web application appear in Central Administration but lack IIS virtual directories?
This occurs when the initial database entry for the web application succeeds, but the subsequent IIS provisioning step fails due to a 'File not found' error. This disconnect is usually caused by missing template paths or insufficient administrative permissions during the IIS setup phase.
Will reinstalling SharePoint fix the 'File not found' error during web application creation?
Reinstallation is rarely necessary and should be a last resort. It is highly recommended to first verify your IIS inetpub paths, ensure the Farm account has local admin rights, and check the ULS logs to manually restore the specific missing file or folder.
Where can I find detailed logs for the SharePoint 2013 provisioning error?
Detailed error messages can be found in the SharePoint ULS (Unified Logging Service) logs. These are typically located in the 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS' directory. Search for 'File not found' around the timestamp of the error.
