I am going through an upgrade from WSS 3.0 to WSS Foundation 2010. I am using several articles to help me with the upgrade.
I have worked my way through creating the new web application and removing the content database. Now I am testing the database for Features, Assemblies, and Setup files for any missing components. I have one missing Feature and one missing setup
file. I determined which Feature to copy over from the old WSS 3.0 server by searching for the Id number referenced in the Message Remedy. I copied the folder over to the new server in the same path (only difference is 14 instead of 12).
When I run
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES>stsadm -o installfeature -name vascSiteAction
I get an error like this....
Failed to load receiver assembly "VASCSiteAction, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c3d77e0415d83b05" for feature "vascSiteAction" (ID: fc5e2840-0b48-42eb-9ad7-076f5add58ad).: System.IO.FileNotFoundException: Could not
load file or assembly 'VASCSiteAction, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c3d77e0415d83b05' or one of its dependencies. The system cannot find the file specified.
File name: 'VASCSiteAction, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c3d77e0415d83b05'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase,
Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boo
lean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& 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] (DWORD) 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].
I am stuck and cannot figure out why the Feature will not install. Can someone help me get past this? thanks already









