Rusty:

Ludek already fixed it in 1232, something about the re-indexing of the full search text, it was added to to the maintain library - complete optimize database. See ticket 5438.

Nyn

nynaevelan or zvezdanD,

So if I understand correctly, the problem occurs independently of any scripts.

In that case can you either:
a) generate a debug log of this happening?
b) send me a copy of your DB so that we can reproduce it?

Thanks.

-Rusty

1232 appears to have fixed the problem for me, I am not getting any more errors.

Nyn

Ludek:

This is great news, thank you. It is always good to read that I can get my rebellious db fixed.

Nyn

Nyn, see:
http://www.ventismedia.com/mantis/view.php?id=5438

Once build 1231 is available then download it and run
Maintain Library -> [x] Optimize database (complete)

I've tested on your DB and it fixes your issue by re-creating the full text search index.

[quote="MoDementia"]Hmm 2 days after 3.1 is released I make this post [url]http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=34568[/url] :roll:[/quote]

True but it doesn't help me now. :cry:

Hmm 2 days after 3.1 is released I make this post [url]http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=34568[/url] :roll:

Yes,
thank you.

Now, I can reproduce too without any scripts.
As you are saying:
if I input "move" -> works
if I input "come" -> works
if I input "m" -> works
if I input "t" -> the error appears!

It seems that the DB has been somehow corrupted, rather a part of the DB (the full text search index). I have opened one issue in Mantis http://www.ventismedia.com/mantis/view.php?id=5438

Nyn, in order to ensure me it is the case could you finish 4? i.e.
[quote]I clean my db on a weekly basis so this shouldn't be a factor. When you say rescan do you mean start with a new db? If so, that is not an option I have playcounts which I cannot lose, my entire listening experience is based on my playcounts and playlists. But I will test with a "new" db in my test account.[/quote]
i.e. try to start with a new DB, but just for this "testing" purposes.
We are working on fix for your current DB and the new DB could help us to find the cause of corruption.

Thank you.

This problem is not related with the scripts at all. As I said, I removed all scripts and I got that error.

By the way, in meantime I tried rest of your filters and I am getting same error, so it seems that all filters are affected.

EDIT: I am getting error even without any filter applied. It seems that any string which begins with "t" that doesn't exist as a whole word in your library causes an error.

BTW; here are all the scripts which I have installed in case there is some other conflict involved: http://www.mediafire.com/?sharekey=2238f9326e9eb21691b20cc0d07ba4d2111658e91f7c7386

Nyn

THANK YOU!!! I was starting to think I was losing my mind. :D

I removed all scripts from Auto folder, choose your "Editing - Library Editing" filter, choose Genre node and when I typed "te" I got same error as you. This error happens with Entire Library and Library (filtered), but not with the Current selection. It is obviously something wrong with the filtering engine in MM. Tested 1228, 1218, 1213 - all have same problem, with 1211 I got access violation error. Versions 1208, 1209 cannot start with your database at all.

[url=http://img18.imageshack.us/my.php?image=nyn0.png][img]http://img18.imageshack.us/img18/2203/nyn0.png[/img][/url]

When I click Ignore I get:
[url=http://img300.imageshack.us/my.php?image=nyn1.png][img]http://img300.imageshack.us/img300/2902/nyn1.png[/img][/url]

When I choose ignore I get:
[url=http://img18.imageshack.us/my.php?image=nyn2.png][img]http://img18.imageshack.us/img18/7944/nyn2.png[/img][/url]

I've tried it again and again and with or without a combination of scripts I still get the error. Then I changed my search options to "search whole words only" and so far I have not run into problems. But for those who are testing with my db I seem to always run into problems when searching for "teena marie" it will pop up the error before I finish typing in tee. I've tried it with the now playing list empty and with tracks. I also cleaned out left over script info from the mediamonkey.ini file. I have put all my scripts back into production and I will continue to test with the following search options to see if the problem stays clear or returns. By the way all of my searches were conducted on a filtered library using either the Editing - Library Editing or NP - All Playcounts (No Xmas) filters, which are my two main filters.

[img]http://farm4.static.flickr.com/3650/3392127340_9145a5d113_o.jpg[/img]

Nyn

I tried that but I am not getting any consistent results, I am thinking it has to be a conflict between two or more running together. But I cannot figure out what the problem is, but it has to be something recent since I have only been plagued with this since 1227 came out. One of the problems that are frustrating me is the fact that I have not added any new scripts to my arsenal, all of these are scripts which I have been using for some time, so it has to be one that has been updated recently. But once again it is hard to figure out which it is. So I will be slowly adding them back in hoping to figure out where the culprit lies...

Event Logger works fine with your database, there is no error when I use Search (MM 3.1.0.1228).

You don't have too much suspicious scripts. Why don't you try to return back one by one to see with which one this error happens?