View Issue Details

IDProjectCategoryView StatusLast Update
0007733MMW v4DB/FileMonitorpublic2011-05-12 19:36
ReporterLudek Assigned To 
PriorityimmediateSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Fixed in Version4.0 
Summary0007733: MM should not crash when DB is stored in a location that cannot be accessed
DescriptionFor users that have MM.DB stored in a network location can happen that MM cannot access the DB for whatever reason (e.g. missing AV s/w rules to allow file sharing for local IP).

MediaMonkey should show error message that MM.DB cannot be accessed.
Additional Informationhttp://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=11316
TagsNo tags attached.
Fixed in build1372

Activities

jiri

2011-05-05 07:17

administrator   ~0024854

I think that user should be warned in this case and possibly also get an option to create a new MM.DB file in the standard location. E.g. something like:

Library file \\...\MM.DB can't be opened, would you like to create a new local Library?
[Yes] [[Retry]] [Cancel]

We can leave this unlocalized for 4.0, or defer for 4.1.

rusty

2011-05-05 14:42

administrator   ~0024866

String looks good. Setting to 'immediate' so that the string is included right away.

Ludek

2011-05-06 10:48

developer   ~0024891

Fixed in build 1370.

lowlander

2011-05-10 17:21

developer   ~0025024

Choosing Cancel threw AV.

Similarly to: http://www.ventismedia.com/mantis/view.php?id=7466 it should ask to login to network location before showing failure to load DB. (I tested with a network share that requires login).

Ludek

2011-05-10 19:39

developer   ~0025038

Fixed in build 1372.

lowlander

2011-05-12 19:36

developer   ~0025137

Verified in 1373 that networked DB will ask login before loading MM.