Unable to create Web application in SharePoint 2010

Question

I'm working on SharePoint 2010 environment.

I'm trying to create new web application.

but it shows error like below

Please suggest something

Answer 1

You can try creating the web application using Powershell as below:

New-SPWebApplication -Name "Contoso Internet Site" -Port 80 -HostHeader sharepoint.contoso.com -URL "https://www.contoso.com" -ApplicationPool "ContosoAppPool" -ApplicationPoolAccount (Get-SPManagedAccount "DOMAIN\jdoe")

New-Spwebapplication

I had faced this issue some time back when trying to create a web application using Central Admin UI. So, as M. Qassas correctly mentioned, that changing registry keys is extremely dangerous. I created the web app using the powershell, it took some around 15-20 mins, but the web app was created successfully.

Answer 2

Maybe it's a Kerberos authentication issue that occurs when setting Authentication Provider to (Negotiate). so try to select NTLM and check if it is working.

Another reason, the IIS need to be configured to accept larger headers in the registry. MS KB article explains all those settings: http://support.microsoft.com/kb/820129

To Configure IIS to accept larger headers, You will need to adjust The MaxRequestBytes and MaxFieldLength registry keys to in the registry at:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters\

• MaxFieldLength

  • Default Value: 16384
  • Min – Max Value to set: 64 – 65534 (64kb) bytes
  • Sets an upper limit for each header. See MaxRequestBytes. This limit translates to approximately 32k characters for an URL.

• MaxRequestBytes

  • Default value: 16384
  • Min-Max value to set: 256 – 16777216 (16MB) bytes
  • Determines the upper limit for the total size of the Request line and the headers. Its default setting is 16KB. If this value is lower than MaxFieldLength, the MaxFieldLength value is adjusted.

Note: Changing these registry keys can be considered extremely dangerous. These keys allow larger HTTP packets to be sent to IIS, which in turn may cause Http.sys to use more memory and may increase vulnerability to malicious attacks.

For more details check

• "HTTP 400 - Bad Request (Request Header too long)" error in Internet Information Services (IIS)
• Kerberos Authentication Problem with Active Directory