I get System.IO.FileNotFoundException after joining new wfe server to SharePoint 2013 farm

Question

I get System.IO.FileNotFoundException after joining new wfe server to SharePoint 2013 farm

ahmed sharkaway 116

fter joining new wfe server to SharePoint 2013 farm, when I add new website it works in central admin but on the other wfe server I get file not found and get a complete error the uls

System.IO.FileNotFoundException: File Not Found. at Microsoft.SharePoint.ApplicationRuntime.SPVirtualFile.CalculateFileDependencies(HttpContext context, SPRequestModuleData basicRequestData, ICollection& directDependencies, ICollection& childDependencies) at Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.EnsureDependencies(HttpContext context, SPRequestModuleData requestData) at Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.EnsureCacheKeyAndViewStateHash(HttpContext context, SPRequestModuleData requestData) at Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.GetVirtualPathProviderCacheKey(HttpContext context, SPRequestModuleData requestData) at Microsoft.SharePoint.ApplicationRuntime.SPVirtualPathProvider.GetCacheKey(String virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

2 answers

Your answer

Answer 1

Chelsea Wu 6,341 Moderator

Hi @ahmed sharkaway , thank you for posting in the Q&A forum.

You can check the official document for the full process to add a new WFE server to the farm, see if you have configured everything successfully: Add web or application servers to farms in SharePoint 2013.

A few things to start with:

Make sure you have run SharePoint Configuration Wizard successfully on the new WFE serve.
Check the status of the new WFE server via Central Administration > System Settings > Manage servers in this farm.
Make sure you have the SharePoint services started and running via Manage services on server.

If an Answer is helpful, please click "Accept Answer" and upvote it.
**Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. **

ahmed sharkaway 116 Reputation points

2020-12-10T13:17:38.343+00:00

I follow official documentation and these services are runing
Chelsea Wu 6,341 Reputation points Moderator

2020-12-11T02:02:18.72+00:00
Thanks for the update. A few things I would like to confirm with you:

Can you reach the new created website from other servers in this farm? Also, can you access exiting sites from the new joined WFE server?

Do you have anti-virus installed in the new server? Make sure it is not blocking SharePoint farm if any, and also make sure certain folders are excluded from antivirus scanning.
ahmed sharkaway 116 Reputation points

2020-12-11T21:57:29.303+00:00

I have 1 application server for central admin and one for frontend .
wfe server has reflected the web application created in central admin and the solutions deployed too.
yes I can access any web site from application server ,no anti-virus installed
Chelsea Wu 6,341 Reputation points Moderator

2020-12-14T09:51:46.787+00:00
A few more things to check:

Make sure you have configured DNS properly.

Disable loopback check on the WFE server. Reference: SharePoint 2013: Disable Loopback Check.

Make sure you have set Managed Path for the new web application via Central Administration > Manage Web Applications > select web application > Managed Path.

You can refer to a post here with similar discussion for more troubleshooting: Cannot access site collection on new web server hosting SharePoint.
You can also check the System Event Viewer or SharePoint Health Analyzer for possible error message related to this issue. If you see any error listed in SharePoint Health Analyzer, try fixing them and see if it helps.
Chelsea Wu 6,341 Reputation points Moderator

2021-01-01T01:06:11.687+00:00

Hi @ahmed sharkaway , I’m checking on how things are going on with this thread. Do you have any update or process that care to share?

Answer 2

trevorseward 11,711

Can you run the following on the server experiencing the issue:

$wa = Get-SPWebApplication https://webAppUrl
$wa.Unprovision()
$wa.Provision()

Verify the IIS physical path for the Web Site is identical on both the working and non-working servers.

ahmed sharkaway 116 Reputation points

2020-12-15T00:31:58.517+00:00

I get this error

Get-SPWebApplication : Cannot find an SPWebApplication object with Name, Id, or Url: http://localhost:9000/.
trevorseward 11,711 Reputation points

2020-12-15T03:37:03.197+00:00

Remove the non-working SharePoint Server from the farm. Use the SharePoint Products and Configuration Wizard. Then re-run the wizard to add the server back to the farm.
ahmed sharkaway 116 Reputation points

2020-12-15T15:53:24.877+00:00

i made this too but the same error

Share via

I get System.IO.FileNotFoundException after joining new wfe server to SharePoint 2013 farm

2 answers

Your answer