View Issue Details

IDProjectCategoryView StatusLast Update
0011029MMW v4DB/FileMonitorpublic2013-09-21 04:07
Reporterpeke Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product Version4.1 
Target Version4.1Fixed in Version4.1 
Summary0011029: When scanning Duplicate location entries are created for some users
DescriptionFor some long time user of MMW he is experiencing Duplicate Location creations after Scanning/Adding new files to library.

Ther is no Specific files but rather creation of Full Duplicate Location (Same serial under new name) with Newly added/updated files in library. But if new location is deleted user loose same tracks on old location too.

Full Logs and User DB (500k+ of tracks) is Uploaded onto FTP.
Additional InformationTicket:
PND-343173
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=71707
TagsNo tags attached.
Fixed in build1648

Relationships

related to 0011006 closedLudek Locate Moved/Missing Tracks automatically during scans 

Activities

Ludek

2013-07-04 12:26

developer   ~0036737

Last edited: 2013-07-04 12:27

I checked the user database, shown all 512061 music files sorted by Path and I see no duplicates.

Also if I search for 'beatles' it shows 28 files in search results and no duplicates, am I missing something?

peke

2013-07-04 22:07

developer   ~0036746

You were right, I contacted user and in remote session we have made new DB with Duplicates.

I'll reassign back to you as soon as I get it.

peke

2013-07-09 02:26

developer   ~0036776

Uploaded new MM.DB

You should see problem with

Artist: 2'nd Chapter Of Acts
Album: With Footnotes

Ludek

2013-07-09 21:38

developer   ~0036782

Last edited: 2013-07-09 21:42

You are true that there are triplicates for that album with same Songs.IDMedia = 17 and same Songs.SongsPath

I've been very surprised how it could happen, but then I found the answer when I read the first post in the user ticket (PND-343173), he attached screenshots in the TMP.zip (100.16 KB) where on the Picture1.bmp he demostrated the original Medias table and on Picture2.bmp how he manually edited that table. He changed DriveLetter for media ID = 17 from letter Z: (DriveLetter = 25) to letter X: (DriveLetter = 23). This broken the relation and causes the issues.

I would suggest to edit it back to the original state.

----------------------------

I've also seen an attached ELF where is a dialog:
Your media files will not be physically copied, but the location of files will be updated in the database from:_[]\Music\ to:_Z:\Music\
Are you really sure that you want to do that?

And soon after that it has frozen on this SQL:
UPDATE Songs SET IDMedia = 12 WHERE IDMedia = 7 AND SongPath LIKE ':\Music\%'

What was that dialog? Is this dialog and the query offered by a script? I've gone through our code and there is no such a feature in MMW natively AFAIK.
Peke, do you know which script can do this?

peke

2013-07-09 22:04

developer   ~0036783

I suspected something like this and your findings confirms it.

Can you please take over the ticket and instruct user what to do or make SQL query that will change DB to correct one using OnStartup Script?

If needed I can do another remote session.

Assign back to me so that I can correct Forum posts, Wiki and create general mail to others what scripts needs to be avoided with caution.

Ludek

2013-07-10 00:12

developer   ~0036787

Instructed the user via ticket PND-343173

Ludek

2013-07-11 14:43

developer   ~0036812

Fixed in build 1648.

There indeed was a problem when drive is replaced and thus two rows with different SN (but same drive letter) exists in the medias table

peke

2013-09-21 04:07

developer   ~0037620

Verified 1659