Just upgraded to mm3 (said to be vista compatable!?) from older version, which tho buggy, did work with farily frequent crashes...
I got round the problem by installing an older alpha over the top of my recent install, deleting the library, then reinstalling the newest version.
hey presto! it worked!
Joe

Just to confirm, I had the same thing happen.

I just wanted to confirm that I too am getting this error. Mine is happening when scanning some mp3s in the root of my music folder. I too cannot 'Retry' or 'Ignore' successfully. I am running b1 on Vista Ultimate and have also started from scratch without success.

Jiri has said it will be fixed on the next release...let's hope is not too long before that! (If the same release rate that was going on with alphas goes on with betas, then don't expect it to be ready before a week or two)...also, if your monkey is really unusable, you can always go back to Alpha 8

Did a complete uninstall of MM3 and reinstall. Hit the same error pretty early in a file monitor scan. Can a quick fix be delivered for this fatal bug??? I upgraded (again) to Gold so I could use the Monkey on my Vista box. I'm now dead in the water. (I know it is beta, but this is worse than any alpha bug I had to deal with).

Steegy wrote:This ugly thing was crawling over the keyboard:

Oooo nasty, wouldn't want to get bitten by that!

I get the same error while dragging mp3 files into the now playing list. Below you will find a description of the different cases.

operating system: WinXp SP2
Media Monkey Version: beta 1, showing now playing list

Case 1: - Dragging one single mp3 file into the list
-> error occurs
-> when pressing cancel or ignore, error window disappears
-> mp3 file is listed in the now playing list and works fine

Case 2: - Dragging several mp3 files into the list
-> error occurs
-> when pressing cancel, error window disappears
-> when pressing ignore, error window disappears and appears again depending on the number of songs
-> mp3 file are listed in the now playing list and can be used

Case 3: - Dragging a directory containing mp3 files
-> no error occurs
-> songs are usable in the list

Case 4: - Dragging a directory containing only subdirectories
-> no error occurs
-> no files are shown in the list
-> MM seems to read only one directory layer

Case 5: - Dragging a directory containing subdirectories and mp3 files
-> error sometimes (but reproducible) occurs
-> only the mp3 files in the highest directory layer are shown


Example:
Directory structure ACDC\ containing 1.mp3 and 2.mp3

- When dragging the ACDC folder, no error occurs
- When dragging the 1.mp3, the error occurs

Does this observation clear anything?

Regards

Maaspuck

This ugly thing was crawling over the keyboard:

jiri wrote:Correction: it will be fixed in the next release.

Hi Jiri, any chance you can tell us what it was?

Correction: it will be fixed in the next release.

Jiri

Judas (or anyone else),

Please send me the problem folder that triggers this. Maybe it'll give us a clue.

Thx.

-Rusty

Agree to Teknojnky

Getting this too, both imported mm2.5 database and a clear new one.

I'm having the same problem. Choosing two of the three options, Retry or Ignore, results in a hung MM and I have to go to the task manager to kill MM. Tried deleting my DB but it keeps happening. If a MM DB does not exist, does a new one get created automatically? This blocking error makes B1 worse than the Alphas from my perspective.

I'm looking into this with more detail...i was wrong, i hadn't deleted those files i mentioned.

I identified the culprit now, I don't know whether its a single file, a folder or MM's DB fault. If the developers want I can .zip you the problem folder and see if you can identify the problem?

If I delete the problem folder: No Problem
If the folder is empty (but still exists): No Problem
If the folder has one of four files: Error occurs
If folder has any mp3 (except above mentioned four files): Error Occurs

It's a really strange problem, cause the error isn't related to the files but to any file inside the problem folder...

@tarasis: can you do any further testing as to confirm any of the above?