Faceted Upgrade

Jan 29, 2008 at 5:26 AM
Has anyone upgraded their install to the latest 2.0? If so did you do anything special and or run into any issues?
Jan 30, 2008 at 7:50 PM
Edited Jan 30, 2008 at 7:54 PM
After i installed the new 2.0 version as an upgrade, the webparts on the SearchCenter results page failed.

I had to rename the Faceted Search 2.0.wsp file in the downloaded zip to Faceted Search 2.0.cab and unpack it. The unpacked cab contains the webparts of the 2.0 version. After manually inserting the version 2.0 webparts to the webparts library and removing and reapplying the new webparts on the searchcenter results page, the upgraded faceted search worked as expected. We have been using it from the day of the release.

Version 2.0 is experienced by our users as a major advencement and a perfect search 'buddy'. As such, it has become an invaluable addition to our search.
Jan 30, 2008 at 11:18 PM
So i tried to just install it, seemed to go fine. However the old webparts still remained. I deleted them and de-activated --- Re-actived the feature. Then i saw the new webparts there. However when i went to the results page the old webparts where still showing. So i removed and tried to re-add and it gave me an error message about the Faceted search dll being the wrong version.

Thoughts
Jan 30, 2008 at 11:30 PM
ok i searched and there are some of the 1.x dll and some of the 2.0 dll


i renamed the 1.x dll and kaboom, went bad. So i changed the name back Advice on how to get unstuck?
Jan 30, 2008 at 11:35 PM
ok just for some clarification here is the error i get when i try to add the new webpart

Unable to add selected web part(s)
Search Facets: could not load file or assembly "microsoft.sharepoint.portal.extendedSearch, Version=2.0.0.0, culture=neutral, publickey Token=a646907c4a695009 or one of its dependancies The located assembly's manifest definition does not match the assemly reference. (exception from Hresult: 0x80131040
Jan 31, 2008 at 7:55 PM
I assumed that the Microsoft.SharePoint.Portal.ExtendedSearch.dll was located in the GAC but it isn't. It's in the bin directory. My first thoughts were a version conflict with several of the same assemblies in the GAC, only difference should be then the GUID.
Can you check the bin directory? (lokated in inetpub\wwwroot\wss\virtual directories\yourwebapp\bin) is the dll available and what version is it?
If you view the xml or export the web part and then view the source (can be done via "site settings" ==> "web parts") you'll find a line between the metadata tags, similar to: <type name="Microsoft.SharePoint.Portal.ExtendedSearch.WebControls.SearchFacets, Microsoft.SharePoint.Portal.ExtendedSearch, Version=2.0.0.0, Culture=neutral, PublicKeyToken=a646907c4a695009" />

Let me know the results, if you need any help, mail me :-)
Jan 31, 2008 at 9:03 PM


Stoneford wrote:
I assumed that the Microsoft.SharePoint.Portal.ExtendedSearch.dll was located in the GAC but it isn't. It's in the bin directory. My first thoughts were a version conflict with several of the same assemblies in the GAC, only difference should be then the GUID.
Can you check the bin directory? (lokated in inetpub\wwwroot\wss\virtual directories\yourwebapp\bin) is the dll available and what version is it?
If you view the xml or export the web part and then view the source (can be done via "site settings" ==> "web parts") you'll find a line between the metadata tags, similar to: <type name="Microsoft.SharePoint.Portal.ExtendedSearch.WebControls.SearchFacets, Microsoft.SharePoint.Portal.ExtendedSearch, Version=2.0.0.0, Culture=neutral, PublicKeyToken=a646907c4a695009" />

Let me know the results, if you need any help, mail me :-)


Thanks for the response. Yes I found the DLL in a few places the bin folder being the one that went boom. Both DLL's are in bin directory. However I renamed the 2.0 one as when it is the primary one nothing works.

The webparts in the webpart gallery are 2.0 as shown below
type name="Microsoft.SharePoint.Portal.ExtendedSearch.WebControls.SearchFacets, Microsoft.SharePoint.Portal.ExtendedSearch, Version=2.0.0.0, Culture=neutral, PublicKeyToken=a646907c4a695009" />
<importErrorMessage>Cannot import this Web Part.</importErrorMessage>



<type name="Microsoft.SharePoint.Portal.ExtendedSearch.WebControls.SearchBreadCrumbs, Microsoft.SharePoint.Portal.ExtendedSearch, Version=2.0.0.0, Culture=neutral, PublicKeyToken=a646907c4a695009" />
<importErrorMessage>Cannot import this Web Part.</importErrorMessage>


on the seach results webpage it appears that they are using the old webparts, so when i add the new ones for 2,0 thats when things go boom....

Thoguhts>
Jan 31, 2008 at 9:48 PM
Ok, seems you've the correct dll in the bin folder and the correct web parts are installed.
What's located in the folder C:\Program Files\Common Files\microsoft shared\web server extensions\12\TEMPLATE\FEATURES\FacetedSearch?
Did you install SharePoint SP1? (I have no idea of FS 2.0 is suitable for SharePoint SP1)
You did an upgrade, is version 1.x still installed? (I don't know if you've checked this one. In Central Administration ==> operations ==> solution management)
I assume you grabbed the installer and didn't do a rebuild of the source code?
You are indeed using the 2.0 web parts because it can't find the correct dll (which is Microsoft.SharePoint.Portal.ExtendedSearch, Version=2.0.0.0, PublicKeyToken=a646907c4a695009)
I will discuss this with a colleague tomorrow. It's time to catch some sleep :-)

Feb 1, 2008 at 1:29 AM
OK So I am up and running on 2.0 here is what I did

1. Removed the webparts form the search results pages
2. De(deployed) search facet features from the web app
3.. Deleted any remaining DLL;s stragling round
4. Re-deployed feature to web app
5. Added web parts back to Search Page
WAMMO fixed

I am interested in seeing what other schemas, and columns people are using as facets and hearing about cool configs people are using.....anyone want to share?
Feb 1, 2008 at 8:58 AM
Good to hear you're up and running :-)
Coordinator
Feb 1, 2008 at 7:39 PM
It seems that Install Guide can be complimented by Common Problems Guide. Would be glad to gather comments. As of upgrade, the 2.0 will not remove previous WPs from the Web Part Gallery if those exist. Also, it will not remove WPs from the search result page.


cgeier wrote:
Has anyone upgraded their install to the latest 2.0? If so did you do anything special and or run into any issues?

May 21, 2008 at 11:44 PM
I have installed 2.0 on a couple of machines and the install went without any problems.  Today I tried to install on our main intranet and install went fine, but when I tried to activate the feature I got the following:

Feature '4ad6146d-6ada-4931-ab81-0e179de7008e'  cound not be installed because the loading of event receiver assembly "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009" failed:System.IO.FileNotFoundExceptioin:  Could not load file or assembly "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009" or one of its dependencies.  The system cannot find the file specified.  "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009"...

If more is needed let me know and I can provide it.  Our maintenance window wasn't long enough to sit and figure it out so I am going to tried loading it up again later this week. 

Thanks for any help on this issue.
Coordinator
May 22, 2008 at 4:20 AM
Normally such exception occurs if the strong name of the assembly doesn't much to the one used by the solution. Often it happens due to the wrong name in the manifest.xml. Please check or post your manfest.

jikner wrote:
I have installed 2.0 on a couple of machines and the install went without any problems.  Today I tried to install on our main intranet and install went fine, but when I tried to activate the feature I got the following:

Feature '4ad6146d-6ada-4931-ab81-0e179de7008e'  cound not be installed because the loading of event receiver assembly "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009" failed:System.IO.FileNotFoundExceptioin:  Could not load file or assembly "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009" or one of its dependencies.  The system cannot find the file specified.  "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009"...

If more is needed let me know and I can provide it.  Our maintenance window wasn't long enough to sit and figure it out so I am going to tried loading it up again later this week. 

Thanks for any help on this issue.


May 22, 2008 at 11:19 AM
leonidly,

Thanks for the reply, my install is straight from the Faceted setup.exe.  I downloaded the zip file last week and ran it on a couple of or other networks with no issues.  So the manifest.xml is the one right from the download.  Here is the manifest.xml that came with the download.

Thanks again for the help.


 
<?xml version="1.0" encoding="utf-8" ?>
- <!--
 Solution created by WSPBuilder. 3/11/2008 2:17:58 PM 
  -->
- <Solution xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" SolutionId="d9da20ea-87db-4d39-b6e8-ce1cac4fab3c" DeploymentServerType="WebFrontEnd" ResetWebServer="True" xmlns="http://schemas.microsoft.com/sharepoint/">
- <FeatureManifests>
  <FeatureManifest Location="FacetedSearch\feature.xml" />
  </FeatureManifests>
- <Assemblies>
- <Assembly Location="Microsoft.SharePoint.Portal.ExtendedSearch.dll" DeploymentTarget="WebApplication">
- <SafeControls>
  <SafeControl Assembly="Microsoft.SharePoint.Portal.ExtendedSearch, Version=2.0.0.0, Culture=neutral, PublicKeyToken=a646907c4a695009" Namespace="Microsoft.SharePoint.Portal.ExtendedSearch.WebControls" TypeName="*" Safe="True" />
  </SafeControls>
  </Assembly>
  </Assemblies>
- <TemplateFiles>
  <TemplateFile Location="IMAGES\DeployReportInfo.gif" />
  <TemplateFile Location="IMAGES\DLMAX.GIF" />
  <TemplateFile Location="IMAGES\DLMIN.GIF" />
  <TemplateFile Location="IMAGES\ewr237s.gif" />
  <TemplateFile Location="IMAGES\FacetedSearchFeature.gif" />
  <TemplateFile Location="IMAGES\FacetedSearchWP.gif" />
  <TemplateFile Location="IMAGES\filteroff.gif" />
  <TemplateFile Location="IMAGES\kpiprogressbar.gif" />
  <TemplateFile Location="IMAGES\progressdone.gif" />
  <TemplateFile Location="LAYOUTS\FacetedSearch.js" />
  </TemplateFiles>
- <Resources>
  <Resource Location="FacetedSearch\SearchBreadCrumbs.webpart" />
  <Resource Location="FacetedSearch\SearchFacets.webpart" />
  </Resources>
- <CodeAccessSecurity>
- <PolicyItem>
- <PermissionSet class="NamedPermissionSet" version="1" Description="WSPBuilder generated permissionSet" Name="Microsoft.SharePoint.Portal.ExtendedSearch446647aa-2f12-4707-85b7-e1d8af885861">
  <IPermission class="System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Level="None" />
  <IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Flags="Execution" />
  <IPermission class="System.Security.Permissions.RegistryPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Unrestricted="true" />
  <IPermission class="Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" version="1" ObjectModel="True" />
  <IPermission class="Microsoft.SharePoint.Security.WebPartPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" version="1" Connections="True" />
  <IPermission class="SecurityPermission" version="1" Flags="Execution" />
  <IPermission class="WebPartPermission" version="1" Connections="True" />
  <IPermission class="System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Level="Minimal" />
  <IPermission class="Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" version="1" ObjectModel="True" />
  <IPermission class="System.Security.Permissions.RegistryPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Unrestricted="true" />
  </PermissionSet>
- <Assemblies>
  <Assembly Name="Microsoft.SharePoint.Portal.ExtendedSearch" Version="2.0.0.0" PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100257FAE170ABB2AB4A8EF914DFEA757F7DB8C221F01850FC8753A4C6585C0B07749DA33DF4D64A721A070E7CDCDEFC8C786E3626418389BCF461E4300E6F4C477BE5CE64AD12C29D517208D6BA627D9F73A9066B7638BE1FEE3EABE6C3E537B546CB3B5DE5E436F95278BB1E9DBDE85C2A6B624010A8073841D467CC7A0A0C6C8" />
  </Assemblies>
  </PolicyItem>
  </CodeAccessSecurity>
  </Solution>


leonidly wrote:
Normally such exception occurs if the strong name of the assembly doesn't much to the one used by the solution. Often it happens due to the wrong name in the manifest.xml. Please check or post your manfest.

jikner wrote:
I have installed 2.0 on a couple of machines and the install went without any problems.  Today I tried to install on our main intranet and install went fine, but when I tried to activate the feature I got the following:

Feature '4ad6146d-6ada-4931-ab81-0e179de7008e'  cound not be installed because the loading of event receiver assembly "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009" failed:System.IO.FileNotFoundExceptioin:  Could not load file or assembly "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009" or one of its dependencies.  The system cannot find the file specified.  "Microsoft.SharePoint.Portal.ExtenedSearch, Version=2.0.0.0, Cluture=neutral, PublicKeyToiken=a646907c4a695009"...

If more is needed let me know and I can provide it.  Our maintenance window wasn't long enough to sit and figure it out so I am going to tried loading it up again later this week. 

Thanks for any help on this issue.





Jun 17, 2008 at 11:47 PM

Hi Jikner,

Where can I find the manifest file?

Thanks,
Vaegy

Jun 18, 2008 at 2:23 PM
Make a copy of the faceted.wsp and rename to .cab and then open with WinZip.