So how do you fix a missing virtual folder in IIS? I first tried running the configuration wizard again, which usually reprovisions some stuff, that didn’t helpt. I then tried stopping and starting the “SharePoint Web Applications” service, which basically does a reprovision of everything in IIS. But why the hell would that folder be missing? I honestly have no clue. Notice that the first one (port 80) has the _trust folder, but the second one (443) didn’t! So that 404 error was a pretty accurate one.
I had two IIS web sites running for this web application one for port 80 and one SSL secured one on port 443. I mentioned I had checked quickly, and that was why I initially didn’t see the issue. For reference, that folder should be in your virtual directory path of IIS. I had checked quickly to see if the /_trust folder was on disk, which is was.
Initially I thought SharePoint was throwing this error because of a fault in the configuration or something. The 404 indicates a page not found of course. Then I double checked all of my configuration, which all seemed to be fine. The logging was consistent with what was happening. First I checked the ULS logs, which didn’t reveal anything out of the ordinary. I did several things trying to find out what was going wrong.
#SHAREPOINT 404 NOT FOUND WINDOWS#
After configuring ADFS, it will list Windows and ADFS (provided you had Windows / NTLM authentication beforehand). That page allows you to select the login provider you want to use. When I opened up SharePoint, I got to the “Sign In” page. But following all the steps, I was left with a non-working authentication scheme. I’m not going to go into too much detail here because that process is well documented on its own. I was in the process of configuring ADFS for SharePoint.
Those of you who know SharePoint, probably also know those annoying problems you just cannot get your head around. SharePoint, ADFS and 404 on /_trust/default.aspx