I have setup a SharePoint 2019 high-availability farm with 2 WFE's, 2 APP and 2 SQL Servers. All servers state is good and patched the farm with May 2022 Cumulative Update. We are running F5 load balancer and public IP of the load balancer (LB) is also added in the host file of both WFE servers.
We created a web application (its public facing site, so also added anonymous authentication) and added DNS to it. We have setup the AAM in central Admin and also added IIS binding for web application port and 443 (wildcard certificate is installed on both WFE servers).
When Load Balancer is pointed to WFE1, the application is loading perfectly fine, however when LB is pointed to WFE2, its showing a blank white page (with no JS or CSS loaded on the page, no errors). However, when we do IISRESET on WFE2, first time site loads on WFE2 and then goes blank if we refresh the browser or click on any link on the website. The application is working fine with server name on both the servers
We have tested on different browsers. Also added Disableloopbackcheck in Registry. All required firewall rules (ports) are open. Each server is getting pinged from one another, so there is no server communication issue. Even the required SharePoint files/folders are excluded from antivirus (Bitdefender). Also, there is no other web application on this farm which is using SSL/https.
I have also checked SharePoint ULS logs, Event Viewer logs and IIS logs, but it seems there are no errors.
Any help would be highly appreciated!
Related
The problem is that I cannot create new web app on SharePoint 2016, it takes a too long time, loading infinitely with hours until I end it, and the central admin gives 404 not found
First I restarted and made sure the SQL server is started and the farm admin account has correct roles all passes, but with no luck. Finally, I decided to start the configuration wizard but I found this error
WEBCONFIG.ACCSRV.XML, does not have element "configuration/configSections/sectionGroup[#name='SharePoint']" or it is invalid.
I have compared this file with its pair on one server, which it works found they are the same content. Any help, please.
The solution is as follows:
1-Delete All unused Web Apps
2-Delete Some unused IIS sites which are used the ports of SharePoint (port 80,...)
3-clear SharePoint recycle bin
4-confirm all SharePoint service and IIs App pools are running " as I found Service Application App Pool was stopped"
5-Delete the additional trust provider
The main reason is the user was trying to install SharePoint add-in so he changes the trust and changes the port of default site of SharePoint and central admin seeking to change them to HTTPS and then try to create many web apps which have been created with the corrupted web. configs and those changes make all this hassle
I hope this Question may help others
I have a windows server 2019 VM in Azure.
On this server I have multiple web sites running.
One web site has two URL's
For example https://api.oldcompanyname.com (192.1.1.5) and https://api.newcompanyname.com (192.1.1.6)
I have certificates for both, each has its own binding, and each has its own IP address.
Locally on the machine I can access both sites with no issue.
However remotely the old site URL pulls up just fine, but the new site URL gives me a 503 error.
I have checked the IIS logs and I don't see any of the 503 errors listed in there.
I checked the windows logs and there are no crashes with the AppPool and again running locally (with FQDN) works just fine so the site is loading.
Windows firewall is turned off.
In Azure we do have this server behind a Traffic Manager, PF Sense, and App Gateway.
I want to rule out any issues on this server before I go searching in one of these areas
Funny thing is that even from another machine inside the network I get the 503 on this one binding and I don't think that that connection would go through any of above items as it is an internal address it is using.
Any ideas?
I created a Azure VM in DevTestLab using base Windows Server 2016 DataCenter. Then I enabled web server role referencing this.
It seems there is some issue with IIS 10 as I am not able to access default website on this server. To verify further, I also tried to host a website with single html page but same issue "Page can't be displayed."
I gave a try with chrome browser and able to browse localhost website on chrome. So IIS 10 seems good on VM. Initially I guess was IIS 10 not configured properly but now it seems proxy on IE not allowing website content getting displayed. Now I am able to proceed with chrome and will reach out our network team if required.
I just installed TFS2010, and set it up with the single server wizard. It installed me Sharepoint Services an let everything working pretty well.
But, the sharepoint URLs it generates from the Server name "server". As my setup is without a domain, the URLs work okay only from the server computer, not from the others.
I have to give access to LAN clients, and Internet Clients, both connected thought my Public Ip.
How can I change those sharepoint IPs from TFS to be generated From the IP, not from the Server's name??
Thanks in advance
Sharepoint is simply an ASP.Net web application sitting on IIS so all the configuration for host headers etc can be added in IIS itself - if you have multiple instance of sharepoint running on the server, you'll have to add URL's using the sharepoint configuration site but most stuff can be tweaked through IIS (IP's its listening on etc)
If you not on an domainan and want people to have access to the site though you'll have to add your machines IP to the DNS server that you clients are using
I've just installed Microsoft SQL Server Express 2008 (with Reporting Services).
My installation is side by side with SQL Server 2005.
So far creating reports and testing them in the development environment has worked fine, however I can't get the web server or report manager working.
In the Reporting Services Configuration Manager, it appears that they have been configured and have a working address (eg: http://mymachine:8080/ReportServer_EXPRESS2008/ and http://mymachine:8080/Reports_EXPRESS2008/).
The Virtual Directories don't exist in IIS, and clicking on the links in the config manager results in a "The page cannot be found".
If I create the Virtual Directories in IIS, and then use Reporting Services Configuration Manager to modify the two sites, Reporting Services Configuration Manager appears to be working correctly (all the right messages appear, indicating that it created the new site and dropped the old site successfully). However, it only drops the existing Virtual Directory and does not create a new one.
Has anyone had this problem before and/or know of a possible solution?
Basically, Reporting Services 2008 doesn't use IIS anymore.
By coincidence (or default?), I already had IIS (with Reporting Services 2005) running off port 8080. Reporting Services 2008 also wanted to run off port 8080.
It appears that the new IIS free address reservation system doesn't work in this situation. Changing the port number fixes the problem.