locked
Error when running PSCONFIG SP2013 RRS feed

  • Question

  • Recently we had  moved a Site (Site A)  from SP2013 Farm to another site (Site B) in the same Farm  as a subsite. Following the move, we patched the farm and got errors , which indicated issues with the Site B.    Error message was: MossSiteSequence ajywk ERROR Exception: Invalid field name. {32e03f99-6949-466a-a4a6-057c21d4b516} http://xxxxx.yyyyy.net  07c74b79-53fe-4923-aa1b-f6e1e17fda3c                This was followed by: SPUpgradeSiteSession ajxnk INFO SPSite Url=http://xxxxx.yyyyy.net  07c74b79-53fe-4923-aa1b-f6e1e17fda3c
    03/19/2016 07:03:49.61 powershell (0x1514) 0x1338 SharePoint Foundation Upgrade SPUpgradeSiteSession ajxnk ERROR Upgrade [SPSite Url=http://xxxxx.yyyyy.net] failed. Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence has the ContinueOnFailiure bit set. Moving on to the next object in sequence. 07c74b79-53fe-4923-aa1b-f6e1e17fda3c                           We disconnected the content database of the site (Site B)  and successfully ran PSCONFIG for the farm. The site (Site A) is still in the FARM a READ only site (with a different URL)and it did not fail  the PSConfig.  I plan on deleting the subsite and recopying the Site A to Site B using powershell or Metalogix. Any other suggestions here?  Thanks                          

    MP

    Monday, April 4, 2016 7:17 PM

Answers

  • From the primary site , removed the sub sites that caused issues following which psconfig completed successfully.

    MP

    • Proposed as answer by Dean_Wang Thursday, April 28, 2016 8:04 AM
    • Marked as answer by Victoria Xia Sunday, May 8, 2016 11:44 AM
    Monday, April 25, 2016 3:02 PM

All replies

  • You have to make sure that the solution that brings the field 32e03f99-6949-466a-a4a6-057c21d4b516 into the site is installed or enabled in both farms, otherwise you will always get the error while running the wizard. If for some reason you can not deploy that, you will always have upgrade failed error and functionality rely on this field will not work.  You will see the errors in upgrade-error.log file and on central administration.

    Jerry Yasir - Office Server & Services MVP/MCT Hewlett Packard Enterprise - If this reply helped you resolve your issue, please propose as answer. It may help other community members. Thanks!

    Monday, April 4, 2016 7:40 PM
  • Looks Like you have a content type associated with your site. 

    Content Type Name Content Type ID Field Internal Name Field ID
    Reusable HTML 0x01002CF74A4DAE39480396EEA7A4BA2BE5FB ShowInRibbon 32e03f99-6949-466a-a4a6-057c21d4b516


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://krossfarm.com

    • Proposed as answer by Dean_Wang Friday, April 15, 2016 1:47 AM
    Tuesday, April 5, 2016 1:50 AM
  • Yes. One site Master Page template had customization. Working on resolving the issue. Thanks for the response

    MP

    Tuesday, April 5, 2016 6:21 PM
  • Thanks for the input. Have setup the site in a development environment to test solution based on the error reported.

    Thanks again


    MP

    Tuesday, April 5, 2016 6:25 PM
  • Hi MP,

    Is there any update?

    If Waqas' reply is helpful to you, you can mark as answer.

    Thanks,

    Dean Wang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, April 15, 2016 1:46 AM
  • We restored the content database for site with issues in our QA environment and tried recommended solutions. Yes. Both recommendations lead to a solution, however, we got new errors popup. Finally, we deleted the new subsites created importing the data from a legacy site and were able to successfully complete psconfig in QA.

    We will try it in our production environment next weekend. If we are successful, we will provide a link in the left navigation to the Legacy data which resides in the original location. Easy way out. but better than spending hours  fixing an issue which provides no added value to our clients.


    MP

    Friday, April 15, 2016 9:14 AM
  • From the primary site , removed the sub sites that caused issues following which psconfig completed successfully.

    MP

    • Proposed as answer by Dean_Wang Thursday, April 28, 2016 8:04 AM
    • Marked as answer by Victoria Xia Sunday, May 8, 2016 11:44 AM
    Monday, April 25, 2016 3:02 PM
  • Hi MP,

    Thanks for your sharing.

    Thanks,

    Dean Wang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, April 28, 2016 8:04 AM