Jump to content

Scan Media Library Failed


Recommended Posts

ComputerNerd
Posted

Hello MB3 Community, I need your help.  I am new to the MB3.  I built my first HTPC a few weeks ago and installed MB3 as it was highly recommended by a friend.  Have to say that so far, I love it.  Besides the minor known issue with the CPU getting maxed out because of all the streaming to my kids iPads, everything else has been going great.  That is until the recent MB3 server update.

 

After the server update, it appears that MB3 server is getting stuck doing a library scan.  I even tried completely uninstalling MB3 and reinstalling, no such luck.  When I am on the MB3 server dashboard, I keep seeing "Scan media library failed.  Object reference not set to an instance of an object".  When I review the logs, the only errors I see are the same one (see below).  I am running MB3 server Win7 Ultimate x64.  I appears that MB3 server is reaching out to my router (Asus RT-AC66R) and detecting that it supports UPNP?  I can restart the MB3 service and the library scan will continue to reach a little further before it dies again.  I assume I can keep restarting until the library scan is complete; however, that's not a fun solution.  Any suggestions you might have would be greatly appreciated.

 

Respectfully,

Ryan

 

Here is the error I keep seeing in the logs...

 

2014-03-04 11:01:07.3299 Info - App: Client connected from 127.0.0.1:49292
2014-03-04 11:01:07.8319 Debug - SessionWebSocketListener: Received Identity message: Dashboard|1ed105bc7765665627b084b425ea52b641c1f30d|3.0.5171.19958|Chrome 33.0.1750.146
2014-03-04 11:01:07.8319 Info - App: DashboardInfoWebSocketListener Begin transmitting over websocket to 127.0.0.1:49292
2014-03-04 11:01:40.6458 Debug - App: Searching for: UpnpSearcher
2014-03-04 11:01:40.7118 Debug - App: Searching for: PmpSearcher
2014-03-04 11:01:40.7268 Debug - App: NAT device found: 192.168.1.1
2014-03-04 11:01:40.7648 Info - App: Creating port map on port 8096
2014-03-04 11:01:41.2688 Info - App: Creating port map on port 8945
2014-03-04 11:01:41.7738 Error - App: Error reported by Mono.Nat:
 An existing connection was forcibly closed by the remote host
 System.Net.Sockets.SocketException
    at System.Net.Sockets.Socket.ReceiveFrom(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, EndPoint& remoteEP)
    at System.Net.Sockets.UdpClient.Receive(IPEndPoint& remoteEP)
    at Mono.Nat.NatUtility.Receive(ISearcher searcher, List`1 clients)
    at Mono.Nat.NatUtility.SearchAndListen()
 
2014-03-04 11:01:41.8868 Debug - App: UPnP Response: Router advertised a 'urn:schemas-upnp-org:service:WANIPConnection:1' service
2014-03-04 11:01:41.8918 Debug - App: Found device at: http://192.168.1.1:41710/rootDesc.xml
2014-03-04 11:01:41.8918 Debug - App: Parsed device as: 192.168.1.1:41710
2014-03-04 11:01:41.9118 Debug - App: UPnP Response: Router advertised a 'urn:schemas-upnp-org:service:WANPPPConnection:' service
2014-03-04 11:01:41.9648 Debug - App: Found device at: http://192.168.1.1:41710/rootDesc.xml
2014-03-04 11:01:42.0138 Debug - App: Parsed device as: 192.168.1.1:41710
2014-03-04 11:01:42.1329 Debug - App: UPnP Response: Router advertised a 'urn:schemas-upnp-org:service:WANIPConnection:1' service
2014-03-04 11:01:42.1949 Debug - App: Found device at: http://192.168.1.1:41710/rootDesc.xml
2014-03-04 11:01:42.2439 Debug - App: Parsed device as: 192.168.1.1:41710
2014-03-04 11:01:42.3029 Debug - App: UPnP Response: Router advertised a 'urn:schemas-upnp-org:service:WANPPPConnection:' service
2014-03-04 11:01:42.3489 Debug - App: Found device at: http://192.168.1.1:41710/rootDesc.xml
2014-03-04 11:01:42.3979 Debug - App: Parsed device as: 192.168.1.1:41710

Koleckai Silvestri
Posted

They will most likely need to see a complete log file. There is nothing above related to the Scan Library task.

 

You can probably clear the error above by turning off UPNP under Advanced -> HTTP Server.

Posted

that's coincidental. it has nothing to do with the library scan.

ComputerNerd
Posted

I just turned off the UPNP option and restarted the MB3 server, now bam, it's working like a champ!  It's now scanning and downloading the library metadata without stopping after a brief period.  So far it's up to 34%, the highest I have seen yet since I reinstalled in attempt to fix the problem.

 

I have a wireless USB3 / 802.11AC network card (Linksys WUSB6300) connect to an Asus RT-AC66R router I assume wasn't playing well with the UPNP turned on.  I will keep on monitoring it and let you know how this story ends...I hope it has a happy ending.

 

Maybe the problem is with the wireless losing connection, who knows?  /shrug

 

-Ryan

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...