|
|
Rank: Newbie
Joined: 5/15/2008
Posts: 2
Location: Denmark
|
I have 2 sites (version 3.0.5) that are giving me big problems. Both sites keeps crashing the .Net WorkerProcess. I happens when i wan't to create a (sub item / new page).
Error msg:
An unhandled exception occurred and the process was terminated.
Application ID: /LM/W3SVC/1307918377/Root
Process ID: 6208
Exception: System.NullReferenceException
Message: Object reference not set to an instance of an object.
StackTrace: at Lucene.Net.Store.FSIndexOutput.Finalize()
Does anyone have any idea's why? And by the way, I've already read this thread (http://forum.umbraco.org/yaf_postst4134_Lucene-Error-Crashing-net-worker-process.aspx) but it concerns an earlier version of Umbraco.
Kind regards
Jais Holstein
Kind regards
Jais Holstein
|
|
Rank: Newbie
Joined: 5/15/2008
Posts: 2
Location: Denmark
|
Hi
It seems that I solved the problem myself.
I think the solution is: Make sure each umbraco site has a unique application name in IIS.
Kind regards
Jais Holstein
|
|
Rank: Umbracoholic
Joined: 9/27/2007
Posts: 1,136
Location: Belgium
|
Great! And thanks for sharing the answer! Greetz, /Dirk
level 1 & 2 certified - umbraco MVP 2008/2009 - umbraco blog at netaddicts.be - working on an integrated forum4umbraco
|
|
Rank: Newbie
Joined: 4/10/2008
Posts: 12
Location: Denmark, Copenhagen
|
I was having the same problem, and downloaded v. 2.0.0.4 of Lucene.Net.dll from http://incubator.apache.org/lucene.net/download/The version of Lucene.Net.dll included in umbraco 3.0.5 is version 1.9.0.0. This solved it for me.
|
|
Rank: Addict
Joined: 7/19/2006
Posts: 671
Location: Preston, UK
|
milandt,
Did the indexing not break? The indexing > 1.9 has changed and it breaks the umbraco lucene indexing code. I dont think the search stuff has changed so it may be if things are'nt broken that its using the index that you already have?
Regards
Ismail
Level 2 certified. If it aint broke dont fix.
|
|
Rank: Newbie
Joined: 4/10/2008
Posts: 12
Location: Denmark, Copenhagen
|
imayat12 wrote:milandt,
Did the indexing not break? The indexing > 1.9 has changed and it breaks the umbraco lucene indexing code. I dont think the search stuff has changed so it may be if things are'nt broken that its using the index that you already have?
Regards
Ismail Well, something did break after upgrading Lucene.Net.dll included 1.9.0.0 to version 2.0.0.4. I had the same problem as Jais described, which was solved by upgrading this dll, but after this I had problems deleting stuff from umbraco. Whenever I deletes an item it is only partial deleted, and garbage is left in the umbracoNode table, which causes the UI to screw up, and a number of other errors. Leaves me with a broken installation which I will need to recover, and the original issue as Jais described. :(
|
|
Rank: Addict
Joined: 3/17/2008
Posts: 982
Location: Nyborg, Denmark
|
Milandt,
Shoot me an email and lets get this issue solved. Makes sense that upgrading from 1.9 to 2.0.x of lucene can break an umbraco implementation; after all it's two different versions of Lucene even though they share the assembly name ;-)
/n
Jeeeez, did I really start this :-)
|
|
Rank: Newbie
Joined: 4/10/2008
Posts: 12
Location: Denmark, Copenhagen
|
hartvig wrote:Milandt,
Shoot me an email and lets get this issue solved. Makes sense that upgrading from 1.9 to 2.0.x of lucene can break an umbraco implementation; after all it's two different versions of Lucene even though they share the assembly name ;-)
/n Sent a mail to umbraco support - you can pick it up from there.
|
|
Rank: Addict
Joined: 7/19/2006
Posts: 671
Location: Preston, UK
|
Guys, I also blogged about 1.9 to 2.0 a while back see http://ismail.umbraco.net/2008/4/22/merge-dlls.aspxRegards Ismail
Level 2 certified. If it aint broke dont fix.
|
|
|
Guest |