Timeline for Add new WFE to existing farm
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 5:41 | vote | accept | Emaborsa | ||
| Jun 11, 2020 at 20:18 | comment | added | DubStep | I'd assume it's because of one of two things. It (localhost) is set in the binding in IIS, or you are listening on all IP addresses, but no hostname specified in bindings on the SharePoint site in IIS, so SharePoint will respond. You'll still get the AAM error though. Based on some of the other errors, it looks like some solutions are also missing from the new server. Possibly things that were installed into the GAC on the old server directly, rather than deployed via WSPs. The solution failing to deploy on the new server when added to the farm could cause the same errors it too. | |
| Jun 10, 2020 at 4:59 | comment | added | Emaborsa | Ok, but why does localhost work on the old wfe? | |
| Jun 9, 2020 at 21:50 | history | answered | user6024 | CC BY-SA 4.0 |