- Extend Web Application to Another IIS Web SIte
This week one of my clients had a particular issue that I found very funny. Turn out that someone a.k.a MySite killer decide to use “SharePoint Web Services” IIS web site to host a new extended web application. As you may know, “SharePoint Web Services” IIS web site it’s a common web site that other service applications use, so it’s very important to leave intact and without any changes. SharePoint Configuration Wizard a.k.a PSConfig.exe provisions this web site.
But you know, things happen, for those who are new to the platform and are not familiar with the UI they can make mistakes thinking that Use and existing IIS web site is the same that Use an existing application pool. And also once noticing that extended web application is not working you can always remove extended zone and guess what? You will erase the Root folder that SharePoint Web Services IIS web site is pointing and that’s too not good.
Found this amazing article but didn’t work, the reason was that Root folder is missing and IIS web site is not properly referenced. I decide to copy Root folder from other server, dropped on C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\ and run it again. It works properly.
Now client SharePoint farm it’s working just fine.
Hope it helps!
I may have done the same thing just poking around but I don’t have another server to copy from. how do I get it back?
You can install SharePoint 2010 to a Virtual Machine using HyperV or Virtual Box, just saying!
Awesome!!It worked… In my case I copied from Test server to DEV Server Dev server was the one giving issues . So guys even if you do not have multiple servers in your farm you can copy the root folder from another farm .. Only thing is that you have to reprovision all the service applications through powershell.
$h = Get-SPServiceHostconfig
$h.Provision()
$services = Get-SPServiceApplication
foreach ($service in $services) { $service.provision();
write-host $service.name}
HOLY SHIT YOU SAVED MY ASS, thanks dude!
For any others that have this problem. I fixed by restoring a backup of the entire C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15 directory, then copied and pasted the script left by Smruti into Sharepoint Powershell…
$h = Get-SPServiceHostconfig
$h.Provision()
$services = Get-SPServiceApplication
foreach ($service in $services) { $service.provision();
write-host $service.name}