Sharepoint 3.0 to Foundation 2010 Migration Issue
-
Freitag, 18. Mai 2012 12:20
Hello,
I'm down to 4 errors now. I just can't seem to find any solutions on how to fix it. Here are the errors i'm receiving currently:
[powershell] [SPSiteWssSequence2] [WARNING] [5/16/2012 4:08:20 PM]: Feature could not be upgraded. Exception: Feature definition id '367b94a9-4a15-42ba-b4a2-32420363e018' could not be found.
[powershell] [SPSiteWssSequence2] [INFO] [5/16/2012 4:08:24 PM]: SPSite Url=http://sharepoint
[powershell] [SPSiteWssSequence2] [WARNING] [5/16/2012 4:08:24 PM]: Feature could not be upgraded. Exception: Feature definition id '75a0fea7-fe65-41c3-a965-c5df83fb098b' could not be found.
[powershell] [SPSiteWssSequence2] [INFO] [5/16/2012 4:08:24 PM]: SPSite Url=http://sharepoint
[powershell] [SPSiteWssSequence2] [WARNING] [5/16/2012 4:08:24 PM]: Feature could not be upgraded. Exception: Feature definition id '75a0fea7-b0ef-434e-90d6-ce997d970564' could not be found.
[powershell] [SPSiteWssSequence2] [INFO] [5/16/2012 4:08:29 PM]: SPSite Url=http://sharepointThese 3 features that will not install are: ReportServer - Says its already installed and lists a different GUID
ListPropertyFeature - See Below
PostProvisioningFeature - Says it can't install
PS C:\Users\admin> stsadm -o installfeature -name ListPropertyFeature
Failed to load receiver assembly "ListPropertyHandler, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9b
ce111e9429c" for feature "ListPropertyFeature" (ID: 75a0fea7-fe65-41c3-a965-c5df83fb098b).: System.IO.FileNotF
oundException: Could not load file or assembly 'ListPropertyHandler, Version=12.0.0.0, Culture=neutral, Public
KeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
File name: 'ListPropertyHandler, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Ass
embly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlM
ark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark
& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DW
ORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].Also how do i fix a webpart missing?
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [65539348-52e5-ad3e-ba5a-a670c2704e5a] is referenced [8] times in the databas
e [WSS_Content], but is not installed on the current farm. Please install any feature/solut
ion which contains this web part.
Remedy : One or more web parts are referenced in the database [WSS_Content], but are not installed o
n the current farm. Please install any feature or solution which contains these web parts.Thank You: JP
Jpyzowski -- PC Works Plus
Alle Antworten
-
Freitag, 18. Mai 2012 13:14
If you're this close, I would go ahead and mount the database. You can then examine your sites for any potential issues such as missing features or web parts.Corey Roth - SharePoint Server MVP blog: www.dotnetmafia.com twitter: @coreyroth
- Als Antwort markiert Rock Wang– MSFT Samstag, 26. Mai 2012 06:38
-
Freitag, 25. Mai 2012 01:02
Hello,
well i got it mounted and tested. everything seems to work fine so far. I did try to upgrade the view and that ended in disaster. Not sure what to do so i reverted back to my backup and restored.
Jpyzowski -- PC Works Plus

