Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

Error: Method not found: 'Void Bring2mind.Lucene.Net.Index.INdexWriter.Commit()'
Last Post 06/05/2012 10:06 PM by Peter Donker. 9 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Brandon Hartsell
New Member
New Member
Posts:73


--
01/04/2012 4:27 PM
Filnal step of uploading a file it get: Method not found: 'Void Bring2mind.Lucene.Net.Index.INdexWriter.Commit()'

The file does upload however.

I did do this and it did not resolve the issue.
http://bring2mind.net/Sup...ic/Default.aspx#8763

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
01/09/2012 10:50 AM
It is complaining that it can't find that component. Have you checked disk permissions in the bin folder and on that dll specifically?

Peter
Nicolo Pitsch
New Member
New Member
Posts:18


--
01/26/2012 3:44 PM
Hello
Here the same error:

-----------

ModuleId: 1049
ModuleDefId: 191
FriendlyName: Dokumente
ModuleControlSource: DesktopModules/Bring2mind/DMX/Dispatch.ascx
AssemblyVersion: 6.1.2
RawURL: /Intern/Dokumente/tabid/443/Default.aspx?Command=Core_Edit&CollectionId=22&EntryType=File
AbsoluteURL: /Default.aspx
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 3ad4cf39-d90e-4a2b-89f5-def131b60336
InnerException: Methode nicht gefunden: "Void Bring2mind.Lucene.Net.Index.IndexWriter.Commit()".
Method: Bring2mind.DNN.Modules.DMX.Services.Search.LuceneSearchProvider.LuceneSearchProvider.AddDocument
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Methode nicht gefunden: "Void Bring2mind.Lucene.Net.Index.IndexWriter.Commit()". ---> System.MissingMethodException: Methode nicht gefunden: "Void Bring2mind.Lucene.Net.Index.IndexWriter.Commit()". bei Bring2mind.DNN.Modules.DMX.Services.Search.LuceneSearchProvider.LuceneSearchProvider.AddDocument(EntryInfo Entry) bei Bring2mind.DNN.Modules.DMX.Controls.EditEntry.ᜀ() bei Bring2mind.DNN.Modules.DMX.Controls.EditEntry.IntermediateFinishButton_Click(Object sender, EventArgs e) --- Ende der internen Ausnahmestapelüberwachung ---

--------------
I have installed the latest DMX version 06.00.02
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
01/26/2012 4:18 PM
This is a DNN error. It sometimes doesn't copy in the latest dll. You'll need to copy in the dlls by hand.

Peter
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
01/26/2012 5:22 PM
I've tried replicating the behavior but can't until now. Can someone tell me what the upgrade order was of both DNN and DMX?

Peter
Brandon Hartsell
New Member
New Member
Posts:73


--
01/26/2012 5:26 PM
I upgraded DNN then DMX.
Nicolo Pitsch
New Member
New Member
Posts:18


--
01/26/2012 6:16 PM
I did update to dnn6 and then installed dmx 6.0.1.

I could solve the problem according to this thread:
http://bring2mind.net/Sup...fr/9160/Default.aspx

Thanks
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
01/29/2012 9:37 AM
What I'm looking for is an accurate "recipe" to reproduce this. I.e. exact version nrs (before and after) and order of installation. I've tried a DNN 4 to 5 to 6 upgrade and then a DMX upgrade from 5 to 6 but this problem did not occur.

Peter
40Fingers
New Member
New Member
Posts:3


--
06/05/2012 11:08 AM
version dnn 523 -> upgrade to 615, test, test, test: no problems

dmx 539 -> upgrade to 603, this issue crops up. further testing in progress

Peter
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
06/05/2012 10:06 PM
Actually the Lucene ... Indexwriter.Commit not found error has been found. It is due to the fact that DNN 5 incorrectly labels the auxiliary dlls of a module with the same version as the module. So the previous Lucene dll was labeled as ver 5.3.9 or whatever. That is actually wrong and should be 2.x. Now the next update of DMX tries to write a later version of the Lucene library (still in 2.x somewhere) and DNN refuses to install it.

Unfortunately, as this is an edge case, DNN Corp is reluctant to move on this. So that's more or less where it stops.

Peter
You are not authorized to post a reply.