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
Related
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!
I have created a provider-hosted app which was developed and tested against SharePoint Online. I now want to install this on SharePoint 2013 On Premise.
It is my intention that, despite being a provider hosted app, I wish to host the app web in IIS on the SharePoint server (single farm not a cluster). I then intend to use a local URL for my App Web URL.
I understand the process of setting up an App Catalog (On SharePoint Online) as a repository for my App which in turn will enable users to add it to a site.
I have only been able to find a guide to setup On Premise SharePoint to allow users to use the SharePoint store but I only want to set it up for third party apps.
My question is do I need to go through all the steps in this link https://technet.microsoft.com/en-gb/library/fp161236.aspx even if I don't want/require store access? I don't not want to do more than necessary and I would prefer a simple solution for my clients.
I followed this guide https://technet.microsoft.com/en-gb/library/fp161234.aspx in the hope that creating the app catalog would be sufficient but I get the error "Sorry, apps are turned off. If you know who runs the server, tell them to enable apps."
We are running into an issue when we try and setup a new SSRS Application within Central Administration.
I am able to set the Name, App Pool, Configurable App Pool Account, Database Server, Database Authentication, but unable to set the Web Application Association.
The first time I setup the Application it allows me to select the Service Application Sites. When I return back to the Properties, Above the Web Application Association I get this message:
"There are no web applications available to associate with this sql server reporting services server application."
I am suck and cant seem to get this resolved. Has anyone came across this issue before?
You have to approach this in a different way; instead of configuring the associated Web Applications within the Service App. Config, you change the Service Application Associations (Central Admin > Application management > Service Applications > Configure Service Application Associations)
Once there, click on the Application Proxy Group that you're using - in my case, this was 'default'.
That will then pop open a window - "Configure Service Application Associations". Simply untick your old SSRS Service Application and tick the new one.
While it doesn't solve your exact issue... A combination of this and another proxy group might do what you want.
I have a remote Windows 2012 server running IIS 8 from which I am hosting a web application. My local development box is running Visual Studio 2012. Currently I am publishing my app as a web deployment package (.zip), RDP'ing to the production server, copy + pasting to a folder and deploying the application from within IIS. My question is, what changes do I need to make to deploy directly to IIS from Visual Studio 2012 using the web deploy option?
I have tried to follow this guide but it refers to a service URL which I must obtain from my hosting company. I don't have a hosting company, my server is co-located.
I am presented with the following options:
Is the username and password the one I use for the RDP account? I already have Web Deploy 3.0 installed on IIS do I need to enable further settings?
OK I found the solution but it took me a whole day to get it working! Basically the steps are as follows. This is very sketchy but see the detailed guides below which helped me.
Enable the IIS Web Management role feature.
Install Web Deploy 3.0 (or higher). Make sure to customise the install to include the handlers (See notes below). If you're not presented with this option go to add/remove programs, find webdeploy, right click and select "change" option.
In IIS click on the server node and find the "Management Service" icon. Enable remote access and configure a dedicated IIS User for remote deployment (These will be the credentials that will go in the user name and password boxes).
At the site level in IIS assign this user to manage the website.
Make sure port 8172 is open on the web server (you can check this port here).
Try reconnecting from Visual Studio. There was some trial and error here for me but the error messages do link to a MS guide for decoding :)
Even after connecting successfully I had to wrangle with permissions, so my IIS user had sufficient privileges to create the app pool, directories and general file management jobs.
The following links really helped!
Configuring the handler on the web server:
http://www.iis.net/learn/publish/using-web-deploy/configure-the-web-deployment-handler
Connecting via Visual Studio:
http://msdn.microsoft.com/en-us/library/dd465337(v=vs.110).aspx
NOTES:
To ensure the handler is running, login into your IIS server and point your browser to the following URL.
https://<servername>:8172/MsDeploy.axd
F12 to open up the dev tools to see the HTTP response. Also MsDeploy also creates IIS logs in inetpub/logs which should give you some clue if you're having connectivity problems.
I had the same problem and this post was very useful to help me solve the issue. I had anyhow serious troubles while trying to install Web Deploy on my Windows Server 2012. The installation of Web Deploy 3.0 was giving me several errors and it couldn't be completed.
I tried to solve the problem installing "Microsoft Web Platform Installer 5.0" from http://www.microsoft.com/web/downloads/platform.aspx but it didn't solve it.
I thought it was due to Firewall Settings, Authorizations issues, Users without permissions or something like that. Finally I found out it wasn't due to any of the mentioned reasons.
I found the most simple solution and I hope it will help other users too: it was enough to download Web Deploy 3.5 installation directly from Microsoft Website:
http://www.microsoft.com/en-us/download/details.aspx?id=39277
This may sound banal but it solved it. I was able to install "Web Management Service" but not the second needed IIS service "Web Deployment Agent Service".
So, I have three servers in my moss farm. A database server and two front-end servers...
On server 1 I am able to access my web application just fine and the services are running fine. However, on server 2 I am unable to start the Web Application service; I receive a error message on the screen stating "Check the server event logs for additional error information"...
When I check the event logs on server I see this error...
Error executing service instance (un)provisioning job. Service instance: "Windows SharePoint Services Web Application" (id "2d8886db-4b63-4841-bf48-4bd48d9a0c89) "1387""
Any thoughts..?
I would guess that either you have something up with IIS on Server 2 or that there's a deeper MOSS problem on Server 2. First thing is to figure out which web application is causing the problem.
Under Central Administration > Application Management > Web Application List. When you click on a web application name you'll see the ID for it in the query string. (i.e. /applications.aspx?WebApplicationId=ID-here)
Find the matching ID and you know that's the web application having issues. Check to make sure there's nothing wrong with that web application in IIS on Server 2.
If everything looks fine, I would remove server 2 from the farm and re-add to provision. If that doesn't work, remove server 2 from farm, reinstall MOSS, and then add back to farm.
I would check that the service account used for the web application has got the nessecary rights.
Go to central administration
then open "operations" > "service accounts"
click web application
Select the web application or check what users are used for the different web applications. Then check if they have the nessecary rights. I cant remember if it is nessecary for them to be local administrators on the server, but at least i would try making them local administrators. Then check if they have the nessecary rights on the SQL server. I think that db creator and writer is the only nessecary roles.
But i generally up the rights until it works, then remove what i think is unnessecary rights afterwards.