Mezzmo hanging accessing network drive

[cresc]

I've searched a lot on the forum for this without finding in real fix,

I have installed Mezzmo on a fresh install of Windows 8, I have an open network drive mapped to the machine. (I have read the NAS FAQ, but because no permissions are needed to access the drive I am kind of confused about that?)

Basically whenever in the program I try to access this drive (whether via the setup wizard, or by dragging it into my library) it hangs the system for up to 5 minutes. Even trying to expand the drive to explore the folders in the setup wizard causes Mezzmo to hang for a minute.

When I check the logs the only thing that gets added is this... suggestions to fix welcome!

Many thanks


644 - Jan 01 23:35:50.108 [ThreadID:117c] - (1357083350.108) - [00] - <00> - CS > ControlService: QueryServiceConfig = 2

645 - Jan 01 23:36:50.132 [ThreadID:117c] - (1357083410.132) - [00] - <00> - CS > ControlService: QueryServiceConfig = 2

646 - Jan 01 23:37:50.183 [ThreadID:117c] - (1357083470.183) - [00] - <00> - CS > ControlService: QueryServiceConfig = 2

647 - Jan 01 23:38:50.221 [ThreadID:117c] - (1357083530.221) - [00] - <00> - CS > ControlService: QueryServiceConfig = 2

648 - Jan 01 23:39:50.259 [ThreadID:117c] - (1357083590.259) - [00] - <00> - CS > ControlService: QueryServiceConfig = 2

649 - Jan 01 23:40:50.302 [ThreadID:117c] - (1357083650.302) - [00] - <00> - CS > ControlService: QueryServiceConfig = 2

650 - Jan 01 23:41:50.353 [ThreadID:117c] - (1357083710.353) - [00] - <00> - CS > ControlService: QueryServiceConfig = 2

[Paul]

We really need a full set of logs to see what is happening. Please create a new set of logs when you are trying to access this drive in Mezzmo. Once it fails, stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

[cresc]

Thanks, I have emailed them across.

[Paul]

Got your logs. We'll analyze them shortly and get back to you via email.

[Peter]

This problem appears to be caused by the Network Pane in Mezzmo locking Mezzmo while it waits for a response from the NAS, we have made some improvements that should resolve this problem in Mezzmo 3.0.

[cresc]

This problem appears to be caused by the Network Pane in Mezzmo locking Mezzmo while it waits for a response from the NAS, we have made some improvements that should resolve this problem in Mezzmo 3.0.


Hi guys,

I have installed Mezzmo beta, unfortunately I'm having the same issue. I managed to add my network folders which seemed to be a bit faster. I let mezzmo take its time indexing them all and adding them to the library.

When I click All Video Files Mezzmo works as expected and I can stream to my Bravia fine via this method.

However as soon as I go to Folders and click on one of my network folders the system hangs for a minute or so and then eventually shows me all of the contents. If I try to stream from the 'Folders' on my Bravia it says 'No items found' presumably because the server takes too long to respond.

This hasn't been an issue until I installed Windows 8 and also upgraded Mezzmo so I'm not sure what the fix is. I've attached logs of me trying to access the network Folder in my library!

Many thanks,

Rob

[Paul]

Thanks for the Beta feedback. Rather than posting Beta feedback on the forum, please email it directly to our support [at] conceiva [dot] com email address. In your logs, you are missing several Mezzmo server logs files - probably because Mezzmo server was not restarted after turning on logging. Please turn on logging again and make sure you restart your Mezzmo server. Then, repeat the steps to to reproduce the problem you mention. After it fails, stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

[cresc]

Hi Paul... although technically this is Beta feedback, the exact same problem existed in the previous version so I felt this wasn't really a beta issue but if you like I will post via email from now on

[Paul]

Many thanks. Please email us a new set of logs as I mention in my previous post and we'll look into the problem you are having.