Parser Error after changing physical path of SharePoint site via IIS7
Hi out there, Apologies if this is a dum question, but I'm kinda new to SharePoint and was wondering if anyone else has experienced the problem that I'm encountering. I've tried googling but not found anyone with this issue so any help would be appreciated. First off some background info: I've backed up an SSP from our current live box, and have successfully restored it onto the new machine that will be replacing it using stsadm -backupmethod full and then -restoremethod new. Had some issues with the restore process to be honest, but got round them and got the site restored and working fine. Unfortunately the restore process has placed the directory for the site under c:\inetpub tree, whereas I want it on a different drive. So using IIS7 I've changed the physical path of the site to be what I want and then copied the contents of the sites directory from c: to g: with no apparent ill effects. Where I encounter a problem is when the original directory on the c: is deleted/renamed AND the underlying application pool for the site is recycled. This causes a Parser Error on line 1 of category.aspx: <%@ Page Inherits="Microsoft.SharePoint.Publishing.TemplateRedirectionPage,Microsoft.SharePoint.Publishing,Version=22.214.171.124,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %> <%@ Reference VirtualPath="~TemplatePageUrl" %> <%@ Reference VirtualPath="~masterurl/custom.master" %> Line 2: <html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"><head> Line 3: <!--[if gte mso 9]><xml> If I then undelete/reset the directory name on c: and recycle the app pool, the web site works fine again! I can’t see what's keeping the link to the c:, as there's no settings in IIS7 for the app pool that I can find that reference the c:. Which has me thinking it must be in the content, search or ssp databases for the site? Anyone got any ideas? Cheers Alan
February 24th, 2010 3:57pm
Paul is correct in stating that this is also stored in the config DB. You would have to either recreate the web application for a different pysical drive location for your IIS files.
February 25th, 2010 1:27am