I have a site which I inherited and I believe started out life as an early v4 install. An upgrade earlier in the year saw the site move to a more recent v4 install (4.11.4) but the logs are full of errors similar to the one below:
Error loading actionhandler 'umbSearchUpdate': System.IO.FileLoadException: Could not load file or assembly 'Lucene.Net, Version=1.9.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'Lucene.Net, Version=1.9.0.0, Culture=neutral, PublicKeyToken=null' at umbracoUtilities.umbSearchResult.AddPageToIndex(Int32 PageID) at umbracoUtilities.SearchUpdateActionHandler.Execute(Document documentObject, IAction action) at umbraco.BusinessLogic.Actions.Action.RunActionHandlers(Document d, IAction action) 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'm guessing its a legacy thing but unfortunately I can't just remove this with any confidence due to the size and complexity of the site and not knowing currently what it is likely being used for.
Any ideas/pointers appreciated as neither Google or forums have turned up much in the way of information on this particular dll.
umbracoUtilities used to have autoform,search and contentype it also used old version of lucene which is what it is moaning about so on publish the indexing actionhandler is firing. You should be able to get rid of it.
The old search in the bad old days before the wonder that is examine it was done using search in umbracoUtilities the content type thing was just a macro you could drop on your template to change page type eg text/xml so it would change the response header.
The project used to be on codeplex it seems to have been removed?
Turns out I can't just remove it. I need to look at this again today but they have some elements of the site using this. I'm yet to track down v1.9.0.0 of the assembly so I can setup a bindingRedirect in the app in order to have 2 versions of the library.
I need to check back but the first occurrence I think it was something to do with setting content type headers but I have no clue atm as to where else it may be used. The site I inherited is a real over-complicated mess, all of this needs to be re-factored but I was/am looking for a "quick fix" in the interim until I get the budget to clear this all up properly.
What is/was umbracoUtilities.dll ?
I have a site which I inherited and I believe started out life as an early v4 install. An upgrade earlier in the year saw the site move to a more recent v4 install (4.11.4) but the logs are full of errors similar to the one below:
I'm guessing its a legacy thing but unfortunately I can't just remove this with any confidence due to the size and complexity of the site and not knowing currently what it is likely being used for.
Any ideas/pointers appreciated as neither Google or forums have turned up much in the way of information on this particular dll.
Thanks, Simon
Simon,
umbracoUtilities used to have autoform,search and contentype it also used old version of lucene which is what it is moaning about so on publish the indexing actionhandler is firing. You should be able to get rid of it.
Regards
Ismail
Thanks for the info Ismail. I remember autoform but what are the search and content elements within the library?
Simon
The old search in the bad old days before the wonder that is examine it was done using search in umbracoUtilities the content type thing was just a macro you could drop on your template to change page type eg text/xml so it would change the response header.
The project used to be on codeplex it seems to have been removed?
Thanks, I will give it a trial run and see how it goes.
Turns out I can't just remove it. I need to look at this again today but they have some elements of the site using this. I'm yet to track down v1.9.0.0 of the assembly so I can setup a bindingRedirect in the app in order to have 2 versions of the library.
Simon, What part of utilities they using?
Regards
Ismail
I need to check back but the first occurrence I think it was something to do with setting content type headers but I have no clue atm as to where else it may be used. The site I inherited is a real over-complicated mess, all of this needs to be re-factored but I was/am looking for a "quick fix" in the interim until I get the budget to clear this all up properly.
Simon
if you find where its being used get rid of the macro and use inline code to set the header then you can get rid.
Regards
Ismail
is working on a reply...