Import error - file can not be imported because its parent web does not exists RRS feed

  • Question

  • 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,


    Walid Gharwal
    Wednesday, April 27, 2011 8:02 PM

All replies

  • 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:




    Thanks & Regards,

    Peng Lei

    Thursday, April 28, 2011 2:19 AM
  • Thank you, Peng Lei.

    I had already read and tried both options but it did not work.

    Walid Gharwal
    Thursday, April 28, 2011 3:08 AM
  • Anyone look at this yet?

    Walid Gharwal
    Friday, April 29, 2011 11:11 PM
  • 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
    Saturday, April 30, 2011 3:13 AM
  • 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!

    Saturday, April 30, 2011 3:35 AM
  • 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
    Sunday, May 1, 2011 5:25 AM
  • 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
    Sunday, May 1, 2011 5:26 AM
  • Well my experience says 'Managed path' does. I would be interested to how if anyone else had similar experience.
    Sunday, May 1, 2011 6:18 PM
  • I was able to resolve this issue after some troubleshooting.  The issue appeared to be related to the fact that the two farms (source and destination) were at different sharepoint patch levels - the source being more updated than the destination.

    There is a file in the 12 hive called DeploymentManifest.xsd.  This is a schema file which supports the validation of the Manifest.xml file (or files) on export. This manifest file is the core migration file, as it captures a record of the contents and structure of the source site so that the migration operation can fully reconstitute the source site and its components upon import to the destination site.  The file contains several elements each declaring its own set of attributes.  It appeared that the SPWeb element did not have some attributes declared.

    So, this is what I did in order to fix the import issue on the destination farm:

    Edit the following file on each WFE (mainly on the WFE that holds the Central Admin site but it is a good idea to do this all):

    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML\DeploymentManifest.xsd

    Under section
    <! -- SPWeb definition -->

    Add the following:

            <xs:attribute name="ASPXPageIndexMode" type="xs:string" use="optional" />
            <xs:attribute name="NoCrawl" type="xs:boolean" use="optional" />
            <xs:attribute name="CacheAllSchema" type="xs:boolean" use="optional" />

            <xs:attribute name="AllowAutomaticASPXPageIndexing" type="xs:boolean" use="optional" />


    I hope this will help those who come across this issue.




    Walid Gharwal
    Friday, October 14, 2011 4:32 PM