Deployment error web.config is invalid IIS Web Site

Error :

Deployment error “The web.config is invalid on this IIS Web Site”

I’ve developed a web part that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error:

SOMESERVER : http://sharepointtechnicalsupport.com/ : SharePoint – 41981 :
Error: The web.config is invalid on this IIS Web Site:

C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config.

SOMESERVER : http://sharepointtechnicalsupport.com/ : SharePoint – 41981 : Error: The web.config is invalid on this IIS Web Site:

C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config.

SOMESERVER1 : http://sharepointtechnicalsupport.com/ : SharePoint – 23994 : Error: The web.config is invalid on this IIS Web Site:

C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config.

None of these virtual directories exist.

Solution :

In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service, SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service again, SharePoint will recreate the sites in IIS based on information stored in configuration database.

A SharePoint web application can have several zones, each zone will have a separate site in IIS. You will not see all the zones in Central Administration->Application Management->Web Application List. You can find the information in Central Administration->Operation->Alternate Access Mapping.

SharePoint sites not opening locally IIS Error

I am having this strange problem . All of a sudden all of the new sites created in the SharePoint are not opening locally. And even iis is failing to pick up the ip binding with a site. All my existing sites when browsed from IIS manager are giving certificate error and ultimately showing connection problem error. Only thing that was done was the patching this week. I have no idea why all this is happening. Has any one faced similar problems before.

Solution :

  • try stopping the Foundation Web service on the affected farm member and re-starting it.

  • If you were adding SSL certs to the IIS sites, it may be a case of attempting to use the same IP with different SSL certificates across IIS web sites.  IIS 7.5 and below do not support SNI, so you have to have a unique IP:SSL Cert combination, or get a Wildcard or SAN certificate instead.