The plot thickens. Just got home and checked, and apparently the rescan finally went through several times. I've now got 39,051 files registered when there should be 26972. The total number of genres, artists and albums is the same on both machines though.

Very odd.

Generate a debug log (step 4b) capturing the startup of MediaMonkey and the expansion of the Media Servers node in the Media Tree and send it to support: viewtopic.php?f=7&t=69

Tinkered with this more over the weekend and it's still giving me grief. I cleared the db on the jukebox machine and reverted to the old INI so it isn't sharing a db anymore. That was all simple and worked fine. The problem is that the DLNA server won't show up under the Media Servers node, nor is it accessible to scan from Add/Rescan.

It's definitely running, and accessible from BubbleUPnP on my Android phone. It's just not coming up on the jukebox laptop at all. Same network, same homegroup. It's even able to find the files under Networks (albeit slowly).

I really dunno what's up. What should be a simple process is turning into a pain. I'm half tempted to just duplicate the entire library on an external HDD, but I don't want to have to keep two locations up to date.

You don't need to scan it in. You can access it in the Media Servers node. If you do want to scan it in select the DLNA server in the Media Tree and right click on it to access Add/Rescan Files. It will now be selected to be scanned in. Note that files scanned in from a DLNA server can't be edited (you can modify the local DLNA client DB tags, but not the DLNA server DB tags or the files themselves).

Yes, with both running at once.

I run a DLNA server on my desktop that I access via UPnP on my phone. To use DLNA from the jukebox machine, would I just scan in the DLNA server from the Add/Scan box? Where would it show up? It wasn't under the Network tab when I looked last night.

Are the SQL errors happening when both machines are running MediaMonkey simultaneously?

You may want to explore DLNA sharing as it avoids dual access of DB.

Subject pretty much says it all. I followed the knowledgebase article on sharing MM.db across two installs of MediaMonkey, and it's reading the library perfectly but I'm getting some glitches. Here's what I've got:

1. My main desktop, with approximately 26,000 mp3s stored in a single shared folder on a 1TB 7200rpm drive. MM.db is in the top level of this folder.
2. A jukebox machine, basically a mini laptop running nothing but MediaMonkey connected to a set of stereo speakers built into an old 1950s console stereo. This is a temporary solution until some hardware arrives, but I need it to work for next weekend.

Files were scanned into the library from \\machine_name\path\. Both machines are able to see the full library just fine, but both machines are throwing SQL errors, which look to be a result of trying to update the "times played" field in the database. Both machines will still continue playing music also, but the constant errors are very annoying.

I'm assuming this is a permissions issue of some sort, but the knowledgebase article didn't explain much about permissions other than "open MediaMonkey to make sure it works".

Would greatly appreciate some help solving this particular challenge.

Thanks!