MOSS – Common Issue – Content Deployment fails with "Failed to compare two elements in the array."

29 Comments

1. 

   Anonymous
   On 12. April 2008 Permalink

   [ Part 1 – Part 2 – Part 3 – Part 4 – Part 5 – Part 6 ] Requirements for a successful content deployment

   Reply
2. 

   Val Bongiorno
   On 21. April 2008 Permalink

   Sorry about the title

   how do i install/run your wssanalyzefeatures.exe?

   is there any documentation?

   Reply
3. 

   Stefan Goßner
   On 22. April 2008 Permalink

   Hi Val,

   please click on the link for the tool and check the page. The Usage is listed.

   Cheers,

   Stefan

   Reply
4. 

   skillmaster
   On 23. May 2008 Permalink

   how do you set your server for this tool?

   Reply
5. 

   Stefan Goßner
   On 23. May 2008 Permalink

   Hi Skillmaster,

   you have to run the tool on the server itself.

   You cannot run it from remote.

   Cheers,

   Stefan

   Reply
6. 

   Li
   On 30. May 2008 Permalink

   any other ideas, when I run WssAnalyzeFeatures, there are no errors.. when I run Export against the top level site if fails with the "Failed to compare …" msg. I can run it successfully against all subsites ?

   Reply
7. 

   Stefan Goßner
   On 31. May 2008 Permalink

   Hi Li,

   is the callstack identical to the one listed above?

   And there is no error reported in the FeatureProblems.txt file?

   I haven’t seen this till now.

   I would suggest to open a support case with Microsoft to get this analyzed.

   Cheer,

   Stefan

   Reply
8. 

   Li
   On 2. June 2008 Permalink

   Hi Stefan,

   Well actually looking at the stack again its not identical…

   [5/30/2008 1:59:44 PM]: FatalError: Failed to compare two elements in the array.

     at System.Collections.Generic.ArraySortHelper`1.QuickSort[TValue](T[] keys, TValue[] values, Int32 left, Int32 right, IComparer`1 comparer)

     at System.Collections.Generic.ArraySortHelper`1.QuickSort[TValue](T[] keys, TValue[] values, Int32 left, Int32 right, IComparer`1 comparer)

     at System.Collections.Generic.ArraySortHelper`1.Sort[TValue](T[] keys, TValue[] values, Int32 index, Int32 length, IComparer`1 comparer)

     at System.Collections.Generic.ArraySortHelper`1.Sort(T[] items, Int32 index, Int32 length, IComparer`1 comparer)

     at System.Array.Sort[T](T[] array, Int32 index, Int32 length, IComparer`1 comparer)

     at System.Collections.Generic.List`1.Sort(Int32 index, Int32 count, IComparer`1 comparer)

     at System.Collections.Generic.List`1.Sort(IComparer`1 comparer)

     at Microsoft.SharePoint.Deployment.WebSerializer.GetDataFromObjectModel(Object obj, SerializationInfo info, StreamingContext context)

     at Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectData(Object obj, SerializationInfo info, StreamingContext context)

     at Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object obj, ISerializationSurrogate surrogate, String elementName, Boolean bNeedEnvelope)

     at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream serializationStream, Object topLevelObject)

     at Microsoft.SharePoint.Deployment.ObjectSerializer.Serialize(DeploymentObject deployObject, Stream serializationStream)

     at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()

     at Microsoft.SharePoint.Deployment.SPExport.Run()

   *** Inner exception:

   Value does not fall within the expected range.

     at Microsoft.SharePoint.SPSecurity.ValidateSecurityOnOperation(SPOperationCode code, ISecurableObject obj)

     at Microsoft.SharePoint.SPFeature.EnsureProperties()

     at Microsoft.SharePoint.SPFeature.get_TimeActivated()

     at Microsoft.SharePoint.Deployment.WebSerializer.ExportFeatureComparer.System.Collections.Generic.IComparer<Microsoft.SharePoint.Deployment.ExportObject>.Compare(ExportObject exportObject1, ExportObject exportObject2)

     at System.Collections.Generic.ArraySortHelper`1.QuickSort[TValue](T[] keys, TValue[] values, Int32 left, Int32 right, IComparer`1 comparer)

   [5/30/2008 1:59:44 PM]: Progress: Export Completed.

   [5/30/2008 1:59:44 PM]: Finish Time: 5/30/2008 1:59:44 PM.

   [5/30/2008 1:59:44 PM]: Completed with 0 warnings.

   [5/30/2008 1:59:44 PM]: Completed with 1 errors.

   have you seen anything like this before ?

   Reply
9. 

   Stefan Goßner
   On 2. June 2008 Permalink

   Hi Li,

   please open a support case to get this analyzed.

   Cheers,

   Stefan

   Reply
10. 

    Jack
    On 10. July 2008 Permalink

    HI Stefan,

    I have a feature, that is not installed on one of two farms. how is the updatepath for the second farm to update in that way, that both are equal?!

    Please let me know.

    the feature, that is missing is called "S2SiteAdmin".

    Please le mw know, in cause of a customerneedance for a running CD..

    Thanks and bye for now,

    jack

    Reply
11. 

    Stefan Goßner
    On 10. July 2008 Permalink

    Hi Jack,

    that means that both servers are on different hotfix levels.

    You need to ensure that both servers are on the same hotfix level.

    Cheers,

    Stefan

    Reply
12. 

    Richard
    On 18. August 2008 Permalink

    Hi Stefan,

    I have a similar problem when trying to perform a content deployment between 2 seperate farms. The error I get is as follow:

    <ReportMessage Title="Could not find Feature S2SiteAdmin. at Microsoft.SharePoint.Deployment.ImportRequirementsManager.VerifyFeatureDefinition(SPRequirementObject reqObj) at Microsoft.SharePoint.Deployment.ImportRequirementsManager.Validate(SPRequirementObject reqObj) at Microsoft.SharePoint.Deployment.ImportRequirementsManager.DeserializeAndValidate() at Microsoft.SharePoint.Deployment.SPImport.VerifyRequirements() at Microsoft.SharePoint.Deployment.SPImport.Run()" Time="2008-08-18T19:15:18.5846804Z" Severity="Error" Phase="ImportInProgress" />

     <ReportMessage Title="Content deployment job ‘Remote import job for job with sourceID = 20eca940-3a65-4804-bb75-f45fef4af181’ failed.The exception thrown was ‘Microsoft.SharePoint.SPException’ : ‘Could not find Feature S2SiteAdmin.’" Time="2008-08-18T19:15:19.8034304Z" Severity="Error" Description="" Recommendation="" Phase="ImportInProgress" />

     </ArrayOfReportMessage>

    I do not seem to find much on the net for this. Let me know if you have seen this.

    Thanks

    Richard

    Reply
13. 

    Stefan Goßner
    On 8. September 2008 Permalink

    Hi Richard,

    this will happen if the hotfix level of the target farm is lower than the hotfix level of the source farm.

    Please keep the hotfix level in sync between the different farms to avoid such problems.

    Cheers,

    Stefan

    Reply
14. 

    Ken
    On 10. November 2008 Permalink

    Hi Stefan,

    I have also faced the error "S2SiteAdmin". However, I try to export the site from web application A and import to web application B in the same farm.

    This seems that the error "S2SiteAdmin" is not related to hotfix level.

    Thanks.

    Regards,

    Ken

    Reply
15. 

    Stefan Goßner
    On 10. November 2008 Permalink

    Hi Ken,

    your specific issue seems to be different. Has the database been moved to a different farm using backup/restore?

    Because it seems as if some of the MOSS features coming with the product are missing on the file system.

    Cheers,

    Stefan

    Reply
16. 

    Ken
    On 10. November 2008 Permalink

    Hi Stefan,

    Thanks for your reply.

    The database has not been moved since the farm is created. Moreover, I tried to export different site from web application A and import the site to web application B. The site can be imported successfully.

    For your information, the moss farm version is 12.0.0.6324. The site which has import error contain a "search center" sub site.

    Could you like to talk more about feature "S2SiteAdmin?

    Thanks a lot

    Regards,

    Ken Tsui

    Reply
17. 

    Stefan Goßner
    On 10. November 2008 Permalink

    Hi Ken,

    the version number you mentioned is the WSS version number of your system. What is the MOSS version number?

    Please check the file version of your Microsoft.SharePoint.Portal.dll and Microsoft.SharePoint.Publishing.dll

    Cheers,

    Stefan

    Reply
18. 

    Ken
    On 10. November 2008 Permalink

    Hi Stefan,

    I installed the MOSS and then upgrade to SP1. I applied the hotfix ( 946517,953137,941422) and then applied Infrastructure Updates. Finally, I applied hotfix (956248)

    Microsoft.SharePoint.Portal.dll  and Microsoft.SharePoint.Publishing.dll version are 12.0.6318.5000

    How to check the MOSS version number? I have check the Central Administration site and it also mention that the version is 12.0.0.6324.

    I get a verson 3.1.5.0 from the content database table (dbo.version). Is it a version number of MOSS?

    Regards,

    Ken

    Reply
19. 

    Stefan Goßner
    On 10. November 2008 Permalink

    Hi Ken,

    the central admin always only lists the WSS version. The MOSS version can only be seen by looking at the DLLs I mentioned.

    Here you are pre-Infrastructure update.

    I would suggest to install the Infrastructure update or the October CU on the system:

    http://blogs.technet.com/stefan_gossner/archive/2008/10/29/the-october-cumulative-update-for-wss-v3-and-moss-2007-has-been-released-yesterday.aspx

    Cheers,

    Stefan

    Reply
20. 

    Ken
    On 10. November 2008 Permalink

    Hi Stefan,

    Thanks for your reply,

    I would like to know whether I can applied Oct CU directly and bypass August CU?

    Regards,

    Ken

    Reply
21. 

    Stefan Goßner
    On 10. November 2008 Permalink

    Hi Ken,

    yes that is ok. If the problem still occurs after applying the October CU please open a support case to get this analyzed.

    To check if the October CU has been applied correctly please check the version of the following files:

    Microsoft.SharePoint.dll

    Microsoft.SharePoint.Publishing.dll

    They should have build 6332 and 6331.

    Cheers,

    Stefan

    Reply
22. 

    DraheAnd
    On 12. December 2008 Permalink

    Hi,

    did anyone get the issue with the following message solved?

    Value does not fall within the expected range.

     at Microsoft.SharePoint.SPSecurity.ValidateSecurityOnOperation

    It is from Li’s message above. It is really frustrating because it is not possible to get a solution to this problem. I always get this error when I try to export a publishing site. Exporting the childs itself finishes without errors. But I cannot import these exports because the importer reports dependencies between the subsites that I cannot resolve. If I import site a it states site b is not present and vice versa.

    I would be very pleased, if it would be possible to solve this issue.

    Regards,

    Andreas

    Reply
23. 

    Stefan Goßner
    On 12. December 2008 Permalink

    Hi Andreas,

    please check with the WssAnalyzeFeatures tool. This should be a different flavor of the same issue.

    Cheers,

    Stefan

    Reply
24. 

    Anonymous
    On 16. January 2009 Permalink

    In the past I have released several blogs about the various problems that can occur with Content Deployment.

    Reply
25. 

    Appaji
    On 4. February 2009 Permalink

    hi,

    i am getting following error while runing jobs

    Could not find Feature S2SiteAdmin. at Microsoft.SharePoint.Deployment.ImportRequirementsManager.VerifyFeatureDefinition(SPRequirementObject reqObj) at Microsoft.SharePoint.Deployment.ImportRequirementsManager.Validate(SPRequirementObject reqObj) at Microsoft.SharePoint.Deployment.ImportRequirementsManager.DeserializeAndValidate() at Microsoft.SharePoint.Deployment.SPImport.VerifyRequirements() at Microsoft.SharePoint.Deployment.SPImport.Run()

    Reply
26. 

    Stefan Goßner
    On 5. February 2009 Permalink

    Hi Appaji,

    that means that your two farms are not on the same hotfix level.

    Content deployment requires that both farms are on the same hotfix level.

    Cheers,

    Stefan

    Reply
27. 

    Till Skidzun
    On 10. March 2009 Permalink

    Hi,

    we had also the error "Could not find Feature S2SiteAdmin. at Microsoft.SharePoint.Deployment.ImportRequirementsManager …" during a content deployment. Because we were sure that both farm has the same hotfix level, we tried the command

    "stsadm -o installfeature -name S2SiteAdmin" on the target farm. This seems to work…

    Kind regards

    Till

    Reply
28. 

    David
    On 30. April 2009 Permalink

    Thank you sooooo much for writting these tools – they are a complete life saver!!!

    Reply
29. 

    Trevor
    On 21. July 2009 Permalink

    Thank you for this blog posting and your feature analyzer!  Excellent!

    Reply