Server Error in '/' Application. The Web application at [Domain name] could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content.

We are using SharePoint server 2013 Enterprise installed on windows server 2012 R2 Standard

This is the internet facing website with the following settings
-      Anonymous access enabled
-      Integrated Windows Authentication : NTLM
-      Authentication provider : Claim Based Authentication


When browsing the website publicly using the domain name I get the above mentioned Error, But if I login locally on the server [http://serverName/] then browse the website again using domain name the error disappears.



When browsing the website locally using the server name [http://serverName/]
1. I can access the website with no problems
2. And I am able to login into to SharePoint
3. When I browse a website locally on the server but using the domain name not the server name I cannot login into SharePoint it keeps displaying the authentication box as if I am entering the wrong credentials.


Below is the full error

Server Error in '/' Application.
The Web application at http: [public url] could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: The Web application at [public url] could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[FileNotFoundException: The Web application at [public url] could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.]
   Microsoft.SharePoint.SPSite.LookupSiteInfo(SPFarm farm, Boolean contextSite, Boolean swapSchemeForPathBasedSites, Uri& requestUri, Boolean& lookupRequiredContext, Guid& applicationId, Guid& contentDatabaseId, Guid& siteId, Guid& siteSubscriptionId, SPUrlZone& zone, String& serverRelativeUrl, Boolean& hostHeaderIsSiteName, Boolean& appWebRequest, String& appHostHeaderRedirectDomain, String& appSiteDomainPrefix, String& subscriptionName, String& appSiteDomainId, Uri& primaryUri) +3369
   Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, Boolean swapSchemeForPathBasedSites, SPUserToken userToken) +569
   Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken) +32
   Microsoft.SharePoint.SPSite..ctor(String requestUrl, SPUserToken userToken) +105
   Microsoft.SharePoint.Publishing.CachedObjectFactory.get_SuperReaderSite() +441
   Microsoft.SharePoint.Publishing.AclCache.GetAclForScope(Guid scopeId, Boolean disposeOfSite) +96
   Microsoft.SharePoint.Publishing.AclCache.GetEffectivePermissions(Guid scopeId, SPWeb contextWeb) +117
   Microsoft.SharePoint.Publishing.CachedObject.GetEffectivePermissions(SPWeb contextWeb) +63
   Microsoft.SharePoint.Publishing.WebControls.CombinedBasePermissions..ctor() +457
   Microsoft.SharePoint.Publishing.WebControls.ConsoleVisibleUtilities.get_CanShowSiteActionsMenuItems() +31
   Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingRibbon.OnLoad(EventArgs e) +510
   System.Web.UI.Control.LoadRecursive() +129
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Control.LoadRecursive() +226
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3997


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1069.1
MohlalefiAsked:
Who is Participating?
 
Walter CurtisConnect With a Mentor SharePoint AEDCommented:
Here are a few questions that might help troubleshoot the problem:

What has changed?

Where is the message coming from?
Maybe be load balancer? FireWall? Other server or applicance? (Although the stack trace looks to be SharePoint.)

Did you have the web app extended so that you could provide a public facing url? If so, make sure that web extension has not been deleted. Check in IIS to make sure that the extension is not stopped.

If you do have a web extension, are the settings correct? You mention that using the public url internally you get a login prompt. Has the start or landing page that should be anonymous been changed to not allow anonymous access? Has the page been modified and not published? Is there a link to something that requires authentication? Has a developer touched the system in any way?

A few other things to check;
Have AAM's been changed?
Are service accounts that are needed enabled and working correctly?
Can you hit the public site using an IP address? (Just a standard troubleshooting step.)

Good luck...
0
 
MohlalefiAuthor Commented:
Thank you for our informative reply

Yes we can hit the website using the public IP address. We did not configure alternative access mapping could that be our problem?
0
 
Walter CurtisSharePoint AEDCommented:
Yes, that's the problem. I should have asked, has this every worked and it now broken, or has it never worked. If it never worked, check the alternative access mappings.

Good luck...
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
MohlalefiAuthor Commented:
We were just on deployment stage, I will implement the AAM's.

Thank you very much
0
 
Walter CurtisSharePoint AEDCommented:
The provided answers had information that was accurate, correct and provided a way to solve the problem.
0
 
Walter CurtisSharePoint AEDCommented:
The answer provides is accurate and offers solutions for the reported issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.