cannot open db file on another drive

[tugadaq1]

New Install of MM 2024 refuses to open db file on any drive except C. User has full permissions on drives, can open, create and delete files on those drives. The ini file has been updated. The db is the db created initially in users roaming file on installation.
Message is:

Library database E:\Media\MediaMonkey2024\"n:\MM5.DB can't be opened, would....local Library?<br><br>Failed to open database....

OS is Windows 11 Pro 24H2 fully updated.

[Lowlander]

E:\Media\MediaMonkey2024\"n:\MM5.DB

It seems the path may have been set incorrectly.

Related: https://www.mediamonkey.com/support/kno ... ini-files/

[tugadaq1]

New install of MM on Win Pro 24H2 (Updated). MM will not open data base on any drive other than C drive. User has Full Control Permission on drives and can create and delete files on those drives. Attempted on 2 separate drives with same results.
Message: Library database E:\Media\MediaMonkey2024\"n:\MM5.DB can't be opened, would you.....local library?<br><br>Failed open.....

[Timo_Beil]

Message: Library database E:\Media\MediaMonkey2024\"n:\MM5.DB can't be opened,

A path with two driveletters?
Please check and correct the DBName= entry in your Mediamonkey.ini

[tugadaq1]

A review of the dbname does indeed show the addition of the the E:\Media\MediaMonkey2024\ as part of the path. I remove it, check the file path and it is correct ie dbname=n:\MM5.db. Then when I open MM I get the same error. Check the dbname and discover MM has added E:\Media\MediaMonkey2024\ back to path. That addition is the path to the MM exe.

[Peke]

A review of the dbname does indeed show the addition of the the E:\Media\MediaMonkey2024\ as part of the path. I remove it, check the file path and it is correct ie dbname=n:\MM5.db. Then when I open MM I get the same error. Check the dbname and discover MM has added E:\Media\MediaMonkey2024\ back to path. That addition is the path to the MM exe.

Are you using MM portable?

[tugadaq1]

So far as I know, I am not using portable. Never have. Unless I made a mistake on this last installation the answer is no, but I do not know how to confirm that.

[Lowlander]

Copy the Path from the Location in Properties of the db file in File Explorer and add it to [url[https://www.mediamonkey.com/support/kno ... ini-files/]DBName in the ini[/url]. Just to make sure there is no issue with characters in the Path you used.

Presumably the N drive is accessible when you launch MediaMonkey?

Also, which Build (Help > About) of MediaMonkey are you running?

[tugadaq1]

2024.0.0.3082
Using copy path does not change results. N drive is full accessible - it is my 'temporary' drive where stuff is added and deleted every day.

[Lowlander]

You're using an old release. Can you please try with the latest MediaMonkey 2024.2 beta and see if this resolves the issue: https://www.mediamonkey.com/forum/viewt ... 86639&sd=d

[Peke]

So far as I know, I am not using portable. Never have. Unless I made a mistake on this last installation the answer is no, but I do not know how to confirm that.

As N is Temporary drive may I suggest that you install MM as Portable on N Drive and start MM from there, because you do not need to have DBName ini file anymore.

Let me know if you need steps how to setup.

[tugadaq1]

The temp drive was an attempt to isolate the problem. The drive that i wish to use is "H:\OneDrive\MediaMonkeyDatabase\Den\MM5.DB". I thought maybe that the fact that it was on one drive was the problem, so I moved it to the temp drive as a test.

I had MM installed on this computer without problems until another issue cause me to reload an earlier image file that had not yet had MM installed. I also have installed on laptops without problems using the same music from onedrive.

The question is why is MM writing to the ini file and more specifically why is it writing to the dbname

[Peke]

Hi,

The question is why is MM writing to the ini file and more specifically why is it writing to the dbname

INI files is uses for MM Settings and it is constantly read/write. I tried today on several PCs with few MM versions and could not replicate DBName change from Within MM it looks like read only value for me.