MediaMonkey forum

I´ve had Mediamonkey for a lot of time now and i´ve never had a problem like this, please help me.

First i had problems from time to time when trying to access the tracks i had on an external HD (where i had all my music). I thought it was because there where some conection problem or something like that and i copied every song into the internal HD (my intention is to use the external one as backup of my mp3s). Then i deleted from the database every song i had... at the end i found that there where 1 album with only 4 songs still on it. Every time i try to delete/play/whatever i got an error.

Then i tryed uninstalling (and deleting everything related to mediamonkey, like scripts just in case) and reinstalling again (i redownloaded the last version) , no luck (i´ve tried 2 times).

Now everytime i open Mediamonkey i get this error:



And everytime i try to add the tracks to the library, after a short time (100 tracks added more or less) i get this two errors alternating:





Can you help me PLEASE?
I love Mediamonkey and now im craving... have mercy.

it means your database is corrupted, either from a windows crash (blue screen or power out maybe?) or a MM crash perhaps.

your probly gonna have to delete (or rename) your mm.db and start a new one... or if you have a backup you could try copy that over mm.db.



Database location
Windows XP: C:\Documents and Settings\<USERNAME>\Local Settings\Application Data\MediaMonkey\MM.DB
Windows Vista: C:\Users\<USERNAME>\AppData\Local\MediaMonkey\MM.DB

cant find any MM.DB,,,

windows has the user app data files are hidden by default, you probly have to enable the 'show hidden and system files' options in explorer...

Just do this:
del C:\Users\<USERNAME>\AppData\Local\MediaMonkey\MM.DB
in windows console (windows key + r, then type cmd)

thnaks, this helped me alot!

BIG THANK YOU all men

I had a message about a problem querying the database, after it played a track and was trying to update the PlayCounter, LastTimePlayed & TrackModifed. I clicked Retry and it continued with playing the next track.

Based on the replies above, I closed MM (3.0.2.1134) & renamed the MM.DB database.

When I restarted MM I received another message about querying the database (error creating table Medias). I clicked retry and it continued with starting MM. I then re-scanned my directories to recreate the database of my music.

I found one of my recently imported albums to have extra tracks that did not belong to the album. So, I decided to remove the album for the library and physically from disk.

I then re-ripped the CD. After completing the ripping I selected to add an image for the album cover and received another error about a problem querying the database. This time with insert into the COVERS table.

I was going to post the images of the errors, but unable to determine where that option is.

Anyway, if you want more details of the messages, let me know.

What can be done to rectify this problem?

I did not have the problem when using 2.5 nor when I originally upgraded to 3..0.1.

Thanks

I've received a further two database query errors.

Are there any other files besides MM.DB to be deleted?

Thanks

I once again lost my database. I guess it was a crash but didn't see it appear. I closed the program and then many hours later restarted MM. When I was presented with no songs, no playlist, but a few songs on the current list.

When it started it asked if I wanted to load my 2.5 database, which I said no to.

Went looking for the database and found MediaMonkey.MDB in
- C:\Program Files\MediaMonkey
- C:\Documents and Settings\Administrator\My Documents\My Music\MediaMonkey

The file in Program Files was dated 21 dec 2005 & the two in "Documents and Settings" folder for MediaMonkey were dated 13 Nov 2007 & 22 Nov 2007. One of those databases was named "MediaMonkey.mdb.~mdb".

I renamed all of the extensions to be something else.

This time when I started MediaMonkey, I found my music database and the playlists.

I wonder if this was the cause of my other corrupted databases.

Will let you know if it happens again.