12

Let's imagine there is no web application to create the site collection, and you will create the site collection directly without creating a web application, In this case, Every site collection will require an Application Pool to be created !! So what's the issue, What's this mean? This means You will be restricted to create maximum 10 site ...


8

Resetting the environment with an iisreset did the job.


7

Please include Microsoft.SharePoint.Client.Runtime.dll in your project.


7

The host header is the URL on which the web application will respond. If you specify a host header during the creation of a web application, you'll notice that a binding with the same URL is added in IIS Manager as well. This allows IIS (and thus SharePoint) to respond with the correct content when you request a specific URL. The web application host ...


6

This seems to be an issue with the powersheel_ise.exe and once I close and reopen it, it seems to be fine. Here's a link I found.


6

You would need to Create a new Web Application in farm 2 Export solutions* from farm 1 Install solutions in farm 2 Backup content databases belonging to the web application in farm 1 Restore all content databases in farm 2 Enable all features on farm 2 Web App | Site | Web that are enabled in farm 1 web app Test From an abstract level, this works. To make ...


6

Since you're on the internal network and run your farm inside a firewall protected area, you should use the same port 80 for HTTP traffic and port 443 for HTTPS traffic. When you create a new web app, you need to fill in the field "Host Header" which separates the port 80 applications in ISS from each other. In the path, which updates automatically based ...


5

In case this helps anyone else (or me in the future) you can do this with: $winAp = new-SPAuthenticationProvider -UseWindowsIntegratedAuthentication $stsAp = Get-SPTrustedIdentityTokenIssuer "YourSTS" Set-SPWebApplication -Identity $webApp -AuthenticationProvider $stsAp, $winAp -Zone "Default"


5

The right way to grant access is to use the SPWebApplication.GrantAccessToProcessIdentity method. It sets up the database permissions for you, but remember to run it again if you add content databases. You can do this with the following PowerShell: $webApp = Get-SPWebApplication TEAM_SITE_URL $webApp.GrantAccessToProcessIdentity("domain\username of MY SITE ...


5

Use ServerRelativeUrl, eq. /sites/site/libraryname/folder/filename.ext. Function returned File object.


5

I strongly recommend to have only one content Web Application on port 443 and one admin Web Application. Then create your site collections as host-named site collections instead of path-based site collections. It's a far more efficient, scalable and flexible architecture. This is also how Microsoft hosts site collections in Office 365. With Web Applications ...


4

If your web application is in Claims mode (uses Claims based authentication, CBA), you need to grant permission for username that is in claims format, like i:0#.w|dev\administrator. More info here.


4

You can`t. The Client Object Model (CSOM) does not provide access above the Site Collection level. As far as I know, the only way to do what you want is to create a custom web service that gets the Web Application information using the Server Object Model and have the remote application use it instead of the CSOM.


4

When you create the Web Application you decide what should be the URL of it. And in your setup it should not be the URL of any of your servers, but the URL for the load balancer which distributes the work between wfe01 and wfe02. And normally you'll leave the web application service running on the App server as well and let Search Crawl use that locally by ...


4

The RSViewerPage.aspx is a Out the boxed application page in the _Layouts folder. Application pages, which are also known as "_layouts" pages, are stored in a site's Microsoft Internet Information Services (IIS) virtual directory and support application implementations. Application pages are shared across all sites on the server, whereas a site page ...


4

As the name suggests, Assembly deployment Target; specifies where the assembly i.e. dll of the SharePoint will be deployed to. So, in case of WebApplication deployment target, the assembly will be loaded in the bin folder represented by the IIS site. For example, the deployment is done to port 80 site. Then the path may look like this C:\inetpub\wwwroot\wss\...


4

Yes you can, but be sure to try this in your test environment first. Follow the steps in the article SharePoint with more than one SQL instance: possible or not possible On the SQL server Backup the content database. Restore the database on the second instance Add the same permissions for the content database that you had on the source ...


4

I believe there is no error in creating Web Application. Based on this approach I am trying to help. You need to create any Site Collection into it, Web Application cannot be opened directly. You can create a root level Site Collection. As you are new to SharePoint 2013 you can go through Create a Web Application and Site Collection in SharePoint 2013 Let ...


4

You might be victim of LoopBackCheck. Possible solutions: Bypassing your proxy server for local addresses (Source) Adding a team Web site to the list of trusted intranet sites (Source) SharePoint disable loopback check (DisableLoopbackCheck dword in registry)(Source) For me DisableLoopbackCheck worked.


4

When you create a new Web Application you have to add host header name to your webapp. This means that your Web App with the host header name "portal" will have the path C:\inetpub\wwwroot\wss\VirtualDirectories\portal80, and another web app with host header name "test" will have the path C:\inetpub\wwwroot\wss\VirtualDirectories\test80. That way you can use ...


4

Just to add to Benny's answers: Using port 80 and 443 means you don't have to rely on end users having to type in port numbers Hopefully does not need saying but make sure your host headers are added to DNS Be aware of resources. Don't get carried away with creating many web apps. Have a look into host named site collections.


4

Well, the Web Application itself does not really take up much space! It's just an IIS site on each SharePoint server in the farm. All content is stored in the SharePoint Content Databases. Hence, you can get the size by adding up the size of all attached databases.


4

Web application in SharePoint is like an IIS site, which you can access it via a url either Http or Https and also you can configure the different authentication method for each web application. A SharePoint 2013 web application is composed of an Internet Information Services (IIS) web site that acts as a logical unit for the site collections that ...


4

deletion is easy process but housekeeping is little timy. We are following the below steps as a practice for decommission the Web Application: Make Inventory of the Web application data, i.e. Content DB name9s0, #of site collections, url of site collections, custom settings, Take the Backup of Content Database ( For safe play, in case you need the data ...


3

First, get all your web applications and iterate through them. While in the loop print web application name and application pool name. Last, iterate all solutions and print their names - like this: $contentWebAppServices = (Get-SPFarm).services | ? {$_.typename -eq "Microsoft SharePoint Foundation Web Application"} foreach($webApp in $...


3

What you describe is actually the recommended way to change a web application's URL. http://technet.microsoft.com/en-us/library/cc262366(v=office.15).aspx Essentially, the process is to go to CA, remove the site from IIS (you can safely leave the IIS site to preserve your web.config changes) then re-extend to the default zone.


3

I had the same problem just a couple of days 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 pool ...


3

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 pool ...


3

Create a Root Site Collection (at "/") via Central Administration/PowerShell. It is not supported to run without a Root Site Collection on a Web Application.


3

Here you go :) if ( (Get-PSSnapin -Name Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue) -eq $null ) { Add-PsSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue Write-Host "PSSnapin SharePoint is now ON" -ForegroundColor Green `n } else{ Write-Host "PSSnapin SharePoint already ON" -ForegroundColor ...


Only top voted, non community-wiki answers of a minimum length are eligible