I created a 2013 web application a few months back and extended it to the Internet Zone to provide for anonymous and FBA access. In 2013 when you do that it somehow merges the two web apps together in Central Administration and there doesn't seem to
be a way to manage them separately within the UI. The "extended" addresses just become AAMs on the main web app's collection (with the selected zones).
This worked for some period of time and then there was a point when I wanted to change it for some reason. I used AAMs and changed the bindings in IIS for the extended site, but I think I deleted the original AAMs for the site prior to adding new ones
and the new IIS settings. Now I can't hit the site at all with the new AAMs (the original ones for the internal-facing-web-application still work).
The only hint is an error in the Event Log about this web application concerning SPPING not working. I tried to add that with powershell but it didn't work out.
Event Log:
Machine 'machine(AppPool(_LM_W3SVC_1410342202_ROOT))' failed ping validation and has been unavailable since '12/6/2013 10:35:44 AM'.
Here's my request script for testing the issue:
$url = "http://machine:port" $myReq = [System.Net.HttpWebRequest]::Create($url) $myReq.Method = "SPPING"; $response = $myReq.GetResponse(); $response.StatusCode Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (400) Bad Request." At line:4 char:1+ $response = $myReq.GetResponse();+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException+ FullyQualifiedErrorId : WebException
To prove the IIS web application works I backed up all the SharePoint files, deleted them, and put a plain-jane index.html in the appropriate inetpub folder. So it would seem to be a primarily sharepoint-based
issue.
What do I need to do to get my external-facing web app moving again and fix the error I mentioned above?
Matt Olson, MS Content Development Specialist MCITP, MCTS