ok so I am attempting to migrate a large amount of content from one MOSS
server to another on a different farm in the same domain. I have migrated
all of the sites except the largest (of course) which has failed using the
same technique as the others which was to use "stsadm -o export".

If I use "stsadm -o export" it failes about 50-60% the way through the
import. I have even tried the nofilecompression option on export and import
to get around disk space problems.

Anyway, i want to try the migration path option but when I attempt to set up
the path I get

Value does not fall within the expected range.

After some hunting around I found two references to this problem:
http://office.microsoft.com/en-us/products/FX101633851033.aspx
http://support.microsoft.com/kb/926281
The machine I am trying to migrate has been in use since Beta TR1(?) I
believe and has since been upgraded to RTM.

The problem occurs when I attempt to run the set of commands described in
both articles as follows:

Stsadm -o deactivatefeature -name deployment -url URL
Stsadm -o deactivatefeature -name migration -url URL
Stsadm -o activatefeature -name deployment -url URL
Stsadm -o activatefeature -name migration -url URL

When I run either of the first two commands I get the following error

Failed to find the XML file at location
'12\Template\Features\deployment\feature.xml'

Failed to find the XML file at location
'12\Template\Features\migration\feature.xml'

I have looked and of course those files do not exist. What I dont understand
though is that they do not exist on my new clean server to which I have been
importing content to and that I am able to create deployment paths from the
new machine to the old... Am I missing some feature files?

All help and advice greatly appreciated

Cheers!

Kyle

P.S. apologies for the cross-post here and on the public forums.

Re: error creating deployment path - known issue resolution fails by stefang

stefang
Tue Jun 10 02:53:36 CDT 2008

Hi Kyle,

looks as if your application uses these features.
Please have a look at the following article on how to isolate such issues:
http://blogs.technet.com/stefan_gossner/archive/2008/04/12/moss-common-issue-content-deployment-fails-with-failed-to-compare-two-elements-in-the-array.aspx

Cheers,
Stefan


"Kyle" <Kyle@discussions.microsoft.com> wrote in message
news:9DA26B26-8EFB-4D3D-80CB-CFCA3ADC17A8@microsoft.com...
> ok so I am attempting to migrate a large amount of content from one MOSS
> server to another on a different farm in the same domain. I have migrated
> all of the sites except the largest (of course) which has failed using the
> same technique as the others which was to use "stsadm -o export".
>
> If I use "stsadm -o export" it failes about 50-60% the way through the
> import. I have even tried the nofilecompression option on export and
> import
> to get around disk space problems.
>
> Anyway, i want to try the migration path option but when I attempt to set
> up
> the path I get
>
> Value does not fall within the expected range.
>
> After some hunting around I found two references to this problem:
> http://office.microsoft.com/en-us/products/FX101633851033.aspx
> http://support.microsoft.com/kb/926281
> The machine I am trying to migrate has been in use since Beta TR1(?) I
> believe and has since been upgraded to RTM.
>
> The problem occurs when I attempt to run the set of commands described in
> both articles as follows:
>
> Stsadm -o deactivatefeature -name deployment -url URL
> Stsadm -o deactivatefeature -name migration -url URL
> Stsadm -o activatefeature -name deployment -url URL
> Stsadm -o activatefeature -name migration -url URL
>
> When I run either of the first two commands I get the following error
>
> Failed to find the XML file at location
> '12\Template\Features\deployment\feature.xml'
>
> Failed to find the XML file at location
> '12\Template\Features\migration\feature.xml'
>
> I have looked and of course those files do not exist. What I dont
> understand
> though is that they do not exist on my new clean server to which I have
> been
> importing content to and that I am able to create deployment paths from
> the
> new machine to the old... Am I missing some feature files?
>
> All help and advice greatly appreciated
>
> Cheers!
>
> Kyle
>
> P.S. apologies for the cross-post here and on the public forums.