This project is read-only.

Another Faceted Search on Search Server Express error

Mar 27, 2008 at 7:04 PM
Although I get the same error on the search results page as the discussion Error installing Faceted Search on Search Server Express and I have applied the suggested fix for it; the problem is still present. The log file appears to indicate a problem to do with .Net permissions.
My install is onto a clean Windows 2003 Standard Server running on virtual machine, with MSSExpress installed, which appeared to work fine. When I then installed Faceted Search I get the error The type initializer for 'Microsoft.Office.Server.EvaluatorModeProvisioning.OfficeServerProductToProvision' threw an exception.
on the results page in the location where the Faceted webpart should show.

The log file follows:
Your search cannot be completed because of a service error.
Try your search again or contact your administrator for more information. --->
System.TypeInitializationException:
The type initializer for 'Microsoft.Office.Server.EvaluatorModeProvisioning.OfficeServerProductToProvision' threw an exception.
---> System.Security.SecurityException:
Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' failed.
at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet)
at System.Security.CodeAccessPermission.Demand()
at System.Reflection.Assembly.VerifyCodeBaseDiscovery(String codeBase)
at System.Reflection.Assembly.GetName(Boolean copiedName)
at System.Reflection.Assembly.GetName()
at Microsoft.Office.Server.EvaluatorModeProvisioning.OfficeServerProductToProvisionctor
(String id, String name, String provisioningAssemblyWithoutExtention, String fullyQualifiedProvisioningClass)
at Microsoft.Office.Server.EvaluatorModeProvisioning.OfficeServerProductToProvisioncctor()
The action that failed was: Demand
The type of the first permission that failed was: System.Security.Permissions.FileIOPermission
The first permission that failed was: <IPermission class="System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" version="1"
PathDiscovery="C:\WINDOWS\assembly\GACMSIL\Microsoft.Office.Server\12.0.0.0_71e9bce111e9429c\Microsoft.Office.Server.dll"/>
The demand was for: <IPermission class="System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" version="1"
PathDiscovery="C:\WINDOWS\assembly\GACMSIL\Microsoft.Office.Server\12.0.0.0_71e9bce111e9429c\Microsoft.Office.Server.dll"/>
The granted set of the failing assembly was:
<PermissionSet class="System.Security.PermissionSet" version="1">
<IPermission class="System.Security.Permissions.RegistryPermission, mscorlib, Version=2.0.0.0, Culture=neutral,PublicKeyToken=b77a5c561934e089" version="1" Unrestricted="true"/>
<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.StrongNameIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1"
PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100257FAE170ABB2AB4A8EF914DFEA757F7DB8C221F01850FC8753A4C6585C0B07749DA33DF4D64A721A070E7CDCDEFC8C786E3626418389BCF461E4300E6F4C477BE5CE64AD12C29D517208D6BA627D9F73A9066B7638BE1FEE3EABE6C3E537B546CB3B5DE5E436F95278BB1E9DBDE85C2A6B624010A8073841D467CC7A0A0C6C8"
Name="Microsoft.SharePoint.Portal.ExtendedSearch" AssemblyVersion="2.0.0.0"/>
<IPermission class="System.Security.Permissions.UrlIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral,PublicKeyToken=b77a5c561934e089" version="1"
Url="file:///C:/Inetpub/wwwroot/wss/VirtualDirectories/80/bin/Microsoft.SharePoint.Portal.ExtendedSearch.DLL"/>
<IPermission class="System.Security.Permissions.ZoneIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" version="1" Zone="MyComputer"/>
<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="Microsoft.SharePoint.Security.WebPartPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" version="1" Connections="True"/>
</PermissionSet>
The assembly or AppDomain that failed was: Microsoft.SharePoint.Portal.ExtendedSearch, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=a646907c4a695009
The method that caused the failure was: System.Data.DataTable GetResults(Int32)
The Zone of the assembly that failed was: MyComputer
The Url of the assembly that failed was: file:///C:/Inetpub/wwwroot/wss/VirtualDirectories/80/bin/Microsoft.SharePoint.Portal.ExtendedSearch.DLL
--- End of inner exception stack trace ---
at Microsoft.Office.Server.Administration.SetupLicensing.get_InstalledOfficeServersProduct()
at Microsoft.Office.Server.Search.Administration.SearchContext.get_IsSupportedTopology()
at Microsoft.Office.Server.Search.Query.Query.ThrowIfUnSupportedTopologyForMSSExpress()
at Microsoft.Office.Server.Search.Query.KeywordQuery.Execute()
at Microsoft.Office.Server.Search.WebControls.SearchResultHiddenObject.GetResultData()
--- End of inner exception stack trace ---
at Microsoft.Office.Server.Search.WebControls.SearchResultHiddenObject.GetResultData()
at Microsoft.Office.Server.Search.WebControls.SearchResultHiddenObject.get_ResultsReturned()
at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.ModifyXsltArgumentList(ArgumentClassWrapper argList)
at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform()
erException 1: System.TypeInitializationException:
The type initializer for 'Microsoft.Office.Server.EvaluatorModeProvisioning.OfficeServerProductToProvision' threw an exception.
---> System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet)
at System.Security.CodeAccessPermission.Demand()
at System.Reflection.Assembly.VerifyCodeBaseDiscovery(String codeBase)
at System.Reflection.Assembly.GetName(Boolean copiedName)
at System.Reflection.Assembly.GetName()
at Microsoft.Office.Server.EvaluatorModeProvisioning.OfficeServerProductToProvisionctor(String id, String name, String provisioningAssemblyWithoutExtention,
String fullyQualifiedProvisioningClass)
at Microsoft.Office.Server.EvaluatorModeProvisioning.OfficeServerProductToProvision..cctor()
The action that failed was: Demand The type of the first permission that failed was:
System.Security.Permissions.FileIOPermission
The first permission that failed was:
<IPermission class="System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
PathDiscovery="C:\WINDOWS\assembly\GACMSIL\Microsoft.Office.Server\12.0.0.0_71e9bce111e9429c\Microsoft.Office.Server.dll"/>
The demand was for: <IPermission class="System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" version="1"
PathDiscovery="C:\WINDOWS\assembly\GACMSIL\Microsoft.Office.Server\12.0.0.0_71e9bce111e9429c\Microsoft.Office.Server.dll"/>
The granted set of the failing assembly was:
<PermissionSet class="System.Security.PermissionSet" version="1">
<IPermission class="System.Security.Permissions.RegistryPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1" Unrestricted="true"/>
<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.StrongNameIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" version="1
" PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100257FAE170ABB2AB4A8EF914DFEA757F7DB8C221F01850FC8753A4C6585C0B07749DA33DF4D64A721A070E7CDCDEFC8C786E3626418389BCF461E4300E6F4C477BE5CE64AD12C29D517208D6BA627D9F73A9066B7638BE1FEE3EABE6C3E537B546CB3B5DE5E436F95278BB1E9DBDE85C2A6B624010A8073841D467CC7A0A0C6C8"
Name="Microsoft.SharePoint.Portal.ExtendedSearch" AssemblyVersion="2.0.0.0"/>
<IPermission class="System.Security.Permissions.UrlIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1" Url="file:///C:/Inetpub/wwwroot/wss/VirtualDirectories/80/bin/Microsoft.SharePoint.Portal.ExtendedSearch.DLL"/>
<IPermission class="System.Security.Permissions.ZoneIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1" Zone="MyComputer"/>
<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="Microsoft.SharePoint.Security.WebPartPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" version="1" Connections="True"/>
</PermissionSet> The assembly or AppDomain that failed was: Microsoft.SharePoint.P
Mar 29, 2008 at 3:40 PM
I ran into the same issue. Step 1: Give the network service the required permission on IIS WAMREG admin Service didn't solve it, but it looks cleaner in the event log anyway ;-).
Step 2: Base install uses the Local Service to run the SSP Web Services. After changing to a dedicated domain searchservice-account, resetting crawled context and starting a full crawl, everything was working like exptected.
May 1, 2008 at 2:21 PM
Edited May 1, 2008 at 2:38 PM
Hey Rainer.

I have the exact same problem as charly. I have tried your solution I think:

1. I have added network service to IIS WAMREG.
2. I did not do a base install I did an advanced install where I used a domain account for the Shared Sevice. I tried to find a way to confirm this. I check in the IIS on the SharedServices application pol and that one runs as a domain user. Is this the correct place? Or how can I look and change the SSP web service user account?
Looked in to the SSP settings and saw that SSP Credential has in the description that this is the credentials used for the Web Service. I have a domain account present here.


We are trying to use MSSX in a project here but this halts us completly. So any quick help would be really appreciated.
Jun 27, 2008 at 5:21 AM
Had the same error on two fo my servers...one at home and one at work.....shouldn't have to worry about this breaking my installs???  Teaches me a lesson not to trust "free" features.
Jun 27, 2008 at 9:00 AM
Just wanted to record how this was resolved in our case.
The issue was due to the configuration of the trust level security setting, which was resolved by editing the web.config <secruityPolicy>.
We hit the problem when undertaking an internal test install of SearchExpress, and so to get it going just set the trust level to "Full" to get round the issue.
We have since moved to a final implementation but did not hit the error on the new machine, so can't advise on how to set the security so that it both works and is still secure
- but thought it interesting to pass on that this is this an area to look into if you have the same problem.
Jun 30, 2008 at 5:09 PM
Can you be more explicet about exactly what you did?  I could guess...but would rather not have to.