Win 10 and new WD NAS problems

[Gary]

I've done a clean install of Win10 and can't get Mezzmo to serve files from my new WD NAS. I've tried creating a Windows credential based on the NAS IP address, but no joy giving Mezzmo the credential. Giving the Mezzmo app my admin credentials in the service properties, I get error 1053 starting the Mezzmo service. Need some guidance on how to get this working. Logs attached.888

[richard55uk]

I have Mezzmo running on Windows 10 and I have recently moved my media to my new WD My Cloud Mirror NAS and now the Mezzmo server keeps crashing.

[Paul]

Hi Gary,

We'll need your Mezzmo server logs. To do this, turn logging on in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and restart your Mezzmo server. Connect to Mezzmo server from your DLNA device and try to browse playlists/folders that contain files from your NAS. When they don't display or play, stop your Mezzmo server and exit Mezzmo (Windows) app. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

[Paul]

I have Mezzmo running on Windows 10 and I have recently moved my media to my new WD My Cloud Mirror NAS and now the Mezzmo server keeps crashing.

Please email us at support [at] conceiva [dot] com and we'll provide a patch that fixes these crashes.

[Gary]

Hi Paul, I would need to remove the credentials I provided the Mezzmo service since, with my Win admin credentials assigned, the service crashes on start. Do you want me to revert the mezzmo service to use the Local System Account?

An odd behavior I'm seeing, whether it's on the local system account or on a credential I established with the admin login/pw of the NAS server (the credentials I use to administer the NAS, connecting to it via a 192.168.x.x. IP): when I add the NAS folder with videos, for example, it zooms through the scan and shows something like 90% of the files "skipped". Yet, they show up in the Mezzmo file list in the mezzmo app in Windows. But when I then access the mezzmo DLNA instance on my TV, it shows no files at all. Just some additional data for consideration.

Please advise on how you want me to set up the service for the best view into the issue for your purposes. I'll follow your instructions once I know how you want the service configured. I could also, if you like, run through several scenarios, either in a series of experiments going to one log file, or as one-off efforts in which I clear the logs before each new variable, then capture discrete sets of logs for each variable. Just let me know your preference.

Gary

[Paul]

Hi Gary,

Mezzmo server should not be crashing. Email us at support [at] conceiva [dot] com and send us the crash ZIP files that are generated when it crashes (click the 'Go To Folder' button on the Mezzmo Crash message box when it appears to locate the crash ZIP files). Once we get the crash dump ZIP files, we'll provide a patch to fix the problem.

Regarding getting Mezzmo server to be able to access your WD NAS files, have you tried setting the Log On setting for Mezzmo server Windows service to the same user account that you use for logging into your Windows 10 computer?. See this FAQ tot do this - http://forum.conceiva.com/showthread.php/4597-FAQ-Accessing-files-from-external-computers-and-NAS-drives-on-your-home-network.

If that does not work, then turn on logging in Mezzmo. Stop your Mezzmo server. Set the Log On account for Mezzmo server Windows service to be your Local System account and then start your Mezzmo server. Try browsing and playing your files on your DLNA device. When you cannot play your files from your WD NAS, then stop your Mezzmo server. Now, set the Log On account to the Windows user account you use to log into your Windows 10 computer. Start Mezzmo server and try browsing and playing files on your DLNA device. When that fails, stop your Mezzmo server and exit Mezzmo (Windows) app. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

[Gary]

Hi Paul, when I assign the Mezzmo service, on the Log On tab of the service Properties, to use my Win login, which has admin priveleges, I get an error starting the Mezzmo media server. The .exe is not crashing, but the service won't start. Here's the error message:

889

Since this config of the service credential can't run, I'll have to revert to having the service use the Local System account (and I will enable Allow service to interact with desktop). The media server should run under this config.

Next, I'm going to try to add video files to the Library. I'll also add some mp3s to the Music library.

Once I see the files in the library in Mezzmo, I'll access the Mezzmo Video share on my TV and I'll also try accessing the Mezzmo Music library with my Bubble uPnP Android app.

Then I'll grab the logs and email them. Logging has been enabled since I first sent you logs a couple of days ago. But I'm not doing much of anything in Mezzmo since it's not accessible either on my TV or another uPnP client to stream media from my WD MyCloud DL4100 array.

[Gary]

OK, logs sent via email.

Quick clarification. It's not that I can see the files in the library from my devices, but can't open them. I can't see ANY contents of the folders in the Mezzmo libraries from either my TV or my uPnP client app. I added a folder of videos to the main library. In theory I now have 4 main folders: Video, Music, Pictures, (My Customer folder containing vids). But I don't see 4 main folders. I still only see the three folders. Interestingly, in the process of adding the folder, I could see Mezzmo scan the contents I was adding, in the status window. It tallied the number of files correctly and there were 0 skipped files.

I added a folder of mp3s, which contained a large number of sub-folders. This one I added within the main Music folder in the library. In the status window, as it tallied the files, ALL of them were numbered as "skipped". Yet, in both cases, I can see all the files in the library in the app. I just can't see them from a client.

Also, when I select a file in the library, in an attempt to push the file, using the Play To facility, I see the error message "501: Action Failed" near the bottom of the Play To. Window. If I click the Play icon in that window the message says: "702: no contents".

I think that's it... if you need me to test something and generate more logs, just let me know. Thanks!

[Paul]

Thanks for the logs and additional testing notes, Gary. We've checked the logs and the problem is that Mezzmo server (running as a Windows service on your computer under the Local System account) does not have access rights to read the files on your NAS. We've sent you an email with a few things to try on your NAS setup. Let us know how you go.

[Gary]

I've tried several approaches to adding files from the NAS to the Mezzmo library. I unmapped the Windows drives I'd created. Then I moved all the mp3s from a "mp3" share I had set up on the NAS and put them in the Public\Shared Music share that is a default share. I then added the mp3 files/folders to the Mezzmo Music library. It processed the files correctly (50k+ files took a long while to scan, with 0 skipped) but I still see no contents in the Music part of the library in my DLNA clients. One would think the Public/Shared element of the NAS would be open to any users on the internal network. But it seems that is not correct. Am I out of options at this point? Definitely a bummer, as Mezzmo has some excellent options for serving content that the built-in DLNA service on the NAS is lacking. :(

[Paul]

Hi Gary,

One thing to try is adding your folder of files into Mezzmo using the IP address of your NAS - e.g. \\192.168.0.14\mp3. Before doing this, I'd also suggest resetting your Mezzmo database so you start with a clean Mezzmo library. Go to the Options dialog (General page) and click 'Reset Database' to do this. Let us know if this works.

[Paul]

Hi Gary,

A follow-up: If my previous idea does not work, then we want to see a set of logs when you get the 1053 error when starting your Mezzmo server. Turn on logging in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and stop your Mezzmo server (if running) and exit Mezzmo (Windows) app. Run Mezzmo (Windows) app again. Now change the Mezzmo server's Windows Service Log On settings to use your Windows user account (i.e. not Local System), and try starting your Mezzmo server. When you get the 1053 error, exit Mezzmo (Windows) app and zip up all the logs and email them to us at support [at] conceiva [dot] com for analysis.

[Gary]

Well, you gotta love a good ol' intermittent problem. I gave the Mezzmo service my Win credentials, for about the 5th time, and this time it did not throw the 1053 error. And now, of course, it scanned all my videos correctly (no skipped files) and they show up as playable on my TV. And can be played. Wtf?

I'm not going to begin to try to parse through the possibilities. Rather, I will chalk it up to Microsoft BS and be thankful I have Mezzmo back in service. Unbelievable...

Really appreciate your suggestions and help along the way Paul. And relieved I don't have to rely on the WD DLNA service, or Plex, which is an app you can install from the WD NAS control panel (built-in), but which is inferior to Mezzmo. ;-)

[Paul]

Hi Gary,

That's a great (but a little strange) result. Perhaps Windows 10 updated itself with updated drivers/components/etc. Anyway, glad you are up and running now :).