?
Solved

How do I Identify and Resolve STSADM -o PreUpgradeCheck errors for SharePoint 2010 Upgrade?

Posted on 2010-09-10
8
Medium Priority
?
3,311 Views
Last Modified: 2012-05-10
Greetings!

After two failures so far upgrading to SP 2010 from MOSS 2007, I've fallen back on a previous snapshot of the server farm in order to run through the upgrade preparation checks that I've seen posted online.  We're trying to do an In-Place upgrade.

I ran the stsadm -o preupgradecheck and everything passed (or was "informational"), except for one error.  During the processing of the configuration file, it said "ServerConfigErrors... FAILED".  

I'm not sure what failed exactly, but when the "SharePoint Products and Technologies Pre-Upgrade Check Report" was displayed, I get these types of errors (there's a lot of them).

Id = 94e9c166-264a-f84b-2377-bccefb8b3771, Type = Unknown, Reference = 56, Status = Missing
Id = f2c50a02-9894-4ace-bb3f-4146a24cd940, Type = Unknown, Reference = 47, Status = Missing
Id = 2242cce6-491a-657a-c8ee-b10a2a993eda, Type = Unknown, Reference = 11884, Status = Missing
Id = ce9aa113-48cf-ddee-0c03-597445e5b7ab, Type = Unknown, Reference = 340, Status =

I have tried looking those IDs up on Google, but as of yet have not found any useful information.
because the "SharePoint Products and Technologies Pre-Upgrade Check Report" does not state where those IDs were found (which site collections, etc), I ran the following command:

stsadm.exe -o enumallwebs -includewebparts > c:\users\admin\desktop\enumallwebs.log.txt

This, at least, gave me an idea of where to look for the missing "things" (the upgrade report doesn't tell if it's web parts, lists, users, or what...).  

Here is what the enumallwebs command spat out:


  <Database SiteCount="1" Name="content_HR" DataSource="MOSS2007PortalSvr">
    <Site Id="e37080a9-b996-4916-9fbb-842a8f0a81d4" OwnerLogin="MyDomain\john.doe1" InSiteMap="True">
      <Webs Count="2">
        <Web Id="f3ad2bd7-a61f-4363-992f-7af12dbfa29a" Url="/HR" LanguageId="1033" TemplateName="STS#0" TemplateId="1">
          <WebParts>
            <WebPart Id="d55b3b6b-6281-707b-73d0-0c49581475ad" Count="2" Status="Missing" />
            <WebPart Id="f5c3ff60-e752-3a90-84f8-3677f8384e2d" Count="4" Status="Missing" />
            <WebPart Id="f2c50a02-9894-4ace-bb3f-4146a24cd940" Count="4" Status="Missing" />
            <WebPart Id="ce9aa113-48cf-ddee-0c03-597445e5b7ab" Count="1" Status="Missing" />
            <WebPart Id="e60f6c95-e86c-4717-2c0d-6d8563c9caf7" Count="1" Status="Missing" />
            <WebPart Id="293e8d0e-486f-e21e-40e3-75bfb77202de" Count="41" Status="Missing" />
            <WebPart Id="2242cce6-491a-657a-c8ee-b10a2a993eda" Count="41" Status="Missing" />
            <WebPart Id="74bd016c-baa0-14a8-d5d8-b75dc7e6f429" Count="2" Status="Missing" />
            <WebPart Id="fb35a198-aea0-3c26-e40c-df473fe9b07b" Count="4" Status="Missing" />
            <WebPart Id="669602d9-e116-ccb8-eea3-e37ad589b14b" Count="2" Status="Missing" />
            <WebPart Id="f5897322-ddd4-c990-d012-f9d4fe2180ad" Count="4" Status="Missing" />
          </WebParts>
        </Web>
        <Web Id="5ab276d4-593e-41be-8319-95223777e848" Url="/HR/IT" LanguageId="1033" TemplateName="STS#1" TemplateId="1">
          <WebParts>
            <WebPart Id="ce9aa113-48cf-ddee-0c03-597445e5b7ab" Count="1" Status="Missing" />
            <WebPart Id="293e8d0e-486f-e21e-40e3-75bfb77202de" Count="9" Status="Missing" />
            <WebPart Id="2242cce6-491a-657a-c8ee-b10a2a993eda" Count="9" Status="Missing" />
          </WebParts>
        </Web>
      </Webs>
    </Site>
  </Database>

However, when I go look at those web sites (/HR, for instance), I don't see any reference for those web parts.  I've tried adding "contents=1" to the end of the URL (ie - http://MOSS2007PortalSvr/HR/default.aspx?contents=1) to see if the web parts were just "closed", but nothing came up.

I also went to Site Actions > Edit Page > click Add Web Part > choose "Advanced Web Part Gallery" > and looked at the "Closed Web Parts" gallery.  This gallery had nothing in it.

Has anyone ever encountered these errors in their upgrades?  Or what steps they took to prepare the farm for an upgrade?  We don't have very much customization (unless you count SP Designer to enhance the way the sites look).  Almost all of our site collections were migrated from another server farm (Windows Server 2003 > Server 2008), but both had the same version of MOSS running on them.

I'm very interested in hearing what other experts have to say about this.  The upgrade is very important to me (read: my job?), and so far I have not found any information on how to resolve this.  Occasionally, I'll get one step closer, but never quite there.  


0
Comment
Question by:ThatSharepointGuy
  • 4
  • 2
7 Comments
 
LVL 38

Expert Comment

by:Justin Smith
ID: 33651759
do you have custom web parts in your farm?  was this an upgrade from 2003?
0
 
LVL 6

Author Comment

by:ThatSharepointGuy
ID: 33652155
There are custom web parts, I'm sure.  We have a development team that codes web applications for one of the organizations under mine, although I'm not a developer myself.  I've spoken with them a few times, and it seems to me that most of their "custom" web parts are Content Editor Web Parts.

I've been the admin here for about 7 months now, so all I know is that it's a 2007 farm.  However, I've asked if any of the servers were upgrades from 2003 and the answer was no.  I've also asked, instead of the servers being from 2003, if any of the sites were migrated from a 2003 server to a 2007 server.  The answer was still no.


0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 33653939
Curious if you have a bunch of closed web parts on the HR/IT site.  Can you check?  If you choose to add a new web part to the site, you should be able to choose "closed web parts" from the edit menu on the right.  Wondering if the web parts it's complaining about are closed instead of deleted.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 6

Author Comment

by:ThatSharepointGuy
ID: 33654147
I tried that as well, and nothing.  
I went to  Site Actions  > Edit Page > click Add Web Part > choose "Advanced Web Part  Gallery" > and looked at the "Closed Web Parts" gallery.  This gallery had nothing in it.

I also added "?contents=1" to the end of the URL, and it showed nothing there as well.

For most subwebs from the enumallwebs output, it looks like the same three GUIDs for the web part on each site.  Some have more, but there are quite a few sites, in different site collections, that have the same three GUIDs.

           <WebPart Id="ce9aa113-48cf-ddee-0c03-597445e5b7ab" Count="1" Status="Missing" />            <WebPart Id="293e8d0e-486f-e21e-40e3-75bfb77202de" Count="9" Status="Missing" />            <WebPart Id="2242cce6-491a-657a-c8ee-b10a2a993eda" Count="9" Status="Missing" />

I just don't know how to tell which web parts these were.

0
 
LVL 6

Accepted Solution

by:
ThatSharepointGuy earned 0 total points
ID: 33692887
I found out what it was, but as for what to do about it without angering my customer base, I'm not sure.

It turns out that one of the site collections had Publishing features turned on, although the template it was using wasn't a Publishing template.  So this is what I think the errors are for now, because when I checked the logs, this particular site collection had a ton of errors (the exact same number of errors that the upgrade failed at) for Publishing features.

I'm going to see if I can't create a blank publishing site and then export the site, import it into that, and then try the upgrade.  I'm not sure if only the top-level site in the site collection being a publishing site would fix this though, but it's worth a try.

Of course, I could always disable Publishing features, but that will break anything that might be using them.  I know that they have some sort of custom navigation drop-down stuff going on, and when I turned the features off in a test environment, it broke all of the navigation.
0
 
LVL 6

Author Comment

by:ThatSharepointGuy
ID: 33692892
So for the upgrade, i dismounted the database that this site collection was using with powershell, and the rest of the upgrade went fine.  I've just got to work on this site collection a bit more and hopefully i'll be able to keep everything intact.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 34636983
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In case you ever have to remove a faulty web part from a page , add the following to the end of the page url ?contents=1
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
Suggested Courses

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question