Tag Info

New answers tagged

0

After changing the Central admin IIS app pool timeout ,I was seeing the site only in CA server and not in WFes .What did the trick for me is i ran the SharePoint Configuration Wizard on all the WFE and App Servers and then tried creating the web app and Voila!!!!! i was able to create the web app fine ..Thanks a lot for your comment "User19952" you ...


2

I had the same problem couple of months ago. Do you run many web-applications in your farm? From the blogpost: This is usually because you either have too many Web Applications in your SharePoint Server, or because your SharePoint Server is slow! As part of the Web Application creation process, SharePoint resets IIS. By Default, the application ...


1

Solution 1: Start -> All Programs -> right click on SharePoint 2013 Central Administration -> click on Run as administrator Still the Issue occurs, follow solution 2 Solution 2: Start –> Control Panel –> System and security Now here under Action center click "Change user account control settings". Get the scroll bar to never notify. Click on OK. Restart ...


0

Try opening the Internet Explorer in Administrator mode and plus the settings modification made by @Anuja as explained above!


0

As per my experince I think you will be fine with one site collection for each department. No one from divsion1 site collection can access division 2 site unless you grant permission(this is also true for Web Application). Normaly you can create managed path site collections but if you need a FQDN for each site collection then you can use the HNSC. But ...


1

Go to Central administration - Application Management - Under Service Applications click Manage Services on Server . On the top Right corner you will see the server name. Click on it. Select CA server. The most important services that have to be stopped are "Microsoft SharePoint Foundation Web Application" (that prevent the server from hosting web app) ...


0

AFIK, You can create site collections in the Central Admin web but it is not recommend.Simple reason(best practice) always keep Central admin on the APP servers while other content driven site collections hosted on the WFE. Central admin site is only for farm administrator not for every body. Another Risk involved is you may expose your central to all the ...


0

This is really dependent on how you want things set up. There's no 'right answer', but here's some considerations: Each web application gets their own application pool. If everything is under the same web application, they are all under the same application pool - if this application pool stops working, everything stops working. If you really want things ...



Top 50 recent answers are included