Hello - I have successfully exported a subsite on a WSS 3.0 SP2 farm. While I try to import the site to another farm, I get the following error: The file cannot be imported because its parent web /site/SiteA does not exist. Here is the import command I issue: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o import -url http://intranet/SiteA -filename "D:\SiteA_backup\SiteA.dat" Can someone please help and let me know what may be the cause or if there is an error with the command? Thank you, WalidWalid Gharwal

Hi WalidG, According to your description and the error message, it seems that this is a permission problem. You can go through the following two articles and try the solutions there to solve this problem: http://patrikluca.blogspot.com/2008/05/restore-subsite-parent-web-does-not.html; http://www.dev4side.com/community/blog/2010/7/19/fatalerror-the-file-cannot-be-imported-because-its-parent-web-does-not-exist.aspx. Thanks & Regards, Peng Lei

Thank you, Peng Lei. I had already read and tried both options but it did not work.Walid Gharwal

Anyone look at this yet?Walid Gharwal

Try create a new/clean site collection on your destination farm and import the your SiteA.dat there. At this point, we are not sure where the problem lies in SiteA.dat or your destination farm.Allen Wang | http://blogs.msdn.com/allenwang

Hi Walid, Is it a different farm you are trying to import the site to? On your source farm looks like you had a managed path (/site) which is not present in your target farm. If these are correct try creating a similar managed path (from central admin) on your destination farm. As your error message telling you it's not finding the managed path "/site" and then try importing your SiteA under it. Hope this helps!BlueSky2010

I have created a new/clean site collection on my destination farm and it still gives me an error. It seems to always be looking for a site under the site I am try use in my import. Just doesn't make sense. Walid Gharwal

It is a different farm. The managed path should not matter. I should be able to take the export and import it to whatever site I assign. The import is not behaving as it normally should' Walid Gharwal

It is a different farm. The managed path should not matter. I should be able to take the export and import it to whatever site I assign. The import is not behaving as it normally should' Walid Gharwal

Well my experience says 'Managed path' does. I would be interested to how if anyone else had similar experience.BlueSky2010

Well my experience says 'Managed path' does. I would be interested to how if anyone else had similar experience.BlueSky2010