I hope no-one minds me repeating this post, but I previously posted it in someone else's thread that was marked as "solved", so wasn't sure it was going to get any attention.
I have installed XSLTSearch on an Umbraco 4.6.1 system and keep getting the error below when I try and save XSLTSearch.xslt:
Cannot find a script or an extension object associated with namespace 'urn:PS.XSLTsearch'.
I ran the debugging script designed to highlight missing DLLs mentioned on page 4 of this thread and got the output below. Can anyone advise about this mysterious "Castle.DynamicProxy2"? :-)
Someone please help as I was relying on this search for my website search and I'll be stuck if I can't get it to work!
Thanks, Jenni
Assembly: Remotion, Version=1.13.52.2, Culture=neutral, PublicKeyToken=0669cf0452175907 Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Castle.DynamicProxy2, Version=2.1.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies. The system cannot find the file specified. File name: 'Castle.DynamicProxy2, Version=2.1.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' 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].
Follow up to this: I think it's a clash between XSLTSearch and another Umbraco component I installed to read data from Excel. The Excel package uses a newer version of log4net (1.2.11), whereas XSLTSearch uses 1.2.10. I am now totally stuck, as I cannot use both versions of the same DLL. :-(
As the original thread noted, you may need to copy the System.Web.Mvc.dll file from a computer with asp.net mvc2 installed to the ~/bin folder of your site.
This does nothing for a newer version of log4net but I can tell you that XSLTsearch doesn't use log4net or any dlls. However, resolving the underlying issue either by upgrading to Umbraco 4.6.2 or later, or sorting out the dll issue as Alex describes it (probably by including the mvc dll) may take care of everything.
Thanks for the reply! I understand what you're saying about XSLTSearch not actually using log4net, but the usage of it triggering a problem Umbraco 4.6.1 has.
Unfortunately the reason I chose 4.6.1 is because we run IIS6 on our server. I'm not aware of 4.6.2 - isn't this AKA 4.7, which must run on IIS7?
I had earlier tried the MVC dll after reading the thread you mentioned, however in my case it didn't make any difference.
Error when saving SearchXSLT file in Umbraco 4.6.1 - "urn:PS:XSLTsearch"
Hi All,
I hope no-one minds me repeating this post, but I previously posted it in someone else's thread that was marked as "solved", so wasn't sure it was going to get any attention.
I have installed XSLTSearch on an Umbraco 4.6.1 system and keep getting the error below when I try and save XSLTSearch.xslt:
Cannot find a script or an extension object associated with namespace 'urn:PS.XSLTsearch'.
I ran the debugging script designed to highlight missing DLLs mentioned on page 4 of this thread and got the output below. Can anyone advise about this mysterious "Castle.DynamicProxy2"? :-)
Someone please help as I was relying on this search for my website search and I'll be stuck if I can't get it to work!
Thanks,
Jenni
Assembly: Remotion, Version=1.13.52.2, Culture=neutral, PublicKeyToken=0669cf0452175907
Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Castle.DynamicProxy2, Version=2.1.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies. The system cannot find the file specified. File name: 'Castle.DynamicProxy2, Version=2.1.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' 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].
Types from App_Code: PS.XSLTsearch
Follow up to this: I think it's a clash between XSLTSearch and another Umbraco component I installed to read data from Excel. The Excel package uses a newer version of log4net (1.2.11), whereas XSLTSearch uses 1.2.10. I am now totally stuck, as I cannot use both versions of the same DLL. :-(
Hi, Jenni,
The problem isn't with XSLTsearch per se (it uses no dlls at all). Rather, it is related to how an early version of Umbraco loaded dlls (see Alex' description of the problem at http://our.umbraco.org/projects/website-utilities/xsltsearch/xsltsearch-bugs/16139-Error-when-saving-XSLT-file-in-Umbraco-46-beta?p=4#comment65597). This has been fixed in later versions of Umbraco (4.6.2 and later) and is a worthwhile upgrade if that's an option for your site.
As the original thread noted, you may need to copy the System.Web.Mvc.dll file from a computer with asp.net mvc2 installed to the ~/bin folder of your site.
This does nothing for a newer version of log4net but I can tell you that XSLTsearch doesn't use log4net or any dlls. However, resolving the underlying issue either by upgrading to Umbraco 4.6.2 or later, or sorting out the dll issue as Alex describes it (probably by including the mvc dll) may take care of everything.
cheers,
doug.
Hi Doug,
Thanks for the reply! I understand what you're saying about XSLTSearch not actually using log4net, but the usage of it triggering a problem Umbraco 4.6.1 has.
Unfortunately the reason I chose 4.6.1 is because we run IIS6 on our server. I'm not aware of 4.6.2 - isn't this AKA 4.7, which must run on IIS7?
I had earlier tried the MVC dll after reading the thread you mentioned, however in my case it didn't make any difference.
Thanks,
Jenni
is working on a reply...